Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1232310

Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

El 06/02/25 a las 17:46, László Böszörményi (GCS) escribió:
> Hi Santiago,
> 
> On Wed, Feb 5, 2025 at 8:18 PM Santiago Ruano Rincón
> <santiagorr@riseup.net> wrote:
> > Testing (trixie) currently ships fuse3 3.14.0. FYI, upstream released
> > 3.16.2 on Oct 10th 2023:
> > https://github.com/libfuse/libfuse/releases/tag/fuse-3.16.2.
>  Indeed, a long time ago. While I've some time constraints nowadays,
> there are reasons that this is not packaged yet.
> 
> > While I am not aware of any release schedule and EOL policy for
> > fuse3, I would say that the more recent release can be included in
> > trixie, the better. And the easier would be to provide security updates
> > to the users during the trixie life cycle.
>  Security support has precedence. But please note that 3.16.2 has an
> unfixed issue that causes severe file corruption [1]. Then it changes
> a function signature of a symbol (ABI break) [2], which can cause
> problems with software using it. Then there is another ABI break with
> 3.15.0+ [3].

Yeah, I forgot to mention [2] and [3] in my initial email, but I was
unaware that [1] was caused by 3.16.2.

Security support is important, but stability too!

> It seems 3.17 is coming, at least this commit [4] seems interesting
> and a 64 bit value truncation fix [5] would be nice to have as well.
> But I do not know if the new release is coming soon or not.
> 
> > Do you have any plans to upload to fuse3 to unstable (before the trixie
> > freeze)?
>  I do have. In the hope that at least some of the above bugs get
> fixed. I do not think it is worth the risks to have those with Trixie.

ACK!

> But I'm open to hear your thoughts.

For the moment, I've asked upstream about their plans. If they release
3.17 **soon**, I could give a try to test reverse dependencies, if that
helps. But as you say, the risks are too high.

> 
> Regards,
> Laszlo/GCS
> [1] https://github.com/libfuse/libfuse/issues/945
> [2] https://github.com/libfuse/libfuse/issues/1092
> [3] https://github.com/libfuse/libfuse/issues/1029
> [4] https://github.com/libfuse/libfuse/commit/1c58dc6c0e4001334b20290d24d20cec9f81e638
> [5] https://github.com/libfuse/libfuse/commit/999aee6c0d6bf1ac67c3b89472f32fd1d384cf44

Cheers,

 -- S

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2 Santiago Ruano Rincón <santiagorr@riseup.net> - 2025-02-05 20:20 +0100
  Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2 Santiago Ruano Rincón <santiagorr@riseup.net> - 2025-02-05 20:30 +0100
  Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2 László Böszörményi (GCS) <gcs@debian.org> - 2025-02-06 18:00 +0100
    Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2 Santiago Ruano Rincón <santiagorr@riseup.net> - 2025-02-08 13:10 +0100
      Bug#1095239: fuse3: Please package latest upstream version available: 3.16.2 Santiago Ruano Rincón <santiagorr@riseup.net> - 2025-02-11 01:10 +0100

csiph-web