Bug#310793: Perl DB_File data not backwards compatible
retitle 310793 [Release notes] perl DB_File migration from 2.0 to 4.2
On Wed, May 25, 2005 at 07:58:28PM -0600, Jeremy Nickurak wrote:
> Just went through a woody->sarge update, and pretty much everything
> went fine, with one exception. I have a perl script that manages some
> data on this server via DB_File. As per perl's changelog, since the
> last woody release:
> "NOTE: DB_File now uses libdb4.0 (previously libdb2). Any DB_File
> databases created with earlier perl packages will need to be upgraded
> before being used with the current module with the db4.0_upgrade
> program (in the libdb4.0-util package, with HTML docs in db4.0-doc)."
> This procudure successfully recovered data I thought for some time was
> lost. Unfortunately this was not mentioned in the upgrade process, and
> appears to not be mentioned anywhere other than this 2+year old
> changelog comment, which I found only by googling.
> I don't know if there's a "known upgrade issues" document somewhere (
> doesn't seem to mention in), but this should probabbly be documented
> as a heads-up for people who will run into the same problem, if not
> brought up in a notification at perl upgrade time.
Hello Jeremy, following your mail to debian-devel, I have raised the
issue on debian-doc (in charge of the release notes). At this stage, we
are mostly looking for a wording. See the thread at
Thanks a lot for this proposal!
Imagine a large red swirl here.