Opened 16 months ago
Closed 16 months ago
#67734 closed defect (fixed)
R-baygel @0.2.0: checksum mismatch
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | barracuda156 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | R-baygel |
Description
https://build.macports.org/builders/jobs-mirror/builds/601354/steps/mirror/logs/stdio
---> baygel-0.2.0.tar.gz does not exist in /Volumes/RAID/opt/local/var/rsync/macports/distfiles/R-baygel ---> Attempting to fetch baygel-0.2.0.tar.gz from http://distfiles.macports.org/R-baygel % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0---> Attempting to fetch baygel-0.2.0.tar.gz from https://codeload.github.com/Jarod-Smithy/baygel/legacy.tar.gz/v0.2.0?dummy= % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 3 128k 3 4622 0 0 8927 0 0:00:14 --:--:-- 0:00:14 8922 100 128k 100 128k 0 0 213k 0 --:--:-- --:--:-- --:--:-- 213k ---> Checksumming baygel-0.2.0.tar.gz Error: Checksum (rmd160) mismatch for baygel-0.2.0.tar.gz Portfile checksum: baygel-0.2.0.tar.gz rmd160 96963ef1067701ad860e4921ae5f1fe8463c72ca Distfile checksum: baygel-0.2.0.tar.gz rmd160 8ffdf933f3eea3ed70fa487b9704ad58716de666 Error: Checksum (sha256) mismatch for baygel-0.2.0.tar.gz Portfile checksum: baygel-0.2.0.tar.gz sha256 faf1ceef64a74873e3ffb6177c39e0d39e11a4c6f1c9a0124c88a15b789a89cf Distfile checksum: baygel-0.2.0.tar.gz sha256 70b3a1e8751f151c5e735ba940f82e8e42ec20775b591a4df0a9c0529ce2558d Error: Checksum (size) mismatch for baygel-0.2.0.tar.gz Portfile checksum: baygel-0.2.0.tar.gz size 129860 Distfile checksum: baygel-0.2.0.tar.gz size 131622 The correct checksum line may be: checksums rmd160 8ffdf933f3eea3ed70fa487b9704ad58716de666 \ sha256 70b3a1e8751f151c5e735ba940f82e8e42ec20775b591a4df0a9c0529ce2558d \ size 131622
Also note you're downloading from the legacy github endpoint. Switch to github.tarball_from archive
please, which will change the checksums.
Change History (5)
comment:1 Changed 16 months ago by barracuda156
comment:2 Changed 16 months ago by barracuda156
- S. I guess, checksums changed due to https://github.com/Jarod-Smithy/baygel/issues/6
comment:3 follow-up: 4 Changed 16 months ago by ryandesign (Ryan Carsten Schmidt)
All ports using the github portgroup should specify github.tarball_from
. Not doing so deprecated and I will modify the github portgroup to print a warning for this soon.
I infer from the fact that the URL contains "legacy.tar.gz" that GitHub considers this method old and I suppose they could deprecate and remove it eventually so it would be wise to remove our dependence on it. Its replacement, the "archive" URLs, have been available for many years. "Archive" URLs have the added advantage that you don't get checksum mismatches if the project is transferred to a different owner account, which turns out happens rather frequently.
For any ports hosted at GitHub where the project offers manually-prepared tarballs, those should be used by specifying github.tarball_from releases
in the Portfile. This is not something the R or github portgroups could automate for you since it is specific to each project whether or not they offer this.
How about modifying the R portgroup to set github.tarball_from archive
when it is using GitHub, and for any existing R port using GitHub, add the line github.tarball_from tarball
to them so they continue to work. When each of those ports is updated next, that line can be removed to switch it to the new download URL.
comment:4 Changed 16 months ago by barracuda156
Replying to ryandesign:
How about modifying the R portgroup to set
github.tarball_from archive
when it is using GitHub, and for any existing R port using GitHub, add the linegithub.tarball_from tarball
to them so they continue to work. When each of those ports is updated next, that line can be removed to switch it to the new download URL.
Yes, this can be done.
comment:5 Changed 16 months ago by barracuda156
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Thank you for letting me know. Weird, but I will fix it.
(Or otherwise we need that line commented out whenever switched to CRAN.)