On Fri, 14 Feb 2025, Sean Whitton wrote:
>Policy has to go through binary-NEW in order to be released. So there
Technicalities.
>isn't a quick fix here.
Not looking for one. dpkg should revert this until then.
>This bug does not count as RC just because Debian upload bureaucracy
>hasn't been performed yet.
If packagers cannot rely on Policy to give correct information, what
*can* they rely on?
>There is a clear agreement that the default value has changed.
I’m still in a place where I question this, and diziet apparently
also is. This is going to cause untold amounts of headaches in both
downstream distro and third-party packages (including organisation-
internel ones).
dpkg introduced this build api thing. Use that.
Or, if you absolutely must cause more useless churn on package
maintainers, at least forbid not setting R³. But don’t silently
change the default to an incompatible value.
bye,
//mirabilos
--
Yes, I hate users and I want them to suffer.
-- Marco d'Itri on gmane.linux.debian.devel.general
