Your message dated Fri, 20 May 2022 21:04:07 +0000
with message-id <e1ns9n5-00067o...@fasolo.debian.org>
and subject line Bug#965798: fixed in redland 1.0.17-1.2
has caused the Debian Bug report #965798,
regarding redland: 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.)


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

Hi,

The package redland 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: redland
Source-Version: 1.0.17-1.2
Done: Sebastian Ramacher <sramac...@debian.org>

We believe that the bug you reported is fixed in the latest version of
redland, 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.
Sebastian Ramacher <sramac...@debian.org> (supplier of updated redland 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, 20 May 2022 22:42:52 +0200
Source: redland
Architecture: source
Version: 1.0.17-1.2
Distribution: unstable
Urgency: medium
Maintainer: Dave Beckett <daj...@debian.org>
Changed-By: Sebastian Ramacher <sramac...@debian.org>
Closes: 965798
Changes:
 redland (1.0.17-1.2) unstable; urgency=medium
 .
   [ Sebastien Bacher ]
   * Update to dh8 to fix the build (Closes: #965798)
Checksums-Sha1:
 e410b24c2f50ad78dc9b73ebc7ae67aada1d0008 2353 redland_1.0.17-1.2.dsc
 6daa54b2285cfc17ad8a6f52d8e2022eae65923d 8344 redland_1.0.17-1.2.debian.tar.xz
Checksums-Sha256:
 14f0efb4fc57ea78b7100f6ea6db5db7126810f4ee860e4fa336b69aac9e0aa3 2353 
redland_1.0.17-1.2.dsc
 61943ab1101cb8bd1bf5d5809a521c78f3e52c00f310f6fba5779720d9fda8ae 8344 
redland_1.0.17-1.2.debian.tar.xz
Files:
 31cfd23a0a57d4f44d90140a959cc39a 2353 devel optional redland_1.0.17-1.2.dsc
 7787c2cf11ab9af83a677800c690bbeb 8344 devel optional 
redland_1.0.17-1.2.debian.tar.xz

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

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmKH/jUACgkQafL8UW6n
GZMmfg/8DSmHzPCepplfaj/o0pwCxfr0IDCn4mdSnRgvImUh8qZD1N3/kJJW67ZR
xG2crGdS0oh2nRvUo5+2oAB7w9t2LLi3cFZyzbvTg4qbFIHsWKKAa9IMd6U8thxc
QG2H7gNQ4GMPg1tx9fSyTTdfbHnTJNGIfwMVZYznip+zZng4V7KaWliKpyiOzXxC
1fSbYk9HMwu8khBN+0a8g6fhCjLzd6p8fe7Yzi/uNAYwXjwTEmKlcrtniQ/JTrhf
AxvZtJsAxuIRsuvUaSxUD5sa/HkL2hKqC+cxSo0l3LdfYSvX1a5CN9PmYyjp2The
MdKSv8DT0n1dyNhwAtQqMkKNzUP6JyQBYRJHVr3Nnt8FXv6Jo+L6/TNapWEQ/58f
PfGZQB+BE8NNjYLXLUAiKc2a0NqjqVMEcy2BQh7xBnWKgcJEpI2JEI5rQLpgTx4w
+sin4n6i3knAKM0gxQc7CwBbovd4zPLlq1jeS+FrHSTK7KEc5DEWW+BqZmyL7FkF
uHYu0YMoBrvLor21GF4A4m+Wuglghqthn3QMDRxfi6HBEwYPvQQTx7Og2boM/WYo
R1GGP20atQh8YhnG9MeERnvOaFnzZLJ/dQlYzNnzGa5eSTRXJosY/aqZZO77ceKf
e25dUIsD6XT7U9P6ZIde+W+Ut4xybU1YNI8dED2hfFlXIwa9ho0=
=vLL3
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to