reopen 621405 block 621405 by 621366 thank you Hi Sergey,
please keep this bug open, so I can keep track of packages still using the old libraries. I have added a blocked by apr-util bug for exactly the same thing, so as soon as the apr-util get's fixed, you will be able to do rebuild. Thank you, Ondrej On Thu, Apr 7, 2011 at 02:21, Debian Bug Tracking System <[email protected]> wrote: > This is an automatic notification regarding your Bug report > which was filed against the libapache2-mod-qos package: > > #621405: Still uses libdb4.8 > > It has been closed by Sergey B Kirpichev <[email protected]>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Sergey B Kirpichev > <[email protected]> by > replying to this email. > > > -- > 621405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621405 > Debian Bug Tracking System > Contact [email protected] with problems > > > ---------- Forwarded message ---------- > From: Sergey B Kirpichev <[email protected]> > To: [email protected] > Date: Thu, 7 Apr 2011 04:18:52 +0400 > Subject: Re: Bug#621405: Still uses libdb4.8 > 2011/4/7 Ondřej Surý <[email protected]>: >> Your package currently still uses Berkeley DB version 4.8 (libdb4.8). > > Yes, but it's not a direct dependence: > Build-Depends: debhelper (>= 7.0.50), apache2-prefork-dev (>= 2.2.3) | > apache2-threaded-dev (>= 2.2.3), libssl-dev (>= 0.9.8g), libapr1-dev, > libaprutil1-dev, libpcre3-dev, libpng12-dev, automake > > Probably, It's due to libaprutil1-dev. > > So, I'll close this bugreport. > > > > ---------- Forwarded message ---------- > From: "Ondřej Surý" <[email protected]> > To: Debian Bug Tracking System <[email protected]> > Date: Wed, 06 Apr 2011 22:57:16 +0200 > Subject: Still uses libdb4.8 > Package: libapache2-mod-qos > Version: 9.54-2 > 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 > > > > -- Ondřej Surý <[email protected]> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
