Your message dated Tue, 25 Nov 2025 23:04:15 +0000
with message-id <[email protected]>
and subject line Bug#1084439: fixed in libfvde 20240502-2
has caused the Debian Bug report #1084439,
regarding libfvde: 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.)


-- 
1084439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084439
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libfvde
Version: 20190104-1.2
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: libfvde
Source-Version: 20240502-2
Done: Hilko Bengen <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libfvde, 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.
Hilko Bengen <[email protected]> (supplier of updated libfvde 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, 25 Nov 2025 23:40:52 +0100
Source: libfvde
Architecture: source
Version: 20240502-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 1084439
Changes:
 libfvde (20240502-2) unstable; urgency=medium
 .
   * Move from fuse to fuse3 (Closes: #1084439)
Checksums-Sha1:
 b66de4b03056377519c74a87ceceb74b23949c1d 2205 libfvde_20240502-2.dsc
 93c74aa7a40d5beb5c813c30c08c62fc24899c51 5604 libfvde_20240502-2.debian.tar.xz
 7c154eeb69d374e9952a04ca4d38a02c70ce337d 6277 
libfvde_20240502-2_source.buildinfo
Checksums-Sha256:
 9e71ad80f635f70e5675099978a5997a38b7a32219c702984f1157cd1295789f 2205 
libfvde_20240502-2.dsc
 7cb6e8242a8eadb8b41fab0fe69cfbe0537c7b61c33b738ec3d6e73a6f23f023 5604 
libfvde_20240502-2.debian.tar.xz
 6423a78a39d0a4f67384d8bb0a9dc3c17c0c6bf46ec5272946b67f712320dca7 6277 
libfvde_20240502-2_source.buildinfo
Files:
 2532dc6615f2007cbe8ef0e75ea51290 2205 libs optional libfvde_20240502-2.dsc
 b6ed1009236338dfa0599d37f07a87f6 5604 libs optional 
libfvde_20240502-2.debian.tar.xz
 b26888e27f58c0253e8e40e34c143cc8 6277 libs optional 
libfvde_20240502-2_source.buildinfo

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

iQIzBAEBCgAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmkmMPQACgkQdbcQY1wh
On7lxBAAmrVLaPqMVinLPVXoMqaJoOmdHnZQzUpLRKhm6Vp+k+cAzWt0gYaInclo
AlaB9L6cxld0CAWy2DV5Ry5O3mZ49uAEiw37APkaRu45UOQVZz+Z0yhJxzBRe91e
1pLFGocB6995TiGCmg2UP3nakChb+Hmz8WQQAdcQNzfRDCWIq8/qErCJG14DxB+a
vsamDzwqQj38yo4OpvUBMpnXOEfpRGFxH5DEG0MB3OuulBTOjg6YdU3BLzRwwC9P
SsR+ikHByVuDpr2gw854rZoh7ZTAqG9Z7NTLbqDICdipXBkiTR+Bph05JuZVtrtC
aW+eclDyx3qifXICSEnlnYWjcelIy5kZvy7f3plAB2Io8wJUeil8EHwFSA+fxQJW
oVX3upU6mV2oazfZnYGj+30FGRp00exiFVjfBMx3vFPN3uhovikW1KpzuofkK4MW
gUR3qwZIZKLJ3MbyeGbhLq4ruEMAxvt0ufR05K98h5iSJZfw0JZsE8pzmKEK5/tF
e5U0xGJvDhD0vnlseQM5zQJ3LQX6zYL+6pqCHK3j5SOmNlxSmBbTkb7BU6MIEEDD
HINMDtmcidSiBHiLlNnivM+wCIYsgclSs4YpaLnG2CFGYGgL8UXyko0lS3pSGrvg
GX0u+O514VBnAZEatFnvhEqMkvasCx8f+1zUgjeKjpDhd4E0GZI=
=5sLy
-----END PGP SIGNATURE-----

Attachment: pgp1Mq7VXNl3O.pgp
Description: PGP signature


--- End Message ---

Reply via email to