On Thu, 28 Jan 2021 06:31:44 +0800, Paul Wise <p...@debian.org> wrote: > On Wed, 2021-01-27 at 20:08 +0100, Stephen Kitt wrote: > > No worries, they’re still bugs affecting loggedfs! I’ll downgrade > > this one and fix the other. (I’ll also suggest a fix for the nonempty > > handling in fuse3...) > > I had a thought that might work for loggedfs: > > Hardcode which fusermount arguments to use and the fuse or fuse3 > dependency based on which library loggedfs linked against at build > time. libfuse2 is never going to switch to fuse3 and vice versa and the
... except it does, which is the problem you ran into: it’s possible to install packages built against libfuse2 along with fuse3 (barring Breaks/Conflicts), and then things break if the libfuse2-using programs try to mount with "-o nonempty". > dependencies should ensure that the corresponding fusermount is > installed (needed since libfuse doesn't have the dep itself). This > should continue to work if the two libfuses get a dependency. But the libfuses can’t *depend* on the corresponding fuse package because the latter depends on the corresponding libfuse already. See #939767 for my proposed fix... Regards, Stephen
pgpZZycpckUXW.pgp
Description: OpenPGP digital signature
