dbus 1.12.20-2ubuntu1 source package in Ubuntu

Changelog

dbus (1.12.20-2ubuntu1) impish; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
    - Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit.
    - 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.
    - 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.
    - Make autopkgtests cross-test-friendly.
    - 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.

dbus (1.12.20-2) unstable; urgency=medium

  * Add Provides for the split binary packages added in experimental.
    Actually splitting up dbus seems too risky for this stage in the
    release process, but if we add them as virtual packages in Debian 11,
    then switching dependencies during the Debian 12 cycle won't require
    alternative dependencies or a flag-day transition.
  * dbus-tests: Silence Lintian warnings for breakout-link
  * Remove unnecessary Readme.txt from sha1 test data.
    This causes Lintian warnings because it isn't UTF-8, and it isn't
    actually useful.
  * Standards-Version: 4.5.1 (no changes required)

 -- Balint Reczey <email address hidden>  Tue, 18 May 2021 10:59:54 +0200