Bug#1000715: dpkg -S fails to identify package for coreutils files: says 'no path found matching pattern' instead

2021-12-14 Thread Guillem Jover
Hi! On Sun, 2021-11-28 at 19:09:37 +, Ray Dillinger wrote: > I suppose this means I don't actually understand how dpkg works at all.  > The files are there in /usr/bin, and SOMETHING, presumably an installer > run by dpkg the most recent time coreutils was updated, installed them.  > But dpkg

Bug#1000715: dpkg -S fails to identify package for coreutils files: says 'no path found matching pattern' instead

2021-11-28 Thread Ray Dillinger
On Sun, 28 Nov 2021 09:48:22 +0100 Niels Thykier wrote: > This is a consequence of the currently incomplete "/usr-merge" > transition, where /bin has been merged into /usr/bin without dpkg's back. > > As such, dpkg knows those paths only by their "officially declared" > paths in /bin. It is

Bug#1000715: dpkg -S fails to identify package for coreutils files: says 'no path found matching pattern' instead

2021-11-28 Thread Niels Thykier
On Sat, 27 Nov 2021 18:58:53 + Ray Dillinger wrote: > Package: dpkg > Version: 1.20.9 > Distribution: Bookworm > Architecture: AMD64 > > Relevant because this could have something to do with which utilities > are statically linked to bash or exactly which coreutils we're talking > about:  >

Bug#1000715: dpkg -S fails to identify package for coreutils files: says 'no path found matching pattern' instead

2021-11-27 Thread Ray Dillinger
Package: dpkg Version: 1.20.9 Distribution: Bookworm Architecture: AMD64 Relevant because this could have something to do with which utilities are statically linked to bash or exactly which coreutils we're talking about:  bash is version 5.1-3.1 and coreutils is version 8.32-4.1 At the command