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

Bug#621366: marked as done (Still uses libdb4.8)



Your message dated Fri, 08 Apr 2011 17:33:30 +0000
with message-id <E1Q8FYo-0001fo-P2@franck.debian.org>
and subject line Bug#621366: fixed in apr-util 1.3.10+dfsg-2
has caused the Debian Bug report #621366,
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 owner@bugs.debian.org
immediately.)


-- 
621366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621366
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apr-util
Version: 1.3.9+dfsg-5
Severity: normal
User: pkg-db-devel@lists.alioth.debian.org
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ý <ondrej@debian.org>

-- 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: apr-util
Source-Version: 1.3.10+dfsg-2

We believe that the bug you reported is fixed in the latest version of
apr-util, which is due to be installed in the Debian FTP archive:

apr-util_1.3.10+dfsg-2.diff.gz
  to main/a/apr-util/apr-util_1.3.10+dfsg-2.diff.gz
apr-util_1.3.10+dfsg-2.dsc
  to main/a/apr-util/apr-util_1.3.10+dfsg-2.dsc
libaprutil1-dbd-freetds_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbd-freetds_1.3.10+dfsg-2_i386.deb
libaprutil1-dbd-mysql_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbd-mysql_1.3.10+dfsg-2_i386.deb
libaprutil1-dbd-odbc_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbd-odbc_1.3.10+dfsg-2_i386.deb
libaprutil1-dbd-pgsql_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbd-pgsql_1.3.10+dfsg-2_i386.deb
libaprutil1-dbd-sqlite3_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbd-sqlite3_1.3.10+dfsg-2_i386.deb
libaprutil1-dbg_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dbg_1.3.10+dfsg-2_i386.deb
libaprutil1-dev_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-dev_1.3.10+dfsg-2_i386.deb
libaprutil1-ldap_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1-ldap_1.3.10+dfsg-2_i386.deb
libaprutil1_1.3.10+dfsg-2_i386.deb
  to main/a/apr-util/libaprutil1_1.3.10+dfsg-2_i386.deb



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 621366@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefan Fritsch <sf@debian.org> (supplier of updated apr-util 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 08 Apr 2011 19:19:23 +0200
Source: apr-util
Binary: libaprutil1 libaprutil1-ldap libaprutil1-dbd-mysql libaprutil1-dbd-sqlite3 libaprutil1-dbd-odbc libaprutil1-dbd-pgsql libaprutil1-dbd-freetds libaprutil1-dev libaprutil1-dbg
Architecture: source i386
Version: 1.3.10+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Apache Maintainers <debian-apache@lists.debian.org>
Changed-By: Stefan Fritsch <sf@debian.org>
Description: 
 libaprutil1 - Apache Portable Runtime Utility Library
 libaprutil1-dbd-freetds - Apache Portable Runtime Utility Library - FreeTDS Driver
 libaprutil1-dbd-mysql - Apache Portable Runtime Utility Library - MySQL Driver
 libaprutil1-dbd-odbc - Apache Portable Runtime Utility Library - ODBC Driver
 libaprutil1-dbd-pgsql - Apache Portable Runtime Utility Library - PostgreSQL Driver
 libaprutil1-dbd-sqlite3 - Apache Portable Runtime Utility Library - SQLite3 Driver
 libaprutil1-dbg - Apache Portable Runtime Utility Library - Debugging Symbols
 libaprutil1-dev - Apache Portable Runtime Utility Library - Development Headers
 libaprutil1-ldap - Apache Portable Runtime Utility Library - LDAP Driver
Closes: 621366
Changes: 
 apr-util (1.3.10+dfsg-2) unstable; urgency=low
 .
   * Remove libdb4.8-dev dependency in libaprutil1-dev. This allows packages
     build-depending on apr-util1 to use a different version of db than
     apr-util.
   * With the libdb build-dependency decoupled from subversion, we can now
     build-depend on libdb-dev instead of libdb4.8-dev. Users of APU_WANT_DB
     in apu_want.h would have to depend on libdb-dev explicitly, but there
     are none outside of apr-util itself. Closes: #621366
   * Add configure support for libdb 5.1.
   * Bump standards version to 3.9.2 (no changes)
   * Fix some lintian warnings about the short descriptions.
Checksums-Sha1: 
 f60598f05b5ba3fa3eb2db0183086979e90caaa7 1739 apr-util_1.3.10+dfsg-2.dsc
 092da65e16e24c7c11dc91275c6489af1632e49e 26339 apr-util_1.3.10+dfsg-2.diff.gz
 b35659dce8e13a53a67647dbd36588bc64726d75 79676 libaprutil1_1.3.10+dfsg-2_i386.deb
 ef1d888234a0f812c5e4354dc85cdc4a84e09ceb 17700 libaprutil1-ldap_1.3.10+dfsg-2_i386.deb
 ba3eba4f028a56c185dc799265c608de66c1e6ce 21916 libaprutil1-dbd-mysql_1.3.10+dfsg-2_i386.deb
 afb1590f32d01a91f7cd9880cfbb30eaffc2f36c 19730 libaprutil1-dbd-sqlite3_1.3.10+dfsg-2_i386.deb
 c0cf0ff86b367940dc5542cb1b36415bc0032d85 26014 libaprutil1-dbd-odbc_1.3.10+dfsg-2_i386.deb
 51385b9c3779ba7804987358998f0d051276526e 21896 libaprutil1-dbd-pgsql_1.3.10+dfsg-2_i386.deb
 ba4c86508ee207f1eb6df0e7232c4d8d1a90b49d 20098 libaprutil1-dbd-freetds_1.3.10+dfsg-2_i386.deb
 952a56cf837f2513e1a18e0c597cafe5827adcdf 611814 libaprutil1-dev_1.3.10+dfsg-2_i386.deb
 9e0abb7d5dcba9b5ee682215630acd3f4e2c3acf 235756 libaprutil1-dbg_1.3.10+dfsg-2_i386.deb
Checksums-Sha256: 
 77092451628face54eb36477f472ee7a462efa086a582c800d01c4dfa8986eb7 1739 apr-util_1.3.10+dfsg-2.dsc
 85f90bd4da0b4caa722dfeb63960123287cd6c275741ece8ab194e559fbe635f 26339 apr-util_1.3.10+dfsg-2.diff.gz
 b669ff5c58d88d56db71a1d2018470af34b277f70fd4b263e7af972b5d158ccb 79676 libaprutil1_1.3.10+dfsg-2_i386.deb
 d3d5ab9e008f9f32216fdc892372ce2c9bcc212cd86f46a1fc016643a79ece74 17700 libaprutil1-ldap_1.3.10+dfsg-2_i386.deb
 74de579af5956ad2a75737bc7e7093a1f296cd18b90575d9c024f8c7ef291bc5 21916 libaprutil1-dbd-mysql_1.3.10+dfsg-2_i386.deb
 d2c910a71d4a46dca13c7511ad1d34961725b7af8a5fd8a6c479d3656e84ffa9 19730 libaprutil1-dbd-sqlite3_1.3.10+dfsg-2_i386.deb
 c43ec4fe03c40da1ce1020a1d1d6d28624bfc93b88f40a71e68308dc0fc5c26a 26014 libaprutil1-dbd-odbc_1.3.10+dfsg-2_i386.deb
 34c0c7c488cbdb33cfb15ddf62f9eb743e9b58aa3036dd27a4c82ddb0376e51d 21896 libaprutil1-dbd-pgsql_1.3.10+dfsg-2_i386.deb
 f7820b6d515d387192971a4dd80dc9590efba33654922329c42e72b65b321f3d 20098 libaprutil1-dbd-freetds_1.3.10+dfsg-2_i386.deb
 f7486da3976b20df33963f55684d3c15f2918d1fb63cd70e2822872569feb9ea 611814 libaprutil1-dev_1.3.10+dfsg-2_i386.deb
 e97b7abfef33e016fda13960877b18bfb69a2e48519a1350e046b2bb5d2444cb 235756 libaprutil1-dbg_1.3.10+dfsg-2_i386.deb
Files: 
 24ffd1a0203e689439b116d4d54c383c 1739 libs optional apr-util_1.3.10+dfsg-2.dsc
 3963322a4c7e299706a4332fa6297fd8 26339 libs optional apr-util_1.3.10+dfsg-2.diff.gz
 ee2e44dbd5ce3995e5ac8e6ba7d6d774 79676 libs optional libaprutil1_1.3.10+dfsg-2_i386.deb
 8f16a2f2ad5cabdbed2414c773558c0f 17700 libs optional libaprutil1-ldap_1.3.10+dfsg-2_i386.deb
 ba26d89f865bdfde426ca13d0bf9343f 21916 libs optional libaprutil1-dbd-mysql_1.3.10+dfsg-2_i386.deb
 4c0974f2416e625f623858c09329a519 19730 libs optional libaprutil1-dbd-sqlite3_1.3.10+dfsg-2_i386.deb
 3b6350a4636dbe124a2d4c3799bc2fac 26014 libs optional libaprutil1-dbd-odbc_1.3.10+dfsg-2_i386.deb
 c5a5b282021f3b95b177c28289aa1ae5 21896 libs optional libaprutil1-dbd-pgsql_1.3.10+dfsg-2_i386.deb
 9f10558fe5e8eba00182ca54a31242cb 20098 libs optional libaprutil1-dbd-freetds_1.3.10+dfsg-2_i386.deb
 9744174e7c4c0ac37d50be488056b794 611814 libdevel optional libaprutil1-dev_1.3.10+dfsg-2_i386.deb
 7dfd3c9e44ecd635acdda88086662e98 235756 debug extra libaprutil1-dbg_1.3.10+dfsg-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQFNn0TNbxelr8HyTqQRAsAEAJ45U+necYL3KbV9wjmtPVS9Ah+oAwCdGsCl
59amYh2wv/7l1biBYH/6tKM=
=7HJB
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: