Re: Bug#1068809: Any reason to (Build-)Depend from dh-buildinfo in ecbuild?

[Santiago Vila <sanvila@debian.org>]

El 28/11/24 a las 0:07, Holger Levsen escribió:
> On Wed, Nov 27, 2024 at 07:17:24PM +0100, Santiago Vila wrote:
> > Because the fix you have in mind involves bothering a lot of people,
> > or worse, a few people with a lot of work, while the intermediate
> > status proposed by Bill fixes all the undesired effects you
> > have listed before.
>
> but then I will still want to bother all those people^wpackages
> eventually.

Such process has already started. наб has already reported several
bugs (with severity:normal). Maybe this is not very orthodox without
a MBF email in -devel first, but so be it. I think "normal" is completely ok
at this point.

I hope наб (in CCO) will find the way to tell Jonas about his 150 packages
without filing 150 different bugs.

> that said, I now can see how the no-op dh-buildinfo helps to bother
> less people^wpackages, eg. those which then can be fixed with a binNMU.
>
> and first, someone needs to actually make dh-buildinfo do a noop,
> which hopefully won't bother it's maintainer too much.

I've proposed a patch to the maintainer (which you can read in the bug logs).
I hope he accepts it. If someone else can propose a change for the extended
description, that would also help.

Thanks.