Your dpkg -S hits an ancient issue https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=134758
You're also exactly right about status quo being an unhappy place. Debian is currently trying to figure out a solution: https://lists.debian.org/debian-devel/2023/04/msg00008.html -- it's been in progress for years and probably will remain in progress for years. I don't think the right answer is for individual packages to make changes -- Simon has enumerated some risks at: https://lists.debian.org/debian-devel/2023/04/msg00090.html I don't know what the right answer is for your computer -- nor how you've even gotten into the situation you're in. I believe just blinding installing the usrmerge package to forcibly move all your executables and build symlinks would probably crash if you've got duplicate executables in both places. My first thought to finding more collisions... cd /bin ; echo * | tr ' ' '\n' > /tmp/bin cd /usr/bin ; echo * | tr ' ' '\n' > /tmp/usrbin comm -12 /tmp/bin /tmp/usrbin cd /sbin ; echo * | tr ' ' '\n' > /tmp/sbin cd /usr/sbin ; echo * | tr ' ' '\n' > /tmp/usrsbin comm -12 /tmp/sbin /tmp/usrsbin ** Bug watch added: Debian Bug tracker #134758 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134758 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2017594 Title: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker Status in apparmor package in Ubuntu: Confirmed Bug description: There appears to be two copies of apparmor_parser installed by previous versions of the apparmor package, in /sbin and /usr/sbin. When updating the apparmor package to apparmor-2.13.3-7ubuntu5.2, only the /sbin/apparmor_parser executable is updated and the /usr/sbin copy is left unchanged. Being earlier the path, /usr/sbin/apparmor_parser is used by Docker when trying to register the docker-default apparmor profile for containers. The orphaned older executable reports a warning about a new parameter in the parser configuration file in the same package, and that warning breaks the version check that docker runs against that executable on the first line of output. trying to parse the warning while looking for the version number results in the error: docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: strconv.Atoi: parsing "file": invalid syntax. As a workaround, we've been replacing the old version in /usr/sbin with a symlink to the file in /sbin, but the package should be corrected to do appropriate behaviour (either delete the unnecessary(?) copy in /usr/sbin or replace it with a symlink) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2017594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
