#9765 Remove invalid module from EPEL8 module repo
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by tdawson.

  • Describe the issue
    In EPEL8 there cannot be the same module name and module stream name as modules in rhel8. Another module with the same name and module name has made it into EPEL8 modularity.

Please remove nodejs:12 from the EPEL8 modularity repository.

I believe the following should do it

koji untag-build epel8-modular-updates nodejs-12-820200803134933.9edba152

  • When do you need this? (YYYY/MM/DD)
    2020-09-30

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    Any RHEL8, or CentOS8 users that have nodejs:12 enabled, will get the EPEL versions upon installation or update.
    nodejs:12 is currently not the default, so the impact isn't huge, but it isn't zero either.


Metadata Update from @humaton:
- Issue tagged with: low-gain, medium-trouble, ops

3 years ago

How did this happen? I thought this was enough as a prevention:

https://src.fedoraproject.org/modules/nodejs/c/2dbc81cbd2dc87f556d955de5001b745391616f8?branch=12

It should be el8 not epel8

And I asked @sgallagh to change the platform to el8 on freenode and also pinging here :smile:

[15:49:09] <+mboddu> sgallagh: Can you change https://src.fedoraproject.org/modules/nodejs/c/2dbc81cbd2dc87f556d955de5001b745391616f8?branch=12 to el8?, since el8 is the platform not epel8
[15:49:32] <+mboddu> That caused https://pagure.io/releng/issue/9765 issue

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Doing it now. That's embarrassing...

nodejs:14 already had the correct exclusion.

Issue status updated to: Open (was: Closed)

3 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Done