Control: tags -1 + unreproducible moreinfo wontfix upstream

Hello Ben Longbons,

On Mon, Mar 06, 2017 at 10:22:06AM -0800, Ben Longbons wrote:
> Package: util-linux
> Version: 2.29.1-1
> Severity: important
> File: /usr/bin/whereis
> 
> Dear Maintainer,
> 
> On other systems, including old releases of Debian, the command
> `whereis libc.so` will return the paths to libc.so *and* libc.a

Not for me.

$ dpkg -l util-linux
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  util-linux     2.29.1-1     amd64        miscellaneous system utilities
$ whereis libc.so
libc: /usr/share/man/man7/libc.7.gz
$ 

> On Debian, this only works for non-multiarch'ed libraries.

But libc.so is in a multi-arch location....

$ dpkg -L libc6-dev | grep libc.so
/usr/lib/x86_64-linux-gnu/libc.so

... so you seem to contradict yourself?!


> 
> Although the man page only says "binary", it also includes libraries,
> as shown by `whereis -l`.

Both libc.so and libc.a are binary files, so not sure what your point is.

Either way, if you want to change the behaviour of something that's been
working in a certain way for decades you'll want to bring your arguments
to the upstream development discussion area. That's where development of
the software happens..... I'm also pretty sure there's already been
another bug report opened on this or similar subject. You might want
to research the archives to learn from past discussions before
preparing your argumentation on behaviour change.

Regards,
Andreas Henriksson

Reply via email to