Hi Andreas, On Thu, 20 Mar 2014 08:35:33 +0100, Andreas Tille <andreas@an3as.eu> wrote: > On Wed, Mar 19, 2014 at 11:54:03PM +0100, Stephen Kitt wrote: > > > Moreover I observed another issue with autopkgtest which is quite > > > astonishing to me: In bug #741274 it was reported that the autopkgtest > > > would fail and the according log is here: > > > > > > http://ci.debian.net/data/unstable-amd64/packages/p/python-pysam/2014-03-12.log > > > > > > The problem is that `make` was not available in the chroot (obviosly) > > > which does not sound very reasonable to me. While I added it to the > > > Depends in debian/tests/control I think it is not sensible to assume > > > that make exists in a build chroot (it is not in the Build-Depends) but > > > trying to build the package somehow and than notice that it is missing. > > > I admit that I'm really confused how autopkgtests are working. > > > > This is actually documented, sort of: the documentation for @builddeps@ > > mentions make as one of the packages which gets pulled in. (Why not > > build-essential? Yet somehow gcc is available...) > > In other words what we can see in the log above conflicts with the > documentation if make is not found and should be reported as bug in > autopkgtest ? As far as I can see from the logs, there was no declared dependency on make or @builddeps@, so make's absence is correct as per the documentation. Regards, Stephen
Attachment:
signature.asc
Description: PGP signature