Your message dated Thu, 13 Oct 2016 11:25:26 +0100 with message-id <20161013102526.5elk5en4yei4l...@perpetual.pseudorandom.co.uk> and subject line Re: Bug#840504: dbus: installation from chroot/systemd-nspawn fails has caused the Debian Bug report #840504, regarding dbus: installation from chroot/systemd-nspawn fails 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 ow...@bugs.debian.org immediately.) -- 840504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dbus Version: 1.8.20-0+deb8u1 Severity: normal Dear Maintainer, I'm currently trying to install dbus in a freshly debootstrapped directory with the following command: $ systemd-nspawn --bind /usr/bin/qemu-arm-static -D "./" /bin/bash -c "export DEBIAN_FRONTEND=noninteractive; apt-get install -y task-desktop" Unfortunately this fails with the following message: ~~~~~ [...] Setting up libsmbclient:amd64 (2:4.4.5+dfsg-3+b1) ... Setting up network-manager (1.4.2-1+b1) ... invoke-rc.d: could not determine current runlevel Reloading system message bus config...Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "force-reload" failed. invoke-rc.d: could not determine current runlevel Processing triggers for libc-bin (2.24-3) ... [...] ~~~~~ Moreover, dpkg is left in a broken state: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Which is only fixable with this command in a fully booted system as otherwise the same dbus reload issue happens again. Would it be possible to just skip the reload part if it wasn't possible to determine the current runlevel? Regards, Linus -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dbus depends on: ii adduser 3.113+nmu3 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-18+deb8u6 ii libcap-ng0 0.7.4-2 ii libdbus-1-3 1.8.20-0+deb8u1 ii libexpat1 2.1.0-6+deb8u3 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u5 ii lsb-base 4.1+Debian13+nmu1 dbus recommends no packages. Versions of packages dbus suggests: pn dbus-x11 <none> Versions of packages dbus is related to: pn dbus-x11 <none> ii systemd 215-17+deb8u5 ii systemd-sysv 215-17+deb8u5 -- no debconf information
--- End Message ---
--- Begin Message ---On Wed, 12 Oct 2016 at 11:59:10 +0200, linus.luess...@c0d3.blue wrote: > Setting up network-manager (1.4.2-1+b1) ... > invoke-rc.d: could not determine current runlevel > Reloading system message bus config...Failed to open connection to "system" > message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No > such file or directory > invoke-rc.d: initscript dbus, action "force-reload" failed. > invoke-rc.d: could not determine current runlevel This is network-manager.postinst asking the dbus-daemon to reload its configuration: if [ -x "/etc/init.d/dbus" ]; then invoke-rc.d dbus force-reload || true fi It isn't dbus' choice to do this at this point. I think it's correct that invoke-rc.d dbus force-reload fails when asked to do something it cannot do (reload the configuration of a dbus-daemon that isn't running). I think it's also correct that NetworkManager's postinst ignores that error. So everything seems to be OK here, except that invoke-rc.d is making it seem like a bigger issue than it really is. On Wed, 12 Oct 2016 at 13:41:18 +0200, Linus Lüssing wrote: > Sorry, this message does not seem to have put dpkg in a broken > state, just verified with another, new installation where this > message occures too, but dpkg is absolutely fine with it. Closing the bug as you requested. For your information, you can do this yourself by sending mail to NNNNNN-done at bugs.debian.org; if the bug was fixed by a change in a later package version, put "Version: 1.2-3" (or whatever is the correct version) in the first line of your mail to that address. S
--- End Message ---
