Bug#930105: systemd: prerm fail breaks apt and renders system hard to recover

On Fri, Jun 07, 2019 at 01:07:56AM +0200, Michael Biebl wrote: > Control: severity -1 normal > > Am 07.06.19 um 00:55 schrieb Adam Borowski: > > Severity: critical > > Justification: breaks the whole system > > When trying to switch to any other init system (and d-i offers no way to > > start

systemd_241-5~bpo9+1_source.changes ACCEPTED into stretch-backports->backports-policy

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 07 Jun 2019 22:51:26 +0200 Source: systemd Architecture: source Version: 241-5~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Michael Biebl Closes:

Processed: tagging 929116

Processing commands for cont...@bugs.debian.org: > tags 929116 - pending Bug #929116 [src:systemd] systemd: CVE-2018-20839 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 929116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929116

Processing of systemd_241-5~bpo9+1_source.changes

systemd_241-5~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_241-5~bpo9+1.dsc systemd_241-5~bpo9+1.debian.tar.xz systemd_241-5~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: Bug#929116 marked as pending in systemd

Processing control commands: > tag -1 pending Bug #929116 [src:systemd] systemd: CVE-2018-20839 Added tag(s) pending. -- 929116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#918606: marked as done (systemd: Missing portablectl and portabled in systemd 239+)

Your message dated Fri, 07 Jun 2019 21:03:44 + with message-id and subject line Bug#918606: fixed in systemd 242-2 has caused the Debian Bug report #918606, regarding systemd: Missing portablectl and portabled in systemd 239+ to be marked as done. This means that you claim that the problem

systemd_242-2_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 07 Jun 2019 22:41:50 +0200 Source: systemd Architecture: source Version: 242-2 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Michael Biebl Closes: 918606 Changes:

Processing of systemd_242-2_source.changes

systemd_242-2_source.changes uploaded successfully to localhost along with the files: systemd_242-2.dsc systemd_242-2.debian.tar.xz systemd_242-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'

Control: tags -1 + moreinfo Am 07.06.19 um 15:51 schrieb J. Pfennig: > The man page of telinit/init says (for 'telinit N'): > >Change the SysV runlevel. This is translated into an activation request > for runlevel2.target, >runlevel3.target, ... and is equivalent to systemctl isolate >

Processed: Re: Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'

Processing control commands: > tags -1 + moreinfo Bug #930120 [systemd-sysv] init: Documentation error for telinit/init - does not use 'systemctl isolate xxx' Added tag(s) moreinfo. -- 930120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930120 Debian Bug Tracking System Contact

Processed: reassign 930120 to systemd-sysv

Processing commands for cont...@bugs.debian.org: > reassign 930120 systemd-sysv Bug #930120 [init] init: Documentation error for telinit/init - does not use 'systemctl isolate xxx' Bug reassigned from package 'init' to 'systemd-sysv'. No longer marked as found in versions

Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'

Package: init Version: 1.56+nmu1 Severity: minor Tags: upstream Dear Maintainer, The man page of telinit/init says (for 'telinit N'): Change the SysV runlevel. This is translated into an activation request for runlevel2.target, runlevel3.target, ... and is equivalent to systemctl isolate