severity 550334 serious
tags 550334 patch
thanks
this bug basically causes the package to fail to install in any chroot
environment (including ltsp, pbuilder, and piuparts) where udev is installed,
as udev doesn't start (by default) when it detects a chroot environment.
preferring udev over makedev (introduced in fuse-utils 2.8.1-1) causes this bug
to get triggered by default in chroots.
this doesn't seem like something that should hit a stable release, so raising
the severity.
On Sun, Nov 15, 2009 at 03:55:28AM +0100, Diederik de Haas wrote:
> The problem is in the fuse-utils.postinst script and modifying line 46 from
> cd /dev && ./MAKEDEV fuse
> to
> cd /dev && MAKEDEV fuse
> fixed it for me.
> Manually installing makedev was not sufficient, since makedev gets installed
> in /sbin/MAKEDEV and not
> in /dev/MAKEDEV
in light of this, here's an updated patch that should handle a little better:
--- postinst.orig 2009-11-22 14:33:33.000000000 -0800
+++ postinst 2009-11-22 14:35:57.000000000 -0800
@@ -17,9 +17,13 @@
fi
# Create device node with the right perms
if [ ${udev} -eq 0 ]; then
- # Call makedev and fix perms
- cd /dev && ./MAKEDEV fuse
- chgrp fuse /dev/fuse
+ if [ -x /sbin/MAKEDEV ]; then
+ # Call makedev and fix perms
+ cd /dev && MAKEDEV fuse
+ chgrp fuse /dev/fuse
+ else
+ echo "MAKEDEV not installed, skipping device node creation."
+ fi
else
# Udev is active, nothing to do.
echo "udev active, skipping device node creation."
live well,
vagrant
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
