Control: reopen 960564 > * d/tests/: > - Add condition check to start/stop dbus only if it is not started. > (Closes: #960564)
That doesn't resolve the issue I described: > On Ubuntu, the "service dbus start" doesn't work. > > | # service dbus start > | Failed to start dbus.service: Operation refused, unit dbus.service may be > requested by dependency only (it is configured to refuse manual start/stop). > | See system logs and 'systemctl status dbus.service' for details. > | > | # cat /lib/systemd/system/dbus.service > | [Unit] > | Description=D-Bus System Message Bus > | Documentation=man:dbus-daemon(1) > | Requires=dbus.socket > | # we don't properly stop D-Bus (see ExecStop=), thus disallow restart > | RefuseManualStart=yes > | > | [Service] > | ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork > --nopidfile --systemd-activation --syslog-only > | ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call > --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig > | ExecStop=/bin/true > | KillMode=none > | OOMScoreAdjust=-900 > > What you can safely do is systemctl start dbus.socket, which will ensure > that DBus starts, and is running. > > Stopping DBus is almost never a good idea, so the test probably > shouldn't do that. If it did, it should declare the isolation-container > restriction. This is still true after -2: "service dbus start" won't work on Ubuntu. That's not necessarily a bug that you need to care about as a Debian maintainer. But if you want your package available in Ubuntu, it helps to write autopkgtests that work there, or Ubuntu will have to fork your package. Failures: http://autopkgtest.ubuntu.com/packages/u/usbauth/focal/amd64 SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
