-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
curl configure --without-libmetalink no longer works #34360
Comments
Commit: |
comment:2
This makes no sense as a separate ticket. This should be part of the review of #34242. I think you can just push your commit to the ticket there. |
comment:3
It's a problem with recent curl versions. It's also still present in 9.7.beta8 and rebuilding artifacts should fail there, too. It does not depend on #34242, that's just related to the only way I tried to build. Sorry for the excess information. It's also not a duplicate. But thanks for linking saraedum in. |
comment:4
The branch on the ticket has no relation to the description |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
I was just wondering where it had gone. My fault, thanks! |
comment:8
I see, this is conditional on |
comment:9
Please put your full name in the Authors field in the ticket box |
comment:10
Thanks for giving me a hand, it's my first attempt to contribute. |
Author: Robert Figura |
comment:12
Your fix works well, thanks very much! |
Reviewer: Matthias Koeppe |
Changed branch from u/gh-RefurioAnachro/curl-without-libmetalink to |
During a docker build (after applying u/saraedum/34242 's changes, which are good and necessary) I got this:
Libmetalink is no longer supported by curl, and apparently this also errors out on --without-libmetalink!
https://daniel.haxx.se/blog/2021/06/07/bye-bye-metalink-in-curl/
CC: @saraedum @dimpase
Component: packages: standard
Author: Robert Figura
Branch/Commit:
c42eef0
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/34360
The text was updated successfully, but these errors were encountered: