Ok, thanks. If you don't use other FUSE filesystems, you can maybe uninstall `fuse3` and install `fuse`.
I'm unfortunately unlikely to have time to port bindfs to FUSE 3 in the near future :( The easiest distro-level workaround in terms of "least code required" would probably be to patch fuse3's fusermount to allow and ignore `nonempty` (and maybe print a deprecation warning). Or some hacks could probably be invented to direct FUSE 2 filesystems to use FUSE 2 helpers. It's up to the Debian maintainers whether they want the maintenance burder of either of these workarounds. On Wed, 12 Feb 2020 at 18:07, Willem Mulder <will...@scintilla.utwente.nl> wrote: > Hi Martin, > > On Wed, 2020-02-12 at 17:17 +0200, Martin Pärtel wrote: > > If that doesn't help, maybe you're running a mixed environment where > > e.g. bindfs is compiled against FUSE 2 but the system runs FUSE 3 > > helper binaries? The version list at the end of your e-mail suggests > > this. > > I haven't used your option, but I can confirm (using `ldd > /usr/bin/bindfs` and `fusermount -V`) that bindfs was linked against > libfuse 2.9.9, and the helper binaries are version 3.7.0. I guess the > package either needs to limit the FUSE version to < 3, or link against > libfuse >= 3. > > Kind regards, > > Willem Mulder >
