On Mon, Jul 20, 2026 at 9:39 PM Maxwell G <[email protected]> wrote:

> Hi,
>
> Thanks for the Change!
>
> I do think it should be reclassified as a System-wide Change, as it
> affects over 500 packages across ecosystems.
>

I agree that if we should update 500+ packages, than its a system-wide
change, but for
that type, we are already too late and as mentioned, we are not happy with
the name.


> Jul 20, 2026 9:03:28 AM Aoife Moloney via devel-announce
> <[email protected]>:
>
> > * Update gpgverify BuildRequires to openpgpverify
>
> Note that some packages pull in gpgverify via BRs on gnupg2 (or any other
> virtual Provides of that package) so we'd have to figure out whether
> those BRs are only to pull in the macro or also for other usages of the
> gpg command during the package build when changing them.
>

Yes, this adds complexity and package maintainers are the best to evaluate
this case by case.
If we change macro under their hands, they will not have a chance to
evaluate. If we will come
with packaging guidelines, macro a PR/bug report, it should be more
straight-forward (and it can come
separately over the Fedora 45 lifetime).

I think it makes sense to handle this by filing PRs and/or using a
> Bugzilla tracker bug instead of pushing mass changes directly to distgit.
> If maintainers don't respond to PRs after a certain amount of time and CI
> is green, a provenpackager can still step in and merge them.
>

Agreed.

Also, are there plans to backport this to any of the EPELs?


We did not discuss this, but we have people interested in building from the
same spec file for
all Fedoras and RHELs so we might eventually pull this into RHEL somehow.

Jakub
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to