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