Opened 15 years ago
Last modified 14 years ago
#19122 closed defect
OpenSSL 1.0.0-beta1 breaks packages that expect libcrypto.0.9.8 — at Version 15
| Reported by: | bretthoerner@… | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | git openssl libcrypto 1.0.0 0.9.8 | Cc: | hkroger@…, raimue@…, macsforever2000@…, fmaillet@…, ryandesign@… |
| Port: | openssl |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
1.0.0 apparently replaces 0.9.8 rather than installing alongside it,
$ git svn fetch dyld: Library not loaded: /opt/local/lib/libcrypto.0.9.8.dylib Referenced from: /opt/local/bin/git Reason: image not found Trace/BPT trap
Is this expected? Should I be rebuilding all packages that depend on OpenSSL?
Change History (14)
comment:2 follow-up: 5 Changed 15 years ago by hkroger@…
comment:4 Changed 15 years ago by bretthoerner@…
For non-developers that just want to go back to a working condition (assuming you upgraded from 0.9.8k to 1.0.0-beta1),
sudo port deactivate openssl sudo port activate openssl@0.9.8k_0
comment:5 follow-up: 6 Changed 15 years ago by raimue (Rainer Müller)
| Cc: | raimue@… added |
|---|
Replying to hkroger@…:
I have tried to reinstall someone of apps that depend on that and it does not work. Currently I have a load of programs in non working condition and no (easy) way to install a working version.
Could you please name the ports here, so they can be investigated?
comment:6 follow-up: 7 Changed 15 years ago by hkroger@…
Replying to raimue@…:
Replying to hkroger@…:
I have tried to reinstall someone of apps that depend on that and it does not work. Currently I have a load of programs in non working condition and no (easy) way to install a working version.
Could you please name the ports here, so they can be investigated?
For example "neon" doesn't compile with openssl 1.0 which leads to the fact that "subversion" doesn't work. I think I also had problems with "ruby" compilation with openssl 1.0.
comment:7 Changed 15 years ago by danielluke (Daniel J. Luke)
Replying to hkroger@…:
For example "neon" doesn't compile with openssl 1.0 which leads to the fact that "subversion" doesn't work. I think I also had problems with "ruby" compilation with openssl 1.0.
If you care about subversion, but not about neon, you can build subversion with the +no_neon variant as a workaround (until this issue can be resolved)
comment:8 Changed 15 years ago by hkroger@…
For now I have reverted back to openssl 0.9.8 using the version from svn. So no worries with that. Only problem is that anyone who upgrades ports nowadays will get for example broken subversion.
comment:10 Changed 15 years ago by hkroger@…
Actually all things compile now however, I get
svn: OPTIONS of 'https://xxx.xxx.com/yyy/trunk/zzz': SSL negotiation failed: SSL disabled due to library version mismatch (https://xxx.xxx.com)
comment:12 Changed 15 years ago by hkroger@…
argh, of course I wanted to say also that it happens with the 0.9.8k version from macports repository. So I cannot easily downgrade either because of these library problems.
comment:14 Changed 15 years ago by raimue (Rainer Müller)
| Owner: | changed from macports-tickets@… to mww@… |
|---|
The openssl upgrade has been reverted back to 0.9.8k in r49057.
comment:15 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Description: | modified (diff) |
I have tried to reinstall someone of apps that depend on that and it does not work. Currently I have a load of programs in non working condition and no (easy) way to install a working version.