Opened 5 months ago
Last modified 5 months ago
#70308 new defect
taglib-sharp: checksum mismatch
Reported by: | barracuda156 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | Cc: | ||
Port: | taglib-sharp |
Description
---> Fetching distfiles for taglib-sharp ---> taglib-sharp-2.0.3.7.tar.gz does not exist in /opt/local/var/macports/distfiles/taglib-sharp ---> Attempting to fetch taglib-sharp-2.0.3.7.tar.gz from http://download.banshee.fm/taglib-sharp/2.0.3.7 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 167 100 167 0 0 3437 0 --:--:-- --:--:-- --:--:-- 3479 100 236 0 236 0 0 351 0 --:--:-- --:--:-- --:--:-- 0 100 52857 0 52857 0 0 45232 0 --:--:-- 0:00:01 --:--:-- 45232 ---> Verifying checksums for taglib-sharp ---> Checksumming taglib-sharp-2.0.3.7.tar.gz Error: Checksum (sha1) mismatch for taglib-sharp-2.0.3.7.tar.gz Portfile checksum: taglib-sharp-2.0.3.7.tar.gz sha1 97beb1473d2fc730fc0289fe54d94ff64070fa82 Distfile checksum: taglib-sharp-2.0.3.7.tar.gz sha1 2ddfc946d07e1630db776d44fa26efe6882e22ec Error: Checksum (rmd160) mismatch for taglib-sharp-2.0.3.7.tar.gz Portfile checksum: taglib-sharp-2.0.3.7.tar.gz rmd160 25cd15206d2090602131341ae0103af3052a2f94 Distfile checksum: taglib-sharp-2.0.3.7.tar.gz rmd160 6c93171c3de4cf9069d2248105bc176ab9dbbba2 The correct checksum line may be: checksums sha1 2ddfc946d07e1630db776d44fa26efe6882e22ec \ rmd160 6c93171c3de4cf9069d2248105bc176ab9dbbba2 \ sha256 1db2cc182967ccc298a9fd07139e5707ad0f71aff495741241897a57bf520323 \ size 52857 Error: Failed to checksum taglib-sharp: Unable to verify file checksums
Change History (3)
comment:1 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 follow-up: 3 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
The autotools build system that the port uses was removed in version 2.2.0.0, which is the earliest version available at GitHub. The build instructions now say just to run dotnet build
. dotnet
is provided by the dotnet-cli port.
When I try to make the port use dotnet build
I get:
Error: [/opt/local/share/dotnet/host/fxr] does not exist
That is provided by several different dotnet-runtime-* ports. I tried adding a dependency on the dotnet-runtime-8 port and then the build error was:
The command could not be loaded, possibly because: * You intended to execute a .NET application: The application 'build' does not exist. * You intended to execute a .NET SDK command: No .NET SDKs were found. Download a .NET SDK: https://aka.ms/dotnet/download Learn about SDK resolution: https://aka.ms/dotnet/sdk-not-found
I don't know anything about dotnet so I will stop trying to make this work now.
According to repology, the only place using version 2.3.0.0 is AUR; most everyone else uses version 2.1.0.0.
comment:3 Changed 5 months ago by barracuda156
Replying to ryandesign:
The autotools build system that the port uses was removed in version 2.2.0.0, which is the earliest version available at GitHub.
They do have earlier versions, 2.1.0.0 and down. https://github.com/mono/taglib-sharp/releases/tag/taglib-sharp-2.1.0.0
The registration for banshee.fm was allowed to lapse; the last version of the site was https://web.archive.org/web/20210211030649/http://banshee.fm/
For years the domain was parked, and then someone else registered it and put up a plausible-looking web site about Banshee made using wordpress not preserving the old download URLs but making them redirect to an HTML page, hence the checksum mismatch. I do not trust this site and we should not use this domain name anymore.
On Wikipedia the Banshee project is listed as using the domain name banshee-project.org but that server is offline right now; the last version of that site was https://web.archive.org/web/20240131032123/http://www.banshee-project.org/
Wikipedia also lists https://gitlab.gnome.org/Archive/banshee as the home for Banshee, which is archived.
taglib-sharp appears to have a home at https://github.com/mono/taglib-sharp. Version 2.3.0.0 is available there so we should update to that or delete it since nothing depends on it.