-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
[ffmpeg] build failure due to yasm cannot be accessed #19121
Comments
I have the same issue with |
The official website actually links to non-https snapshots page: https://yasm.tortall.net/Download.html |
I have the same issue. |
Forgot to mention, there's a temporary workaround you can use to fix this error until it's fixed officially: Powershell: mkdir "C:\vcpkg\downloads\tools\yasm\1.3.0.6" | Out-Null
Invoke-WebRequest -Uri "http://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe" -SkipCertificateCheck -OutFile "C:\vcpkg\downloads\tools\yasm\1.3.0.6\yasm.exe" Bash: mkdir -p "/c/vcpkg/downloads/tools/yasm/1.3.0.6"
curl -k -o "/c/vcpkg/downloads/tools/yasm/1.3.0.6/yasm.exe" "http://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe" Run these commands before running |
Thank you for the workaround @julianxhokaxhiu. |
Hmm plausible workaround from vcpkg side could be to use the domain without the
Doing the same call but without www -> https://tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe results in 200OK.
|
I notified their webmaster as well. |
According to yasm/yasm#135 (comment) the issue should be fixed
|
But will it be fixed forever or until it breaks again? I'd still consider working on a solution that uses at least a fallback logic, knowing the source has broken twice in the past. |
I'd assume the worst as it's just a matter of time for someone forgets to update their ssl certificate. They do use Let's Encrypt, but presumably not automatic refresh. Next date of doom is: 2021-11-09 A fallback solution would be setting up / using a mirror (github for instance) or not use yasm at all for ffmpeg x86 builds see #19501 |
Since the website https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe is not stable. It has broken several times. Do you have any good suggestion or idea for this issue? @BillyONeal |
If ffmpeg is the only one currently relying on yasm we should be able to to get rid of it -> #19501 Another scenario would be to use the github Release assets found here: https://github.com/yasm/yasm/releases as github is probably more relyable |
I don't think we have a choice though.
There is no 1.3.0.6 release there. |
Closing this issue since this is not a problem in vcpkg side. Also there is no better choice to avoid the similar problem. |
So it happened again, today: https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe SSL Certificate invalid, certificate is expired ( set for today ). And no fallback is provided. I'm on the latest vcpkg master branch w/vcpkg.exe from November ( the one downloaded via the bootstrap script ).
How about adding the http link as mirror, if https fails? //EDIT: I sent an email to tortall to ask if it could kindly renew the cert in the meantime. |
Hi,
I noticed that vcpkg fetches
yasm
from this link: https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe which doesn't work at the moment because the website has a broken SSL certificate.Is it possible to change it to this one instead?
https://github.com/yasm/yasm/releases/download/v1.3.0/yasm-1.3.0-win32.exe
At least we would avoid relying on a website which seem that have failed already once in the past ( see #7379 ).
Thank you in advance,
Julian
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg install ffmpeg[avcodec,avdevice,avfilter,avformat,avresample,core,gpl,nvcodec,opus,postproc,speex,swresample,swscale,theora,vorbis,vpx,x264,x265]:x86-windows-static
Failure logs
Additional context
N/A
The text was updated successfully, but these errors were encountered: