-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[package] libjpeg/9d: wrong SHA256 checksum #4151
Comments
|
On first sight, I can't see any contact information for them. Does someone know a way we can contact the maintainers and ask them about this? |
|
Going to the Internet Archive and getting the first Here are the diffs: looks like some extraneous characters were removed from the |
|
|
|
Looks like they are reorganizing existing archives without changing the filename? Strange... Even the timestamps didn't update. |
|
@ all - what do you think how we should handle this?
|
|
I checked the differences for both versions I would say it looks safe if we would like to update the signatures. But how long will this last, when does the next silent change appear? |
|
I'm going to make a PR and include documentation of what changed between the tarballs to justify the checksum change. |
|
On Unix (OSX and Linux), I'm an end user of the Conan's My AFAIU, this issue has been fixed by the PR referred above. Am I supposed to do anything to obtain the fix? |
|
@mloskot Or simply, go into your cache directory and remove all relevant sub-directories in |
|
@andioz Thanks for the tip about the cache. The thing is, I'm getting the failure for CI builds on Azure Pipelines: where, I assume, the cache is clean slate on each build. The Conan is run via |
|
Ah, one more hint: you are using |
Discussion at conan-io/conan-center-index#4151 (comment) Fixes Azure Pipelines builds for boostorg#535
Discussion at conan-io/conan-center-index#4151 (comment) Fixes Azure Pipelines builds for #535
|
@andioz The new syntax is something I wasn't aware of and it did the trick indeed. Thanks! |
Release notes https://alpinelinux.org/posts/Alpine-3.13.0-released.html Update jpeg 9d hash has changed. Seems ok conan-io/conan-center-index#4151
Release notes https://alpinelinux.org/posts/Alpine-3.13.0-released.html Update jpeg 9d hash has changed. Seems ok conan-io/conan-center-index#4151 ldd seem to have changed and does not work on static PIE, switch to file
Discussion at conan-io/conan-center-index#4151 (comment) (cherry picked from develop commit 0c0fe1a)
…547) Discussion at conan-io/conan-center-index#4151 (comment) (cherry picked from develop commit 0c0fe1a)
|
I'm still seeing this issue in a local build: While I could just delete the local data folder entirely, I'd like to know what's causing the issue otherwise I can't really trust that packages are being properly updated. I'm not seeing this issue on CI where everything is downloaded from scratch - is there some additional caching behaviour going on? |
We were running into the same issue presented here: conan-io/conan-center-index#4151 Switching to a new recipe hash seems to fix the problem.
We were running into the same issue presented here: conan-io/conan-center-index#4151 Switching to a new recipe hash seems to fix the problem.
Discussion at conan-io/conan-center-index#4151 (comment) Fixes Azure Pipelines builds for #535
…#547) Discussion at conan-io/conan-center-index#4151 (comment) (cherry picked from develop commit 0c0fe1ae79053d8aedfa95eca39329d135e4ea1c)
Discussion at conan-io/conan-center-index#4151 (comment) Fixes Azure Pipelines builds for #535
Also update jpeg hash conan-io/conan-center-index#4151
Package and Environment Details
Conan profile
Problem
I cannot build, signature is wrong:
Steps to reproduce (Include if Applicable)
I'm pretty sure it worked until today noon UTC (January 7th, 2021), but suddenly the signature doesn't match anymore. Ich checked the source repository on the website, downloaded the archive file and generated the hash. Indeed the result changed!
Is this maybe a serious attack, or some conan internal problem? The timestams on their web site looks ok:
The text was updated successfully, but these errors were encountered: