Steve Langasek <[EMAIL PROTECTED]> wrote: > On Tue, Jan 10, 2006 at 12:24:47PM +0100, Frank Küster wrote: >> Steve Langasek <[EMAIL PROTECTED]> wrote: > >> > Historically such >> > problems were unpleasantly frequent on buildds due to a combination of >> > buggy >> > postrm scripts, and a bug in dpkg's rollback support when calling dpkg >> > --purge for a package in the "installed" state. I believe the dpkg bug is >> > fixed now, but a) I could be wrong, and b) there may be other bugs in the >> > world. > >> Ah - can you point me to something to read about this? > > The dpkg changelog, maybe.
Thanks, it's #296026. >> How can it be architecture-specific, or host-specific? > > It almost certainly wouldn't be. But it's quite possible for a different > combination of package versions (with different maintainer script bugs) to > be used on different autobuilders at a given moment. Hm. But that doesn't explain why only a couple of formats failed to build in tetex-bin's postinst in http://buildd.debian.org/fetch.php?&pkg=mysql-dfsg-5.0&ver=5.0.16-1&arch=hppa&stamp=1132626014&file=log&as=raw and an other build try at the same time. If some formats build fine, this means most parts of tetex-base must be installed properly; if others fail, this means either a misconfiguration (rather unlikely on a buildd) or missing files. Of course it was also on sarti. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
