Hi Nikolaus, On Sat, Oct 8, 2016 at 5:40 AM, Nikolaus Rath <nikol...@rath.org> wrote: > Would you still be able to (and interested in) getting a libfuse3 > package into stretch? Indeed, already saw the pre-release Git tag on it.
> If so, by what time would you require the upstream release (currently > I've only made a pre-release)? It's complicated. Of course, I do _not_ require an upstream release - if it meant to Stretch, I would expect its release when it's stable and ready to be supported for years in that release. Then you may release early, release often to get feedback from projects experiencing with it. > libfuse3 breaks backward compatibility, so I'd imagine it would ship in > addition to libfuse2. That mean these are co-installable? > As far as the fuse binary package is concerned, I'm not so sure. I think > it would be preferable to build it from fuse 3.0 (the fusermount binary > should be backwards compatible). However, fuse 3 no longer includes > ulockmgr_server. In theory, it has been factored out into a separate > project, but I am not aware of any users and I am not able to find the > project.... I don't know ulockmgr_server either, but may fuse and fuse3 source packages (with their libraries and binaries) may co-exist? Then fuse can be removed from Debian after Stretch. Until you release the latter as stable, it can go to experimental. But need to package it first. Regards, Laszlo/GCS
