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

[Johannes Schauer]

Hi,

Quoting Sean Whitton (2016-08-06 00:50:56)
> On Sat, Aug 06, 2016 at 12:07:44AM +0200, Johannes Schauer wrote:
> > this is because autopkgtest is run *outside* the chroot and unless sbuild was
> > instructed to recreated the source package, the system outside will never see
> > the .dsc.
> > 
> > I suggest to fix this by automatically skipping the autopkgtest in cases where
> > sbuild downloads the source package itself to resolve this bug.
> 
> I suppose that would count as fixing the bug, but it would be nice to be
> able to run a package's autopkgtest just by typing `sbuild package`.

the thing is, that autopkgtest is run *outside* the chroot. If it were run
inside, the problem would not exist. There are already ways to do this right
now. For example you could instruct sbuild to rebuild the source package using
the --source flag. Or you could use "apt-get source" yourself and then run
sbuild on it.

> 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?

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/6f0a2b47/attachment.sig>