[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#310793: marked as done ([Release notes] perl DB_File migration from 2.0 to 4.2)

Your message dated Tue, 20 Sep 2005 21:36:04 -0400
with message-id <4330B904.50703@dlgeek.net>
and subject line Closing old bugs
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 26 May 2005 01:59:05 +0000
>From atrus@bugs.debian.spam.rifetech.com Wed May 25 18:59:05 2005
Return-path: <atrus@bugs.debian.spam.rifetech.com>
Received: from shawidc-mo1.cg.shawcable.net (pd2mo3so.prod.shaw.ca) [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Db7eL-0007T0-00; Wed, 25 May 2005 18:59:05 -0700
Received: from pd4mr5so.prod.shaw.ca (pd4mr5so-qfe3.prod.shaw.ca [])
 by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004))
 with ESMTP id <0IH2007PFQT6JL40@l-daemon> for submit@bugs.debian.org; Wed,
 25 May 2005 19:58:18 -0600 (MDT)
Received: from pn2ml6so.prod.shaw.ca ([])
 by pd4mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar
 15 2004)) with ESMTP id <0IH200JCUQT6I980@pd4mr5so.prod.shaw.ca> for
 submit@bugs.debian.org; Wed, 25 May 2005 19:58:18 -0600 (MDT)
Received: from achenar.threea.hub
 (S01060000b48e3b44.cg.shawcable.net [])
 by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003))
 with ESMTP id <0IH20015JQT6AP@l-daemon> for submit@bugs.debian.org; Wed,
 25 May 2005 19:58:18 -0600 (MDT)
Received: from agaeris.threea.hub
	([] helo=localhost ident=Debian-exim)	by achenar.threea.hub with
 esmtp (Exim 4.50)	id 1Db7dV-0007x1-JU; Wed, 25 May 2005 19:58:13 -0600
Received: from atrus by localhost with local (Exim 4.50)
	id 1Db7dk-0001NS-EG; Wed, 25 May 2005 19:58:28 -0600
Date: Wed, 25 May 2005 19:58:28 -0600
From: Jeremy Nickurak <atrus@bugs.debian.spam.rifetech.com>
Subject: Perl DB_File data not backwards compatible
To: Debian Bug Tracking System <submit@bugs.debian.org>
Message-id: <E1Db7dk-0001NS-EG@localhost>
MIME-version: 1.0
X-Mailer: reportbug 3.12
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.4 required=4.0 tests=BAYES_00,FAKE_HELO_SHAW_CA,
	HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: upgrade-reports
Severity: normal

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 ( 
http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html 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.

-- System Information:
Debian Release: 3.1
  APT prefers experimental
  APT policy: (1000, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-rc3-mm3
Locale: LANG=eo_EO.UTF-8, LC_CTYPE=eo_EO.UTF-8 (charmap=UTF-8)

Received: (at 310793-done) by bugs.debian.org; 21 Sep 2005 01:36:15 +0000
>From astronut@dlgeek.net Tue Sep 20 18:36:15 2005
Return-path: <astronut@dlgeek.net>
Received: from sfnc-162-39-87-185.netdialus.com (mail.dlgeek.net) [] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EHtWw-0000Dt-00; Tue, 20 Sep 2005 18:36:14 -0700
Received: from [] (debian [])
	by mail.dlgeek.net (Postfix) with ESMTP id 1AE5D28269;
	Tue, 20 Sep 2005 21:36:12 -0400 (EDT)
Message-ID: <4330B904.50703@dlgeek.net>
Date: Tue, 20 Sep 2005 21:36:04 -0400
From: Benjamin Seidenberg <astronut@dlgeek.net>
User-Agent: Debian Thunderbird 1.0.6 (X11/20050802)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 309146-done@bugs.debian.org, 295213-done@bugs.debian.org,
	310005-done@bugs.debian.org, 316379-done@bugs.debian.org,
	316948-done@bugs.debian.org, 309329-done@bugs.debian.org,
	309548-done@bugs.debian.org, 310124-done@bugs.debian.org,
	310793-done@bugs.debian.org, 310818-done@bugs.debian.org,
	316991-done@bugs.debian.org, 318372-done@bugs.debian.org,
	165604-done@bugs.debian.org, 273299-done@bugs.debian.org
Subject: Closing old bugs
Content-Type: multipart/signed; micalg=pgp-sha1;
Delivered-To: 310793-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
X-CrossAssassin-Score: 9

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

This bug report refers to problems upgrading from a stable woody system 
to an almost complete sarge, while Sarge was still testing or in some 
cases, an even earlier transition. Since sarge has been released for 
several months now, I think this report no longer applies, and am 
closing it. Many of these issues were fixed, the rest most likely do not 
matter. If you feel this bug was closed prematurely, please reopen the bug.

Thank You,
Benjamin Seidenberg

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org



Reply to: