On Mon, Apr 25, 2005 at 11:11:19AM -0400, Adam Di Carlo wrote: > Christian Hammers <[EMAIL PROTECTED]> writes:
> > This bug has the severity "serious" which is "release critical" and no > > comment since month which is definetly too long :) > > 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. > > 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. > > 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? Yes, the bug title is clearly wrong; this bug has nothing to do with libglib1.2-dev, except that libglib1.2-dev is one of the packages that *can* fail when calling install-docs. > Hmm. So if you were unable to reproduce it, maybe it's the right thing > to tag it as unreproducible and lower the severity? If not, I would > take other suggestions on how to fix it. It's certainly not unreproducible. One of the release assistants also followed up to this bug noting that he had seen the problem; and the underlying cause has been analyzed and is definitely still present, we're just missing a fix for the problem. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature