Learn more about these different git repos.
Other Git URLs
Describe the issue Currently there is an overlap between EPEL Modular and AppStream both offering a 1.20 module stream for nginx. It has been reported here: https://bugzilla.redhat.com/show_bug.cgi?id=2036439 I have since corrected this oversight on my end: https://src.fedoraproject.org/modules/nginx/c/72ba87cd0f4dd749bd750a10db01b0a5aee5d593?branch=1.20 I have further corrected this for the 1.14 and 1.16 streams as well. The 1.18 stream had an exclusion for epel8 which I have now corrected to el8. I believe untagging of currently tagged builds needs to happen before the issue is completely remedied. I would kindly like to request some guidance on this. The mainline stream is non-overlapping and is left as-is.
1.20
1.14
1.16
1.18
epel8
el8
mainline
When do you need this? (YYYY/MM/DD) No timeline set
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? EPEL Modular will continue to have an overlapping module stream with AppStream.
It looks like the 1.14, 1.16, and 1.18 streams have been removed from EPEL. The 1.20 stream remains.
Is there any specific reason why this still hasn't been fixed?
If there is anything on my side I can do as a maintainer please let me know.
I don't think I can untag builds myself and as far as I am able to tell this is what needs to happen for the EPEL module stream to disappear.
Right now dnf module install nginx:1.20 leads to the module from EPEL 8 rather than from RHEL 8. Using dnf module install nginx:1.20 --disablerepo=epel-modular works temporarily until the next dnf update.
dnf module install nginx:1.20
dnf module install nginx:1.20 --disablerepo=epel-modular
dnf update
So, I would be happy to close this out, but I have no idea what to untag or even if that will work. ;)
@ppisar can you give some guidance here? Should I untag everything from all the module-epel-nginx-1.20* tags? Or should it be just obsoleted in the metadata? or something else?
The following should fix it, we need to verify it after the next epel8 modular updates compose
$ koji untag-build epel8-modular-updates nginx-1.20-820210421185110.9edba152 nginx-1.20-820210908185433.9edba152
I'm not sure how exactly modules are tagged, but I believe that untagging nginx-1.20-* module builds from epel8-modular-updates is enough.
Though I can only see nginx-1.20-820210908185433.9edba152 in the repository. I don't know where Mohan found the other build.
ok. I only see the appstream ones now... can we close this?
I can still see the module in https://dl01.fedoraproject.org/pub/epel/8/Modular/x86_64/repodata/3b56eab5adb7c2aa0b47bf220de2ca71aa016170e24f04c5a894a0a694fe56a3-modules.yaml.gz. It's repository state file points to /mnt/koji/compose/updates/Fedora-Epel-Modular-8-updates-20220623.0.
Ah right, we need a epel8-modular compose... and bodhi is only going to do one of those if there is a modular update. The last compose was a month ago. ;(
I can confirm that the only nginx module showing up in EPEL 8 Modular is nginx:mainline. This issue can be closed.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.