| Summary: | EPEL7 - nodejs-fs-ext won't install on RHEL 7.6 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Troy Dawson <tdawson> |
| Component: | nodejs-fs-ext | Assignee: | Parag Nemade <pnemade> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | nodejs-sig, pnemade |
| 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: | 2019-02-18 15:16:24 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1647564 | ||
|
Description
Troy Dawson
2019-01-23 21:36:40 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. 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. Thank you Troy for this explanation. I think good to remove this package then. 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. I have retired nodejs-fs-ext from EPEL7. I will close the ticket when I have verified it is not in the EPEL7 anymore. Verified Package is no longer in EPEL7 |