Your message dated Mon, 17 Nov 2025 18:24:48 +0000
with message-id <[email protected]>
and subject line Bug#1084400: fixed in libvmdk 20240510-2
has caused the Debian Bug report #1084400,
regarding libvmdk: 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.)
--
1084400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084400
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvmdk
Version: 20200926-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: libvmdk
Source-Version: 20240510-2
Done: Hilko Bengen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libvmdk, 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 libvmdk 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: Mon, 17 Nov 2025 10:45:08 +0100
Source: libvmdk
Architecture: source
Version: 20240510-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 882229 1084400
Changes:
libvmdk (20240510-2) unstable; urgency=medium
.
* Switch to libfuse3 (Closes: #1084400)
* Install .egg-info file into python package (Closes: #882229)
Checksums-Sha1:
726adf59e55206f4c0fc8b25ed207d980b342c83 2189 libvmdk_20240510-2.dsc
29c3f8ad71ec496da0da001a8dfe095662ba2105 7360 libvmdk_20240510-2.debian.tar.xz
1a194036e2b38371d19611a70b24614298b07e64 7402
libvmdk_20240510-2_source.buildinfo
Checksums-Sha256:
d33658671ab6d4d1220562bae8207eb83f159c9f840611d92b93357eb53b709e 2189
libvmdk_20240510-2.dsc
d32b023b81bc7dd37f29eeeb35ee88fa4e8654026218b446be0c85d01a56628c 7360
libvmdk_20240510-2.debian.tar.xz
5fb6dd07585ef8cb82e981821f4284293ad5ea299c4ee5d878759d8966e13b94 7402
libvmdk_20240510-2_source.buildinfo
Files:
66a2b38d0383173c4da523949084d7fa 2189 libs optional libvmdk_20240510-2.dsc
a9e0521e9c1f938ec9a2139c189871e1 7360 libs optional
libvmdk_20240510-2.debian.tar.xz
4fe407a38082abf39f5dd3d3f1052391 7402 libs optional
libvmdk_20240510-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmkbZFgACgkQdbcQY1wh
On6kpQ//Z4okSTTfNrftkc7hTMXhqIKl+dvbwDgbNc5wcROTeGP8V5dzDKnq4NcA
ckrOLDKEqmZsbsNynND+lcQdnyQ/IR/RO53u7uRNyftyGITLeROqWwexBKv+8XSS
lJO4hj7N0nCUHtfAqzpCSv5Jeq1SJ7n25B5SyTLR1wtuc2SvbbmywkrP1mSH/3jY
CSckV0HG8pAyQ68JnEVahoGcChg+/a+/GBDcCv7GKF/5w7nY4HlepNK5rxxwKxiQ
WrTfsyaYwL2Bu+B3tuXcP9iYQd2jivhXN1DPHtfzhqTauj7dOG2ceLObxHvAPvL/
IhUXSH44NOEAINP7MigA1ofpoODqIY2LhqO18P/voWlowZIGk5gnG9wge+nTI9Rv
Q/HG+rxCiAFG5PLfNscwzNK8CtSwCO4w1985R33rsSL5Y16crZ3UaXquBKfj4Yvg
4smUUbqaaJdD0oUG+JQ5hVedu2+jvkPP4zmGyRpFFnZfxkXbjBhe7EDLxaEEkxPy
Q5d6yFKtAt7uLU59wTjJmAXPF/CbUGMm1FbzTHYeVtrmq6weLDluJs0ZkfKvNjFo
givv+zjCsVRyzBD/MDqsDyL1WeiiulmB3IwEKypyTAAr+B/q/g2jMWAeUBMVSiPN
/9WeC9jpZSDS6pRDf+JtY2oddbE8vESBP/dzseuRD4+lPHfPWts=
=yOdn
-----END PGP SIGNATURE-----
pgpZLzHrR7WM2.pgp
Description: PGP signature
--- End Message ---
