Please merge dbus 1.14.6-1 (main) from debian unstable (main)

Bug #2023301 reported by Olivier Gayot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Debian has dbus 1.14.6-1 in unstable
Ubuntu has dbus 1.14.4-1ubuntu1 in mantic

Two changes from @waveform have been merged upstream and the relevant delta can be dropped in Ubuntu.

 - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
   autopkgtest to the apparmor profile in the test
   [merged upstream in 1.14.6]
- d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
   packages to permit the resolver to use them to satisfy i386 dependencies
   [merged in debian in 1.14.6-1]

Related branches

Olivier Gayot (ogayot)
Changed in dbus (Ubuntu):
assignee: nobody → Olivier Gayot (ogayot)
status: New → In Progress
Olivier Gayot (ogayot)
description: updated
Olivier Gayot (ogayot)
Changed in dbus (Ubuntu):
status: In Progress → New
assignee: Olivier Gayot (ogayot) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dbus - 1.14.6-1ubuntu1

---------------
dbus (1.14.6-1ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable (LP: #2023301). 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.
    - Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit.
    - Rework ubuntu/dont-stop-dbus.patch 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.
    - Rework d/p/ubuntu/dont-stop-dbus.patch 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)
    - git configuration changes for Ubuntu (d/gbp.conf, d/.gitignore)
  * Removed obsoleted patches:
    - d/p/u/concrete-dbus-socket.patch: Add the "real" path used by the apparmor
      autopkgtest to the apparmor profile in the test
      [merged upstream in 1.14.6]
    - d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
      packages to permit the resolver to use them to satisfy i386 dependencies
      [merged in debian in 1.14.6-1]

dbus (1.14.6-1) unstable; urgency=medium

  * New upstream stable release
    - Fixes a denial of service issue that is not relevant for the way
      we compile dbus in Debian
  * d/copyright: Update
  * Standards-Version: 4.6.2 (no changes required)
  * d/control: Mark dbus-*-bus-common as Multi-Arch: foreign.
    Thanks to Dave Jones / Ubuntu
  * d/upstream/metadata: Update Gitlab URLs to preferred format
  * Drop migration path from very old debug symbol packages
  * Avoid explicitly specifying -Wl,--as-needed linker flag,
    which is the default with Debian 12 toolchains
  * Remove version constraints unnecessary since Debian 10

 -- Olivier Gayot <email address hidden> Thu, 08 Jun 2023 17:46:03 +0200

Changed in dbus (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.