Control: tags -1 +moreinfo On Sun, Aug 11, 2019 at 11:24 AM Patrick Schleizer <adrela...@riseup.net> wrote: > The following code from /var/lib/dpkg/info/fuse.postinst is failing. > > if [ -e /dev/fuse ] > then > udevadm test --action -p $(udevadm info -q path -n /dev/fuse) > > /dev/null 2>&1 > fi It's very strange. I've tried several ways to reproduce this, without any luck. Especially that [ -e /dev/fuse ] is checking for the fuse device and only run udevadm if it's there. I've tried hard to reproduce this on a real system and in chroots (Buster and Sid) without success. Just for the record, what kind of architecture do you try this on?
> + [ -e /dev/fuse ] > + udevadm info -q path -n /dev/fuse > Unknown device "/dev/fuse": No such device > > Happening inside a Debian buster chroot. How did you create that Buster chroot? Mine was created with 'pbuilder create' and I do have the fuse device in the chroot. As noted above, if the fuse device is not there, the udevadm is not run due to the check for that being false. One thing came into my mind is that you have the chroot on a mount point that has the nodev option. Can you check that please? Regards, Laszlo/GCS
