reopen 1056980 severity 1056980 serious tags 1056980 patch thanks Hello,
Reopening this bug due to a deliberate attempt to fool the users: Either you move binaries _and_ configuration files to /usr/bin or explicitely depend on usrmerge. And closing this bug as wontfix is not nice. I've modified netcat-traditional.postinst on both usrmerged and non-usrmerged systems without problems. So your second comment b) in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056980#15 is definitely false: From: Chris Hofstaedtler <[z...@debian.org](mailto:z...@debian.org)> ... No, changing the update-alternatives call is a) not necessary on /usr-merged systems, b) will break on these. No the system did not break! Yes, I have read [https://wiki.debian.org/UsrMerge](https://wiki.debian.org/UsrMerge) And found: ! Please suspend further moves temporarily. The effects of moves cause more problems than anticipated people are working to understand and solve them. Exceptions: Continue to perform moves that fix RC bugs (e.g. dh_installsystemd or systemd.pc issues) and DEP17P7 mitigations for udev rules. And: Do not update calls to update-alternatives: - Even if you move e.g. /bin/more to /usr/bin/more, do not change the location used in the update-alternatives invocation. - If you add new alternatives, install them to /usr if possible. And: P4: Even when changing all aliased paths from / to /usr, you must not change the paths passed to update-alternatives invocations that already existed in bookworm. The current plan is to keep existing alternatives aliased as a legacy forever and add new alternatives without aliasing. Who wrote this? The question is why?? All changes to packages moving files to /usr should also move _all_ corresponding configuration files to, or add an explicit dependency on usrmerge! Thanks!
