Bug#347246: xorg-x11_6.9.0.dfsg.1-2(mipsel/unstable): FTBFS on mips and mipsel
On Mon, Jan 09, 2006 at 09:33:35AM -0800, Ryan Murray wrote:
> Package: xorg-x11
> Version: 6.9.0.dfsg.1-2
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of xorg-x11_6.9.0.dfsg.1-2 on mayer by sbuild/mipsel 79
> > Build started at 20060106-0905
>
> [...]
>
> > ** Using build dependencies supplied by package:
> > Build-Depends: bison, bsdmainutils, flex, fontconfig, groff, tetex-bin, libexpat1-dev | libexpat-dev, libfreetype6-dev, libglide2-dev (>> 2001.01.26) [i386], libglide3-dev (>= 2002.04.10-7) [alpha amd64 i386 ia64], libncurses5-dev | libncurses-dev, libselinux1-dev [!kfreebsd-i386 !hurd-i386], libpam0g-dev | libpam-dev, libpng12-dev | libpng-dev, libxcursor-dev, libxft-dev (>> 2.1.2), libxrender-dev (>> 1:0.9.0+CVS20050905), render-dev (>> 1:0.9+CVS20050905), zlib1g-dev | libz-dev, debhelper (>= 4.1.16), dpkg-dev (>= 1.10.14), linux-kernel-headers (>= 2.6.13+0rc3-1.1) [!hurd-i386 !netbsd-i386 !kfreebsd-i386], lynx, po-debconf, quilt, gcc-4.0 (>= 4.0.1-3)
>
> [...]
>
> > +usr/X11R6/man/man3/XcupGetReservedColormapEntries.3x
> > +usr/X11R6/man/man3/XcupQueryVersion.3x
> > +usr/X11R6/man/man3/XcupStoreColors.3x
> > @@ -2437,0 +2458,5 @@
> > +usr/X11R6/man/man3/XevieEnd.3x
> > +usr/X11R6/man/man3/XevieQueryVersion.3x
> > +usr/X11R6/man/man3/XevieSelectInput.3x
> > +usr/X11R6/man/man3/XevieSendEvent.3x
> > +usr/X11R6/man/man3/XevieStart.3x
> > @@ -2538,0 +2564 @@
> > +usr/X11R6/man/man3/XtAddWorkProc.3x
> > @@ -3382,0 +3409 @@
> > +usr/X11R6/man/man4/sisusb.4x
> > MANIFEST check failed; please see debian/README
> > make: *** [stampdir/check-manifest] Error 1
>
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=mipsel&pkg=xorg-x11&ver=6.9.0.dfsg.1-2
>
> manifest checks still fail for mips and mipsel. This causes xbase-clients to be
> uninstallable, so is holding up the KDE 3.5 transition, as kdelibs depends
> on xbase-clients...
Right, this is already fixed in svn. I'm polishing off the last bits for -3
and planning to upload it tomorrow. Basically #347228 is a last-minute
surprise that's causing the holdup.
- David Nusinow
Reply to: