Your message dated Thu, 5 Feb 2026 16:55:33 +0100
with message-id <[email protected]>
and subject line Re: progress-linux-container: directly Depends on dbus
has caused the Debian Bug report #1122699,
regarding progress-linux-container: directly Depends on dbus
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.)
--
1122699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122699
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: progress-linux-container
Severity: normal
Tags: forky sid
User: [email protected]
Usertags: direct-dbus-dependency
This package has a direct Depends on the dbus package, which prevents it
from being used with the non-default dbus-broker package providing the
system bus.
For details of how to replace this dependency, please see:
https://salsa.debian.org/utopia-team/dbus/-/blob/debian/unstable/debian/replacing-dbus-dependency.txt?ref_type=heads
Given the purpose of this package, I'm guessing the intention of this
dependency is "this package needs a working system bus", similar to
polkitd or network-manager. If that's the case, please replace the
dependency on dbus with:
default-dbus-system-bus | dbus-system-bus
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Hi,
Analog to bfh-metapackages' #1122547, progress-linux-container on
purpose depends on the dbus reference implementation, for the time being
(wrt/ nspawn), we don't want it to use any other dbus implementation.
Regards,
Daniel
--- End Message ---
