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


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

We believe that the bug you reported is fixed in the latest version of
libsmraw, 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 libsmraw 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:10:34 +0100
Source: libsmraw
Architecture: source
Version: 20240506-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Hilko Bengen <[email protected]>
Closes: 1084433
Changes:
 libsmraw (20240506-2) unstable; urgency=medium
 .
   * Move from fuse to fuse3 (Closes: #1084433)
Checksums-Sha1:
 e6f40891b1b68ab70a5d0de611c240914dc6431e 2223 libsmraw_20240506-2.dsc
 c66482a21db25b754ca5b459e5882c9828587fc9 5076 libsmraw_20240506-2.debian.tar.xz
 cbc69dfd1bb3e521b48592c9c29f55fc74d11705 6281 
libsmraw_20240506-2_source.buildinfo
Checksums-Sha256:
 9cda69d1b05ae30cd46c31dc4460a78b02c70bf9f843096fdfd6f3ff0cfe2ebd 2223 
libsmraw_20240506-2.dsc
 86ec390eb68b34fdd40b0e1ded0f6198385cc1e529b07a275d1b14b82708abd0 5076 
libsmraw_20240506-2.debian.tar.xz
 778497cf8e59b3915058d4b512492e01e65ecdbfa4d7a85e36e4b7060b781d9a 6281 
libsmraw_20240506-2_source.buildinfo
Files:
 3e182e684636c28d2cbbbaf866373c16 2223 libs optional libsmraw_20240506-2.dsc
 cca4da9971cd275f2ae2717e66b45283 5076 libs optional 
libsmraw_20240506-2.debian.tar.xz
 aa9b2635767af3aa3535b05d5a9a16c3 6281 libs optional 
libsmraw_20240506-2_source.buildinfo

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

iQIzBAEBCgAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmkmObkACgkQdbcQY1wh
On63/A//TsQwzBSHpkKQqDD1++YXPqNkfoXW+zBO38jYGbRGFJTHvj9XrRyDA0lM
RRPkdrnAQ2RgVjZXJcpTztA/pPFcCW+XUFZ7jnGYsDoTB2HnXwEVefobew/OLdwG
sqAUCJnURNZuALeg9R1IXVg2l5jSN/EGh13Mn/OyYDvQWIdk4NFiiuHMw5XJ1GTI
mmWjhcfRpe5uu80M6Cmna46XWjaV/GOYVUAvr28ypChTjHr0qu+rGB1sSyAtPuug
Qe5MkJEDGGDYsK/XmRucG8v4ZlcBPYOnf1Eh3Fg1z/Z8nS3GAVBLDFpJwu1o5lEo
Mxn1QoaTt2fnkVuk5Y4HNSjLkFvM/7aphSICO2sOjDxsWyUWKCzox0ylQw9XFggQ
R8OOQVExKkMICZD/Se7hXrR1tuS8TEZ+MbaS8JSVb2yV8eUoUSpLeqeKu8J9ci1i
pF7ofucozUKHcTuRH4dpCy09n0JYebBTjXu/RFBLjOf9UhkSLzmvbOMQhaWzR93c
3pMKc+RM5dQnNxbCbVMU3joVsAAEd5jMgghBXVzwnbWalTLyvDTDADjTQq5YYDUr
JQxQ9R0r4tcZjjRsaJw4uBAar1l60KkgXXdoUigkSgDUYjsDH4+7vz4SF7xDa6U5
oyQ70iHYRF82gYPx3kFCPCahGM79i1m5GdYfQzI/hAONYNrI96g=
=bPkO
-----END PGP SIGNATURE-----

Attachment: pgpc8DMmQc60Y.pgp
Description: PGP signature


--- End Message ---

Reply via email to