Opened 7 months ago

Closed 7 months ago

Last modified 7 months ago

#69836 closed defect (fixed)

kicad @7.0.11: checksum mismatch

Reported by: Gamespeople Owned by: ra1nb0w
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: kicad

Description (last modified by ryandesign (Ryan Carsten Schmidt))

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 :-#)#

Attachments (1)

KiCad7-0-11-failure-to-launch.rtf.zip (23.0 KB) - added by Gamespeople 7 months ago.
Report to Apple about KiCad 7.0.11 failure to lunch.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 months ago by Gamespeople

Description: modified (diff)
Owner: set to ra1nb0w
Status: newassigned

comment:2 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign added
Description: modified (diff)
Port: kicad added; Kicad removed
Summary: Kicad 7.0.11.0 incorrect Checksums. This is for Catalina 10.15.7 installkicad @7.0.11: checksum mismatch

I 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:

  • kicad-7.0.11/thirdparty/argparse/tools/build.bat

    diff -ru macports/kicad-7.0.11/thirdparty/argparse/tools/build.bat gitlab/kicad-7.0.11/thirdparty/argparse/tools/build.bat
    old new  
    1 call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
    2 
    3 cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DARGPARSE_BUILD_TESTS=ON
    4 ninja -C build
     1call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
     2
     3cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DARGPARSE_BUILD_TESTS=ON
     4ninja -C build

That is to say, a Windows build file's line endings changed from CRLF to LF, which is very frustrating because 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 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 stealth update.

comment:3 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

I've filed a bug with kicad about this to see if they can think of anything on their end that would have caused this. If not, we'll have to figure out how to contact GitLab.

comment:4 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

In 7526e63e820163ef5dcc83d59e155b25814d8b66/macports-ports (master):

kicad: Ignore stealth update of 7.0.11

Closes: #69836

Changed 7 months ago by Gamespeople

Report to Apple about KiCad 7.0.11 failure to lunch.

comment:5 Changed 7 months ago by Gamespeople

Installed fine:

--->  Verifying checksums for kicad                                   
--->  Extracting kicad
--->  Applying patches to kicad
--->  Configuring kicad
--->  Building kicad                                     
--->  Staging kicad into destroot                        
--->  Installing kicad @7.0.11_0                         
--->  Activating kicad @7.0.11_0
--->  Cleaning kicad
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.                             
--->  No broken ports found.

however when trying to launch KiCad 7.0.11 it crashes when I try to do anything past the opening screen.

Is this a Ports problem or a KiCad issue.

I've attached the Apple error report.
Thanks!

Last edited 7 months ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:6 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

This ticket was about a checksum mismatch problem which was fixed. Please file a new ticket for the new problem.

Note: See TracTickets for help on using tickets.