On Tue, Jan 10, 2006 at 11:08:14AM +0100, Frank Küster wrote: > Steve Langasek <vorlon@debian.org> wrote: > > On Mon, Jan 09, 2006 at 02:37:53PM +0100, Frank Küster wrote: > >> The same happened to the planner package, and has been reported as > >> #344538. It seems that hppa buildd is broken, don't know yet whether > >> the buildd admin (Lamont) or anybody of the debian-admin (responsible > >> for the hardware) is at it. > > Hasn't the problem on the hppa buildd been fixed for a while? The pdns > > package (both versions 2.9.19-2 and 2.9.19-3) has built fine on that arch > > now. > It *seems* it has been fixed; but I don't know whether it has just > disappeared, or has been fixed by human intervention, and if yes by > which. Since the first may be true, it might as well reappear again. <sigh> No, buildds don't magically go from believing a dependency is satisfied, to believing it's not satisfied, and back again. If the problem has disappeared, it's due to human intervention. > > or a bug in some > > maintainer script or other; > How a bug in a maintainer script could have the result that installing > an arch-all package fails because an other arch-all package is not > there, and how this can happen on only one particular machine of one > particular architecture, this I fail to see. Then you haven't been looking at buildds for very long. 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. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature