Opened 8 years ago
Closed 8 years ago
#51582 closed defect (fixed)
Error: org.macports.checksum for port t4k_common returned: Unable to verify file checksums
Reported by: | accounts@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | kurthindenburg (Kurt Hindenburg) | |
Port: | t4k_common |
Description
Thanks for MacPorts. It's wonderful software. I think I found a bug though. I see some older (closed) tickets for things related to this, but no current tickets. I did "Clean and try again" with the following:
$ sudo port selfupdate $ sudo port upgrade outdated $ sudo port clean --all t4k_common $ sudo port -v checksum t4k_common
I checked the Problem Hotlist. And I did a Search to see if a Trac ticket has already been filed (which is how I noticed some older closed tickets related to this).
When I attempt to install t4k_common, I get the following error:
---> Verifying checksums for t4k_common ---> Checksumming t4k_common-0.1.1.tar.gz Error: Checksum (sha1) mismatch for t4k_common-0.1.1.tar.gz Portfile checksum: t4k_common-0.1.1.tar.gz sha1 626eddedee86059ccab593a226c8d98571018b46 Distfile checksum: t4k_common-0.1.1.tar.gz sha1 fa9b9355cd81eef5f083b119fff038dd5e100690 Error: Checksum (rmd160) mismatch for t4k_common-0.1.1.tar.gz Portfile checksum: t4k_common-0.1.1.tar.gz rmd160 6c0332ea44e4a44021c645e5b4329c2efd377fed Distfile checksum: t4k_common-0.1.1.tar.gz rmd160 f43ab7c6e0e2be1b7e2a882e7b1d4e71bf758cfe *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: <https://trac.macports.org/wiki/MisbehavingServers> *** The file has been moved to: /opt/local/var/macports/distfiles/t4k_common/t4k_common-0.1.1.tar.gz.html Error: org.macports.checksum for port t4k_common returned: Unable to verify file checksums Warning: targets not executed for t4k_common: org.macports.checksum Please see the log file for port t4k_common for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_t4k_common/t4k_common/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port t4k_common failed
When I saw the error "...non-matching file appears to be HTML...", I checked https://trac.macports.org/wiki/MisbehavingServers and https://trac.macports.org/wiki/ProblemHotlist#fetch-failures and tried to get the distfile from elsewhere manually. But I think I see the problem when I visit http://distfiles.macports.org/t4k_common/ and find there an html file:
http://distfiles.macports.org/t4k_common/t4k_common-0.1.1.tar.gz.html
which takes me to a page that reads in part:
"Login
You've been redirected to this login page because you have tried accessing a page that was not available to you as an anonymous user."
Hope this ticket helps resolve the problem.
Change History (4)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
Keywords: | checksum removed |
---|---|
Milestone: | MacPorts Future |
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
The original files for t4k_common are hosted on a service called alioth. Unfortunately, a couple years ago, the alioth service started requiring logins to download some files. This was reported to us in #45134 in regard to the axel port. I reported this to the developers of axel at the time, but received no response. Our ticket was closed because the axel project moved to GitHub and was thus no longer affected by the alioth problem.
If we can figure out how to contact the maintainers of the alioth service, we should report this problem to them. Or we could report the problem to the developers of t4k_common and let them deal with contacting their hosting provider.
comment:3 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | kurthindenburg added |
---|
comment:4 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → fixed |
---|---|
Status: | new → closed |
The Milestone field is for use by Macports team members only, please do not set it.