Your message dated Fri, 27 Mar 2026 15:48:36 +0000
with message-id <[email protected]>
and subject line Bug#1084453: fixed in afuse 0.5.0-0.2
has caused the Debian Bug report #1084453,
regarding afuse: 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.)


-- 
1084453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084453
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: afuse
Version: 0.5.0-0.1
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: afuse
Source-Version: 0.5.0-0.2
Done: Thomas Glanzmann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
afuse, 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.
Thomas Glanzmann <[email protected]> (supplier of updated afuse 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: Fri, 27 Feb 2026 18:15:00 +0100
Source: afuse
Architecture: source
Version: 0.5.0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Varun Hiremath <[email protected]>
Changed-By: Thomas Glanzmann <[email protected]>
Closes: 1084453
Changes:
 afuse (0.5.0-0.2) unstable; urgency=medium
 .
   * Add patch for libfuse3 support (Closes: #1084453)
   * Refresh packaging:
     + Bump Standards-Version to 4.7.3
     + Rules-Requires-Root: no
     + Update build deps to libfuse3-dev and pkgconf
Checksums-Sha1:
 9763f68cd9e77ab7abaae7b9083cb8e6b018b0d1 1666 afuse_0.5.0-0.2.dsc
 f09f66028bca6008267dc9e0166675f59bb05381 6196 afuse_0.5.0-0.2.debian.tar.xz
 bfb86b82422ee1445edf23cdcde79c99e006b0ef 5513 afuse_0.5.0-0.2_source.buildinfo
Checksums-Sha256:
 ff70ef8783df8c44912b9c26dab28bc6aad73d6d447d48b2252a068e551c2eaf 1666 
afuse_0.5.0-0.2.dsc
 38b8973652d8e36fa75ec1431bb45a96b20dabfecc201ba92eb945d3ec3b6910 6196 
afuse_0.5.0-0.2.debian.tar.xz
 049c26a7836970f326b36865ef1e147a62a248ac2aacd953979801859e60ec58 5513 
afuse_0.5.0-0.2_source.buildinfo
Files:
 cab4235db44c105e3832938705721382 1666 utils optional afuse_0.5.0-0.2.dsc
 9ad7109a460b82308114de2c4c8e7212 6196 utils optional 
afuse_0.5.0-0.2.debian.tar.xz
 d90f1b0a59ad063d06d90b9fa244ca67 5513 utils optional 
afuse_0.5.0-0.2_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmnGpCcQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIDsDACEVbjW4nVz2IZZFLN1XiGIH8AYvio2SNSV
QJ3ko47L2BxCpYQxXVX15v6XDdfQeuVcqc2cf/HLV8xRCHNG8cZxSpMkcsRNXHPt
4gkHFkgxSyHpw4SVws9iwpBSCxVaWl728XB3+J1bt4BHcBZD/WiA2AI+Zg8bEWGc
SjwlOOJq9qJjsPwI9vIz79p21k4pHC7Xw+SzewyQkTpsSivA1Fw0Uh8zj5fHP/7G
6t+UqCRjUfBEuZ4YKWxlot8B557HTOjDp3IE3VWnPl3NOOybPJfZsoU7w/Iup2lV
Kl46GU4UTvH7LhVD8NKoO6Q5mWiOLBAZ5XWsqywUpWJxIdWfbXKwgMjfh6I+fcC7
gKc629fxMfg7Rukt53UOMugMUs+flYq+if1mDl2M/t0jUT9H8BgUqd37dMfrDtor
avd3F+PXL+oRHmUellZ0kf+ZBb2MEtvnL4d6MxEg3zevKj6EYEIAFYK6v5Y0BKEl
pDWucvFvqr5w2TrFrBPemovN4IVdK9E=
=Nm/x
-----END PGP SIGNATURE-----

Attachment: pgpHeyxXPTYvl.pgp
Description: PGP signature


--- End Message ---

Reply via email to