[buildd-tools-devel] Bug#833549: Bug#833549: sbuild: autopkgtest fails when sbuild obtains the .dsc with apt-get source

[Johannes Schauer]

Hi Sean,

Quoting Sean Whitton (2016-08-06 03:16:04)
> On Sat, Aug 06, 2016 at 01:02:59AM +0200, Johannes Schauer wrote:
> > > Doesn't sbuild have a mechanism to get files out of the chroot?  How else
> > > does it extract the .deb files that are built?
> > 
> > It does. But it would be unexpected behaviour if sbuild would also produce the
> > source package if you just tell it `sbuild package`. The expected behaviour in
> > this case would be for sbuild to just create the binary packages. Unless you
> > add the --source flag of course, which would be a workaround as described
> > above.
> > 
> > Do you see a solution to this problem?
> 
> What I had in mind was that sbuild would extract the .dsc just to run
> autopkgtest.  It could put it in /tmp, pass that on the autopkgtest
> command line, and then delete it afterwards.  Would that be hard to
> implement?

no, this is trivial to implement and a good idea!

I think you are right that the user can expect autopkgtest operation to not be
different depending on how the dsc was acquired.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20160806/a5b6c2d9/attachment-0001.sig>