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.

We need the capability of removing a package from a module and including it as bare rpms in appstream.

Here is a usecase (but it's not just related to this):

libslirp is being staticly built and copied into every qemu-kvm build (RHEL and AV). A copy of it is shipped along each qemu release.
A few months ago container-tools:rhel8 started to ship it as a library.

We want to start using that library, but we can't. Because it's shipped by a module that contains other streams, like 1.0 and 2.0. If virt:rhel starts depending on that library, if the user changes to container-tools:1.0, it will break virt's dependencies.

The simplest solution for it would be to move it AppStream as bare RPM. 
But dnf behavior of not allowing modular to non-modular packages upgrades makes this very risky

This is one use case, but we have others. We want to move some packages from virt:rhel into AppStream, so they could be shared between virt:rhel and virt:8.X.

But they all can be summarize into this: We want a way to make a transition of a package from a default module in RHEL to a non-modularied version of it.

*** This bug has been marked as a duplicate of bug 1805260 ***