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

Buildds fail on quite a few architectures



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just prepared a new version for one of my packages, worker. I managed to 
build it for i386 yesterday without any problems in an up-to-date sid chroot 
(with pbuilder).

My sponsor was able to build the package as well, so he did the upload for me. 
Today, after having a look into the progress of the buildds, I noticed that 
all buildds except arm and sparc failed to build the package.

Unfortunately, my sponsor went on holiday today, so I'm seeking for help here.

Every failed buildd stopped with this message:

Building Dependency Tree...
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:

Sorry, but the following packages have unmet dependencies:
  xlibs-dev: Depends: libice-dev but it is not installable
             Depends: libsm-dev but it is not installable
             Depends: libx11-dev but it is not installable
             Depends: libxext-dev but it is not installable
             Depends: libxi-dev but it is not installable
             Depends: libxmu-dev but it is not installable
             Depends: libxmuu-dev but it is not installable
             Depends: libxp-dev but it is not installable
             Depends: libxpm-dev but it is not installable
             Depends: libxrandr-dev but it is not installable
             Depends: libxt-dev but it is not installable
             Depends: libxtrap-dev but it is not installable
             Depends: libxtst-dev but it is not installable
             Depends: libxv-dev but it is not installable
             Depends: xlibs-static-dev but it is not installable
E: Sorry, broken packages
apt-get failed.

xlibs-dev is included in the source package xfree86, which has had an upload 
yesterday -- it seems like there occured some problems with the upload, 
probably because it's an upgrade to version 4.3.0.

Judging from the buildd's error message, I would think that the build failure 
is not my fault. Is that right?

My question is: do I have to do anything about the failure of the buildds, or, 
more specifically: *can* I do anything about it? Will my package be rebuilt 
when xfree86 builds cleanly?

Any help and/or hints are very appreciated.

Cheers,

- -- 

Tobias

    "We either learn from history or, uh, well, something bad will happen."
      -- Bob Church
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAFr5jCqqEJ0Fs8twRAvXMAJ40cHqe4AwvCFMtr0p2Axgc0w/ZMACgqh07
K4exScOasYYgn4EEO1GnwqA=
=k5dh
-----END PGP SIGNATURE-----



Reply to: