Bug 1413864
Summary: | Upgrade of eclipse-epp-logging pulls too many new dependencies | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> |
Component: | eclipse-epp-logging | Assignee: | Sopot Cela <scela> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | mat.booth, scela |
Target Milestone: | --- | Keywords: | Reopened |
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: | 2017-01-18 12:58:38 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
Lukas Slebodnik
2017-01-17 07:54:15 UTC
This is because eclipse-epp-logging had to be moved to lucene 4 from lucene 5 to ensure that it functions correctly. These additional deps are pulled in by lucene4 as an (unfortunate) consequence. This is not a epp-logging bug (since moving to lucene4 is an intentional, but temporary measure until Eclipse upstream moves to newer lucene). Could you explain why lucene was not required in 2.0.3-1 and is required in minor release update 2.0.3-2? If it was not strictly required in 2.0.3-1 could it be changed to weak dependency? http://rpm.org/user_doc/dependencies.html#weak-dependencies. And I can see lucene-upgrade.patch even in 2.0.3-1. (In reply to Lukas Slebodnik from comment #2) > Could you explain why lucene was not required in 2.0.3-1 and is required in > minor release update 2.0.3-2? > > If it was not strictly required in 2.0.3-1 could it be changed to weak > dependency? http://rpm.org/user_doc/dependencies.html#weak-dependencies. > > And I can see lucene-upgrade.patch even in 2.0.3-1. With version 2.0.3-1 you will likely find your workspace logs littered with "could not read lucene index" errors. This is because epp-logging downloads lucene 3 indexes from the internet, but lucene 5 cannot read them. Lucene 4 is able to correctly read these indexes. I moved epp-logging from lucene 5 to lucene 4 to fix this bug. Lucene is not an optional dependency, I cannot make it a weak dep. IMO the reported problem is not a bug with epp-logging, it would be more appropriate to file a bug with lucene 4 to split it up into subpackages if you want to reduce the dependency count. Thank you for detailed explanation. |