dbus 1.10.18-1ubuntu2 source package in Ubuntu

Changelog

dbus (1.10.18-1ubuntu2) artful; urgency=medium

  * Restore accidentally dropped debian/rules modification
    to not start D-Bus on package installation

dbus (1.10.18-1ubuntu1) artful; urgency=medium

  * Sync with Debian. Remaining changes:
    - Clean up /etc/init/dbus.conf on upgrades. This needs to be kept until
      after 18.04 LTS.
    - Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit
      (see patch header and upstream bug for details). Fixes various
      causes of shutdown hangs, particularly with remote file systems.
      (LP: #1438612) (LP: #1540282)
    - 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.
  * Dropped changes:
    - make-uid-0-immune-to-timeout.patch: Applied in new release
    - debian/dbus.user-session.upstart

dbus (1.10.18-1) unstable; urgency=medium

  * New upstream stable release
    - On SELinux systems, make sure the thread that reads AVC
      notifications retains the ability to write the audit log
      (Closes: #857660)
    - Fix a read overflow and some memory leaks in a unit test
      (no effect on production systems)

dbus (1.10.16-1) unstable; urgency=medium

  * New upstream release
    - Contains a security fix for a potential symlink attack in the
      nonce-tcp transport. That transport is not normally used (or
      recommended) on Unix.

dbus (1.10.14-1) unstable; urgency=medium

  * New upstream release

dbus (1.10.12-1) unstable; urgency=medium

  * New upstream release
  * d/p/backports/Replace-DBUS_USE_TEST_BINARY-with-DBUS_TEST_DBUS_LAUNCH.patch:
    backport a change from 1.11.2 to make the debug build of libdbus
    reproducible under varying build paths
  * Move Debian-specific patches to debian/patches/debian (corresponding
    to "Gbp-pq: Topic debian" on the patch queue branch)
  * debian/*.lintian-overrides:
    - override systemd-service-file-missing-install-key for dbus.service,
      which is intentionally statically enabled
    - override embedded-javascript-library for Doxygen's jquery.js,
      which is not actually libjs-jquery (see #736360)
  * Move to debhelper compat level 10
    - drop options and overrides that are now the default

dbus (1.10.10-1) unstable; urgency=medium

  * New upstream stable release 1.10.10
  * Provide new virtual packages for other packages to depend on:
    - dbus-session-bus: any implementation of the D-Bus well-known session bus
      (provided by: dbus-user-session, dbus-x11)
    - default-dbus-session-bus: the recommended implementation of
      dbus-session-bus (currently provided by: dbus-user-session)
  * Add arm64, mips64el, ppc64el to the list of architectures that
    have valgrind
  * debian/gbp.conf: use DEP-14 branch names
  * Standards-Version: 3.9.8 (no changes needed)
  * debian/rules: fail the build if "make install" installs anything we
    don't package or delete. Only do this for final releases (suite
    in debian/changelog is not UNRELEASED) to facilitate future
    autobuilding of new upstream releases.
  * debian/rules: do not require symbols file to be complete if the
    suite in debian/changelog is UNRELEASED, again to facilitate
    autobuilding new upstream releases.
  * debian/source/options: don't fail dpkg-source on changes to
    build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
    and during a snapshot build they might become symlinks.
  * debian/rules: do the build in debian/build-* so it's easier to .gitignore
  * debian/.gitignore: update
  * Use the correct systemctl for Debian even if not installed on the build
    system. (Regression in 1.10.2)

 -- Jeremy Bicha <email address hidden>  Sun, 18 Jun 2017 21:44:39 -0400