On Sun, 2009-06-07 at 12:46 +0200, Kurt Roeckx wrote:
> Both have this in the end of the log:
...
> Do you believe that has been fixed?
I have no reason to.
Why wouldn't the builds be marked as Failed or Maybe-Failed instead of
Building though?
I only see this at the end of the last log links:
Checking for source dependency conflicts...
/usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install autotools-dev libx11-dev libxt-dev libidl-dev libgtk2.0-dev libstartup-notification0-dev libgnomevfs2-dev libgnome2-dev libgnomeui-dev libcairo2-dev libpng12-dev libjpeg62-dev zlib1g-dev libbz2-dev libreadline5-dev libkrb5-dev python-dev python-support libnspr4-dev libnss3-dev libhunspell-dev libdbus-glib-1-dev libsqlite3-dev liblcms1-dev zip xvfb xfonts-base xauth
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libgnome2-dev: Depends: libgnome2-0 (= 2.24.1-2) but it is not going to be installed
libgnomeui-dev: Depends: libgnomeui-0 (= 2.24.1-1) but it is not going to be installed
Depends: libbonoboui2-dev (>= 2.13.1) but it is not going to be installed
E: Broken packages
apt-get failed.
One of the builds actually succeeded on powerpc though, and then it was
given-back (or something) and failed:
https://buildd.debian.org/build.php?pkg=xulrunner&arch=powerpc&ver=1.9.0.10-1
--
bye,
pabs
http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part