Dear Maintainer,

Not sure if this a bug in the fuse3 package or in the mount package.

The problem is that mount passes the arguments of mount.fuse3 in the wrong
order.
Found by strace that this is what is passed:

/sbin/mount.fuse3 -o rw,users,nosuid,nodev,exec sshfs#user@machine:space/
/home/user/mnt/space

This is what mount.fuse3 expects:
$ /sbin/mount.fuse3 --help
usage: /sbin/mount.fuse3 type#[source] destination [-t type] [-o
opt[,opts...]]

In the command line if I move the -o options at the end the mount works.

  * What led up to the situation?

   I have an entry in my fstab for a sshfs mount and I was trying to mount

  * What exactly did you do (or not do) that was effective (or
    ineffective)?

    I gave the following command which was for several years before

    mount ~/mnt/space

  * What was the outcome of this action?

   It said:

   /bin/sh: 1: -o: not found

  * What outcome did you expect instead?

  I was expecting to actually mount the specified remote folder.

Please try again with mount, libmount1, etc version 2.40.4-1 or
newer.

Chris

yep - that fixed it

thanks a bunch

reassign 1093016 mount
found 1093016 mount/2.40.3-1
fixed 1093016 mount/2.40.4-1
affects 1093016 src:fuse3
close 1093016
thanks

Thanks for the feedback, reassigning to mount and marking it as done
there.

Chris