Dear Rian, Matthijs Mohlmann <[EMAIL PROTECTED]> wrote:
> Package: tetex-bin > Version: 2.0.2-27 > Severity: normal > > Hi, > > tetex-bin could not be installed on several architectures including: > mipsel, s390, alpha and powerpc. See for example this buildd log: > http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.17-8&arch=powerpc&stamp=1112391358&file=log&as=raw In fact the chroot on some buildd hosts, including voltaire as in the log url above, seems to be screwed up - it cannot even uninstall the tetex packages cleanly: Removing tetex-base ... dpkg - warning: while removing tetex-base, directory `/var/cache/fonts' not empty so not removed. dpkg - warning: while removing tetex-base, directory `/var/lib/texmf/dvips' not empty so not removed. dpkg - warning: while removing tetex-base, directory `/etc/texdoctk' not empty so not removed. dpkg - warning: while removing tetex-base, directory `/etc/texmf/cslatex' not empty so not removed. dpkg - warning: while removing tetex-base, directory `/etc/texmf/cyrplain' not empty so not removed. dpkg - warning: while removing tetex-base, directory `/etc/texmf/context' not empty so not removed. [...] Purging configuration files for tetex-extra ... Removing texinfo ... dpkg - warning: while removing texinfo, directory `/usr/share/texmf' not empty so not removed. There are leftover files in /etc/texmf, and perhaps even in /usr/share/texmf (some packages don't depend on tetex that install there). The same build log has also similar messages for defoma and libldap2 - no idea whether these are normal. I would be grateful if you could do the following: - Send us the output of "ls -Rl /etc/texmf/" in the buildd chroot after tetex-base has been purged - Similar, "ls -R /usr/share/texmf" - If there are other files in /etc/texmf/ than *.dpkg-old, *.dpkg-new, *.postinst-bak and similar, I'd appreciate if you could send us a tar.gz of the tree, or individual files if there aren't many. - I suspect that in order to clear up the mess, it will be necessary to purge all packages that install files in /etc/texmf and rm -r the complete directory (perhaps the same needs to be done for /usr/share/texmf). I offer my help to find out which files are from ancient versions, and which are actually from installed packages. Keeping a backup for "forensics" would be great - we should really find out how this could happen. The same problem seems to exist on "debian01" (http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.17-8&arch=s390&stamp=1112396965&file=log&as=raw), and on goedel (http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.17-8&arch=alpha&stamp=1112391942&file=log&as=raw). Interestingly, the mipsel build at http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.17-8&arch=mipsel&stamp=1112482076&file=log&as=raw on solitude fails with the same error message, but seems to be able to purge the tetex packages cleanly. Therefore I am not sure that this will actually fix this bug. Regards, Frank -- Frank K�ster Inst. f. Biochemie der Univ. Z�rich Debian Developer
