Your message dated Wed, 26 Nov 2025 00:05:41 +0000
with message-id <[email protected]>
and subject line Bug#1084430: fixed in libvslvm 20240504-2
has caused the Debian Bug report #1084430,
regarding libvslvm: 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.)


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

We believe that the bug you reported is fixed in the latest version of
libvslvm, 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 libvslvm 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: Wed, 26 Nov 2025 00:43:43 +0100
Source: libvslvm
Architecture: source
Version: 20240504-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 1084430
Changes:
 libvslvm (20240504-2) unstable; urgency=medium
 .
   * Move from fuse to fuse3 (Closes: #1084430)
Checksums-Sha1:
 433a0d3fb221f53c16801c9ebc53cf18201427d1 2223 libvslvm_20240504-2.dsc
 29f74d1c29eb2c20a473ce74a44551ffe4a3d462 4992 libvslvm_20240504-2.debian.tar.xz
 0b1eb7859490967d64995298f6e3b80728564ade 6281 
libvslvm_20240504-2_source.buildinfo
Checksums-Sha256:
 76e4f70e47e15e7ea99b5b3e21dc37eb83ad7250f071a03b66848ac46386e876 2223 
libvslvm_20240504-2.dsc
 a48ed8db59c004fa3edad6efad9fe46dc032262bf825b23a950687531345e596 4992 
libvslvm_20240504-2.debian.tar.xz
 39b02676f5e4fcf60c8f460ae4847a306bc8d17a036cc55276cb32db19523e28 6281 
libvslvm_20240504-2_source.buildinfo
Files:
 8378a28fec13783bd5770d54d87a672e 2223 libs optional libvslvm_20240504-2.dsc
 08b2315b5b4f6838959d7f5c7a1c3b52 4992 libs optional 
libvslvm_20240504-2.debian.tar.xz
 77bcaa35fd522c0877e8a27690150baf 6281 libs optional 
libvslvm_20240504-2_source.buildinfo

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

iQIzBAEBCgAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmkmP54ACgkQdbcQY1wh
On5Y1g//b3nB2M+cm8d4OoMYdYsYd1iLKM30nU4iKlhnmtD5FonU8z9UfMa2wtXG
+A4uy/etquN+x7B4UXw8Q32IouZsxvPfJt+8r2mX7x6fj+ECecxfC8Hsjccue8cv
GMnLwOyVmZWq2iCMbKZz0ixFuyBW2ohwcQCS58jJsswdQtH4D6O0mqB5DyPqfRZT
eomKBzcFQphMGWGMf3PkyzvDdAzu2jsBN/YoIXYUqaSCQrC+oNx/m8LVcjXIXBkC
qditrWHD68baVxJx9wmbJiRlptLjFfzu3CjxcGF2JV7690lT1dOFRTkLStDBHKkO
vYe4+FQYTYdJbIpoVajR+XKwb21cKYqjedkE24Kn+Foe3ijUKnURO0OUzrL7s5uq
e7dhMU/ZLHkqeXvFdwzxDnEJhMBVLNBruhZnLVSLp/AZ/7cetELeTxcRfbZVe2kf
4rXhltwdkhUBBfGafo7beF2/g4W2lEMxP9tQt3hQyJtH0zikpPwzuaMe7OT4UIGC
+bobpScpprVMz3t9xIHjSngMGeEhQC748f3V0KRkz1AJdTKcATHZD0J1kCYHwVGq
ZFd9Ru6tgn2Vdn9STsfNe9UvJhDdWTWoWJjsYYMCOv59U+5G1n4Gd3FPMdEtgzrS
Y+sjw4VkGEbQja3mhvMC7kYFvvjwaXJV/7jmqwUnnwY74xfNElI=
=4ReX
-----END PGP SIGNATURE-----

Attachment: pgp6ucA0RlWQB.pgp
Description: PGP signature


--- End Message ---

Reply via email to