Bug 1525565
| Summary: | openssl-devel and compat-openssl10-devel are not able to be installed together | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dylan Myers <ralgith> |
| Component: | openssl | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | c.justin88, jorton, leigh123linux, terry1, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-14 11:21:00 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
Dylan Myers
2017-12-13 15:09:13 UTC
Also, forum thread about this issue: https://forums.fedoraforum.org/showthread.php?316527-Cannot-install-both-compat-openssl10-devel-and-openssl-devel-at-the-same-time These packages conflict intentionally as otherwise all the dependent packages would have to be changed. You simply cannot have two different openssl headers and linker .so symlinks installed without changing the paths which would require changes in the dependencies. Also the compat-openssl10-devel will be removed at some point (Fedora 29 or at the latest Fedora 30). I'm having the same problem. Most of the packages we build want the new openssl version but there are a few old packages that need to be built with the older 1.0 version. We don't really want to have to setup separate build systems for this. I don't understand why Fedora cannot have the two development versions installed at the same time, we use various versions of other libraries such as Qt during development of code. Normally this would be done by installing the openssl 1.0 development files (include and libraries) into a separate directories like /usr/lib64/openssl10 and /usr/include/openssl10 for example. Developers can then change their CFLAGS/LDFLAGS as needed for this if they need to build for that older version. Is there some reason there are difficulties with openssl with doing this ? (In reply to Terry Barnaby from comment #3) > Is there some reason there are difficulties with openssl with doing this ? I've wondered the same thing. It isn't a true -compat lib if it can't be installed at the same time as the primary lib. That makes the name, and concept, very misleading and frustrating. Especially with this attitude in regards to fixing it properly. It honestly feels and sounds like pure laziness to me. I have created a compat-openssl10-beam.spec file that builds compat-openssl10-beam-1.0.2m-1.fc27.x86_64.rpm and compat-openssl10-beam-devel-1.0.2m-1.fc27.x86_64.rpm These override the compat-openssl10 packages and has the development include files in /usr/include/compat-openssl10 and libraries in /usr/lib64/compat-openssl10. It ignores the manuals etc. Using these and building our old SSL1.0 application with -I/usr/include/openssl10 -L/usr/lib64/openssl10 appears to work fine. This is just a hack for us here. It seems to work fine so I don't understand why this cannot be done (properly). If anyone wants the modified compat-openssl10-beam.spec file to build the RPM's I have put it at: https://www.beam.ltd.uk/files/ |