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

Bug#553236: libgnatvsn4.3: missing-dependency-on-libc needed by ./usr/lib/libgnatvsn.so.4.3 but the package doesn't depend on the C library package. Normally this indicates that ${shlibs: Depends} was omitted from the Depends line for this package in debian/control.

On Fri, Oct 30 2009, Ludovic Brenta wrote:

> Manoj Srivastava <srivasta@debian.org> writes:
>> On Thu, Oct 29 2009, Ludovic Brenta wrote:
>>> Manoj Srivastava <srivasta@debian.org> writes:
>>>> Package: libgnatvsn4.3
>>>> Version: 4.3.4-4
>>>> Severity: serious
>>>> Justification: The listed file appears to be linked against the C library,
>>>> User: lintian-maint@debian.org
>>>> Usertags: missing-dependency-on-libc
>>> The library depends on libgnat-4.3 which depends on libc6, so the
>>> dependency on libc6 is there, albeit indirectly.  Is this really a
>>> policy violation?
>>         Yes. You need the library, you depend on it. Just so that the
>>  other package's dependency changing does not break stuff.
> That cannot happen because libgnat-4.3 is built from the same sources as
> libgnat,prj}4.3 and the dependencies on libgnat-4.3 are
> exact-versioned ones.

        The thing is, if you do not have the dpkg-shlibdeps command in
 place, what else are  you missing? How do you know that will not

        You might think "My package is special, this cannot happen to
 us",  but the experience behind policy shows that things
 change. Developers move on, new ones come in. And the specialness of
 the package is not enough reason to grant a policy exception.

        I would say that just add the  dpkg-shlibdeps command, and move
 on. This is a small price to pay for inadvertent future violations of
 the invariant you think you have.

Do not clog intellect's sluices with bits of knowledge of questionable
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: