The only functional difference of between the stable 1.4.16 and 1.4.16-r2 is correct handling of /etc/machine-id on startup (dbus-uuidgen), and removal of keepdir /var/run/dbus. So it makes sense to stabilize -r2, because without the dbus-uuidgen fix, /var/lib/dbus/machine-id is created on dbus startup, and it is the file that is used by dbus if it exists. As a side note, it is also possible to patch dbus to use /etc/machine-id by default (grep for DBUS_MACHINE_UUID_FILE).
It's not that simple; need to verify ibus, dbus, and pulseaudio has been stabilized with the correct searchpath. And I wanted to skip 1.4.16-r2 entirely and go for 1.4.18. So thanks for reporting, but this is really unrequired at this stage.
Regarding latest emul packages prepared to be compatible with this dbus changes, feel free to call its stabilization when you want ;)
Please test and mark stable: =sys-apps/dbus-1.4.18 alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86 =dev-python/dbus-python-1.0.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86
Stable for HPPA.
amd64; apart from a test fail by dbus-python, all looks ok.
Created attachment 304099 [details] failed_test_mixed_hardened_gcc amd64 hardened mixed: builds, runs ok, test fails though (gcc-4.7:hardened-dev, mixed tree machine, build log && emerge --info incl)
amd64/ppc/ppc64 stable
x86 stable
arm stable
dbus stabilization has been moved to bug 412535, so this bug is only for stabilizing dbus-python-1.0.0 now
Any news? A new bug gets opened soon for another incompatible version set of dbus. Would be nice to get these latest from the old ones stable first.
ia64 stable
alpha/ia64/sh/sparc stable