On Wednesday 25 May 2005 10:24, Bill Allombert wrote: > Should we put a note about this in the release notes ? If it is an confirmed issue, sure. We will need a better text that this though. One that really explains the issue and how to solve it (in about two not too long paragraphs preferably). Would the package maintainers be able to provide something? (Others welcome too of course.) Cheers, FJP > perl is quite a central piece of Debian. > > ----- Forwarded message from Jeremy Nickurak > <atrus@debian.spam.rifetech.com> ----- > > I just ran through a woody-sarge update, and (temporarilly) lost a > number of perl databases that an unpackaged app had created. Took me > quite a while to figure out exactly what happened, more time than a > user should normally be expected to put into debugging I think. > > Woody's perl 5.6 uses libdb2. Sarge's uses libdb4. libdb4 cannot > natively open databases created with libdb2, and while this point is > stated in perl's changelog, I don't believe most users will read all 20 > pages of changelog entries that have occured since then, and there > appeared to be no notification in the process of the upgrade that such > an issue would take place. > > There is an upgrade script available, but afaict it's only reference is > buried deep in that changelog. > > Sounds like a perfect place to use a NEWS.gz file and apt-listchanges, > if there's a way to enforce the installation of apt-listchanges. > > Comments? > > ----- End forwarded message ----- > > Cheers, > -- > Bill. <ballombe@debian.org> > > Imagine a large red swirl here.
Attachment:
pgpa5W6vrulNm.pgp
Description: PGP signature