Mattia Rizzolo writes ("Bug#844125: dgit: Built-in support for pbuilder [and 1
more messages]"):
> On Mon, Jan 29, 2018 at 01:09:25PM +0000, Ian Jackson wrote:
> > I'm not sure why anyone would use SOURCE_ONLY_CHANGES=yes so I don't
> > know why and how dgit should allow them to achieve the same result.
>
> Think of the original goal of buildinfo files: a DD uploads a *source*
> package AND a buildinfo, then the source is rebuild and the buildinfo
> compared.
> So, with that you can upload all the sources, plus a _amd64.buildinfo
> describing the build.
Ah. But AIUI source-only upload *must not* be accompanied by an
_amd64.buildinfo (with the same name, anyway) because that *clashes*
with the buildd's .buildinfo.
> > It might be necessary for dgit to override some of the user's pbuilder
> > config. (And, as I said in my other mail, it might also be desirable
> > for dgit to interrogate the pbuilder config so that it can honour it.)
>
> There is a command for this, but it may be a tad noisy:
> mattia@warren ~/devel/debian/limnoria % /usr/sbin/pbuilder dumpconfig >
> /tmp/dumpconfig
> mattia@warren ~/devel/debian/limnoria %
>
> File attached, so you can see all the crap and ends up in it, there is a
> whole `env` output, so…
Right. I was aware of this. Of course `env' output is not reliably
parseable if the values might contain newlines but I think we can hope
that it doesn't and read it accordingly in dgit. (Ideally I think
pbuilder dumpconfig would fail if the output is misleading.)
Ian.
