Your message dated Tue, 26 Jul 2022 16:49:22 +0000
with message-id <e1ognki-00053r...@fasolo.debian.org>
and subject line Bug#965765: fixed in pacparser 1.3.6-1.3
has caused the Debian Bug report #965765,
regarding pacparser: 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.)
--
965765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacparser
Version: 1.3.6-1.2
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package pacparser 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: pacparser
Source-Version: 1.3.6-1.3
Done: Adrian Bunk <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
pacparser, 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 pacparser 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: Mon, 25 Jul 2022 00:20:17 +0300
Source: pacparser
Architecture: source
Version: 1.3.6-1.3
Distribution: unstable
Urgency: low
Maintainer: Manu Garg <manug...@gmail.com>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 965765
Changes:
pacparser (1.3.6-1.3) unstable; urgency=low
.
* Non-maintainer upload.
* debian/compat: 5 -> 7. (Closes: #965765)
Checksums-Sha1:
89e472bfc92e1d91dc5f7b5a8639d330454663b6 1884 pacparser_1.3.6-1.3.dsc
27ee737f5599943eebf641990994d07493bed597 4408 pacparser_1.3.6-1.3.debian.tar.xz
Checksums-Sha256:
247ffd1fc2b0bd52ff27c09f0fb4bcb4a0f43fab43d011f9cc93b1f3471a685e 1884
pacparser_1.3.6-1.3.dsc
0d2446812c81db3726c7633978430747bacef90085d883ab64ba7d15e9548db9 4408
pacparser_1.3.6-1.3.debian.tar.xz
Files:
365a63517983221f5443b3e299b14d40 1884 libs extra pacparser_1.3.6-1.3.dsc
cfa0cd021680b453df8b1f304a5fe011 4408 libs extra
pacparser_1.3.6-1.3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmLdt/AACgkQiNJCh6LY
mLGRyRAAgjTgs3lvoh0+wZzgACJlGCu6Mot1Vh1C48khi12JUASq9xw/DfpI+Hmr
oolQ9Jr0sJlGpRBDA0/oDEG3DP1vDv9G1xNTQ0fzgIppJxkGvSMrKNVA3N8HCrHs
cmlqh8ER0sicTJuO2lxJN5BDaeOdIOjCSBNeWZ0M7mpLPu9AgPBAqkVAx3t5HmK+
rude7riDBIIDTF4lBi8CN/4qAhAhKsprUJDaLKoRLcdaiaSAaXGNwLlHMZBSoUsR
6DijGfoHmTIoZnUvpy/uhlZp7OGkiQgjrjE9X3mfxFUUVlLhS6vd1KFBGjnXgVqy
JA0Q1MJ/FUpMAFxJe008pA7I+o6HjctZZuq39OC0/UgbVjfgkbs10Qab6Dnhg62y
KEGNCwmnS65ez8Pw5qx+6/i4K74Wdeyy7KRlnnQpTSP29XeWVEDvL9yYXev5v9FR
0ZR+1IN0kwAZcRtvpnVv6HHuE3cWvbfbz+ZcZov91WnOpjbxwi0vF54P2gVlhHxf
I5pHnwpgl4+3dU4ZcCbxs+MQHcKCE984kf+fRdcbEa35dP3NwsLimtiFSQIQEYq4
LnEsnTjuIIOFYcSmlPaxdhP0zqlgOlNuJU7jhbPfw307LerpPFVjvilzu4zscpEa
x1r504FT6vGKCHjsl3mfFG9FteQ+vRp2w5c5LDYcwW8C6wC/ei8=
=Y9q6
-----END PGP SIGNATURE-----
--- End Message ---
