#39318 closed defect (fixed)
tig @1.1_1 - checksum mismatch
Reported by: | maverickwoo (Maverick Woo) | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | tig |
Description
I will attached the log file if a port install after a port clean. First, the output:
---> Computing dependencies for tig ---> Fetching archive for tig ---> Attempting to fetch tig-1.1_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/tig ---> Attempting to fetch tig-1.1_1.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/tig ---> Attempting to fetch tig-1.1_1.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/tig ---> Fetching distfiles for tig ---> Verifying checksum(s) for tig Error: Checksum (rmd160) mismatch for tig-1.1.tar.gz Error: Checksum (sha256) mismatch for tig-1.1.tar.gz Error: org.macports.checksum for port tig returned: Unable to verify file checksums Please see the log file for port tig for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_tig/tig/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port tig failed
Attachments (1)
Change History (7)
Changed 11 years ago by maverickwoo (Maverick Woo)
comment:1 follow-up: 2 Changed 11 years ago by cooljeanius (Eric Gallager)
comment:2 follow-up: 3 Changed 11 years ago by larryv (Lawrence Velázquez)
Owner: | changed from macports-tickets@… to cal@… |
---|---|
Port: | tig added |
Summary: | tig @1.1 revision 1 - checksum mismatch → tig @1.1_1 - checksum mismatch |
comment:3 Changed 11 years ago by cooljeanius (Eric Gallager)
comment:4 Changed 11 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks, r106632.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
They've changed back; see #39896.
Note: See
TracTickets for help on using
tickets.
relevant part of log: