Re: arm64 bug in docbook toolchain, maybe
Here are 7 packages that failed to build for arm64 on
buildd.debian.org because of DocBook stuff being messed up:
http://buildd.debian.org/status/package.php?p=aboot,dossizola,le-dico-de-rene-cougnenc,leaktracer,nickle,rblcheck,synergy&suite=sid&a=arm64
(Yes, "nickle" failed too, but was manually installed.)
I think they all worked on buildd.debian-ports.org in the end:
http://buildd.debian-ports.org/status/package.php?p=aboot,dossizola,le-dico-de-rene-cougnenc,leaktracer,nickle,rblcheck,synergy&suite=sid&a=arm64
This is not an easily reproducible bug. It appears that some kind of
global directory/index in /etc/ gets into, or got into, a bad state.
It can perhaps be cured by reinstalling certain DocBook-related
packages. Apparently the problem used to be present on debian-ports,
but then it went away of its own accord.
Does anyone want to try and reproduce the problem by recreating a root
file system in the same way that the buildd root file systems were
created, or does a buildd admin want to try refreshing the chroots
used by buildd.debian.org to make the problem go away?
The bug that made the directory/index get into a broken state may or
may not still exist ...
Reply to: