Bug 2041575 - nodejs(engine) dependency broken
Summary: nodejs(engine) dependency broken
Keywords:
Status: CLOSED DUPLICATE of bug 2041022
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nodejs-once
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: NodeJS Packaging SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-17 18:02 UTC by Jorge Gallegos
Modified: 2022-01-18 01:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-18 01:43:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.