Mmmmmm it *could* be due to the new libxml2 upload. An upload of libxslt (and therefore xsltproc) is programmed soon and might solve the problem if it is that.
I'd be interested in getting a backtrace, though, if you could provide one. BTW, I don't understand how buildds get packages from incoming when they build a package. (libxml2 2.6.11-2 packages are still in incoming at the moment and got used on sparc, ia64, s390 and arm) Mike On Sat, Feb 05, 2005 at 01:47:52PM +0100, Guus Sliepen <[EMAIL PROTECTED]> wrote: > Package: xsltproc > Version: 1.1.12-3 > Severity: serious > Justification: makes another package FTBFS > > The autobuilders of some architectures fail to build gmime2.1. For > example on sparc: > > cd ./html && gtkdoc-mkhtml gmime ../gmime-docs.sgml > Computing chunks... > /usr/bin/gtkdoc-mkhtml: line 45: 16526 Bus error /usr/bin/xsltproc --nonet > --xinclude --stringparam gtkdoc.bookname $module --stringparam gtkdoc.version > "1.3" $gtkdocdir/gtk-doc.xsl $document > > For more details, see http://buildd.debian.org/build.php?&pkg=gmime2.1. > If the problem happens to be caused by another package, please reassign > this bug. > > > -- System Information: > Debian Release: 3.1 > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: i386 (i686) > Kernel: Linux 2.6.9-skas3-v7 > Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) > > Versions of packages xsltproc depends on: > ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries > an > ii libgcrypt11 1.2.0-11 LGPL Crypto library - runtime > libr > ii libgpg-error0 1.0-1 library for common error values > an > ii libxml2 2.6.16-1 GNOME XML library > ii libxslt1.1 1.1.12-3 XSLT processing library - > runtime > ii zlib1g 1:1.2.2-4 compression library - runtime > > -- no debconf information > > > _______________________________________________ > debian-xml-sgml-pkgs mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/debian-xml-sgml-pkgs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]