[Pkg-bluetooth-maintainers] Bug#387410: Fwd: Bug#387410: bluez-utils: fails on upgrade

Eddy Petrişor eddy.petrisor at gmail.com
Thu Sep 14 09:16:01 UTC 2006


Hmm, stupid gmail, doesn't respect Reply-To header if used with a
non-fully supported browser.

---------- Forwarded message ----------
From: Eddy Petrişor <eddy.petrisor at gmail.com>
Date: Thu, 14 Sep 2006 12:14:11 +0300
Subject: Re: Bug#387410: bluez-utils: fails on upgrade
To: Debian Bug Tracking System <submit at bugs.debian.org>

On 14/09/06, Eddy Petrisor <eddy.petrisor at gmail.com> wrote:
> Package: bluez-utils
> Version: 3.1-4+b1
> Severity: serious
> Justification: no upgrade path
>
> Hello,
>
> While trying to upgrade bluez-utils it failed with the following error:
>
> Setting up bluez-utils (3.1-4+b1) ...
> Creating device nodes ...
> /var/lib/dpkg/info/bluez-utils.postinst: line 38: ./MAKEDEV: No such file or
> directory
> dpkg: error processing bluez-utils (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  bluez-utils
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> A package failed to install.  Trying to recover:
> Setting up bluez-utils (3.1-4+b1) ...
> Creating device nodes ...
> /var/lib/dpkg/info/bluez-utils.postinst: line 38: ./MAKEDEV: No such file or
> directory
> dpkg: error processing bluez-utils (--configure):
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  bluez-utils
> Press return to continue.
>
>
> It apparently tries to run MAKEDEV from the current directory. Does the
> postinst cd to the directory where MAKEDEV is installed (/sbin)? Could

the nasty part is at line 38:


[snip]
         # use MAKEDEV instead of the original bluez script below as
per policy 10.6
         echo "Creating device nodes ..."
        cd /dev && ./MAKEDEV bluetooth

         if [ -r /etc/bluetooth/pin ]; then
             echo "Converting default outgoing PIN to default passkey:"
[snip]

Probably something like this could be the fix (for sarge upgrade path):


--- bluez-utils.postinst.orig   2006-09-11 08:26:53.000000000 +0300
+++ bluez-utils.postinst        2006-09-14 12:13:06.000000000 +0300
@@ -35,7 +35,9 @@

         # use MAKEDEV instead of the original bluez script below as
per policy 10.6
         echo "Creating device nodes ..."
-        cd /dev && ./MAKEDEV bluetooth
+       [ -e /dev/MAKEDEV ] && cd /dev
+        [ -e /sbin/MAKDEV ] && cd /sbin
+       ./MAKEDEV bluetooth

         if [ -r /etc/bluetooth/pin ]; then
             echo "Converting default outgoing PIN to default passkey:"


Note that I haven't tested this for upgrades, downgrades...


-- 
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein



-- 
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein


More information about the Pkg-bluetooth-maintainers mailing list