Hi, On Mon, 09 Feb 2015 01:40:21 +0100, jre <jre.winesim@gmail.com> wrote: > On Sun, 8 Feb 2015 21:27:57 +0100 Stephen Kitt <skitt@debian.org> wrote: > > On Sun, 08 Feb 2015 16:05:47 +0100, jre <jre.winesim@gmail.com> wrote: > > > libwine-development 1.7.35-2 from experimental does not depend on > > > libxml2. All other versions seem to be ok though. > > > > > > When I rebuild it locally with gbp the dependency is there again. > > > Looking at debian/control.in and the last changes I wouldn't expect > > > otherwise, everything looks ok. > > > > > > So no idea if it is something with the build daemons or Stephen's > > > specific upload. > > > > Thanks for pointing this out. debian/control doesn't declare a > > build-dependency on libxml2-dev, so it isn't installed on the buildds; > > and my upload forced a rebuild on the buildds for all arches (I don't > > upload binaries any more). > > No, libxml2-dev already was in debian/control.in. That's what I meant > with "everything looks ok". Doh, so it does, I didn't look properly... > > I'm preparing a fix, the upload should be ready in a little while... > > You now just duplicated that entry as I've seen in git. Thanks, I've fixed that in git. > I'm a bit clueless about this bug: > > First I thought you had a somehow corrupted debian/control (since this > is not checked in in git). But I just did a "apt-get source > wine-development": In 1.7.35-2 (yes, your new -3 is not yet available) > both files debian/control and debian/control.in ship with a > build-depends of the source package on libxml2-dev. > > Then I did a "dpkg-buildpackage -us -uc" in the just retrieved source: > $ dpkg -e ../libwine-development_1.7.35-2_amd64.deb > $ grep xml2 DEBIAN/control > Depends: [...] libxml2 (>= 2.9.0), [...] > > Then I uninstalled libxml2-dev and some other dependencies: > $ dpkg-buildpackage -us -uc > dpkg-buildpackage: source package wine-development > dpkg-buildpackage: source version 1.7.35-2 > dpkg-buildpackage: source distribution experimental > dpkg-buildpackage: source changed by Stephen Kitt <skitt@debian.org> > dpkg-buildpackage: host architecture amd64 > dpkg-source --before-build wine-development-1.7.35 > dpkg-checkbuilddeps: Unmet build dependencies: libxml2-dev libxslt1-dev > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > > > So if I rebuild from your shipped source everything works as it should > (builddep is in d/control, aborts if builddep is missing, and the built > packages have the dependency). I run Jessie, amd64, with some sid stuff. > > As I understand the Debian working I used *exactly* the same source as > the build daemons. > Since you do source-only uploads, as I just learned, we can also rule > out anything strange on your side. > > I'm not doing a "Control: found: -1 1.7.35-3" yet, because it's not > available yet. But if it is fixed in there then it can only be by > coincidence. > > Any idea? This is probably related to #776741 (filed by Michael ironically!). Comparing the build logs for 1.7.35-2 and 1.7.35-3 (https://buildd.debian.org/status/logs.php?pkg=wine-development&arch=amd64) reveals that libxml2-dev was installed for -2 but not detected by configure, and installed for -3 and detected by configure. When -2 was built, the libxml2 version was 2.9.2+dfsg1-2, and when -3 was built it was 2.9.2+dfsg1-3. The only change between those two versions is the fix for #776741, and its effects are visible in the build logs since -2 didn't install libicu-dev but -3 did. I suppose the right fix would be to explicitly enable --with-xml, since that will fail the build if libxml2 isn't detected... Regards, Stephen
Attachment:
pgp_X8msRjtZp.pgp
Description: OpenPGP digital signature