[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

libtinymail_0.0.9-4 : needs cleaned powerpc buildd chroot



Getting libtinymail (with a RC bugfix) migrated to testing is prooving
tricky. 0.0.9-3 failed[1] since automake was installed in the dirty
buildd chroot, but libtool wasn't. After the request to cleanup ppc
buildd chroots went ignored (exactly one month ago), we uploaded
0.0.9-4 with build-conflicts on automaken. Turns out sbuild
build-conflicts isn't smart enough to handle reverse dependencies[2],
so the second upload failed too.

A recent buildlog shows that the powerpc chroots are still really
dirty (surely libgtk2.0-dev shouldn't be installed..). So how should
we proceed from here?

-snip-
** Using build dependencies supplied by package:
Build-Depends: debhelper (>= 4.0.0), ecj [!alpha !arm !hppa !hurd-i386],
gcj [!alpha !arm !hppa !hurd-i386], zip, libgtk2.0-dev, libgconf2-dev,
libart-2.0-dev, libx11-dev, libice-dev, libxt-dev, libxtst-dev,
libasound2-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64],
libcairo2-dev, dpatch, libqt4-dev (>= 4.1.0), dssi-dev [!hurd-i386
!kfreebsd-i386 !kfreebsd-amd64], iceape-dev (>= 1.1.9-5), libmagic-dev
Build-Depends-Indep: gjdoc (>= 0.7.9)
Checking for already installed source dependencies...
debhelper: already installed (7.0.13 >= 4.0.0 is satisfied)
ecj: missing
gcj: missing
zip: missing
libgtk2.0-dev: already installed (2.12.11-3)
libgconf2-dev: missing
libart-2.0-dev: missing
libx11-dev: already installed (2:1.1.5-2)
libice-dev: already installed (2:1.0.4-1)
libxt-dev: already installed (1:1.0.5-3)
libxtst-dev: missing
libasound2-dev: missing
libcairo2-dev: already installed (1.6.4-6.1)
dpatch: already installed (2.0.29)
libqt4-dev: missing
dssi-dev: missing
iceape-dev: missing
libmagic-dev: missing
Checking for source dependency conflicts...
-snip-

[1] http://buildd.debian.org/fetch.cgi?pkg=libtinymail;ver=0.0.9-3;arch=powerpc;stamp=1222437346
[2] http://buildd.debian.org/fetch.cgi?pkg=libtinymail;ver=0.0.9-4;arch=powerpc;stamp=1224281501
-- 
"rm -rf" only sounds scary if you don't have backups

Attachment: signature.asc
Description: Digital signature


Reply to: