Hi Daniel,
I've got remote access to the box with the problem...
On 05/26/2011 08:50 PM, Daniel Baumann wrote:
> On 05/26/2011 08:16 PM, Dario Minnucci wrote:
>> It seems '/dev/fuse' directory wasn't present on the system (even having
>> fuse-utils 2.8.4-1.5,
>> libfuse-dev 2.8.4-1.5, libfuse2 2.8.4-1.5 packages already installed)
>
> /dev/fuse is supposed to be a device node, not a directory.
>
I know... when I've tried MAKEDEV fuse I've got 'don't know how to make device
"fuse"'
>> I've created /dev/fuse directory and chgrp it to belog to 'fuse' group, then
>> re-run 'aptitude
>> safe-upgrade' and the upgrade completed successfully. (not sure if this was
>> the best way to solve
>> it, but at least worked...)
>
> that's useless. please remove the directory, and do 'dpkg-reconfigure fuse'.
> if problem persists,
> run the postinst with set -x.
>
>> So, even having access again, fuse-utils on that system is now 2.8.4-2 :(
>
> well, you can just downgrade without problem to 2.6.4-1.5, and 'apt-get
> upgrade' again.
>
Downgrading fuse{*} didn't fix the problem...
I've downgraded udev from 170-1 to version 167-3 ... and then run 'aptitude
upgrade' and this fixed
the problem, so must be related to udev.
Versions running on the system are now...
root@dharma:/tmp# dpkg -l | grep "udev\|fuse"
ii fuse-utils 2.8.4-2 Filesystem in
USErspace (utilities)
ii libfuse2 2.8.4-2 Filesystem in
USErspace library
ii libgudev-1.0-0 170-1 GObject-based
wrapper library for libudev
ii libudev0 167-3 libudev shared
library
ii udev 167-3 /dev/ and hotplug
management daemon
So, fuse{*} 2.8.4-2 seems to be ok... would you reassign or close this bug for
me please?
Please, let me know if further information is needed.
Thanks for your time and sorry for the stupid noice on fuse! :)
Regards,
--
Dario Minnucci <[email protected]>
Phone: +34 902884117 | Fax: +34 902024417 | Support: (+34) 807450000
Key fingerprint = BAA1 7AAF B21D 6567 D457 D67D A82F BB83 F3D5 7033
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
