[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: shlibs and lintian



Hi
What do you mean the libraries are broken ?
I can install the package and everything runs ok . But I do not like these 
messages OR
something can cause a trouble I do not see

thanks

Zvi Dubitzky 
Email:dubi@il.ibm.com





From:   Russ Allbery <rra@debian.org>
To:     debian-mentors@lists.debian.org
Date:   11/10/2010 17:56
Subject:        Re: shlibs and lintian



Zvi Dubitzky <DUBI@il.ibm.com> writes:

> I am having a package for libraries (several)
> The package is called libvae (libvae_1.3_amd64.deb)  and include the 
> libraries (libvae.so.2.0 , libvaeUtil.so.2.0  ..)

> The shlibs is as follows :
> libvae 2 libvae  (>= 1.3)
> libvaeUtil 2 libvae (>= 1.3)
> libvirtExt 2 libvae (>= 1.3)
> libvhi 2 libvae  (>= 1.3)
> libvanos 2 libvae (>= 1.3)

> all the libraries and some sym links to them are positioned in /usr/lib.

> yet after generating the package and running lintian I get the following 

> warning :

> W: libvae: unused-shlib-entry-in-control-file libvae 2
[...]

> Also there are sym links like : /usr/lib/libvae.so -> libvae.so.2.0 . 
they 
> are also included but the lintian seems to want an entry
> for them in the shlibs and issues the following  error:
> E: libvae: shlib-missing-in-control-file libvae.so for 
usr/lib/libvae.so.2.0
[...]

The above seems to indicate that the problem is the shared libraries are
broken.  The Lintian tags that you're getting imply that the SONAME of
this library is just "libvae.so" without any version, not "libvae.so.2"
like it should be.  Such libraries without SONAMEs can't be represented in
shlibs, which is causing both of the errors that you're getting.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>


-- 
To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact 
listmaster@lists.debian.org
Archive: [🔎] 871v7wyb9r.fsf@windlord.stanford.edu">http://lists.debian.org/[🔎] 871v7wyb9r.fsf@windlord.stanford.edu




Reply to: