Bug#950453: marked as done (Mark debhelper compatibility level 9 as deprecated)
Your message dated Wed, 26 Feb 2020 19:08:02 +0000
with message-id <E1j722M-000H6z-Ai@fasolo.debian.org>
and subject line Bug#950453: fixed in lintian 2.56.0
has caused the Debian Bug report #950453,
regarding Mark debhelper compatibility level 9 as deprecated
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 owner@bugs.debian.org
immediately.)
--
950453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950453
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: lintian
Version: 2.48.0
Severity: normal
[…]
* Compatibility level 9 is hereby officially deprecated and will
trigger deprecation warnings soon. We recommend people migrate
their packages to compat 12 or 10 depending on whether oldstable
support is needed. Please note that compat 11 is actively
discouraged in some cases. (see the section above).
[…]
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.56.0
Done: Chris Lamb <lamby@debian.org>
We believe that the bug you reported is fixed in the latest version of
lintian, 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 950453@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 26 Feb 2020 18:30:19 +0000
Source: lintian
Architecture: source
Version: 2.56.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 950238 950453 952529 952539
Changes:
lintian (2.56.0) unstable; urgency=medium
.
* Summary of tag changes:
+ Added:
- nodejs-lock-file
.
[ Chris Lamb ]
* Check for NO_START and FOO_NO_START etc. in /etc/default scripts.
(Closes: #950238)
* Deprecate debhelper compat level 9. (Closes: #950453)
.
[ Felix Lechner ]
* Fix POD markup in man page; indent level caused literal display of
formatting codes. (Closes: #952529)
* Fix the selection of classification tags with -T command line switch.
(Closes: #952539)
* Use JSON::MaybeXS instead of plain JSON in the NodeJS checks.
* Remove and replace the open_gz, open and file_contents subroutines from
File::Path.
* Provide method for all ->descendants in File::Path and use it, retiring
breadth-first recursion.
.
[ Xavier Guimard ]
* Check if NodeJS modules install lock files.
Checksums-Sha1:
8118fa6352da8d66e16fb118c6c36d4f2b2fc7f7 4233 lintian_2.56.0.dsc
bac1efba1f1df0dfb48ed0966bcb64bf58d87664 1901024 lintian_2.56.0.tar.xz
ca68ba5db09bb6763fc550deba80e08e8a7797dd 16307 lintian_2.56.0_amd64.buildinfo
Checksums-Sha256:
e97a441bdbc59bc877ca9a70b5b5d806cb1d9ee5fc12024cda9de38cc2a7f91c 4233 lintian_2.56.0.dsc
e2c753ce891e92709a66d0a78ee79a0f8bd889a7dc88b04e78e5cb4ef6bc879f 1901024 lintian_2.56.0.tar.xz
b5a9d8e95752d96457cbf377df1ecdad72536c67c91604f947e6bb1eeddbc915 16307 lintian_2.56.0_amd64.buildinfo
Files:
7b5dc02d91db3cdb662886a0feda2d0b 4233 devel optional lintian_2.56.0.dsc
e5eeb1ba9e292e149e5bab8a28ecc2fc 1901024 devel optional lintian_2.56.0.tar.xz
aa8c8e5bee5afa6a0c7dd04e033f9e53 16307 devel optional lintian_2.56.0_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl5WvuMACgkQHpU+J9Qx
HlhRjQ/9HOsVUCOW2zPwOzClIG5pfZZNSbq2YHJKl+Rrhyl3VHfcoLZwtbhtdLWT
BFIUC0Z2ZrHJTs7Mh7RKi8Kp/xYBWIO8AA0uFLGWBojjgs1xMa57ng4FV1G4ykwL
Ob523TGO1lpInzDXSEwODdoJHr8H+dmok54hmxwKhoKb+e2/BfOUiB+ciQNPbQHI
B8LmFrmLgyCwCBkpGvO1rt41YO+O+b3c2U85BMavY89AfrTwMikE26cr6SohDqy2
VuWvjZUIY3NAH2bAwlDhb1E4Bs++h5jFWB8bc6u9leLu7/c/UPXHA9LylNMc5jHg
OszkieAzm1/V1iL9H+hVHR3JCQDe6VPSDR/w0gn8yqphnNSyorud6WkWhjSb86GJ
eUsNRwQ/C+g1mEcrwRgxtApWOlujGbOvBRh4/wjhOFRUeSyC2oa9BbzVpAhIMW9P
e+klJkElkjTM5IbrM0beF19eAusnac2fDBstokEfJ1h/BFYCqY90oWRdmZFiQRyz
dD6yu1PEUgkQTJ5rI8FIHOxQdT/E8+tuyFg4wnWrBYsvfxBh3aDrFvPY2KI9pnrb
LNze+QkeqcSLMwt6hbMbDXMq2jXacOtIMbKaeE63GvPqOWXXik4ut82LJWzsYUqk
pkw/FqwuXH/m2DqQ8G+eCGNm59YPcBAi5qC82lMVd6QM3qla15Y=
=Ohhl
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: