Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libgcrypt 1.9.0 #69327

Closed
wants to merge 4 commits into from
Closed

libgcrypt 1.9.0 #69327

wants to merge 4 commits into from

Conversation

J-M0
Copy link
Contributor

@J-M0 J-M0 commented Jan 19, 2021

Created with brew bump-formula-pr.

@carlocab
Copy link
Member

Looks like this needs another patch? The original patch failed to apply, but now there's a build failure.

@J-M0
Copy link
Contributor Author

J-M0 commented Jan 20, 2021

Is embedding the patches like I did ok, or is there a way to download them from the mailing list?

@carlocab
Copy link
Member

carlocab commented Jan 20, 2021

It's a small patch, so I guess embedding it is fine. Not sure there's a way to get the patches from the mailing list. I'd like to wait a little bit to see if that patch will get reviewed, especially given how security-sensitive libgcrypt is. Unless there is something important in this version bump that we don't want to delay?

@J-M0
Copy link
Contributor Author

J-M0 commented Jan 20, 2021

I'm not aware of any pressing reason to upgrade to 1.9 right away, so I think waiting is fine

@carlocab
Copy link
Member

Great. Let's wait a little bit to see if the patch will be reviewed. I think the author of the patch is a libgcrpyt developer, so it probably should be fine even if it isn't.

@carlocab
Copy link
Member

Judging from https://dev.gnupg.org/T5159 (see last comment), it looks like at least some of this

on_macos do
# Slightly hideous hack to help `make check` work in
# normal place on >10.10 where SIP is enabled.
# https://github.com/Homebrew/homebrew-core/pull/3004
# https://bugs.gnupg.org/gnupg/issue2056
MachO::Tools.change_install_name("#{buildpath}/tests/.libs/random",
"#{lib}/libgcrypt.20.dylib",
"#{buildpath}/src/.libs/libgcrypt.20.dylib")
MachO.codesign!("#{buildpath}/tests/.libs/random") if Hardware::CPU.arm?
end

can be removed?

@chenrui333 chenrui333 added CI-requeued PR has been re-added to the queue 11 Big Sur is specifically affected labels Jan 23, 2021
@chenrui333
Copy link
Member

try out hack removal commit.

@carlocab
Copy link
Member

Exactly what I would've tried removing too. Thanks, @chenrui333.

@carlocab
Copy link
Member

Should we keep a comment explaining why we still codesign on ARM? A link to an upstream report would be good for that too...

@carlocab
Copy link
Member

Not sure why dar is failing on Big Sur. Can you try giving it a revision bump, @J-M0?

@SeekingMeaning SeekingMeaning added test failure CI fails while running the test-do block and removed CI-requeued PR has been re-added to the queue labels Jan 26, 2021
@carlocab
Copy link
Member

Third time's not the charm, I guess:

Error: 1 failed step!
brew test --retry --verbose dar

@SeekingMeaning
Copy link
Contributor

Oops, I should have checked #65000; dar is a known failure on Big Sur

@SeekingMeaning SeekingMeaning removed 11 Big Sur is specifically affected test failure CI fails while running the test-do block labels Jan 27, 2021
@BrewTestBot
Copy link
Member

:shipit: @SeekingMeaning has triggered a merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants