Package: vegastrike
Version: 0.4.3-4
Severity: important
From my pbuilder build log:
...
-> Considering automaken
-> Trying automaken
-> Cannot install automaken; apt errors follow:
Reading package lists...
Building dependency tree...
Package automaken is a virtual package provided by:
automake1.9 1.9.6-4+pb1
automake1.8 1.8.5-3+pb1
automake1.7 1.7.9-7+pb1
automake1.4 1:1.4-p6-9+pb1
You should explicitly select one to install.
E: Package automaken has no installation candidate
-> Considering automake1.4 to satisfy the dependency
...
-> Installing libtool automake1.4 autoconf autotools-dev python-dev
libgtk1.2-dev libopenal-dev libalut-dev xlibmesa-gl-dev libexpat1-dev
libsdl1.2-dev libsdl-mixer1.2-dev libpng12-dev libjpeg62-dev libglut3-dev
libxmu-dev debhelper
...
-> Considering automake1.4
Reading package lists...
Building dependency tree...
The following packages will be REMOVED:
automake1.4
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
...
dpkg-checkbuilddeps: Unmet build dependencies: automaken
dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting.
dpkg-buildpackage: (Use -d flag to override.)
pbuilder: Failed autobuilding of package
So pbuilder isn't smart enough to be able to look ahead to the Build-Conflicts
and reject using automake1.4 to satisfy automaken -- neither are the
buildd's, but there they lucked out and chose automake1.9 at random instead.
You need to make that entry something like "automake1.9 | automaken" to help
out automatic build systems.
--
Daniel Schepler
