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/



_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras

Reply via email to