RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1650286 +++

We currently label modular RPM builds by filling the DistTag header field.  However, it turns out this field isn't entirely unused:

https://pagure.io/modularity/issue/113
https://github.com/rpm-software-management/rpm/issues/589

Therefore we would like to add a new field for our purposes, ensuring we don't run into similar conflicts in the future.  We use this as a bool to tell modular and non-modular builds apart when the repodata isn't available but we also use it to store the original module NSVC for accountaing purposes.

I think ModuleTag would be a reasonable name for this.

Please, also ensure we can set this field for both binary and source RPM builds, preferrably via %{moduletag}.  We also need to be able to query this.

Per some earlier discussion on this, I'm adding blocker?

We need this change to land ASAP in order to lay the groundwork for marking all

Apologies.  Hit submit too soon.  Continuing where I left off.

We need this to land ASAP in order to lay the groundwork for marking all module RPMs at build time.

It's my understanding that this is a quite small and low risk change in RPM itself.  If this is not the case please indicate so.

I would appreciate if you will not clone bugs so I don't get subscribed to bugs I'm not interested in!