Your message dated Fri, 13 Sep 2024 18:43:09 +0000
with message-id <e1spbg9-0015nh...@fasolo.debian.org>
and subject line Bug#1081537: fixed in fuse3 3.14.0-8
has caused the Debian Bug report #1081537,
regarding fuse transitional package is required for upgrades
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 ow...@bugs.debian.org
immediately.)


-- 
1081537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fuse3
Version: 3.14.0-7
Severity: serious
Control: affects -1 src:fuse
Tags: patch
X-Debbugs-CC: j...@debian.org

fuse 2.9.9-9 stopped building the fuse binary package. The fuse3
binary package has Provides, Conflicts, Breaks: fuse. This is
insufficient for apt to be able to perform the upgrade. On my system
where I installed fuse (to test this issue), apt was unable to upgrade
libfuse2t64 to 2.9.9-9 without manually ordering it to install that
upgrade, even with  apt dist-upgrade.

We need to add a transitional package to handle this upgrade. For the
transitional package to work, we need to remove the Conflicts and
change the Breaks to a versioned Breaks. As suggested by Julian, I am
using << ${source:Version} to make backports, etc. easier than
specifying the exact version we need.

I am attaching a patch in my follow up email so that it can have the
correct Closes annotation. This upload would also close several other
bugs so I'm marking that in my patch too.

Thank you,
Jeremy Bícha

--- End Message ---
--- Begin Message ---
Source: fuse3
Source-Version: 3.14.0-8
Done: Laszlo Boszormenyi (GCS) <g...@debian.org>

We believe that the bug you reported is fixed in the latest version of
fuse3, 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 1081...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated fuse3 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 13 Sep 2024 19:31:58 +0200
Source: fuse3
Architecture: source
Version: 3.14.0-8
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 918984 927291 1074767 1081537
Changes:
 fuse3 (3.14.0-8) unstable; urgency=medium
 .
   [ Jeremy Bícha <jeremy.bi...@canonical.com> ]
   * Provide fuse transitional package for upgrade (closes: #918984, #927291,
     #1074767, #1081537).
Checksums-Sha1:
 71997a43e6f50c39e5c22a2dfb3ec16e37376d26 2431 fuse3_3.14.0-8.dsc
 c3fa56067786b3a3fb45dc74fe08203566f006a7 18300 fuse3_3.14.0-8.debian.tar.xz
Checksums-Sha256:
 9246bd3230b171d576c6ed5a89b4f8bfdf703d5dfa202d8c1de1f044178718d1 2431 
fuse3_3.14.0-8.dsc
 b5c7d87dabb3ed15a6c7888b5c3503386eb8e345fbce1b0c6ae1eeaae8ee04d7 18300 
fuse3_3.14.0-8.debian.tar.xz
Files:
 9ba61d5c0e40c792451ef40c47f2ab4c 2431 utils optional fuse3_3.14.0-8.dsc
 af21ebdb3ea8e2efedb4b7da3ced9c8e 18300 utils optional 
fuse3_3.14.0-8.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmbkeoMACgkQ3OMQ54ZM
yL/BLg/+M0m5YOZsbqy6Hlall3CG/jVniDDsKOTTdI261bD3qZAIpbimgFtA3nwb
RY3fjM3leUsp90v2aM7HPULzX7bDLAjMG4CadKF7veEjRILLB/nd4aqLhhkt31np
BgIDRfjvxua5mtF9aMxWw+7m6ecAFMM8apEAmxT81Uun5fC6pK9X5GSGiovGWbO6
S2k29NNEUSoKz0IXIuBBFOPzKVsb4QP2ju43t+TAofaX7Ymw5Mlf+e7TWG66p1UZ
Usd9QMsLu+iymePver9S4CWZM4ZAgLoZmw9bRSvL/GQqmu0pZ4+gGR0bRYE865s4
0DlvKujlelFsk99IV+aa+A05mtaL7JeZDmjd3RPCN97/JdG6DKSY0gmnpzLBbTQ5
NL34cHtV/g+2ZwjwDDHfv4if73i3vwB1CdU3HgOEtY3Faneg1O5GgfBUYKW3q1ET
uMXV3LroSJZpr2npwfPFAGx0/Ll/BYS5l3S4L/MPzTXl4N4WPUCdIDaQ1vXXeUsN
ztniOyg5SuXhLD2nYQuOYpD+llO7BJqF38oCrr9Di57Y89DLV/8BwD9k+3OfD0BL
LsZ/MHb1OtpwfwqaGpoS3R0i8N0o86pO6h2p2gIW64d2AeNcrQQwtJLOINWCCsfj
qu48i0Ee1iW0IM6GVz/685ulzF+10qSzS2lhZ/sevdg8vKj9PeY=
=RvrK
-----END PGP SIGNATURE-----

Attachment: pgp6pdJ3dZdMU.pgp
Description: PGP signature


--- End Message ---

Reply via email to