Bug 2041575

Summary: nodejs(engine) dependency broken
Product: [Fedora] Fedora EPEL Reporter: Jorge Gallegos <jgallego>
Component: nodejs-onceAssignee: NodeJS Packaging SIG <nodejs-sig>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: jsmith.fedora, nodejs-sig, tchollingsworth, thrcka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-18 01:43: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 Jorge Gallegos 2022-01-17 18:02:16 UTC
Description of problem:

nodejs-once depends on 'nodejs(engine)' which is not part of the repodata, in fact all packages depending on nodejs(engine) are broken, but I couldn't find the nodejs component in BZ


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

nodejs-once-1.1.1-5.el7.noarch


How reproducible:

Always


Steps to Reproduce:

1. yum install nodejs-once # or coffee-script, or any other package depending on nodejs


Actual results:

Resolving Dependencies
--> Running transaction check
---> Package nodejs-once.noarch 0:1.1.1-5.el7 will be installed
--> Processing Dependency: nodejs(engine) for package: nodejs-once-1.1.1-5.el7.noarch
--> Finished Dependency Resolution
Error: Package: nodejs-once-1.1.1-5.el7.noarch (epel)
           Requires: nodejs(engine)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Expected results:

Package is installed


Additional info:

Comment 1 Jorge Gallegos 2022-01-17 18:05:04 UTC
The package is present at https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/Packages/n/ but it is not part of the repodata.

Comment 2 T.C. Hollingsworth 2022-01-18 01:43:18 UTC

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