On Mon, 15 Jun 2020 15:23:28 -0700 Felix Lechner
wrote:
> Hi Russ,
>
>> I wonder if we would get all of the utility out of the tag if instead it
>> looked for shared libraries with no NEEDED metadata.
Doesn't shared-lib-without-dependency-information check for that?
>> I think it's only
Control: forcemerge 896012 909267
Hi Russ,
> I wonder if we would get all of the utility out of the tag if instead it
> looked for shared libraries with no NEEDED metadata. I think it's only
> catching libraries that aren't linked with anything else, so maybe just
> check for that explicitly?
Chris Lamb wrote:
> > > I wonder if we would get all of the utility out of the tag if instead it
> > > looked for shared libraries with no NEEDED metadata. I think it's only
> > > catching libraries that aren't linked with anything else, so maybe just
> > > check for that explicitly?
> >
> >
Guillem Jover wrote:
> > I wonder if we would get all of the utility out of the tag if instead it
> > looked for shared libraries with no NEEDED metadata. I think it's only
> > catching libraries that aren't linked with anything else, so maybe just
> > check for that explicitly?
>
> Yeah
Hi!
On Thu, 2018-09-20 at 17:19:02 -0700, Russ Allbery wrote:
> Jeremy Bicha writes:
> > On Thu, Sep 20, 2018 at 6:18 PM Russ Allbery wrote:
> >> Maybe exclude shared libraries linked with glib (and whatever the Qt
> >> equivalent is)?
>
> > One package that triggers this tag a lot is samba
Jeremy,
> Chris, see https://bugs.debian.org/896012
(Thanks for the ping/reference. However, as I mention elsewhere in this
bug I am simply not well-versed enough in shared library magic to be
able to comment or move confidently here. Sorry.)
Best wishes,
--
,''`.
: :' :
Chris, see https://bugs.debian.org/896012
Thanks,
Jeremy Bicha
Jeremy Bicha writes:
> On Thu, Sep 20, 2018 at 6:18 PM Russ Allbery wrote:
>> Maybe exclude shared libraries linked with glib (and whatever the Qt
>> equivalent is)?
> One package that triggers this tag a lot is samba and it doesn't use
> glib or qt.
>
On Thu, Sep 20, 2018 at 6:18 PM Russ Allbery wrote:
> Maybe exclude shared libraries linked with glib (and whatever the Qt
> equivalent is)?
One package that triggers this tag a lot is samba and it doesn't use glib or qt.
Chris Lamb writes:
> Dear Simon et al.,
>> Was the goal of this tag to tell the difference between libraries that
>> are linked to their dependencies, and libraries that aren't, like the
>> difference between these?
>>
>> $ gcc -shared -Wl,-soname,libbad.so.0 -olibbad.so.0 libhello.c `pkg-
>>
Dear Simon et al.,
> Was the goal of this tag to tell the difference between libraries that
> are linked to their dependencies, and libraries that aren't, like the
> difference between these?
>
> $ gcc -shared -Wl,-soname,libbad.so.0 -olibbad.so.0 libhello.c `pkg-
> config --cflags glib-2.0`
> $
On Thu, 20 Sep 2018 at 17:42:30 +0100, Chris Lamb wrote:
> > "I think that tag is too high-priority tbh. In frameworks like GLib
> > and Qt it's far from unusual to do everything with higher-level
> > functions and not use libc directly at all, and -Wl,--as-needed turns
> > that into no
tags 909267 + moreinfo
severity 909267 wishlist
thanks
Dear Jeremy et al.,
> "I think that tag is too high-priority tbh. In frameworks like GLib
> and Qt it's far from unusual to do everything with higher-level
> functions and not use libc directly at all, and -Wl,--as-needed turns
> that into
Source: lintian
Version: 2.5.103
X-Debbugs-CC: naes...@gmail.com, s...@debian.org
We noticed that library-not-linked-against-libc is triggered for
several GNOME packages. [1]
smcv had these comments
--
"I think that tag is too high-priority tbh. In frameworks
14 matches
Mail list logo
