On Tue, Oct 08, 2024 at 11:47:46AM +0200, Sascha Steinbiss wrote: > thanks for letting me know! > > > Please migrate your package to the fuse3 library, which is actively > > maintained. It would be great if we could remove fuse 2.x in the > > forky development cycle. > > Unfortunately, fusepy is slow or maybe even dead upstream -- master has not > seen a commit in years and a fuse3 compatibility PR has been sitting without > comment upstream for over a month [1]. I think it is unlikely that migration > to fuse3 is possible in a short timeframe.
If it is upstream-dead, maybe it's time to evaluate if it should be kept for trixie. You probably know best. > > If you cannot migrate yet, please at least update your Depends: line. > > If you currently have: > > > > > Depends: fuse > > > > please update that to: > > > > > Depends: fuse3 (>= 3.10.1-3) | fuse (<< 3) > > This package depends on libfuse and provides ctypes bindings to libfuse. I > don't think the above line is rather meant to be used for packages that > actually use mount.fuse and fusermount? The line is meant for packages currently having "Depends: fuse". "python3-fusepy" apparently does not have that, so this doesn't apply. > Would just using > > Depends: fuse (<<3) > > be ok? No :-) Best, Chris
