Closed DomT4 closed 7 years ago
Patches have landed in Python upstream, next releases on all branches will support 1.1.0.
@DomT4 How could one generate logs like this? Are there any commands or scripts? If so we can crowdsourcing the build logs on other formulas multiplying other platforms.
@JLHwung brew gist-logs <formula>
.
@DomT4 How could one contribute on this list? For example
Maintainers have direct access. Everyone else will need to leave a comment & wait for a maintainer to incorporate it into the master list. Generally the test process is something like:
depends_on "openssl"
or Formula["openssl"]
in formula to openssl@1.1
.brew install -s <formula>
brew test -v <formula>
(If formula defines a test).brew gist-logs <formula>
gist-logs
.@DomT4 don't forget to mention that use
brew uses <formula> --include-build --include-optional
to detect whether this formula is dependent of other formulas.
It is also worthy noting that some formula depends on OpenSSL optionally, so one needs go through the option to make formula building against openssl@1.1
Here is a list of c
initials.
libssh2
and nghttp2
, etc does not support 1.1 now.
https://gist.github.com/c85e2a1524e05cafe758bc0b54bae742mutt
just officially gained support for building openssl
1.1 in HEAD.
libssh2
does support openssl@1.1
in HEAD now.
@vszakats Thank you so much for reminding people of the progress. I raise pull request #4734 to have libssh2
HEAD depends on openssl@1.1
.
Closing this because of https://github.com/Homebrew/brew/pull/1283. Thank you to those who helped work on it a little so far.
Let's leave it open, others will need to continue this work.
I was mostly hoping to avoid the notifications. I'll try the unsubscribe notifications button instead.
@DomT4 Thanks!
Based on https://github.com/Homebrew/homebrew-core/issues/6828 I think we should change approach here and stop migrating things to use openssl@1.1
until we can do it all in a large revision PR i.e. all the projects using OpenSSL 1.0 currently work with OpenSSL 1.1. Migrating things one-by-one is going to result in mixed dependency trees and that's not going to be good. CC @tdsmith and generally @Homebrew/maintainers for this.
Please consider rolling this back for broken packages. For example, ansible has been broken for 3 months now.
@gelraen what issue(s) are you referring to specifically?
@ilovezfs brew install ansible
chokes on installing openssl-1.1. I've worked it around by manually editing ansible.rb
locally to use any version of openssl, not 1.1 specifically.
@gelraen that's an issue specific to your system. openssl@1.1 is a non-optional dependency of ansible, and we have pre-built binary bottles for Sierra, El Capitan, and Yosemite, which were all built against 1.1. Please open an issue.
Sorry, I was indeed too quick to judge. It was broken for me because I have TOP
env var set in my shell for completely unrelated reason (see gist for the full error message). Should I open an issue for general env sanitizing or just this specific instance?
@gelraen you can make a note of the situation here: https://github.com/Homebrew/brew/issues/932
Closing as we're not actively migrating these formulae now.
Borrowing my own comment from another thread:
Immediate potential deps tree:
Usage or potential usage list:
Generate a build report for addition to the list:
Fair warning: This is going to be a messy list.