Please merge dbus 1.8.6-1 (main) from Debian testing (main)

This merge is useful because it brings us much closer to the Debian
package. Some notable changes with the new package:

 - Adds autopkgtests for dbus
   + Previously disabled Build-Depends used for testing are now enabled
 - A new dbus-run-session program that allows one to start a new session
   and run a program in that session
 - Built against libaudit, so system bus AppArmor denials will go to the
   audit log if auditd is installed and running
   + Otherwise, all AppArmor denials will continue going to the syslog
   + All session bus denials will continue to go to the syslog due to
     the session bus not having sufficient privs to write to the audit
     log
 - There's a new org.freedesktop.DBus.GetConnectionCredentials bus
   method that provides a single call to get all of the credentials for
   a connection.
 - I refreshed the AppArmor mediation patches using the v3 patches from
   the upstream bug
   + https://bugs.freedesktop.org/show_bug.cgi?id=75113
   + I think these are fairly close to going in upstream so I hope we
     won't have to carry them much longer
   + These patches include support for sticking the AppArmor confinement
     context in the return value of
     org.freedesktop.DBus.GetConnectionCredentials
 - The upstream NEWS file has all of the gory details
   + http://dbus.freedesktop.org/doc/NEWS

I've tested this debdiff in the following ways:
 - Running QRT's test-dbus.py script in a clean Utopic amd64 VM
 - Running the new autopkgtests in a clean Utopic amd64 schroot
 - Manual exploratory testing in a clean Utopic amd64 VM

I've subscribed ubuntu-sponsors. I expect that this will need landing coordination for Touch. Unfortunately, I won't be around next week to help with that process but I'll be able to help the week of May 26th.

Thanks, I uploaded to ppa:ubuntu-desktop/ppa for testing. Haven't reviewed the diff just yet but people having a go is welcome.

Tyler, is there anything blocking that one? Do you want to get more feedback before uploading?

Nothing is blocking this. After attaching the debdiff, I got busy with other things. I need to refresh the debdiff (there have been some upstream security releases) and then take it through a silo next week. Thanks for the reminder!

There is 1.8.6-1 already available in unstable. Would be nice to get it since it contains CVE fixes.

(unsubscribing sponsors, that doesn't seem ready for sponsoring/needs to be rebased)

I want to move to this - Tyler, is there any chance you could look at the merge this week or next? I'd like to get us on D-Bus 1.8 before Feature Freeze.

Hello Iain. I'll start working on this merge now. tvoss also asked for it this week.

Update dbus should solves also latest cjs fail to build.

On Wed, Aug 13, 2014 at 03:47:23PM -0000, Tyler Hicks wrote:
> Hello Iain. I'll start working on this merge now. tvoss also asked for
> it this week.

By the way, I just spoke to Simon McVittie (dbus upstream). He said that
he'd be open to accepting the apparmor mediation patches if you forward
them to him. I think you should do that.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

@laney: The patches have already been submitted and reviewed upstream here:

https://bugs.freedesktop.org/show_bug.cgi?id=75113

On Thu, Aug 14, 2014 at 12:09:33PM -0000, Marc Deslauriers wrote:
> @laney: The patches have already been submitted and reviewed upstream
> here:

Ta. I guess he forgot so I pointed him at that bug again.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Here's a tested debdiff. I've been running it on my amd64 Utopic laptop for 48
hours without issue and I've ran the following tests in an amd64 Utopic VM:

 * test-dbus.py from lp:qa-regression-testing
 * test-apparmor.py from lp:qa-regression-testing

I tried to test in the i386 ubuntu-emulator but the emulator isn't stable for
me with or without the updated dbus packages. However, I was able to verify
that the emulator will boot to the homescreen without any issues.

Unfortunately, I don't have any real testing hardware that runs the system
image.

I'll need a sponsor for this upload so I'll be unassigning myself and
subscribing ubuntu-sponsors.

I'm currently running that version on my work system which is i386/utopic/unity and didn't notice any issue, +1 from me for upload

I'm going to review/upload but I'll block it in proposed for a couple of hours to do some phone testing

Thanks, Iain and Seb! I've still had no issues while running this merged dbus version on my work laptop daily.

I am now running the -proposed d-bus packages on my amd64 laptop under upstart and systemd. No problems.

that was uploaded, unsubscribing sponsors

Fire ze missiles.

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

---------------
dbus (1.8.6-1ubuntu1) utopic; urgency=low

  * Resynchronize on Debian testing (LP: #1320422). Remaining Ubuntu changes:
    - Install binaries into / rather than /usr:
      + debian/rules: Set --exec-prefix=/
      + debian/dbus.install, debian/dbus-x11.install: Install from /bin
    - Use upstart to start:
      + Add debian/dbus.upstart and dbus.user-session.upstart
      + debian/dbus.postinst: Use upstart call instead of invoking the init.d
        script for checking if we are already running.
      + debian/control: versioned dependency on netbase that emits the new
        deconfiguring-networking event used in upstart script.
    - 20_system_conf_limit.patch: Increase max_match_rules_per_connection for
      the system bus to 5000 (LP #454093)
    - 81-session.conf-timeout.patch: Raise the service startup timeout from 25
      to 60 seconds. It may be too short on the live CD with slow machines.
    - debian/dbus.user-session.upstart, debian/rules: Communicate session bus
      to Upstart Session Init to avoid potential out-of-memory scenario
      triggered by Upstart clients that do not run main loops
      (LP: #1235649, LP: #1252317).
    - debian/control, debian/rules: Build against libapparmor for AppArmor
      D-Bus mediation
    - debian/control: Use logind for session tracking, so that "at_console"
      policies work with logind instead of ConsoleKit. Add "libpam-systemd"
      recommends.
    - debian/rules: Adjust dbus-send path to our changed install layout.
      (LP: #1325364)
    - debian/dbus-Xsession: Don't start a session bus if there already is one,
      i. e. $DBUS_SESSION_BUS_ADDRESS is already set. (Closes: #681241)
  * Dropped changes:
    - debian/control: Drop version bump on the libglib2.0-dev Build-Depends.
      It is no longer needed.
    - debian/control: use "Breaks: unity-services (<< 6.0.0-0ubuntu6)", the
      new dbus eavedropping protection was creating issues with previous
      versions. This can be dropped now since upgrades from Quantal are no
      longer a concern.
    - debian/control, debian/rules: The tests are not run during the build.
      Configure with --disable-tests, drop the build dependencies needed for
      the tests. The tests should now run with the debug build using
      autopkgtest.
    - 00git_logind_check.patch: Fix logind check. This change is present in
      upstream dbus.
    - Add 00git_sd_daemon_update.patch: Update to current sytemd upstream
      sd_booted() to actually check for systemd init. This change is present
      in upstream dbus.
    - debian/patches/aa-build-tools.patch, debian/patches/aa-mediation.patch,
      debian/patches/aa-mediate-eavesdropping.patch: Drop these patches in
      favor of the latest set of patches submitted for upstream inclusion
    - debian/patches/02_obsolete_g_thread_api.patch: This change is present in
      upstream dbus
    - 0001-activation-allow-for-more-variation-than-just-system.patch,
      0002-bus-change-systemd-activation-to-activation-systemd.patch,
      0003-upstart-add-upstart-as-a-possible-activation-type.patch,
      0004-upstart-add-U...