Bug#621431: Still uses libdb4.8
block 621431 621460 thank you On Thu, Apr 7, 2011 at 05:16, Michael Biebl bi...@debian.org wrote: Am 07.04.2011 04:18, schrieb Michael Biebl: Am 07.04.2011 04:05, schrieb Michael Biebl: Am 07.04.2011 04:04, schrieb Michael Biebl: Hi Ondřej Am 06.04.2011 22:57, schrieb Ondřej Surý: 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. My guess is that is is pulled in via libsvn. As soon as libsvn has been updated, a binNMU of kdesvn should be sufficient. hm, maybe it's better to keep the bug open, if you want to track of the libdb removal archive wide. Please let me know, as soon as you have filed a bug against libsvn-dev. Let's then block this bug by the bug against libsvn-dev. As soon as libsvn-dev is fixed, we can fix the kdesvn bug by a binNMU. I am adding the blocked by. I'll try to do as much micromanagement like this as possible, but it's a huge task since we have db4.6, db4.7 and db4.8 in the archive, so please forgive any mistakes I may do. I've looked into this more closely. kdesvn uses libsvn and runs apu-config --link-ld --libs to get the necessary link flags. This outputs: -L/usr/lib -laprutil-1 -ldb and ls -la /usr/lib/libdb.so lrwxrwxrwx 1 root root 12 12. Feb 04:31 /usr/lib/libdb.so - libdb-4.8.so this link is shipped by libdb4.8-dev. I guess you need to start fixing things there. The link is also shipped by libdb5.1-dev, so I think everything is fine here. O. -- Ondřej Surý ond...@sury.org http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621431: Still uses libdb4.8
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621431: Still uses libdb4.8
found 621431 1.5.5-2 thanks Am 07.04.2011 04:05, schrieb Michael Biebl: Am 07.04.2011 04:04, schrieb Michael Biebl: 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. My guess is that is is pulled in via libsvn. As soon as libsvn has been updated, a binNMU of kdesvn should be sufficient. hm, maybe it's better to keep the bug open, if you want to track of the libdb removal archive wide. Please let me know, as soon as you have filed a bug against libsvn-dev. Let's then block this bug by the bug against libsvn-dev. As soon as libsvn-dev is fixed, we can fix the kdesvn bug by a binNMU. Cheers, Michael P.S: thanks for working on this. Those multiple libdb versions have always annoyed me and I support any effort shrinking that list. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#621431: Still uses libdb4.8
Am 07.04.2011 04:18, schrieb Michael Biebl: Am 07.04.2011 04:05, schrieb Michael Biebl: Am 07.04.2011 04:04, schrieb Michael Biebl: Hi Ondřej Am 06.04.2011 22:57, schrieb Ondřej Surý: 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. My guess is that is is pulled in via libsvn. As soon as libsvn has been updated, a binNMU of kdesvn should be sufficient. hm, maybe it's better to keep the bug open, if you want to track of the libdb removal archive wide. Please let me know, as soon as you have filed a bug against libsvn-dev. Let's then block this bug by the bug against libsvn-dev. As soon as libsvn-dev is fixed, we can fix the kdesvn bug by a binNMU. I've looked into this more closely. kdesvn uses libsvn and runs apu-config --link-ld --libs to get the necessary link flags. This outputs: -L/usr/lib -laprutil-1 -ldb and ls -la /usr/lib/libdb.so lrwxrwxrwx 1 root root 12 12. Feb 04:31 /usr/lib/libdb.so - libdb-4.8.so this link is shipped by libdb4.8-dev. I guess you need to start fixing things there. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
