checksum validation fails on ubuntu #241

Closed
mrGrazy opened this Issue Nov 16, 2012 · 7 comments

6 participants

@mrGrazy

The current master version seems to have an issue with sanitizing the checksums of packages, when I do rbenv install 1.9.3-p194 I get:

Downloading yaml-0.1.4.tar.gz...
-> http://cloud.github.com/downloads/sstephenson/ruby-build-download-mirror/36c852831d02cf90508c29852361d01b
-> http://pyyaml.org/download/libyaml/yaml-0.1.4.tar.gz

BUILD FAILED

Inspect or clean up the working tree at /tmp/ruby-build.20121116151651.26504
Results logged to /tmp/ruby-build.20121116151651.26504.log

Last 10 log lines:
X-Cache: Hit from cloudfront


checksum mismatch: yaml-0.1.4.tar.gz (file is corrupt)
expected 36c852831d02cf90508c29852361d01b, got (stdin)= 36c852831d02cf90508c29852361d01b


checksum mismatch: yaml-0.1.4.tar.gz (file is corrupt)
expected 36c852831d02cf90508c29852361d01b, got (stdin)= 36c852831d02cf90508c29852361d01b

You can see the two checksums are the same, but dont match quite right.

Going back to v20121110 fixed the issue.

@postmodern

Also getting this on Fedora 17 / Bash 4.2.39. master appears to be broken at the moment.

@scrogson

Same here on Ubuntu 12.04

@AustinMatherne

Same. Rolling back to v20121110 resolved the issue for me, as well.

Running Gentoo.

@jeremy

Due to newer openssl:

$ echo 'foo' | openssl-0.9.8 md5
d3b07384d113edec49eaa6238ad5ff00

$ echo 'foo' | openssl-1.0.1 md5
(stdin)= d3b07384d113edec49eaa6238ad5ff00
@postmodern

@jeremy Ah ha! So why use openssl vs. the md5sum / sha1sum utilities?

@jeremy

@postmodern see compute_md5 check for a variety of md5 executables: https://github.com/sstephenson/ruby-build/pull/240/files#L1R132

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment