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 line I type: >dpkg -S /usr/bin/cp I expect it to tell me coreutils: /usr/bin/cp instead, it falsely reports dpkg-query: no path found matching pattern /usr/bin/cp So I check some other things and find it working correctly. >dpkg -S /usr/bin/dpkg dpkg: /usr/bin/dpkg >dpkg -S /usr/bin/xz xz-utils: /usr/bin/xz >dpkg -S /usr/bin/yelp yelp: /usr/bin/yelp In fact it responds correctly to everything I've tried EXCEPT files installed by coreutils: >dpkg -S /usr/bin/cp dpkg-query: no path found matching pattern /usr/bin/cp >dpkg -S /usr/bin/ls dpkg-query: no path found matching pattern /usr/bin/ls >dpkg -S /usr/bin/rmdir dpkg-query: no path found matching pattern /usr/bin/rmdir >dpkg -S /usr/bin/mv dpkg-query: no path found matching pattern /usr/bin/mv >dpkg -S /usr/bin/grep dpkg-query: no path found matching pattern /usr/bin/grep But it's not entirely consistent. There are some coreutils files it identifies correctly: >dpkg -S /usr/bin/yes coreutils: /usr/bin/yes I don't know why this is happening. But I thought I should report it. Bear
