Hi Laszlo,
On Mon, Nov 06, 2023 at 06:49:48PM +0100, László Böszörményi (GCS) wrote:
> Just for the record, the change broke self-testing of gphotofs big on
> all architectures. It fails with:
> autopkgtest: test command1: [ "$(./gphotofs 2>&1)" == 'fuse: missing
> mountpoint parameter' ]
> 165s
Hi Helmut,
On Mon, Nov 6, 2023 at 11:28 AM Helmut Grohne wrote:
> On Sun, Nov 05, 2023 at 02:19:18PM +0100, László Böszörményi (GCS) wrote:
> > Yes, it makes upstreams more easily staying with the FUSE 2 API.
> > Making the switch to the FUSE 3 API more difficult. But OK, let it go.
> > I'm
Hi Laszlo,
On Sun, Nov 05, 2023 at 02:19:18PM +0100, László Böszörményi (GCS) wrote:
> I think distributions should do the opposite, somehow enforce
> projects to migrate to the new, supported FUSE version. Basically it
> is deprecated since 2018 and as 2024 is approaching it means for six
>
Hi Helmut,
On Thu, Nov 2, 2023 at 12:15 PM Helmut Grohne wrote:
> I have a slightly unusual request. I know libfuse 2.x is a legacy in
> maintenance mode slated for removal eventually. Unfortunately, 2/3 of
> fuse users still use the 2.x branch so it seems like we will have to
> support it a bit
Package: libfuse2
Version: 2.9.9-6+b1
Tags: patch upstream fixed-upstream
Hello Laszlo,
I have a slightly unusual request. I know libfuse 2.x is a legacy in
maintenance mode slated for removal eventually. Unfortunately, 2/3 of
fuse users still use the 2.x branch so it seems like we will have to
5 matches
Mail list logo
