Your message dated Tue, 02 Dec 2025 13:19:31 +0000
with message-id <[email protected]>
and subject line Bug#1084485: fixed in zfs-fuse 0.7.0-32
has caused the Debian Bug report #1084485,
regarding zfs-fuse: move from fuse to fuse3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1084485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084485
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zfs-fuse
Version: 0.7.0-29
Severity: normal

Dear Maintainer,

your package currently (Build-)Depends on fuse - that is fuse 2.x, it
being obsolete. A newer version of fuse, fuse3, is available since at
least buster. 

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.

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 allows mount.fuse and fusermount to be provided by fuse3, which
is what the majority of new installs already have [1]. You should
still migrate from libfuse 2.x to libfuse 3.x later.

fuse upstream noted important differences in [2].

[1] compare https://qa.debian.org/popcon.php?package=fuse and
https://qa.debian.org/popcon.php?package=fuse3

[2] https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0

--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-32
Done: Aron Xu <[email protected]>

We believe that the bug you reported is fixed in the latest version of
zfs-fuse, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aron Xu <[email protected]> (supplier of updated zfs-fuse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 02 Dec 2025 20:53:29 +0800
Source: zfs-fuse
Architecture: source
Version: 0.7.0-32
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Aron Xu <[email protected]>
Closes: 1084485
Changes:
 zfs-fuse (0.7.0-32) unstable; urgency=medium
 .
   * QA upload.
   * d/patches: port to fuse3 (Closes: #1084485)
   * d/control: b-d on libfuse3-dev
   * d/control: add conflicts/breaks to zfsutils-linux
Checksums-Sha1:
 98d2cd0f6d77d26a15a6551b23b47ddd400c1e67 1681 zfs-fuse_0.7.0-32.dsc
 fe53be6b828c35e89a4634e138203fcd629105ef 33536 zfs-fuse_0.7.0-32.debian.tar.xz
 41c49762b698959f1a1e40b0630b4a4c237ff520 5765 
zfs-fuse_0.7.0-32_source.buildinfo
Checksums-Sha256:
 61eac35374cb6bf6e86a2a4991399e1213210f407bfee3058f89eab2a0f41f5f 1681 
zfs-fuse_0.7.0-32.dsc
 80b9151f86fe15f61a39e39040ccdaf450a9b9df4d951323eba0d40a97b1310c 33536 
zfs-fuse_0.7.0-32.debian.tar.xz
 01121b05532ec5b64daeec2bb196dc060e0c7b9e406bb5f1d970bb827b289e09 5765 
zfs-fuse_0.7.0-32_source.buildinfo
Files:
 3e81bd5a767e0cbe9b1821ae275a255c 1681 otherosfs optional zfs-fuse_0.7.0-32.dsc
 ae1d95909ca1c18ce451b760a791a0c8 33536 otherosfs optional 
zfs-fuse_0.7.0-32.debian.tar.xz
 19ec3bed696946f6a540138718aa4ec1 5765 otherosfs optional 
zfs-fuse_0.7.0-32_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEBLHAyuu1xqoC2aJ5NP8o68vMTMgFAmku4gIACgkQNP8o68vM
TMjkCwgAnhn0maXtFc8yjYE/sC2sleksarwrX+u3cOYLPm/4IeFGFodUI7fLlRQy
vcHVLmnRU237QVxLldHFB0sTF0mx5Kv7zblHfMgRZmsyMxA4IjZ/KXhPM/nB71pM
sLz2rwwB3ibkdSS4fJ6NInR5HkJ1rlmr6TOJHNhKV2yV7dHKlNiJGSLh6vNb4ckk
H1oD/dPNFTzSQ0ocim7ibDgiEkePubdxOm6sRwVP61BkT0nIf/9yAdw5btAS05u8
4974fZU71Ms3b7J/zfaiUklf1cwiGsRcIhE9hG5Rkshbv9dM8hWLLalhyODCAy4u
RRFvUGStpxybsbFgGgna/kClfE5gsA==
=bRei
-----END PGP SIGNATURE-----

Attachment: pgpJoBG2KbMFS.pgp
Description: PGP signature


--- End Message ---

Reply via email to