Opened 6 months ago
Closed 6 months ago
#70034 closed defect (fixed)
dotnet-sdk-6 @6.0.421: checksum mismatch
Reported by: | Enormus (Keith Duggar) | Owned by: | tsabirgaliev (Tair Sabirgaliev) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | Cc: | judaew (Vadym-Valdis Yudaiev) | |
Port: | dotnet-sdk-6 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
dotnet-sdk-6 downloads but the checksum fails:
$ sudo port install dotnet-sdk-6 ... Error: Checksum (rmd160) mismatch for dotnet-sdk-6.0.421-osx-arm64.tar.gz Error: Checksum (sha256) mismatch for dotnet-sdk-6.0.421-osx-arm64.tar.gz Error: Checksum (size) mismatch for dotnet-sdk-6.0.421-osx-arm64.tar.gz Error: Failed to checksum dotnet-sdk-6: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_dotnet_dotnet-sdk-6/dotnet-sdk-6/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port dotnet-sdk-6 failed
Attachments (1)
Change History (5)
Changed 6 months ago by Enormus (Keith Duggar)
Attachment: | dotnet-sdk-6.log added |
---|
comment:1 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | judaew added |
---|---|
Description: | modified (diff) |
Owner: | set to tsabirgaliev |
Status: | new → assigned |
Summary: | port install dotnet-sdk-6 fails on Mac Sonoma 14.5 → dotnet-sdk-6 @6.0.421: checksum mismatch |
:info:checksum Portfile checksum: dotnet-sdk-6.0.421-osx-arm64.tar.gz size 30795879 :info:checksum Distfile checksum: dotnet-sdk-6.0.421-osx-arm64.tar.gz size 178310050
That's a pretty huge size difference.
comment:2 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
It doesn't look like the small distfile size in the Portfile was ever correct. Prior to the 6.0.421 update the arm64 distfile was listed with a larger size as the x86_64 distfile always has been.
6.0.422 is available; this would be solved by just updating the port.
comment:3 Changed 6 months ago by Enormus (Keith Duggar)
Thank you sincerely for jumping on this so quickly! Is this something I can resolve myself and/or something I'm doing incorrectly? Or should I wait for an update to the MacPorts port tree?
comment:4 Changed 6 months ago by tsabirgaliev (Tair Sabirgaliev)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
dotnet-sdk-6/main.log