Your message dated Thu, 18 May 2023 09:38:30 +0000
with message-id <e1pza5e-0037qd...@fasolo.debian.org>
and subject line Bug#965879: fixed in wmdate 0.7-4.2
has caused the Debian Bug report #965879,
regarding wmdate: 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.)
--
965879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmdate
Version: 0.7-4.1
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package wmdate 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: wmdate
Source-Version: 0.7-4.2
Done: Bastian Germann <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
wmdate, 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 wmdate 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: Thu, 18 May 2023 11:08:20 +0200
Source: wmdate
Architecture: source
Version: 0.7-4.2
Distribution: unstable
Urgency: medium
Maintainer: Varun Hiremath <va...@debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 965879
Changes:
wmdate (0.7-4.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Update debhelper to level 7. Closes: #965879.
* Convert to source format 3.0 (quilt).
Checksums-Sha1:
71c7a67341064756ba9855eeb3c6bc0df960dbe3 1797 wmdate_0.7-4.2.dsc
26aa3dbd0c356d3bbb9242f43d160e0d6504f04b 4336 wmdate_0.7-4.2.debian.tar.xz
47f83fb397798c342ed9147f728a9fb599481f89 6550 wmdate_0.7-4.2_source.buildinfo
Checksums-Sha256:
8c921c33a16100f427aaeeb6cd07372784b2ae060018add774426dcde3db27be 1797
wmdate_0.7-4.2.dsc
e810c75580ba159e709d84c534d07dd89648f43929376492ab87cc26a7091bc4 4336
wmdate_0.7-4.2.debian.tar.xz
0d4a7413295732dc82810901aa072e06b48383e765b747ffec9df5bb7f587b0c 6550
wmdate_0.7-4.2_source.buildinfo
Files:
323a2f253cc4eb27c6a37a92477e9743 1797 x11 optional wmdate_0.7-4.2.dsc
ca0665a9b512959b06624e55a9499214 4336 x11 optional wmdate_0.7-4.2.debian.tar.xz
2802feffd8a2ee37c572261cbfdb577c 6550 x11 optional
wmdate_0.7-4.2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmRl7BIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPuuC/0XyEiaxX6hIqKao/MSkosLXz+8Hn23roTv
1ARO6GQlWDAH1PeRQS/VPY752akdjzBA3nSXXr1ZETrudB/jYGe03HXBiJG+cuPn
gaOry7X68gtxAphK/gXSnBPWgwCLIfi5+zwIz/CSprPk5lWJsn0Cc3O8hNN3A1CU
aDh/k88qGMxYz02g0ewioHu7DRX0AapJ1hO6RZTwmTz5ruVsOL5wJD3mWIuToFgz
W7k00qcyBC53GZFUzFTUSx9+ITU77VdMCvqLpW1Wodmy2SOAxEj01DU1KDQ/OFR0
j3atNhf8n49AMSNPDa2bC/eoqeA/DesLOMFYI5VsBZKbYwKZWilY73c27imTNPQM
HYiCzHq0bEi0uXGN6meX66gVPpupfu63kFdk8oSeOi4kS9zhrfxjT2qhK703dGwQ
wPLNj4ocDj0cy7sXSJcNCNH14MBKy9ZBmKTXQ6f52CmKqLjx80vEgUQolC8DmKHZ
GFKXmBjdM7pfQR4x9gQjI8EOVOt9VCM=
=VsXv
-----END PGP SIGNATURE-----
--- End Message ---
