Your message dated Sun, 17 Apr 2011 22:59:21 +0200
with message-id <[email protected]>
and subject line Re: Bug#621352: Still uses libdb4.7
has caused the Debian Bug report #621352,
regarding Still uses libdb4.7
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.)
--
621352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621352
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: etpan-ng
Version: 0.7.1-5.1
Severity: normal
User: [email protected]
Usertags: db5.1
Your package currently still uses Berkeley DB version 4.7 (libdb4.7).
However, there is a newer Berkeley DB version in the archive (libdb5.1),
with a compatible API. Berkeley DB version 4.7 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.7-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.7 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 ---
Hi again.
* Ondřej Surý <[email protected]> [2011-04-06 22:44:39 CEST]:
> Your package currently still uses Berkeley DB version 4.7 (libdb4.7).
No, it doesn't.
> Please port your package to libdb5.1 as soon as possible. In most cases
> only change required is to update build depends from libdb4.7-dev
> to libdb-dev, or just recompile the package.
Actually, eptan-ng does not build-depend on libdb at all, it *uses* a
library that links in libdb. I wouldn't know how and what etpan-ng
itself should do instead of just sit and wait until the library got
updated, and then receive a binNMU (scheduled by the release/buildd
teams).
Can you pretty please check your data and the way things work next time
prior to filing massbugs? Would be very much appreciated.
Enjoy,
Rhonda
--
Fühlst du dich mutlos, fass endlich Mut, los |
Fühlst du dich hilflos, geh raus und hilf, los | Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los |
--- End Message ---
