On Fri, 14 Feb 2025, Guillem Jover wrote:

>> >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?
>
>This is not how Debian Policy has ever worked. By that measure
>packages could not rely on multiarch or triggers to name a coupled
>of examples. And Policy changes in general tend to be done after the
>changes have been implemented and deployed in the archive.

That’s for things which Policy didn’t describe yet because they
were new. But if Policy states a definite value, I *expect* the
tooling to adhere to that value.

>> 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.
>
>The problem that triggered this report was only surfaced by the R³
>change, but it is not really directly affected by it. The real problem
>is that the R³ change made it possible to skip calling the
>«debian/rules build» targets, where the affected package was already

Yes, I know. I’m sorry for having a life in which I needed a quick
workaround for this dpkg RC bug in the package first, since that
affects actual users, and that it takes time fully analysing what
the packaging I only inherited in the first place does wrong, where,
and how to best fix it, plus openjdk-8 takes a full day to build on
my hardware. (Less with nocheck, sure.)

>Policy buggy, but the breakage was not visible. If the R³ default
>would get reverted, but the change to call
>«fakeroot debian/rules binary-arch» kept, the openjdk-8 package would
>still misbuild.

I know. Doesn’t change the fact that dpkg’s change breaks packages.

Would you *please* at least read and consider the alternative
solutions I pointed out above? Thanks.

bye,
//mirabilos
-- 
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design.  <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)

Reply via email to