Bug#344538: hppa dependency problems on build of pdns
Steve Langasek wrote: > On Mon, Jan 09, 2006 at 02:37:53PM +0100, Frank Küster wrote: > >>Matthijs Mohlmann <[EMAIL PROTECTED]> wrote: > > >>>I don't know where to send this else, so forgive me if this is the wrong >>>mailinglist. > > >>>See: >>>http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.19-2&arch=hppa&stamp=1135294848&file=log&as=raw > > >>>[..] >> >>[...] >> >>>As you can see, tetex-base depends on tex-common (>= 0.12). But the hppa >>>build daemon doesn't install tex-common. > > >>>So can somebody tell me what's going on here ? > > >>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. > I haven't fixed anything on this issue, so I'm still wondering why it's now working in a sudden. > If the buildd wasn't installing a package that was part of the dependencies, > then it surely thought for some reason it was already installed. If this > wasn't actually the case, it points to a buildd problem or a bug in some > maintainer script or other; either way, it seems to be corrected now. > The maintainer scripts are not changed as of 2.9.18-3, then it's actually a buildd problem. If the package was already installed then it shouldn't fail with a "command not found". Regards, Matthijs Mohlmann
Bug#344538: hppa dependency problems on build of pdns
LaMont Jones <[EMAIL PROTECTED]> wrote: > On Tue, Jan 10, 2006 at 11:08:14AM +0100, Frank Küster wrote: >> Steve Langasek <[EMAIL PROTECTED]> wrote: >> > 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. > > Simple. Buggy postrm (or was it prerm) fails, and the package is left > with all its files removed, but still marked as installed in dpkg. And > it never gets installed again. There have been a few packages like > this, and tetex-$mumble seems to ring a bell as one of the b0rken ones. That might well be, and maybe even the new postrm or prerm scripts that I wrote from scratch suffer from that. But why does it only occur on the hppa buildd, then? And how could it be detected and fixed - of course I do remove and purge in a pbuilder chroot all the packages I upload. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#344538: hppa dependency problems on build of pdns
On Tue, Jan 10, 2006 at 11:08:14AM +0100, Frank Küster wrote: > Steve Langasek <[EMAIL PROTECTED]> wrote: > > 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. Simple. Buggy postrm (or was it prerm) fails, and the package is left with all its files removed, but still marked as installed in dpkg. And it never gets installed again. There have been a few packages like this, and tetex-$mumble seems to ring a bell as one of the b0rken ones. lamont
Bug#344538: hppa dependency problems on build of pdns
Steve Langasek <[EMAIL PROTECTED]> 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. > If the buildd wasn't installing a package that was part of the dependencies, > then it surely thought for some reason it was already installed. If this > wasn't actually the case, it points to a buildd problem Which is what I've been trying to say for weeks. > 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. > either way, it seems to be corrected now. No, it seems to work now. I have not indication that it has been *corrected*, a word which to me implies that it has been dealt with by a human being. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#344538: hppa dependency problems on build of pdns
On Mon, Jan 09, 2006 at 02:37:53PM +0100, Frank Küster wrote: > Matthijs Mohlmann <[EMAIL PROTECTED]> wrote: > > I don't know where to send this else, so forgive me if this is the wrong > > mailinglist. > > See: > > http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.19-2&arch=hppa&stamp=1135294848&file=log&as=raw > > [..] > [...] > > As you can see, tetex-base depends on tex-common (>= 0.12). But the hppa > > build daemon doesn't install tex-common. > > So can somebody tell me what's going on here ? > 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. If the buildd wasn't installing a package that was part of the dependencies, then it surely thought for some reason it was already installed. If this wasn't actually the case, it points to a buildd problem or a bug in some maintainer script or other; either way, it seems to be corrected now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#344538: hppa dependency problems on build of pdns
Matthijs Mohlmann <[EMAIL PROTECTED]> wrote: > Hi, > > I don't know where to send this else, so forgive me if this is the wrong > mailinglist. > > See: > http://buildd.debian.org/fetch.php?&pkg=pdns&ver=2.9.19-2&arch=hppa&stamp=1135294848&file=log&as=raw > > [..] [...] > As you can see, tetex-base depends on tex-common (>= 0.12). But the hppa > build daemon doesn't install tex-common. > > So can somebody tell me what's going on here ? 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. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
