Your message dated Mon, 30 May 2011 22:10:29 +0000
with message-id <[email protected]>
and subject line Bug#628504: Removed package(s) from unstable
has caused the Debian Bug report #621461,
regarding Still uses libdb4.8
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
621461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621461
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3.1
Version: 3.1.3-1
Severity: normal
User: [email protected]
Usertags: db5.1
Your package currently still uses Berkeley DB version 4.8 (libdb4.8).
However, there is a newer Berkeley DB version in the archive (libdb5.1),
with a compatible API. Berkeley DB version 4.8 will be eventually
removed from unstable in favor of version 5.1.
Please port your package to libdb5.1 as soon as possible. In most cases
only change required is to update build depends from libdb4.8-dev
to libdb-dev, or just recompile the package.
More complicated scenarios:
- Package does check for DB_VERSION_MAJOR == 4 - this should be updated
to (DB_VERSION_MAJOR > 4) || ((DB_VERSION_MAJOR == 4) && (DB_VERSION_MINOR >=
XX)).
- Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2, etc.,
this
needs to be updated to just db (or db-5.1 db-5 db), or at least list the 'db'
in the front
You can see example patch in cyrus-imapd-2.2:
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD
- The packages which use Berkeley DB transactional mode need to upgrade
the database files before the upgrade. This is fairly straightforward
and is well documented on the Berkeley DB website. But you probably
already know that because it's not the first Berkeley DB transition.
The example script can be found in the cyrus-imapd-2.4 (not yet released):
http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD
Thanks,
--
Ondřej Surý <[email protected]>
-- System Information:
Debian Release: squeeze/sid
APT prefers maverick-updates
APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500,
'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 3.1.3-1+rm
Dear submitter,
as the package python3.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/628504
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)
--- End Message ---
