/var/lib/dpkg/info/bluez-utils.postinst bluez-utils 3.1-4
bdale at gag.com
Wed Aug 23 21:53:43 UTC 2006
On Wed, 2006-08-23 at 16:19 +0200, Filippo Giunchedi wrote:
> On Wed, Aug 23, 2006 at 04:03:22PM +0200, Lubomir Host wrote:
> > Hi gyus,
> > during upgrade of bluez-utils 3.1-4 a error occurs:
> > Setting up bluez-utils (3.1-4) ...
> > Installing new version of config file /etc/init.d/bluetooth ...
> > 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)
> > Here is the patch, which fix my problem:
> > # diff -u /var/lib/dpkg/info/bluez-utils.postinst.orig /var/lib/dpkg/info/bluez-utils.postinst
> > --- /var/lib/dpkg/info/bluez-utils.postinst.orig 2006-08-23 17:59:42.846935000 +0200
> > +++ /var/lib/dpkg/info/bluez-utils.postinst 2006-08-23 17:59:45.899125750 +0200
> > @@ -35,7 +35,7 @@
> > # use MAKEDEV instead of the original bluez script below as per policy 10.6
> > echo "Creating device nodes ..."
> > - cd /dev && ./MAKEDEV bluetooth
> > + MAKEDEV bluetooth
> I don't see the bug here, shouldn't MAKEDEV be present under /dev for
> compatibility? I'm CCing makedev maintainer to have a comment.
Don't depend on it being in /dev, because it won't necessarily be there
if you're running devfs or udev. Instead, always call it explicitly as
More information about the Pkg-bluetooth-maintainers