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 package hint: bluez
  
  Preparing to replace bluez 4.45-0ubuntu1 (using 
.../bluez_4.45-0ubuntu2_i386.deb) ...
  invoke-rc.d: initscript bluetooth, action "stop" failed.
  dpkg: warning: old pre-removal script returned error exit status 1
  dpkg - trying script from the new package instead ...
  invoke-rc.d: initscript bluetooth, action "stop" failed.
  dpkg: error processing /var/cache/apt/archives/bluez_4.45-0ubuntu2_i386.deb 
(--unpack):
   subprocess new pre-removal script returned error exit status 1
  postinst called with unknown argument `abort-upgrade'
  Errors were encountered while processing:
   /var/cache/apt/archives/bluez_4.45-0ubuntu2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  E: Some packages could not be upgraded.
  
  ProblemType: Bug
  Architecture: i386
  Date: Tue Jul 14 23:58:34 2009
  DistroRelease: Ubuntu 9.10
  Package: bluez 4.45-0ubuntu1
  ProcEnviron:
   LANGUAGE=fi_FI:fi:en_GB:en
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
  SourcePackage: bluez
  Uname: Linux 2.6.30-10-generic i586
+ 
+ 
+ ---
+ It's been decided that this bug won't be fixed due to the large amount of 
breakage going on in the last 24 hours anyway with other packages.
+ The problem only happens when upgrading from 4.45-0ubuntu1 or 4.45-0ubuntu2 
to 4.45-0ubuntu3 when bluetoothd is *not* already running.
+ 
+ If you are affected, there are two ways that it can be currently worked 
around:
+ 1) Start bluetoothd before doing the upgrade
+ 2) Add a || true to the pkill line in /etc/init.d/bluetooth

-- 
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to