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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
