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
chromedriver hash is incorrect #106272
Comments
Some links to better document this:
diffoscope output: $ diffoscope /nix/store/ip7sbkrkj1gqjsfb01f449zvgqm8qrdr-chromedriver_linux64.zip /nix/store/xssshmydphnbbc2hc0r4gmn9ixsf3byx-chromedriver_linux64.zip
--- /nix/store/ip7sbkrkj1gqjsfb01f449zvgqm8qrdr-chromedriver_linux64.zip
+++ /nix/store/xssshmydphnbbc2hc0r4gmn9ixsf3byx-chromedriver_linux64.zip
├── zipinfo {}
│ @@ -1,3 +1,3 @@
│ Zip file size: 6121623 bytes, number of entries: 1
│ --rwxr-xr-x 3.0 unx 12405080 bx defN 20-Dec-02 16:42 chromedriver
│ +-rwxr-xr-x 3.0 unx 12405080 bx defN 20-Dec-03 18:14 chromedriver
│ 1 file, 12405080 bytes uncompressed, 6121449 bytes compressed: 50.7% |
primeos
added a commit
to primeos/nixpkgs
that referenced
this issue
Jan 3, 2021
I just regenerated upstream-info.json using update.py again and got a different hash this time (but the same hash as in NixOS#106272). Therefore, the only possible explanation I have is that upstream changed the file that is hosted at [0]. I'll try to contact upstream regarding this. Fix NixOS#106272. [0]: https://chromedriver.storage.googleapis.com/87.0.4280.88/chromedriver_linux64.zip (cherry picked from commit d35b635)
1 task
#108631 (comment) - Unfortunately the ZIP archive / chromedriver timestamp changed again... :o I've also opened a bug report now (after I had no luck on their ML): https://bugs.chromium.org/p/chromedriver/issues/detail?id=3703 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Installing the
chromedriver
package fails due to a hash mismatch:To Reproduce
Steps to reproduce the behavior:
nix-env -iA nixos.chromedriver
Expected behavior
It should build and install successfully.
Additional context
Add any other context about the problem here.
Notify maintainers
@cillianderoiste @marsam @primeos
Metadata
Maintainer information:
The text was updated successfully, but these errors were encountered: