On Mon, Apr 25, 2005 at 01:28:38AM +0200, Christian Hammers wrote:
> This bug has the severity "serious" which is "release critical" and no
> comment since month which is definetly too long :)
Nobody knows what to say to it :/

> In the bug logs I see some proposals regarding the perl dependencies
> and Frank's last mail which suggests that the problem is probably fixed
> but not yet confirmed as such.

No, it is not fixed AFAIK and there were objections to the proposal
of changing the dependencies (e.g. by vorlon, IIRC)...

> I'm not sure how to do that but I just created a woody chroot, installed
> libglib1.2-dev and then dist-upgraded to sarge. Worked fine at least. :)
> If I have to confirm a more special scenario, just tell, I can quickly
> rsync the chroot back to Woody.

It's not that simple. The following list of installed packages is known
to give you the effect:
http://www.lichtenheld.de/debian/perlupdate.installed

> BTW: Maybe this bug should be retitled, too, as it the bug seems to be
>      some race-condition between the installation of perl and doc-base?

Yeah, feel free to do that. And to reassign it to perl as doc-base
doesn't really have anything to do with the problem, it just points it
out...

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to