Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#32540 closed defect (fixed)

tidy build fails on PPC — at Version 1

Reported by: dgonyier (Dwaine Gonyier) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ryandesign@…
Port: tidy

Description (last modified by neverpanic (Clemens Lang))

--->  Fetching archive for tidy
--->  Attempting to fetch tidy-20090325_0.darwin_9.ppc.tbz2 from http://packages.macports.org/tidy
--->  Fetching tidy
--->  Attempting to fetch tidy-20090325.tar.bz2 from http://gentoo.ynet.sk/pub/distfiles/
--->  Verifying checksum(s) for tidy
Error: Checksum (md5) mismatch for tidy-20090325.tar.bz2
Error: Checksum (sha1) mismatch for tidy-20090325.tar.bz2
Error: Checksum (rmd160) mismatch for tidy-20090325.tar.bz2
***
The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<https://trac.macports.org/wiki/MisbehavingServers>
***
Error: Target org.macports.checksum returned: Unable to verify file checksums
Error: Failed to install tidy
Log for tidy is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_tidy/tidy/main.log
Error: The following dependencies were not installed: tidy xercesc3
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Change History (3)

Changed 12 years ago by dgonyier (Dwaine Gonyier)

Attachment: main.log added

Port build log

Changed 12 years ago by dgonyier (Dwaine Gonyier)

Attachment: tidy-20090325.tar.bz2 added

contents of tidy-20090325.tar.bz2

comment:1 Changed 12 years ago by neverpanic (Clemens Lang)

Cc: ryandesign@… added
Description: modified (diff)
Resolution: invalid
Status: newclosed

Please remember to use WikiFormatting and Cc the maintainer.

This is not a build, but a fetch/download problem. Please see MisbehavingServers as advised in the error message and rule out the possible causes on your side (since the mirror gentoo.ynet.sk does not resolve for me, it's probably the problem listed first in MisbehavingServers).

Note: See TracTickets for help on using tickets.