OK: I've uploaded bluez_4.9-0ubuntu1~ppa3 to the PPA. This returns the init script back to bluetooth.
Also: this switches the binary package names back to what we had before (bluez-utils and bluez-audio). The stuff that was in bluez-gstreamer and bluez-alsa is now part of bluez-audio. The stuff that was in bluez is now part of bluez-utils.
The reason for this is so that we don't stray from what debian has this late in the cycle. If debian decides to not choose that naming scheme, we would have a very complicated situation come Jaunty. The debian maintainer was not available for immediate feedback so this is a saner solution for now.
The unfortunate consequence of this is that people who activated the PPA won't have a clean upgrade from the ppa2 to ppa3 version. Sorry about that :(
Upgrades should be properly handled still for Intrepid mainline users though.
OK: I've uploaded bluez_4. 9-0ubuntu1~ ppa3 to the PPA. This returns the init script back to bluetooth.
Also: this switches the binary package names back to what we had before (bluez-utils and bluez-audio). The stuff that was in bluez-gstreamer and bluez-alsa is now part of bluez-audio. The stuff that was in bluez is now part of bluez-utils.
The reason for this is so that we don't stray from what debian has this late in the cycle. If debian decides to not choose that naming scheme, we would have a very complicated situation come Jaunty. The debian maintainer was not available for immediate feedback so this is a saner solution for now.
The unfortunate consequence of this is that people who activated the PPA won't have a clean upgrade from the ppa2 to ppa3 version. Sorry about that :(
Upgrades should be properly handled still for Intrepid mainline users though.