source-only builds and .buildinfo

[Sean Whitton]

On Wed, May 24, 2017 at 09:47:09PM +0100, Ian Jackson wrote:
> dgit manipulates _source trees_ in git.  The .dsc is not represented
> directly in git (and in general cannot be regenerated from git because
> there may be missing origs etc., and also there may be deviations in
> behaviour of tools like dpkg-source).  dgit may need to construct a
> source package, in which case the intent is that in similar
> circumstances dgit will produce .dscs which are semantically
> equivalent.  I don't think it's necessary to generate an identical
> .dsc, because actual builds take (or can take) a source directory tree
> as input, not a .dsc; and an "appropriate" .dsc by this definition
> implies the same source tree (which is a property dgit does check - at
> least, as far as the local dpkg-source is concerned).

Not directly relevant, but there are some comments regarding 100%
reproducible builds of source packages in #756978.

-- 
Sean Whitton
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20170525/02f06089/attachment.sig>