Your message dated Thu, 07 Apr 2011 04:04:15 +0200 with message-id <4d9d1b9f.3040...@debian.org> and subject line Re: Bug#621431: Still uses libdb4.8 has caused the Debian Bug report #621431, 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 ow...@bugs.debian.org immediately.) -- 621431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: kdesvn Version: 1.5.5-2 Severity: normal User: pkg-db-de...@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ý <ond...@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 ---Hi Ondřej Am 06.04.2011 22:57, schrieb Ondřej Surý: > Package: kdesvn > Version: 1.5.5-2 > Severity: normal > User: pkg-db-de...@lists.alioth.debian.org > Usertags: db5.1 > > Your package currently still uses Berkeley DB version 4.8 (libdb4.8). My package has: Build-Depends: debhelper (>= 8), cmake (>= 2.4), kdelibs5-dev, libsvn-dev (>= 1.2.0), libssl-dev (>= 0.9.8a), libsqlite3-dev, gettext, pkg-kde-tools (>= 0.9) So this must me a indirect dependency. This is nothing I can do about in kdesvn itself as kdesvn is not using libdb directly, thus closing. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________ pkg-kde-extras mailing list email@example.com http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras