Your message dated Wed, 20 Apr 2011 05:32:45 +0000
with message-id <[email protected]>
and subject line Bug#621426: fixed in onak 0.4.0-1
has caused the Debian Bug report #621426,
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.)
--
621426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621426
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: onak
Version: 0.3.8-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 ---
Source: onak
Source-Version: 0.4.0-1
We believe that the bug you reported is fixed in the latest version of
onak, which is due to be installed in the Debian FTP archive:
onak_0.4.0-1.diff.gz
to main/o/onak/onak_0.4.0-1.diff.gz
onak_0.4.0-1.dsc
to main/o/onak/onak_0.4.0-1.dsc
onak_0.4.0-1_amd64.deb
to main/o/onak/onak_0.4.0-1_amd64.deb
onak_0.4.0.orig.tar.gz
to main/o/onak/onak_0.4.0.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonathan McDowell <[email protected]> (supplier of updated onak package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 19 Apr 2011 21:59:28 -0700
Source: onak
Binary: onak
Architecture: source amd64
Version: 0.4.0-1
Distribution: unstable
Urgency: low
Maintainer: Jonathan McDowell <[email protected]>
Changed-By: Jonathan McDowell <[email protected]>
Description:
onak - OpenPGP Key Server
Closes: 621426
Changes:
onak (0.4.0-1) unstable; urgency=low
.
* Only seed empty database for if we're using default config
* Use generic db dependencies rather than 4.8 versioned ones.
(Closes: #621426)
* Bump Debian Standards-Version to 3.9.2.0
* Add ${perl:Depends} to dependencies
* Add init.d file for keyd
* Add logrotate config snippet
Checksums-Sha1:
ac1786a62a960a9cfc94e80f500ba4d1c43e5155 1737 onak_0.4.0-1.dsc
76e01f5e7bcbc73fcb86c01c85dba991e9a7d033 230996 onak_0.4.0.orig.tar.gz
ce447ac55f94c70db842e523cfbeda0b457bde6b 4402 onak_0.4.0-1.diff.gz
0bc99b453fde2c21276a135ca9f7d7b344927818 401700 onak_0.4.0-1_amd64.deb
Checksums-Sha256:
b056e924e9f79f20913410a6790373fd507d8f2ebc12ed9fb498d330ae9bfbad 1737
onak_0.4.0-1.dsc
e402042d2cbcbe34cfac1d737a564054fea84ad5c00386ab0c877698c3076ecd 230996
onak_0.4.0.orig.tar.gz
a99f35ed4ff251b727803d1f3f993bdad25d75c4b631d13628ca7925f323900d 4402
onak_0.4.0-1.diff.gz
3c7872a213a4703a4e6e5123aea67084ec971645ffcaf61112bb0abb870f16d3 401700
onak_0.4.0-1_amd64.deb
Files:
7be7ca419910e59dcfc835b64fa418d1 1737 net optional onak_0.4.0-1.dsc
c73afbb24abcb35f1fba0a20b61ae1e8 230996 net optional onak_0.4.0.orig.tar.gz
2f48fecfbfafb552c83623be6c3343ae 4402 net optional onak_0.4.0-1.diff.gz
d2b5a697b8b84531b3565fb094c84f0e 401700 net optional onak_0.4.0-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJNrm0vAAoJEP8WL8XPP7rREz0P/3kuxmiutLN8WsDe+I3jIs6B
oYu1J4rqjWaBYBQR/K8i48LR7MCDZU4w5xO+040QwDlRxQP+jyhtTM5hQaYuT0jd
U3gSxM3f7AOA6G+vwCV6BT8I+4MmFU+PgtYLEVuZ4ij8HzlXpMbIbogK1q87Pv9T
n7q4KtH0boNmwFqdioFBSx3VXdqpnzHlbySf7sAognGRlwLrJ2sbUB969WnKodev
LLAmxqkgo65DwQ+kfrg6ZpoVoteN8FCxiZJEDCs/WNcG8ktv56yKen949NT1kF+A
7cAyxN9rhGKuzc3ZOeBFNi1UoGb/o2xKMVDDJQ8l8gQDBff0G5OXUMWNRf9e3vMf
GmtwTtkniHUCcZ7/NEBOfqdf2SN2DXm0nYrfEije3Fwh111eZ2LCiVQ593QpIUHp
7tcme2UnHqrTW3IEpaYsyESvrvyevt7LdHuTa0IbDW7eNmUmxFuxZ+OscULNWpo4
NWsko23VFl1718Q1Ky7S/PTAqQKYFi6QKri+YVWRerA6l1Bkko3cFP8hdqaP1E4V
TySPCyHRlKwMWyUqpRfvuR6FgT8viCwSFbOv7JUC/CCgDNV6Ck12tZ87+4TG5n5g
dcmmmRJUMhuI5ByjVX4vM4UjFuxnp3cN1BpvK7/Cs5v0uwJ1+sEktouBrpGiihGA
l5wNeGeb6kmJUacyGT/n
=irI1
-----END PGP SIGNATURE-----
--- End Message ---
