[MacPorts] #69836: kicad @7.0.11: checksum mismatch (was: Kicad 7.0.11.0 incorrect Checksums. This is for Catalina 10.15.7 install)
MacPorts
noreply at macports.org
Fri Apr 26 22:28:34 UTC 2024
#69836: kicad @7.0.11: checksum mismatch
--------------------------+----------------------
Reporter: Gamespeople | Owner: ra1nb0w
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: kicad |
--------------------------+----------------------
Changes (by ryandesign):
* cc: ryandesign (added)
* port: Kicad => kicad
Old description:
> I've done the Checksum error test - reran: sudo port /self update, /clean
> —dist kicad and tried /install kicad again… and I am still getting:
>
> ---> Computing dependencies for kicad
> ---> Fetching archive for kicad
> ---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
> https://packages.macports.org/kicad
> ---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
> http://mirror.fcix.net/macports/packages/kicad
> ---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
> https://ywg.ca.packages.macports.org/mirror/macports/packages/kicad
> ---> Verifying checksums for kicad
> Error: Checksum (rmd160) mismatch for kicad-7.0.11.tar.bz2
> Error: Checksum (sha256) mismatch for kicad-7.0.11.tar.bz2
> Error: Checksum (size) mismatch for kicad-7.0.11.tar.bz2
> Error: Failed to checksum kicad: Unable to verify file checksums
>
> I see that KiCad updated 7.0.11 Feb 22 (I assume 2024), and perhaps no
> one else has tried to install this since.
>
> Hope I didn't make a mistake assigning this to ra1nb0w!
>
> John :-#)#
New description:
I've done the Checksum error test - reran: sudo port /self update, /clean
—dist kicad and tried /install kicad again… and I am still getting:
{{{
---> Computing dependencies for kicad
---> Fetching archive for kicad
---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
https://packages.macports.org/kicad
---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
http://mirror.fcix.net/macports/packages/kicad
---> Attempting to fetch kicad-7.0.11_0.darwin_19.x86_64.tbz2 from
https://ywg.ca.packages.macports.org/mirror/macports/packages/kicad
---> Verifying checksums for kicad
Error: Checksum (rmd160) mismatch for kicad-7.0.11.tar.bz2
Error: Checksum (sha256) mismatch for kicad-7.0.11.tar.bz2
Error: Checksum (size) mismatch for kicad-7.0.11.tar.bz2
Error: Failed to checksum kicad: Unable to verify file checksums
}}}
I see that KiCad updated 7.0.11 Feb 22 (I assume 2024), and perhaps no one
else has tried to install this since.
Hope I didn't make a mistake assigning this to ra1nb0w!
John :-#)#
--
Comment:
I [changeset:d267a1cb353b4d144987cc0915e7da582dedd126/macports-ports
updated kicad to 7.0.11] on April 7 and the checksums were correct at that
time. I agree that they are incorrect now:
{{{
% sudo port fetch --no-mirrors kicad
Portfile for kicad changed since last build; discarding previous state.
---> Fetching distfiles for kicad
---> Attempting to fetch kicad-7.0.11.tar.bz2 from
https://gitlab.com/kicad/code/kicad/-/archive/7.0.11
% sudo port checksum kicad
---> Verifying checksums for kicad
Error: Checksum (rmd160) mismatch for kicad-7.0.11.tar.bz2
Error: Checksum (sha256) mismatch for kicad-7.0.11.tar.bz2
Error: Checksum (size) mismatch for kicad-7.0.11.tar.bz2
Error: Failed to checksum kicad: Unable to verify file checksums
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_kicad/kicad/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe
there is a bug.
Error: Processing of port kicad failed
}}}
The difference between the file we mirrored April 7 and the file available
from GitLab today is:
{{{#!diff
diff -ru macports/kicad-7.0.11/thirdparty/argparse/tools/build.bat
gitlab/kicad-7.0.11/thirdparty/argparse/tools/build.bat
--- macports/kicad-7.0.11/thirdparty/argparse/tools/build.bat 2024-02-21
06:39:11.000000000 -0600
+++ gitlab/kicad-7.0.11/thirdparty/argparse/tools/build.bat 2024-02-21
06:39:11.000000000 -0600
@@ -1,4 +1,4 @@
-call "C:\Program Files (x86)\Microsoft Visual
Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
-
-cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
-DARGPARSE_BUILD_TESTS=ON
-ninja -C build
+call "C:\Program Files (x86)\Microsoft Visual
Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
+
+cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
-DARGPARSE_BUILD_TESTS=ON
+ninja -C build
}}}
That is to say, a Windows build file's line endings changed from CRLF to
LF, which is very frustrating because
[https://gitlab.com/kicad/code/kicad/-/blob/7.0.11/thirdparty/argparse/tools/build.bat
the file in their repository has not changed] so this should absolutely
not happen. Perhaps GitLab changed how they automatically generate
tarballs. This is one of the perils of tying ports to automatically-
generated tarballs and why we really don't want to do it and only do it
when the developers do not give us any other option.
Updating to 7.0.11 was always intended to be a stopgap before
[ticket:69647 updating to 8.x] which will of course fix the issue since
the new version will have different checksums. Until then we can ignore
the inexplicable [PortfileRecipes#stealth-updates stealth update].
--
Ticket URL: <https://trac.macports.org/ticket/69836#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list