Your message dated Wed, 17 May 2023 21:18:46 +0000
with message-id <e1pzoxm-0012mk...@fasolo.debian.org>
and subject line Bug#965516: fixed in fapg 0.41-2
has caused the Debian Bug report #965516,
regarding fapg: 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.)
--
965516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fapg
Version: 0.41-1
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package fapg 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: fapg
Source-Version: 0.41-2
Done: Bastian Germann <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
fapg, 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.
Bastian Germann <b...@debian.org> (supplier of updated fapg 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: Wed, 17 May 2023 22:57:50 +0200
Source: fapg
Architecture: source
Version: 0.41-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 965516 999118
Changes:
fapg (0.41-2) unstable; urgency=medium
.
* QA upload
* Update debhelper compat to 7 (Closes: #965516)
* Add missing rules targets (Closes: #999118)
* Convert to source format 3.0 (quilt)
Checksums-Sha1:
a5cf56382d9fefddabba0af5c0d9e66391248118 1543 fapg_0.41-2.dsc
6f40a92bd240dd8d9f7562ac923999e55eda9eb7 2572 fapg_0.41-2.debian.tar.xz
59183537d07f032c30d1498fdcfccdd436218f08 5489 fapg_0.41-2_source.buildinfo
Checksums-Sha256:
69ac1a94db74fcb74f0840096ae90fb417747a6ca0345410b89fe3bea7c13ffa 1543
fapg_0.41-2.dsc
528e815b627b1d269aa482ea8e92112e64f6489c2c0e35984cc60a41257282ec 2572
fapg_0.41-2.debian.tar.xz
83b84139aacdcdcc92c96dc3eccf874833214b637a1162bc424f4eecd28a7610 5489
fapg_0.41-2_source.buildinfo
Files:
7bf8b982f371a7d2f3fdfd4c20932d80 1543 sound optional fapg_0.41-2.dsc
290d77a190eee8b9cd67e5331cd976fe 2572 sound optional fapg_0.41-2.debian.tar.xz
26a9a93d05ddb090f69eec3127b7603f 5489 sound optional
fapg_0.41-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmRlQTAQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFFOJDACyJaSwMmr+F23+CHtc7entvKRiT3przRuB
LZo9zop+uR7rQ4Zg778/N0YVvgbj0Za2/VAWqeHZQQvngvDePEGJsmUQXUFMYP/l
IBgQcHQqZwrX4Jt5re37z3G0GHrGwTQXIXGko2Tfd5bXG1+RFapBqKGxJP4+JKcD
Foaf8CKC5juxjeP9ZxzrwI/N1yMuEZueTLLpoKf22WAIsUdcCpLQfzIs/amlv71U
ojMZsLnuBWDKrEMoBEnuRptVt3/jusEvsr79ZWbqISXdW/5/7uak9u9hkQv+Cpdt
MipU/E5kV8+JsFmVp9E5V1lSUdJHbysUA99WatCNiLD2841jBkk/fvqpEzRvWTwC
+0h2kWAbyBnd2GZsDbwW5oZfX5/aeZ38b0l1U7LmN1EgP0geVY7hi7lRr2r/O+a5
cdneSMqKc8yYPp5dOFz+BHYOLm9TkuGk5J3iaLksZw0WZtRmNbaGxXuumyraBW2g
aibVKt6OZ9wNNiBxzAQCZbC+uIouLUc=
=O4s4
-----END PGP SIGNATURE-----
--- End Message ---
