Your message dated Tue, 11 Jan 2022 10:18:36 +0000
with message-id <e1n7eee-000atu...@fasolo.debian.org>
and subject line Bug#965406: fixed in afuse 0.4.1-1.1
has caused the Debian Bug report #965406,
regarding afuse: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: afuse
Version: 0.4.1-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package afuse uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.

--- End Message ---
--- Begin Message ---
Source: afuse
Source-Version: 0.4.1-1.1
Done: Adrian Bunk <b...@debian.org>

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

Debian distribution maintenance software
pp.
Adrian Bunk <b...@debian.org> (supplier of updated afuse 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: Tue, 04 Jan 2022 17:02:06 +0200
Source: afuse
Architecture: source
Version: 0.4.1-1.1
Distribution: unstable
Urgency: low
Maintainer: Varun Hiremath <va...@debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 965406 974614
Changes:
 afuse (0.4.1-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/compat: 6 -> 7. (Closes: #965406)
   * debian/control: Update Homepage. (Closes: #974614)
Checksums-Sha1:
 aff04ff433d911c5a38cc1a2c19acd4d076f1fd2 1821 afuse_0.4.1-1.1.dsc
 550054d253f9fce2c3d4ae20e81fd4bca3373737 3388 afuse_0.4.1-1.1.debian.tar.xz
Checksums-Sha256:
 324d2e888d16bfa815a516670cfbfc83260c2df0fc1af7e8302eda2382a0fcfd 1821 
afuse_0.4.1-1.1.dsc
 dc8653c1e1b30289808a33d3eebfaa83fd3a597e2f6c2c3275245bc8326efe22 3388 
afuse_0.4.1-1.1.debian.tar.xz
Files:
 fecf21055880f17d58ef4bdfd76b8327 1821 utils optional afuse_0.4.1-1.1.dsc
 eb7ae08bf9423a51d7209fc83fc18960 3388 utils optional 
afuse_0.4.1-1.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHUYgoACgkQiNJCh6LY
mLH2aBAAtUEk9i2wDV3CR7x0V+qV8ivEVrqTMERt8Yhg1Ii0+WOha5ZwsXIMk/at
c6smB5vxE8fHBHLz8Sv5/60bw/qHb4u64BjQjlSO1K1ileLHH/6UDs7rrxwixw2E
IxjftT7M6IgznGmNF8gyugcUWdHqzk0HvQAV8MfYYB8uJhoaXDc1Eecf9PJqU6ba
iRJ8ZZQ9tE+iPeqYJE60Gn5ncmi6IhRvf8uxvDxNHkG5Pk2YgP9MEQuquluFlPpn
Z9xilo5n2EjM3yUz+NCOYOz6zEJ+SWPxU7ZbDidCGSDz1Yk1at3MmXNAj3rZuWjF
L+eVDi0X+OSnxAOjiyGqhsniBuZpvM1zQXYqqJtNU0Oc9C9Gw6xNh6pK8MD7IC5Z
3yjcbOMQRuCLj3iolKMf2QIoN/pJkYALKmFdlc+qMD2gGOtAcYULq8gd7yYnoIiT
MsaDieEobLpul9f27+lahOGDTwChzHvtWSaDmbcWRlzuK8Gcz2GIRjB4un2HJMjl
gkRX9Jv8t6Stf21wh5w2pdV6WSOTxz5y1+s4Qm7jkJh3IM2xNjAwWZREDUjwhDgu
qnG/SmR/U7NT5qzceeQzL0KNNwP6QNxEFDDhBIhRxD6Efc529hHMli9EoSVu2EUW
8/xIkwv/Ukc18rpYkFxjkFNB1S0PnGkIu1kTKWgZ9WIgwDbuNqs=
=+5Nz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to