dbus 1.14.10-3ubuntu1 source package in Ubuntu
Changelog
dbus (1.14.10-3ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2045668). Remaining changes: - Add aa-get-connection-apparmor-security-context.patch: This is not intended for upstream inclusion. It implements a bus method (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor security context but upstream D-Bus has recently added a generic way of getting a connection's security credentials (GetConnectionCredentials). Ubuntu should carry this patch until packages in the archive are moved over to the new, generic method of getting a connection's credentials. (LP #1489489). - Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit (LP #1438612) - Reworked to actually make dbus.service _and_ dbus.socket to not be part of the shutdown transaction. And yet make it possible to still stop/kill/restart dbus.service if one really wants to, because it is stuck and stopped responding to any commands. This allows allows to restart dbus.service with needrestart. However a finalrd hook might still be needed, to kill dbus-daemon for good, once we pivot off rootfs. - Reworked to avoid a deadlock during boot (LP #1936948) - debian/dbus.postinst, debian/rules: Don't start D-Bus on package installation, as that doesn't work any more with dont-stop-dbus.patch. Instead, start dbus.socket in postinst, which will then start D-Bus on demand after package installation. - Prevent dbus from being restarted on upgrade (LP #1962036) * Drop dependency on usr-is-merged; this transition is long completed in Ubuntu. dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Olivier Gayot <email address hidden> Tue, 05 Dec 2023 16:36:45 +0100
Upload details
- Uploaded by:
- Olivier Gayot
- Sponsored by:
- Simon Quigley
- Uploaded to:
- Noble
- Original maintainer:
- Ubuntu Developers
- Architectures:
- any all
- Section:
- devel
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
dbus_1.14.10.orig.tar.xz | 1.3 MiB | ba1f21d2bd9d339da2d4aa8780c09df32fea87998b73da24f49ab9df1e36a50f |
dbus_1.14.10.orig.tar.xz.asc | 833 bytes | 5f292cd0603c3d736026ed3f4d1c1937847981669c1f0a389083518f013e1081 |
dbus_1.14.10-3ubuntu1.debian.tar.xz | 67.7 KiB | a99f42886bcdab475933328dbc283d37bf3d01e774240cbe5e8b3a28c319227c |
dbus_1.14.10-3ubuntu1.dsc | 3.7 KiB | 8731779f44f82972d23c87b108f55c1432a697d8bf4b21e32394edf2e6989829 |
Available diffs
Binary packages built by this source
- dbus: simple interprocess messaging system (system message bus)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
D-Bus supports broadcast messages, asynchronous messages (thus
decreasing latency), authentication, and more. It is designed to be
low-overhead; messages are sent using a binary protocol, not using
XML. D-Bus also supports a method call mapping for its messages, but
it is not required; this makes using the system quite simple.
.
It comes with several bindings, including GLib, Python, Qt and Java.
.
This package provides a fully-functional D-Bus system bus with activation
support, used for communication between system services, and depends on
most of the other components of the reference implementation of D-Bus.
.
To provide a complete D-Bus session bus, install one of the packages
that implement the dbus-session-bus virtual package, such as
dbus-user-session. The recommended implementation is indicated by
the default-dbus-session- bus virtual package.
- dbus-1-doc: simple interprocess messaging system (documentation)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains the API documentation for D-Bus, as well as
the protocol specification.
.
See the dbus description for more information about D-Bus in general.
- dbus-bin: simple interprocess messaging system (command line utilities)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains the D-Bus command-line utilities such as dbus-send
and dbus-monitor.
- dbus-bin-dbgsym: debug symbols for dbus-bin
- dbus-daemon: simple interprocess messaging system (reference message bus)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains dbus-daemon, the reference implementation of a
D-Bus message bus, and dbus-run-session, a utility to start a temporary
session dbus-daemon in a constrained environment or for automated tests.
.
To provide a complete D-Bus session bus, install one of the packages
that implement the dbus-session-bus virtual package, such as
dbus-user-session. The recommended implementation is indicated by
the default-dbus-session- bus virtual package.
- dbus-daemon-dbgsym: debug symbols for dbus-daemon
- dbus-dbgsym: debug symbols for dbus
- dbus-session-bus-common: simple interprocess messaging system (session bus configuration)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains the configuration files defining the behaviour of
the D-Bus session bus, used for applications and per-user services.
These are used by the reference implementation in the dbus package,
and by the reimplementation in the dbus-broker package.
.
To provide a complete D-Bus session bus, install one of the packages
that implement the dbus-session-bus virtual package, such as
dbus-user-session. The recommended implementation is indicated by
the default-dbus-session- bus virtual package.
- dbus-system-bus-common: simple interprocess messaging system (system bus configuration)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains the configuration files defining the behaviour of
the D-Bus system bus, used for system services such as networking and
storage management services. It is also responsible for creating the
'messagebus' system user account used to run the system bus.
These are used by the reference implementation in the dbus package,
and by the reimplementation in the dbus-broker package.
.
To provide a complete D-Bus system bus, install one of the packages
that implement the dbus-system-bus virtual package, such as dbus.
The recommended implementation is indicated by the default-dbus-system- bus
virtual package.
- dbus-tests: simple interprocess messaging system (test infrastructure)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package provides automated and manual tests for D-Bus, and the
dbus-test-tool utility. It also provides copies of the D-Bus libraries and
executables compiled with extra debug information and logging.
.
See the dbus package description for more information about D-Bus in general.
- dbus-tests-dbgsym: debug symbols for dbus-tests
- dbus-user-session: simple interprocess messaging system (systemd --user integration)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
On systemd systems, this package opts in to the session model in which
a user's session starts the first time they log in, and does not end
until all their login sessions have ended. This model merges all
parallel non-graphical login sessions (text mode, ssh, cron, etc.), and up
to one graphical session, into a single "user-session" or "super-session"
within which all background D-Bus services are shared.
.
Multiple graphical sessions per user are not currently supported in this
mode; as a result, it is particularly suitable for gdm, which responds to
requests to open a parallel graphical session by switching to the existing
graphical session and unlocking it.
.
To retain dbus' traditional session semantics, in which login sessions
are artificially isolated from each other, remove this package and install
dbus-x11 instead.
.
See the dbus package description for more information about D-Bus in general.
- dbus-x11: simple interprocess messaging system (X11 deps)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
This package contains the dbus-launch utility, which automatically
launches one D-Bus session bus per X11 display per user. If the
dbus-user-session package is also installed, it takes precedence over
this package.
.
See the dbus description for more information about D-Bus in general.
- dbus-x11-dbgsym: debug symbols for dbus-x11
- libdbus-1-3: simple interprocess messaging system (library)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
D-Bus supports broadcast messages, asynchronous messages (thus
decreasing latency), authentication, and more. It is designed to be
low-overhead; messages are sent using a binary protocol, not using
XML. D-Bus also supports a method call mapping for its messages, but
it is not required; this makes using the system quite simple.
.
It comes with several bindings, including GLib, Python, Qt and Java.
.
The message bus daemon can be found in the dbus-daemon package.
- libdbus-1-3-dbgsym: debug symbols for libdbus-1-3
- libdbus-1-dev: simple interprocess messaging system (development headers)
D-Bus is a message bus, used for sending messages between applications.
Conceptually, it fits somewhere in between raw sockets and CORBA in
terms of complexity.
.
See the dbus description for more information about D-Bus in general.