On Wed, Sep 21, 2022 at 08:32:53AM +0200, Helmut Grohne wrote: > On Wed, Sep 21, 2022 at 10:41:18AM +1000, Craig Sanders wrote: > > Stop closing this bug without fixing it. > > The change you are objecting to was planned and presented to various > teams in Debian including the technical committee and the release team.
This bug report is ABOUT A BROKEN PACKAGE that causes apt upgrade and apt dist-upgrade etc to fail. IT IS NOT ABOUT THE USR MERGE DECISION. THAT IS ANOTHER ISSUE ENTIRELY - IT HAPPENS TO BE THE ULTIMATE CAUSE OF THE BUG BEING CREATED BUT THE BUG IS SEPARATE AND CAN BE FIXED WITHOUT REVISITING ANY DECISIONS. I'M NOT EXPECTING ANYONE TO REVERSE THE DECISION. JUST FIX THE FUCKING PACKAGE SO IT DOESN'T BREAK APT. > The change is implementing a technical committee decision and has been > agreed to by the technical committee and the release team. You should be > able to find the rationale in the relevant technical committee bug > reports. If you want to change this, please file your objection with the > technical committee or start a GR instead of reopening this bug over and > over again. The technical committee decision does not mandate an incompetent implementation that breaks apt. No matter how fucked up and stupid the decision was, it is possible to implement it without breaking apt. > > It is breaking upgrades and dist-upgrades etc. > > As others have pointed out, this is breaking on your side, because These "others" you mention are making shit up because they don't want to even investigate the problem, let alone fix it. As I have pointed out several times now, THIS IS **NOT** SOMETHING JUST HAPPENING ON MY SIDE DUE TO SOME ODDITY WITH MY SYSTEMS' CONFIGURATIONS. MY SYSTEMS ARE NOT MISCONFIGURED. THE BUG OCCURS ON STANDARD DEBIAN SID VMS. IF YOU THINK I AM WRONG, THEN DO SOME TESTING TO CONFIRM OR DISPROVE IT YOURSELF. > usrmerge is somehow prevented from being installable. Please figure out > why that happens. I suppose the most likely cause would be use of > dpkg-fsys-usrunmess. Refer to the new faq entry at > https://wiki.debian.org/UsrMerge on how to revert that. I have never run anything like that, so there is nothing to revert. I was barely even aware of this usr merge bullshit happening because it is not important to me. The ONLY reason I'm aware of it now is because, during a routing dist-upgrade, init-system-helpers 1.65.2 broke upgrades on several of my systems, breakage which was only fixable by reverting to 1.64. AS WAS DESCRIBED IN MY INITIAL BUG REPORT. craig -- craig sanders <c...@taz.net.au>
