works fine, thank you
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
https://bugs.launchpad.net/bugs/399482
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Everything seems alright from here! Thanks.
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
https://bugs.launchpad.net/bugs/399482
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had the same problem upgrading to bluez_4.53.
My /etc/init.d/bluetooth didn't had a pkill -TERM bluetoothd line, instead it
had a killall bluetoothd line, so i did the same as suggested before and
changed the line to be killall bluetoothd || true, restarted bluetooth and
then the upgrade
I did the following fix in Terminal:
* sudo gedit /etc/init.d/bluetooth
* Find the pkill -TERM bluetoothd line
* Replace it with pkill -TERM bluetoothd || true
After doing this, the update went just fine.
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
Here is a debdiff with a prerm for bluez catching the error from the old
prerm script and exiting with return code 0 (nothing has to be done as
the deamon is already stopped else the bug won't occur).
Preparing to replace bluez 4.45-0ubuntu1 (using
.../bluez_4.45-0ubuntu4_amd64.deb) ...
Given that that prerm change ignores ALL errors from the old prerm,
would it not be better, for safety's sake, to limit it to *just* the two
broken versions explicitly, rather than those versions and all earlier
versions?
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
And probably also comment that it's a workaround for a problem present
in packages which were never part of any Ubuntu release, not even an
alpha release, so can be dropped again in a month or so.
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
Updated the debdiff with this suggestions.
** Attachment added: bluez.debdiff
http://launchpadlibrarian.net/29133899/bluez.debdiff
** Attachment removed: bluez.debdiff
http://launchpadlibrarian.net/29133350/bluez.debdiff
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later
This bug was fixed in the package bluez - 4.45-0ubuntu4
---
bluez (4.45-0ubuntu4) karmic; urgency=low
* Fix upgrade breakage from 4.45-0ubuntu{1,2} (lp: #399482)
-- Michael Bienia ge...@ubuntu.com Thu, 16 Jul 2009 11:04:02 +0200
** Changed in: bluez (Ubuntu)
Status:
Mario: the scripts *do* solve the issue that what's currently shipping
fails to react to arguments passed to them.
--
Upgrading from bluez 4.45-0ubuntu{1,2} to 4.45-0ubuntu3 or later fails
https://bugs.launchpad.net/bugs/399482
You received this bug notification because you are a member of
Martin:
I did test with your two additional skeleton scripts in place, and it
does not help the problem.
Look at http://women.debian.org/wiki/English/MaintainerScripts for the
Upgrading section. Yes after the old prerm fails, it will go into try
the prerm for the new one with an argument
Given the amount of breakage outside of bluez that's been happening in
the last 24 hours, it's been decided trying to add cases in here to fix
upgrades between 4.45-0ubuntu{1,2} and 4.45-0ubuntu3 is not an important
scenario. Upgrades work from earlier versions.
** Description changed:
Binary
12 matches
Mail list logo
