Control: tags -1 + wontfix
On Sun, 2025-03-09 at 09:08 +0200, Martin-Éric Racine wrote:
The newer-standards-version tends to be printed by mistake, usually because someone upgraded their packaging according to the latest debian-policy before a new Lintian got uploaded to the repository. What Lintian should instead do is source the current Standards live from Masters, and only issue the warning if the declared version is newer than that. src:routine-update already has the code to perform this.
lintian must retain the ability to operate offline, so it has to include debian-policy data. routine-update is different in that it's designed to connect to the internet and fetch a new upstream version, so it might as
well also grab the latest policy data while it's at it.
The issue here isn't bringing lintian up-to-date (that's easy), it's maintenance. I've requested access to the Salsa repo for lintian so I
can work on maintaining it since ~6 weeks ago, and still haven't been
given access nor a definitive response.
--
Maytham
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmfNRpcACgkQ1ZeJcgbF 8H8dPRAAjyi+4DAy2Bf8iufwS70iFo4dnyN9LTXf5N2x7QPCRMr/TB3iGtPvVdAS kxWba0zI2Cct23MUSC0+n6EQEtBNpPwXd64A73KGcZrMty/eMibX5TUilYUkm652 619LPESz2+6RllYNQGH2iayxfqQYV95cRF+Lx/qcmRWPATUix7QSQo7lFCx/hqFb ABmyb0eGIopDCtDtpUcVL/NAdX0MYfcP1wDe6aBSnQfflervDHHOKDPZRtow9veE PvOwWzGYWl4SyDAh3iRZ15/ukTnOj4PAmm5wnbFUg/qh58VZeQuGBVBB2s8kFQRH 4AI64yHSEnrlnH5UqXjjPOcP1Q6nm7fj1LJTJ23nxa+8VzkkqQ/OGOMiACvV9pD9 X+9hOru3GKjgDlPLncBJCKzRrDBdn3ZCALgLqQvTrWb4aE3WvYkp8V7YkK0g2n+b 5+pMoca4WghInf9W6KAfcEvpujd8hzD3tjZ5gRY5oFUxI6Sx6AkazxSIjXF6YKIW Ar8saIMFzjqMia+QV99KyVcQ5U8VIG4pOeyamxcwbVSJKSedgVrS7IiqgGfv0cQ5 agp62KYyKSLRf+foX6vM+QrCnZ0WkqR6klbCbL7CX0PE6zMF7ZwzAYiH5meyh6/o KpUNDBASn3+WV3eL1ZJ0pcT4YC9hmp7tPI7q/5uUMTmOeaw/wcg=
=khDY
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)