Skip to content
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

checksums.json on puppetforge is incorrect #24

Open
elatt opened this issue Dec 10, 2014 · 2 comments
Open

checksums.json on puppetforge is incorrect #24

elatt opened this issue Dec 10, 2014 · 2 comments

Comments

@elatt
Copy link

elatt commented Dec 10, 2014

It seems that the value of metadata.json in the checksums.json file on the puppetforge is wrong which causes 'puppet module' command to complain that there are local edits when there are not.

@garethr
Copy link
Owner

garethr commented Dec 19, 2014

Mmm, interesting. Could you post details of Puppet version and an output showing the problem?

I've just downloaded with puppet module and not been able to recreate the error.

@elatt
Copy link
Author

elatt commented Dec 19, 2014

Puppet version is irrelevant. If I simply fetch the latest tarball from the forge:
$ wget https://forgeapi.puppetlabs.com/v3/files/garethr-diamond-1.0.0.tar.gz

And then extract it and examine checksums.json:
"metadata.json": "6915ffd1a43d9815726ed6a44e5c5d6f",

But if I compute the md5 of that file it is actually "79a9a3cf7f601e23a7625259e5c73201"

Maybe in your testing, you simply downloaded the package from the forge but didn't try to upgrade it (it seems that puppet only checks the checksums on upgrade... it might be a good idea for them to validate on install as well to detect these broken packages but that's an upstream issue).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants