Re: fuse -> fuse3

2019-01-01 Thread Nikolaus Rath
On Dec 25 2018, "Theodore Y. Ts'o"  wrote:
> On Fri, Dec 21, 2018 at 11:03:34PM +0100, Oibaf wrote:
>> The package fuse3 is available since awhile in sid/buster.
>> Their users however are still using old fuse (v2), e.g. sshfs-fuse.
>> According to this:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
>> fuse3 is not co-installable with fuse, but a patch is available.
>> 
>> So is there a chance this get fixed and sshfs-fuse and other package can be
>> updated to use fuse3 for buster?
>
> Thanks for mentioning it!  I didn't even *know* about the existence of
> fuse3.  Is libfuse3 API compatible with fuse2?

No, but in most cases the necessary changes are not too invasive.

> P.S.  If fuse3 and fuse are not co-installable, we really should have
> managed this as a formal buster migration earlier.

They are co-installable in principle, this is just a bug in packaging.

Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«



Re: fuse -> fuse3

2018-12-31 Thread Oibaf
Il giorno mar 25 dic 2018 alle ore 17:12 Theodore Y. Ts'o 
ha scritto:

> On Fri, Dec 21, 2018 at 11:03:34PM +0100, Oibaf wrote:
> > The package fuse3 is available since awhile in sid/buster.
> > Their users however are still using old fuse (v2), e.g. sshfs-fuse.
> > According to this:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
> > fuse3 is not co-installable with fuse, but a patch is available.
> >
> > So is there a chance this get fixed and sshfs-fuse and other package can
> be
> > updated to use fuse3 for buster?
>
> Thanks for mentioning it!  I didn't even *know* about the existence of
> fuse3.  Is libfuse3 API compatible with fuse2?  In other words, is it
> just a recompile away for e2fsprogs to be able to produce a fuse2fs
> binary that works with fuse3?
>

Here are some info on fuse3 changes:
https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0

If so, I wonder if we would be better off renaming libfuse3-dev to
> something like fuse-dev?  That would mean that people who just
> recompiled their packages would pick up fuse3 support.  It would also
> make it easier for people like myself, who try to make e2fsprogs and
> its debian packaging trivially backportable to stable, old-stable, and
> old-old-stable.
>
> Well, it would still be annoying in the short-term, since I'll have to
> teach my scripts how to generate a different debian/control from
> debian/control.in so that we use libfuse2-dev for pre-Buster, and
> libfuse3-dev or fuse-dev for Buster+.  But if we chase things so that
> it's fuse-dev for Buster+. in the future it will be easier to support
> debian packaging trivially for muliple Debian releases.
>
> Cheers,
>
> - Ted
>
> P.S.  If fuse3 and fuse are not co-installable, we really should have
> managed this as a formal buster migration earlier.  Oh, well, water
> under the bridge, but we're going to have to move briskly before the
> Debian Buster transition freeze of January 12, 2019.  :-/
>

It appears fuse3 was fixed and upgraded, now it should be co-installable
with fuse (v2):
https://tracker.debian.org/pkg/fuse3


Re: fuse -> fuse3

2018-12-25 Thread Theodore Y. Ts'o
On Fri, Dec 21, 2018 at 11:03:34PM +0100, Oibaf wrote:
> The package fuse3 is available since awhile in sid/buster.
> Their users however are still using old fuse (v2), e.g. sshfs-fuse.
> According to this:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
> fuse3 is not co-installable with fuse, but a patch is available.
> 
> So is there a chance this get fixed and sshfs-fuse and other package can be
> updated to use fuse3 for buster?

Thanks for mentioning it!  I didn't even *know* about the existence of
fuse3.  Is libfuse3 API compatible with fuse2?  In other words, is it
just a recompile away for e2fsprogs to be able to produce a fuse2fs
binary that works with fuse3?

If so, I wonder if we would be better off renaming libfuse3-dev to
something like fuse-dev?  That would mean that people who just
recompiled their packages would pick up fuse3 support.  It would also
make it easier for people like myself, who try to make e2fsprogs and
its debian packaging trivially backportable to stable, old-stable, and
old-old-stable.

Well, it would still be annoying in the short-term, since I'll have to
teach my scripts how to generate a different debian/control from
debian/control.in so that we use libfuse2-dev for pre-Buster, and
libfuse3-dev or fuse-dev for Buster+.  But if we chase things so that
it's fuse-dev for Buster+. in the future it will be easier to support
debian packaging trivially for muliple Debian releases.

Cheers,

- Ted

P.S.  If fuse3 and fuse are not co-installable, we really should have
managed this as a formal buster migration earlier.  Oh, well, water
under the bridge, but we're going to have to move briskly before the
Debian Buster transition freeze of January 12, 2019.  :-/



Re: fuse -> fuse3

2018-12-21 Thread Dmitry Smirnov
On Saturday, 22 December 2018 9:03:34 AM AEDT Oibaf wrote:
> The package fuse3 is available since awhile in sid/buster.
> Their users however are still using old fuse (v2), e.g. sshfs-fuse.
> According to this:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
> fuse3 is not co-installable with fuse, but a patch is available.
> 
> So is there a chance this get fixed and sshfs-fuse and other package can be
> updated to use fuse3 for buster?

IMHO some progress could be made if Laszlo allows co-maintainers to 
participate in maintenance of "fuse3" package (#912526).

I'd very much like to update sshfs for FUSE3 but #912528 is a blocker and 
changes should be made in "fuse3" to move forward...

-- 
All the best,
 Dmitry Smirnov.

---

It is a mistake to try to look too far ahead. The chain of destiny can only
be grasped one link at a time.
-- Winston Churchill



signature.asc
Description: This is a digitally signed message part.


fuse -> fuse3

2018-12-21 Thread Oibaf
The package fuse3 is available since awhile in sid/buster.
Their users however are still using old fuse (v2), e.g. sshfs-fuse.
According to this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912528
fuse3 is not co-installable with fuse, but a patch is available.

So is there a chance this get fixed and sshfs-fuse and other package can be
updated to use fuse3 for buster?

Thanks to everyone involved.