On 2016-03-03 02:40, Ryan Schmidt wrote: > I consider it the responsibility of the committer who updated the > openssl port to the version that changed its library ABI to revbump > the ports that link with it, regardless of maintainer status. It > should have been done at the same time that openssl was updated of > course. I'm not working on it so someone else is welcome to do it.
I still see related errors such as this one: $ sudo gem install ERROR: Loading command: install (LoadError) dlopen(/opt/local/lib/ruby2.0/2.0.0/x86_64-darwin14/openssl.bundle, 9): Symbol not found: _SSLv2_client_method Referenced from: /opt/local/lib/ruby2.0/2.0.0/x86_64-darwin14/openssl.bundle Expected in: /opt/local/lib/libssl.1.0.0.dylib in /opt/local/lib/ruby2.0/2.0.0/x86_64-darwin14/openssl.bundle - /opt/local/lib/ruby2.0/2.0.0/x86_64-darwin14/openssl.bundle ERROR: While executing gem ... (NoMethodError) undefined method `invoke_with_build_args' for nil:NilClass The longer we wait, the harder it will be to catch these. Should we rev-bump all dependents of OpenSSL now? Is it already too late and we fix them case-by-case? Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev