Your message dated Thu, 18 May 2023 10:02:05 +0000
with message-id <e1pzast-003aui...@fasolo.debian.org>
and subject line Bug#965877: fixed in wmcpu 1.4-4.1
has caused the Debian Bug report #965877,
regarding wmcpu: 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.)
--
965877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmcpu
Version: 1.4-4
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package wmcpu 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: wmcpu
Source-Version: 1.4-4.1
Done: Bastian Germann <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
wmcpu, 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 wmcpu 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:23:38 +0200
Source: wmcpu
Architecture: source
Version: 1.4-4.1
Distribution: unstable
Urgency: medium
Maintainer: Varun Hiremath <va...@debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 965877
Changes:
wmcpu (1.4-4.1) unstable; urgency=medium
.
* Non-maintainer upload
* Update debhelper to compat 7 (Closes: #965877)
* Drop non-existing URLs
* Convert to source format 3.0 (quilt)
Checksums-Sha1:
5b904652b894ee02746fab58dc37d8dcb6147b72 1561 wmcpu_1.4-4.1.dsc
0e27bc5098846661ae9019f4f1e5b1e5113c31bd 4720 wmcpu_1.4-4.1.debian.tar.xz
f874ffc5f9e2588856cf75742be57592380b72dc 6456 wmcpu_1.4-4.1_source.buildinfo
Checksums-Sha256:
4ec1b909d324d906aa12780fea2d9a64c1e81aaa6e896c3908a38f673868606b 1561
wmcpu_1.4-4.1.dsc
09f0f4fecfb1b7e9d008c7081ee8a2b5ec9f11bf1e65dc1bd94e687a32d2d599 4720
wmcpu_1.4-4.1.debian.tar.xz
78df5516a0980d43036e357d4a6aa88e805d4ef83d7827d0af4c734181461376 6456
wmcpu_1.4-4.1_source.buildinfo
Files:
85e7be537c4596389a2130a4fbe1945f 1561 x11 optional wmcpu_1.4-4.1.dsc
29210c86b0d1356b5e8400033b96aeab 4720 x11 optional wmcpu_1.4-4.1.debian.tar.xz
80ec25437408d960b07ae02d7fa785ba 6456 x11 optional
wmcpu_1.4-4.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmRl79cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDubC/9x3v9ihMuPt9E0v6vCk405dAkwrbkYKT2Q
gOI7ZbTC8jVsiwsbsEBKIMOGUz3FxdNQc/0C5KuUWBDOr32z7WpUmFFtDnb5HE0X
Bu/Uqv8z/8cBf7MheosgVAlknvD4qCGdXmWyOm88GpYQT1NyHdioqZdwI6Ky9Mlx
Ru2tB6wEWACeza7Tz7Rg+Hk7SBpPx3uvjU+Wec/uuPhLkJCezD+slwe/Pv6JdI/J
rdITD3BJoMDiGd6decVdftvsyXbxb5dvY7FtS40ETJR9dY8ukbcEPvWM4b1IF/PG
lDqhBSSXZhgUMltGez8jPFAB2omDgxdxhUMkF4mtk3FeY/t4eizJBKzVKdnEeLb0
i0zvr70opUwJth61DokVgg7PquPbkg98UkeVoHbyB4bxI5mgflaWLyQ/ocLHwazw
niAsbot0EwKGblJBzUSeQ90SKh+iZ2s92dLZWQWIK5tyZycdE/4Cvj8U9sLF4u08
y52jVf6Qo1XWycjncVH31ENUKzteMv0=
=hoJn
-----END PGP SIGNATURE-----
--- End Message ---
