On Sun, May 13, 2018 at 08:09:43PM +0200, Thorsten Alteholz wrote:
> Hi Bill,
>
> On Tue, 1 May 2018, Bill Allombert wrote:
> >There is a circular dependency between libosmocodec0, libosmocore9 and
> >libosmogsm8:
> >
> >libosmocodec0 :Depends: libosmocore9 (>= 0.10.2)
> >libosmocore9 :Depends: libosmocodec0 (>= 0.9.6), libosmogsm8 (>=
> >0.10.2)
> >libosmogsm8 :Depends: libosmocore9 (>= 0.10.2)
>
> but all of those packages just have
> Depends: ${shlibs:Depends},
> ${misc:Depends}
>
> So do you have any idea how to avoid that automatically generated loop?
They come from the debian/*.symbols files.
In the buildlog:
<https://buildd.debian.org/status/fetch.php?pkg=libosmocore&arch=i386&ver=0.10.2-6&stamp=1523204276&raw=0>
there is a big warning:
dh_makeshlibs -a
dpkg-gensymbols: warning: new libraries appeared in the symbols file:
libosmocoding.so.0
dpkg-gensymbols: warning: debian/libosmocore9/DEBIAN/symbols doesn't match
completely debian/libosmocore9.symbols
--- debian/libosmocore9.symbols (libosmocore9_0.10.2-6_i386)
+++ dpkg-gensymbolsk8_uNr 2018-04-08 16:17:40.230621785 +0000
@@ -1,3 +1,112 @@
+libosmocoding.so.0 libosmocore9 #MINVER#
+ LIBOSMOCODING_1.0@LIBOSMOCODING_1.0 0.10.2-6
In any case, the packaging need to be improved to generate less
buildtime warning and less lintian warning.
Cheers,
--
Bill. <ballo...@debian.org>
Imagine a large red swirl here.
