Bug 2041022

Summary: Provide nodejs for EPEL 7
Product: [Fedora] Fedora EPEL Reporter: Mattias Ellert <mattias.ellert>
Component: nodejsAssignee: NodeJS Packaging SIG <nodejs-sig>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: giacomo.sanchietti, jgallego, manuel.vacelet, mrunge, nodejs-sig, sgallagh, thrcka, w.deborger, zsvetlik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nodejs-16.13.2-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-21 17:27:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mattias Ellert 2022-01-15 10:11:16 UTC
Description of problem:

The old nodejs 6 in EPEL 7 was recently removed without having been replaced by a newer version. This means uglify-js is not installable and all packages that use it at buildtime are no longer buildable.

Version-Release number of selected component (if applicable):

None - which is the problem

How reproducible:

Always

Steps to Reproduce:
1. Try to install e.g. the uglify-js package

Actual results:
Missing deps.

Expected results:
No missing deps.

Additional info:
I understand the need to remove the nodejs version 6, but please replace it with a newer version rather than dropping it.

Comment 1 Stephen Gallagher 2022-01-18 00:15:22 UTC
I've looked into it and it turns out I *can* bludgeon 16.x into working on EPEL 7. I've opened up https://pagure.io/releng/issue/10541 to get it unretired and I'm building a COPR of 16.x at https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs_epel7/build/3192501/

Comment 2 T.C. Hollingsworth 2022-01-18 01:43:18 UTC
*** Bug 2041575 has been marked as a duplicate of this bug. ***

Comment 3 Zuzana Svetlikova 2022-01-18 15:37:26 UTC
There is v14 SCL, maybe that can be used?

Comment 4 Fedora Update System 2022-01-18 20:47:51 UTC
FEDORA-EPEL-2022-bf9c411793 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793

Comment 5 Fedora Update System 2022-01-19 02:19:00 UTC
FEDORA-EPEL-2022-bf9c411793 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-01-19 20:10:18 UTC
FEDORA-EPEL-2022-bf9c411793 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793

Comment 7 Didier Fabert (tartare) 2022-01-20 07:19:40 UTC
*** Bug 2041453 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Update System 2022-01-20 08:41:54 UTC
FEDORA-EPEL-2022-bf9c411793 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-01-21 17:27:18 UTC
FEDORA-EPEL-2022-bf9c411793 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.