12/14/2006

Correcting the incorrectness of the GWN

Cardoe wrote this mid-afternoon:

So this week’s GWN was published with info about D-Bus, however no one ever mentioned anything to me about it. The first and only notice of it I received in e-mail was on 12/12 but this is from 12/11. For those that say it was published 12/13, Ok fine. But I was already off the computer by the 12/12 notice and didn’t receive it until 12/13 and I did reply back with some fixes which did not make it to print. I can’t speak for when steev saw the GWN, but as far as I’m concerned neither of us knew in time to catch this.
So here we go with the list:

  1. sys-apps/dbus-1.0.1-r2 was released with more then just ~amd64. It was released as ~arch to all arches that had were on sys-apps/dbus-0.62-r1. Which was every arch except m68k, mips, ppc-macos, sparc-fbsd, and x86-fbsd. However x86-fbsd was added since D-Bus now supports FreeBSD properly in the 1.0.x series. mips has since been added as well.
  2. A security issue was published on 12/12 about D-Bus and consequently 1.0.2 was released. The 1.0.1 ebuilds were removed and only 1.0.2 is available so the article was already out of date before it’s official publishing. The security fix has also been backported to sys-apps/dbus-0.62-r2, which most arches have marked stable.
  3. Do not emerge all the binding packages, every package out there is suppose to depend on the specific binding package that you need. If it does not, there was a bug created for this, bug #154521.
  4. There was no “radical” shift in the API. APIs that have been marked deprecated since 0.30 were finally removed for the release. Applications that were 100% API proper with 0.62 will work 100%. Only problem comes with applications that were not coded properly, yes HAL is one of those apps. The exception being Mono based apps where the bindings are different, however most packages that are being maintained upstream have been updated to use the new bindings. Bugs have been created in Bugzilla in all these instances, however most Gentoo maintainers have not corrected the issue.
  5. Learn to run revdep-rebuild when the einfo/elog/ewarn tells you to run it. Also, read the possible parameters you can pass to revdep-rebuild. -x allows for new versions of pre-existing packages. Some packages might have rev-bumps for the new D-Bus and you’ll need to pull those new versions down. Also, some USE flags might have changed. Use the -v option. And lastly, toss a -a on there so you can review what it’s about to do. All in all, revdep-rebuild -avx is probably what you’re looking for.
  6. Yes, for GNOME users there are a lot of packages to recompile. This is because gnome-vfs depends on D-Bus and most GNOME applications link in gnome-vfs. This is what makes –as-needed so attractive. That and getting GNOME to stop linking in D-Bus when the application that’s linking it in doesn’t even use D-Bus, it uses gnome-vfs.

And lastly as a final wrap up, D-Bus 1.0.x will be the new and only supported version shortly after the New Year, once the 1.0.x has been cooking in the Portage tree for 30 days.

* Filed under: General, Gentopia, Linux

Leave a Reply