Your message dated Thu, 20 Aug 2026 20:23:58 +0000
with message-id <[email protected]>
and subject line Bug#1084456: fixed in casync 2+20201210-2.1
has caused the Debian Bug report #1084456,
regarding casync: move from libfuse to libfuse3
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.)


-- 
1084456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084456
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: casync
Version: 2+20201210-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: casync
Source-Version: 2+20201210-2.1
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
casync, 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.
Bastian Germann <[email protected]> (supplier of updated casync 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, 07 Jul 2026 12:00:49 +0200
Source: casync
Architecture: source
Version: 2+20201210-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 
<[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1084456
Changes:
 casync (2+20201210-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop optional fuse dependency (Closes: #1084456)
Checksums-Sha1:
 554a9682ed41c8f02fea6250340087892f988afc 2140 casync_2+20201210-2.1.dsc
 931e42e415227f59306c3d0346076c5200dd0ef2 3476 
casync_2+20201210-2.1.debian.tar.xz
 b0bc0cafb87147932fbadc3a9d1278db82b2ab4c 9031 
casync_2+20201210-2.1_source.buildinfo
Checksums-Sha256:
 058bee37a5bef7b6d36e4b8826b418708c0b06e6ac8dec31d1d2b0d421ebef70 2140 
casync_2+20201210-2.1.dsc
 cc565bee0f1731b6aa9b6d22ec9e677659c3cf4b87ae093931d2a6e77dbb07c8 3476 
casync_2+20201210-2.1.debian.tar.xz
 31521d3728fa09c7c1adfa0c3fd6fe916470f0e6f415eb3ad344387ff19bc907 9031 
casync_2+20201210-2.1_source.buildinfo
Files:
 d9bf396f59e5fa6902074b811feeaca8 2140 utils optional casync_2+20201210-2.1.dsc
 03dddffbb58792076da674de6bd042d3 3476 utils optional 
casync_2+20201210-2.1.debian.tar.xz
 cd262e5d3b9c17810920e655a59ae43c 9031 utils optional 
casync_2+20201210-2.1_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmp6Id4QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHOCDACF5BR2842WsBxj/JFLYoXSYmyHOj9eyZ9b
OoQnVnVDKzTlqyT51spJuJV6e46svSZf8kuqbgqZmMVHqebuJoA3MM7KvUhY7XMw
MzJcXrHQBoDq0lXWyvUicj7E95E9JYOwauUEquygzp3+k5XJLQdQciC4f1KhDRSU
lXus8s4J9QDCc/EaLK9mcsjou51OkfPZIY61+mjd19ZpOwRVN6RA8HFuwAkwLDYe
9GqIRa1+vV6JxIDOrK34AIY9Y89ggI4VA9pthlYp89v8n+DEwVz/TZRko+wyKXob
Uhj5dx5qsPDw50OT1fKIFLirQAIfOZzJN35wwPjEgpnQ6Z4ETqYK8cbxErZ4h/Lc
6SZcZPyp63kvniWlGIrUtUo0q5/atR36hJZ+vHFS3xu3ApohOVd6sKF+dvfHYWkQ
GVp0QBkYtcc5yZCKfssFGR+VZ0djgODqY6GTBBjTKaVgZNhk9LyQkVpIciLsTuO7
z0pJimX2g/XYZVS5aYj16eWF7/pwUEA=
=4dWK
-----END PGP SIGNATURE-----

Attachment: pgpKC2LFe5AOW.pgp
Description: PGP signature


--- End Message ---

Reply via email to