Your message dated Thu, 11 Feb 2016 22:42:48 +0100
with message-id <[email protected]>
and subject line Re: systemd: systemctl 227 fails in chroots (instead of
ignoring)
has caused the Debian Bug report #802780,
regarding systemd: systemctl 227 fails in chroots (instead of ignoring)
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.)
--
802780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 227-2
Severity: normal
Dear Maintainers,
with 227-2 (not found in 226-2), systemctl behaves differently
in chroots for (at least) services that only provide a sysv init
script, breaking package install or removal:
226-2, jessie: Ignored, retval 0:
# root? systemctl restart non-existing.service
Running in chroot, ignoring request.
# root? systemctl restart wicd.service
Running in chroot, ignoring request.
227-2, sid: Fails, retval 6:
# root? systemctl restart non-existing.service
Failed to restart non-existing.service: Unit non-existing.service failed to
load: No such file or directory.
# root? systemctl restart non-existing.service
Failed to restart non-existing.service: Unit non-existing.service failed to
load: No such file or directory.
As systemctl is also run implicitely via invoke.rc.d on postinst
etc., this actually breaks package installation/removal on such
systems (one current example is the wicd package).
Fwiw, calling systemctl as /sbin/runlevel still works fine:
# root? /sbin/runlevel
Running in chroot, ignoring request.
Hth!
S
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-2
ii libapparmor1 2.10-2+b1
ii libaudit1 1:2.4.4-4
ii libblkid1 2.27-3
ii libc6 2.19-22
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.4-3
ii libkmod2 21-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27-3
ii libpam0g 1.1.8-3.1
ii libseccomp2 2.2.3-2
ii libselinux1 2.3-2+b1
ii libsystemd0 227-2
ii mount 2.27-3
ii sysv-rc 2.88dsf-59.2
ii udev 227-2
ii util-linux 2.27-3
Versions of packages systemd recommends:
ii dbus 1.10.0-3
ii libpam-systemd 227-2
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 23 Oct 2015 13:32:05 +0000 Stephan Suerken <[email protected]>
wrote:
> Package: systemd
> Version: 227-2
> Severity: normal
>
> Dear Maintainers,
>
> with 227-2 (not found in 226-2), systemctl behaves differently
> in chroots for (at least) services that only provide a sysv init
> script, breaking package install or removal:
>
> 226-2, jessie: Ignored, retval 0:
> # root? systemctl restart non-existing.service
> Running in chroot, ignoring request.
> # root? systemctl restart wicd.service
> Running in chroot, ignoring request.
>
> 227-2, sid: Fails, retval 6:
> # root? systemctl restart non-existing.service
> Failed to restart non-existing.service: Unit non-existing.service failed to
> load: No such file or directory.
> # root? systemctl restart non-existing.service
> Failed to restart non-existing.service: Unit non-existing.service failed to
> load: No such file or directory.
>
> As systemctl is also run implicitely via invoke.rc.d on postinst
> etc., this actually breaks package installation/removal on such
> systems (one current example is the wicd package).
>
> Fwiw, calling systemctl as /sbin/runlevel still works fine:
>
> # root? /sbin/runlevel
> Running in chroot, ignoring request.
>
This has been fixed upstream in v229 [1]
Closing the bug report.
Regards,
Michael
[1]
https://github.com/poettering/systemd/commit/1e726cc963016b91dfe3bb31319dec652f3b6f3a
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
