Search Criteria
Package Details: ruby-pleaserun 0.0.32-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/ruby-pleaserun.git (read-only, click to copy) |
---|---|
Package Base: | ruby-pleaserun |
Description: | pleaserun |
Upstream URL: | https://rubygems.org/gems/pleaserun |
Licenses: | Apache |
Submitter: | jtgoguen |
Maintainer: | envolution |
Last Packager: | a.kudelin |
Votes: | 4 |
Popularity: | 0.85 |
First Submitted: | 2017-03-03 04:20 (UTC) |
Last Updated: | 2021-07-07 18:14 (UTC) |
Dependencies (8)
- ruby
- ruby-cabinAUR
- ruby-clampAUR
- ruby-dotenvAUR
- ruby-insistAUR
- ruby-mustache
- ruby-studAUR
- ruby-bundler (make)
Latest Comments
skeksis268 commented on 2021-07-07 10:42 (UTC) (edited on 2021-07-07 10:42 (UTC) by skeksis268)
Looks like hash is wrong again, maybe something changed upstream? https://rubygems.org/gems/pleaserun lists the correct sha.
RX14 commented on 2020-11-26 16:04 (UTC)
Sorry, I'm not able to really maintain this package any more, since I don't use it actively any more I can't spot issues like these. I'll disown it for a new maintainer.
ayekat commented on 2020-11-24 08:01 (UTC) (edited on 2020-11-24 08:02 (UTC) by ayekat)
I am not very familiar with Ruby Gem, but it appears that the build process actually modifies the gem file. That would explain why we are constantly getting confusing SHA256 sums.
I assume RX14 might have put the sha256sum of his local/modified .gem file in the PKGBUILD after they had already run makepkg at least once before (back in March), hence the mismatch for many users initially.
And in yahx' case, I see this:
This means the .gem file was already present the moment you tried to build there, i.e. this is a file that was already modified in a previous makepkg run. If you delete that file and rebuild (and it downloads the source again), it should work fine again.
Essentially, one cannot build this more than once in a row without deleting the source files inbetween. No idea if this is normal behaviour.
yahx commented on 2020-11-14 02:09 (UTC) (edited on 2020-11-14 02:22 (UTC) by yahx)
Seems the issue still exists (for 0.0.31-2), as @corsaw stated. My error is identical.
The sha256sum seems correct. I tried overwriting the existing key, same error. Please advise.
RX14 commented on 2020-03-18 21:19 (UTC)
Not sure what happened there, perhaps the upstream file was replaced, but the previously downloaded gem had a different hash.
Fixed.
warigan commented on 2020-03-18 21:15 (UTC) (edited on 2020-03-18 21:16 (UTC) by warigan)
It seems the sha256sum in the
PKGBUILD
is wrong. There is a different one on upstream.