OpenSSL 1.0.0-beta1 breaks packages that expect libcrypto.0.9.8

[bretthoerner@…]

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?

[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.

[hkroger@…]

Cc Me!

[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

[raimue (Rainer Müller)]

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?

[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.

[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)

[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.

[mf2k (Frank Schima)]

Cc Me!

[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)

[hkroger@…]

I mean I get that when I try to use svn.

[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.

[fmaillet@…]

Cc Me!

[raimue (Rainer Müller)]

The openssl upgrade has been reverted back to 0.9.8k in r49057.

[ryandesign (Ryan Carsten Schmidt)]

WikiFormatting.

[(none)]

Milestone Port Bugs deleted

[raimue (Rainer Müller)]

This is the way MacPorts works at the moment. There is no way to force a rebuild of dependents, see #17473.

[watsonix@…]

Replying to 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

running the first command produces the following error for me.

--->  Deactivating openssl @1.0.0a_0
--->  Unable to uninstall/deactivate openssl @1.0.0a_0, the following ports depend on it:
--->  	curl @7.21.0_0+ssl
--->  	cyrus-sasl2 @2.1.23_1+kerberos
--->  	git-core @1.7.1.1_0+doc+svn
--->  	gnome-vfs @2.24.3_0
--->  	neon @0.29.3_1
--->  	p5-crypt-ssleay @0.57_0
--->  	python26 @2.6.5_2
--->  	python26 @2.6.5_3
--->  	serf @0.6.1_0
Error: Target org.macports.deactivate returned: Please uninstall the ports that depend on openssl first.
Log for openssl is at: /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_openssl_1.0.0a_0/main.log
Warning: Failed to execute portfile from registry for openssl @1.0.0a_0
--->  Deactivating openssl
--->  Unable to uninstall/deactivate openssl @1.0.0a_0, the following ports depend on it:
--->  	curl @7.21.0_0+ssl
--->  	cyrus-sasl2 @2.1.23_1+kerberos
--->  	git-core @1.7.1.1_0+doc+svn
--->  	gnome-vfs @2.24.3_0
--->  	neon @0.29.3_1
--->  	p5-crypt-ssleay @0.57_0
--->  	python26 @2.6.5_2
--->  	python26 @2.6.5_3
--->  	serf @0.6.1_0
Error: port deactivate failed: Please uninstall the ports that depend on openssl first.

I am unclear how to proceed to break the least amount of stuff. Please don't tell me i have to uninstall each of these things seperately and then reinstall them!

BTW, here is the sad story of how I got to this point: In trying to install Matplotlib (python plotting util)... i ran into trouble with wxWidgets-python failing. Someone posted a workaround involving installing Mesa which I followed here: ​http://www.mail-archive.com/macports-users@lists.macosforge.org/msg19905.html

Apparently, in the process of doing this I screwed up (by upgrading?) OpenSSL, which breaks a lot of things I use including Git.

[watsonix@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

MacPorts 1.9 now prevents you from deactivating a port that is being used. If you're sure you still want to, force it with

sudo port -f deactivate openssl

The issues leading to this ticket being filed were that openssl was updated to 1.0.0 beta but dependents did not have their revisions increased to force a rebuild, hence things broke. Now that openssl has been updated to 1.0.0a final and dependencies have had their revisions bumped, the problem should no longer exist, so I would not expect you to need to go back to 0.9.8anything. If you would like to discuss why you think you do need that, or need further assistance using MacPorts, please write to ​macports-users. This ticket is closed.