Hi,
First-off, a general reminder: it would be great if changes affecting
many packages could be discussed on this list before being pushed
across a bunch of repositories. That doesn't mean anyone should be
blocked forever until a number of positive answers are received; merely
that a heads-up can help people suggest different solutions, and
sometimes advise not to implement a given change. And of course, that
lets people know what you're working on.
Now, spotted while working on apt-setup/hw-detect for non-free-firmware support:
* Set Standards-Version to 3.8.4 (checked).
I understand the longstanding issue in lintian (#991533, just poked) has
been a pain (especially for those uploading many packages, I fully
acknowledge that!), but adding a field just to work around a bug in
lintian feels wrong. This was discouraged in the thread around [1] last
year.
1.
https://lists.debian.org/debian-boot/2022/03/msg00120.html
The aforementioned version is 10+ year old, and I'm not sure how
packages could have been “checked” against it, since udebs are clearly *not* policy-compliant. So it looks to me that wrong metadata was added
to silence a tool that's wrong in the first place.
I intend to revert those changes; possibly automatically, which might
end up resulting in the relevant entry being dropped from a released debian/changelog entry if the package has been uploaded already since
the commits in January; while not ideal, I'm not willing to spend much
more time on what's been a huge time sink already.
The only packages where this field makes sense are packages which build
at least one deb binary package (not just udebs). For those, compliance
against current(-ish) Policy should be *actually* checked before adding
this field.
Cheers,
--
Cyril Brulebois (
kibi@debian.org) <
https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmPOkFwACgkQ/5FK8MKz VSAn4w//TB5xuvIh8PiiG1laTSF/bSJ94Ov9w1ZUCHukMOu7Op0JksszGq9gv3CS mI1LLaEdTPNIfcxDkqGV23QwE934TiOMgYueg/0qBp2kGEjoanybEOlmm9DIK0r3 MzSxatpGr/vAcdxNhm75Hson3hCzzH9mXFurViPJf141hVNTV0UncPxNvXwYiMeA yMjTdH32b3kIrrwX7OxTFapTpSu1RY5MJfNoejYDgwAy5B6v5SytWkGtXFmn+Oz6 xyxjGsjcJU79d4yQeHmgu+x3ad6GT4DB4P7VYa1N5zlblTsQskY94SW47/uz+N7J bVVbWLXBsvyrRZvnzociH+nrmbNwCj6nA/3oXJtlcPAFy2nzwnf6eOEKvl/sTmWn X7gSBIRbILDgS8gl08qEmW8kD85NHcZquxyqX4NEqZDElBWt2brNbwDhFHRADjAv 3SdtB3eTQcyPVyKcB+YPcx3BqcVvb8GwUN/Og7H00EnE7IlHu1k4VOGzMLQ6J5wZ ZV4v3skOAtSrt4X0C+MH5gHGO0U7XHr2FeoodIF0o8AjR6NMcwc31dh/V7MYGxUc m82N04qPs41l7mOY5GsslM6TDWGNiusqhGFzHH9lZRwOHJJ7gJTJPT38mSz7vqNe 7n+K/RbsP6+tCCb74HPYYO9dTsz+V6GY1xAo/d3PwRC7Y2nAEk0=
=C+B0
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
*