Your message dated Tue, 25 Nov 2025 22:49:45 +0000
with message-id <[email protected]>
and subject line Bug#1084435: fixed in libregf 20240421-2
has caused the Debian Bug report #1084435,
regarding libregf: 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.)


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

We believe that the bug you reported is fixed in the latest version of
libregf, 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 libregf 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:34:55 +0100
Source: libregf
Architecture: source
Version: 20240421-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 1084435
Changes:
 libregf (20240421-2) unstable; urgency=medium
 .
   * Move from fuse to fuse3 (Closes: #1084435)
Checksums-Sha1:
 c841d9afac403cb3fee3a2a06c3b93fa531a1de7 2205 libregf_20240421-2.dsc
 88055fbe39a0c08388809683b435b385795778f6 5624 libregf_20240421-2.debian.tar.xz
 a79bb0cf37201f1ee3c920403496884ca59b4a51 6277 
libregf_20240421-2_source.buildinfo
Checksums-Sha256:
 95c0fcd77a80c46a97207a32db0b7dddca1be93c6224b747de941ba81ef59b6d 2205 
libregf_20240421-2.dsc
 a355538d5a956b2f358576bd7a55fa78a4bfd96f35fe801d1cbb8d24285f397d 5624 
libregf_20240421-2.debian.tar.xz
 ca3e3479c8f2820a14ccbb26f944bf375daaff8fac6c1e01f4982d016de869ec 6277 
libregf_20240421-2_source.buildinfo
Files:
 60c988381d4c749cf699886f3240aa4c 2205 libs optional libregf_20240421-2.dsc
 1db66aee4e6f756be6e13eb0cd5bdec8 5624 libs optional 
libregf_20240421-2.debian.tar.xz
 ad8e3f300683fbb2fe02b8b6cec9dcbb 6277 libs optional 
libregf_20240421-2_source.buildinfo

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

iQIzBAEBCgAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmkmLyQACgkQdbcQY1wh
On5y2Q/9Fg+DpPdm2WkEB+4CoJ8X6WSLJyMdRRN/eB92hAfqL/cFPaZiy3AP+mR3
j9UvB3ppSUnlOdbfEDllsy1rJASjEr3ugbtP0eM7QN6NR5NBPuFt6Qsg53ky1UZB
BtlZWCw9yhkV+BAAbvfKBeTqZaS1Is0pFZPhDI590Z4vsvS3DItPfjcx9MoDOQ+K
lo/w4Y6oBn/z++Du9Qv8uO6FixR/F1py9jE6z3ZvkzDzCOkkcENhx33s+NfTdoVJ
mdJZm4jAepU+foEJB6ZaujN4ZdVC0TVkWEad8XcDtrkMJybiNUV/9BWAfpIYO2oO
PHawm7adYLlaQVzWBHMTsnf3h8d984sHVRk5IgYYpKcMoTpbrzIScNqaO64rRcJr
5RNo/3r9dJBZjClbwEZwOBqztzWJQ7L/UqLo/c/G4CZhkskjnxSz9UX9dFO8nXrt
O9I2DA5K7wMsmbIF7pW4XECdmKAN1N1QHF1TBzpX1a87S1atXjcs2aoHtGbYiP4F
RL+rMFzaQqVqsEAgHS/wMsves6g097PDhi06NLSTxfKny+rr7vF1PahLwZO+UlVK
67o9OiXFBO6ghXF1grcsdNwCTgKphFlbuVDNmk5nCr/Hbb+Fmp9SmQwwr0Ma6EIt
TMXCnoOqduTbJOHdU1J668Qmb7OAQ+Snb7ubwcnzCL22RYFudcM=
=26mT
-----END PGP SIGNATURE-----

Attachment: pgpo86wEVjDzW.pgp
Description: PGP signature


--- End Message ---

Reply via email to