Your message dated Wed, 21 Sep 2022 09:58:37 +0200 with message-id <[email protected]> and subject line Re: Bug#1020290: closed by Ansgar <[email protected]> (Re: Bug#1020290: init-system-helpers depends on usrmerge | usr-is-merged) has caused the Debian Bug report #1020290, regarding init-system-helpers depends on usrmerge | usr-is-merged to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1020290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020290 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: init-system-helpers Version: 1.65.2 dist-upgrade was broken on four systems tonight due to: Depends: usrmerge | usr-is-merged This effectively makes these packages Essential by stealth. Debian's usrmerge FAQ says: * Is it mandatory to install this package? No. All four systems (3 running systemd, one running sysvinit - because systemd is incapable of booting this machine) gave the following error message and aborted the upgrade: Selecting previously unselected package usr-is-merged. Preparing to unpack .../01-usr-is-merged_30+nmu1_all.deb ... ****************************************************************************** * * The usr-is-merged package cannot be installed because this system does * not have a merged /usr. * * Please install the usrmerge package to convert this system to merged-/usr. * * For more information please read https://wiki.debian.org/UsrMerge. * ****************************************************************************** dpkg: error processing archive /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb (--unpack): new usr-is-merged package pre-installation script subprocess returned error exit status 1 . . . Errors were encountered while processing: /tmp/user/0/apt-dpkg-install-zRN5ON/01-usr-is-merged_30+nmu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This could only be fixed by reverting back to 1.64 and purging usr-is-merged, followed by 'apt-mark hold init-system-helpers' of course. This is an essential package. Why is it forcing this usr merge idiocy on me, even on systems that don't run systemd? what actual benefit does it provide? And WTF does forcing usrmerge have to do with init-system-helpers' purpose? How does forcing usrmerge qualify as a helper tool for switching between "all" init systems? Description-en: helper tools for all init systems This package contains helper tools that are necessary for switching between the various init systems that Debian contains (e. g. sysvinit or systemd). An example is deb-systemd-helper, a script that enables systemd unit files without depending on a running systemd. . It also includes the "service", "invoke-rc.d", and "update-rc.d" scripts which provide an abstraction for enabling, disabling, starting, and stopping services for all supported Debian init systems as specified by the policy. . While this package is maintained by pkg-systemd-maintainers, it is NOT specific to systemd at all. Maintainers of other init systems are welcome to include their helpers in this package. craig ps: I'm annoyed enough that this tried to install usr-is-merged and failed. I would have been furious if it had successfully installed usrmerge and irreversibly fucked with my filesystems without warning and especially without my CONSENT.
--- End Message ---
--- Begin Message ---Hi owner@, please stop Craig from further abusing the bug tracking system. Thanks, Ansgar On Wed, 2022-09-21 at 17:50 +1000, Craig Sanders wrote: > reopen 1020290 > severity 1020290 critical > stop > > > Please stop playing BTS ping-pong. > > STOP CLOSING BUG REPORTS WITHOUT FIXING THE PROBLEM. > > > Either way it looks like you misconfigured you apt sources as you > > said earlier: > > NO. I DID NOT MISCONFIGURE MY SYSTEM. I think you did. Even your caps key seems to not work correctly.
--- End Message ---
