Bug 1668928 - EPEL7 - nodejs-fs-ext won't install on RHEL 7.6
Summary: EPEL7 - nodejs-fs-ext won't install on RHEL 7.6
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nodejs-fs-ext
Version: epel7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Parag Nemade
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: EPEL7FailsToInstall
TreeView+ depends on / blocked
Reported: 2019-01-23 21:36 UTC by Troy Dawson
Modified: 2019-02-18 15:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-02-18 15:16:24 UTC
Type: Bug

Attachments (Terms of Use)

Description Troy Dawson 2019-01-23 21:36:40 UTC
Current nodejs-fs-ext for EPEL7 (nodejs-fs-ext-0.4.2-2.el7) requires
  nodejs = 0.10
The nodejs in EPEL7 is currently nodejs-6.14.3

Please fix this package so that it can be installed in RHEL 7.6.
If you have not responded in a week, we will have a proven packager fix it.
If you know you will not be able to get to it and would like it fixed sooner, please let us know in this bug.
If you feel this package should no longer be in EPEL7, please let us know in this bug.

Comment 1 Parag Nemade 2019-01-24 04:02:08 UTC
I am confused here. I don't remember I had worked on epel7 nodejs-fs-ext package.
Let's go stepwise

1) What does epel7 branch says
SPEC file showed I have no changelog written there
git log showed I had done initial import and then 3-4 commits till 0.4.6 release of upstream
Then further all updates are done by Tom Hughes.

2) What does koji builds says
The last completed build was  nodejs-fs-ext-0.4.2-2.el7
and latest build in failed state is nodejs-fs-ext-0.5.0-11.el7.1

I have no idea what happened to builds between above 2 builds, might be they failed and koji removed them

3) The last good build happened on 2014-12-08 which have dependency https://koji.fedoraproject.org/koji/rpminfo?rpmID=5810615 as
nodejs(abi) = 0.10

and I am getting this report on 2019-01-23

I remained confused what is happening or have happened that cause suddenly this bug to be reported.

I am not looking into epel7 builds currently so feel free to apply your fix or remove this package from epel7 but please check for any dependencies.

Thank you.

Comment 2 Troy Dawson 2019-01-24 14:23:03 UTC
What caused the bug to be reported?
  I am going through and cleaning up all the "fails to install" packages in EPEL7.  It was a plan originated with the EPEL governing board after RHEL 7.6 broke several package dependencies.  It turns out nobody has done this for several years (if ever).

What happened between those two builds (2014 and 2017)?
  nodejs was updated to nodejs-6 in early 2017.
  There was a team that went through all the nodejs packages at the time to try to rebuild/update/fix them.  Turns out they were unsuccessful with 8 packages, but they didn't file bugzilla's at the time.

Should this package be fixed vs removed?
  Nothing depends on it, either in runtime or for building.
  It hasn't been installable for close to 2 years.
  Not a single bugzilla has been filed about it for EPEL.

My recommendation is to remove the package.

If you don't have any objection, I will put this package on my list of packages to remove from EPEL7.

Comment 3 Parag Nemade 2019-01-25 15:08:43 UTC
Thank you Troy for this explanation.

I think good to remove this package then.

Comment 4 Troy Dawson 2019-01-25 16:42:49 UTC
Sounds good.
I have added it to my list of packages to remove from EPEL7.
I will close this bug when it has been removed, and verified.

Comment 5 Troy Dawson 2019-02-15 17:18:49 UTC
I have retired nodejs-fs-ext from EPEL7.
I will close the ticket when I have verified it is not in the EPEL7 anymore.

Comment 6 Troy Dawson 2019-02-18 15:16:24 UTC
Package is no longer in EPEL7

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