Opened 10 years ago

Closed 10 years ago

#28175 closed defect (worksforme)

ghostscript: checksum mismatch

Reported by: andy.wood@… Owned by: takanori@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: ghostscript

Description

Try as I might, I continue to get checksum errors when trying to install ghostscript. Worked fine on my other mac (Snow Leopard), and I've tried cleaning, updating everything else, from macports to x11, to using Onyx to fix all permissions. I'm not an expert sys admin.

I'm attaching the log. Any help would be greatly appreciated.

Attachments (1)

buildlog_ghostscript.txt (44.1 KB) - added by andy.wood@… 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by andy.wood@…

Attachment: buildlog_ghostscript.txt added

comment:1 Changed 10 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Keywords: ghoscript checksum removed
Owner: changed from macports-tickets@… to takanori@…
Summary: checksum error installing ghostscript 9.0 on Leopardghostscript: checksum mismatch

Did you read the notice in the log you attached that says:

The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<http://trac.macports.org/wiki/MisbehavingServers>

Did you read the MisbehavingServers page? Did you examine the contents of the HTML file that was downloaded to see what it says?

comment:2 in reply to:  1 ; Changed 10 years ago by andy.wood@…

Replying to ryandesign@…:

Did you read the notice in the log you attached that says:

The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<http://trac.macports.org/wiki/MisbehavingServers>

Did you read the MisbehavingServers page? Did you examine the contents of the HTML file that was downloaded to see what it says?


Thanks for responding. I did in fact read the log and also visited the page. I looked for the HTML file without success -- where would it be located? The error msg and log don't give much info on that. I've also tried the install from different locations, cities, ISPs, etc. without success, and installed numerous other packages, which suggests it's not my firewall or ISP. Any info on the offending HTML file would help; also on other strategies for diagnosing it. Thanks, -Andy

comment:3 Changed 10 years ago by jmroot (Joshua Root)

Type: requestdefect

comment:4 in reply to:  2 ; Changed 10 years ago by jmroot (Joshua Root)

Replying to andy.wood@…:

I looked for the HTML file without success -- where would it be located?

See the first line of the output of port distfiles ghostscript.

comment:5 in reply to:  4 Changed 10 years ago by andy.wood@…

Replying to jmr@…:

Replying to andy.wood@…:

I looked for the HTML file without success -- where would it be located?

See the first line of the output of port distfiles ghostscript.

thanks for fixing the type. I checked the dir from that output, but found no HTML.

ls -l /opt/local/var/macports/distfiles/ghostscript/
-rw-r--r--  1 root  admin    44310 Dec  7 21:21 ghostscript-9.00.tar.gz
-rw-r--r--  1 root  admin   796086 Dec  7 21:30 ghostscript-fonts-other-6.0.tar.gz
-rw-r--r--  1 root  admin   371345 Dec  7 21:30 mappingresources4pdf_2unicode-20091208.tar.Z
-rw-r--r--  1 root  admin  1403027 Dec  7 21:30 mappingresources4pdf_other-20091208.tar.Z

I wiped out the files, though, did a install clean ghostscript and then tried a new install and the install worked. I wonder if one of the files didn't download fully the first time, and then the remaining tries stumbled on the same file.

thanks again for the help. I think this ticket can be closed. -- Andy

comment:6 Changed 10 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed

Per the original error message, the file ghostscript-9.00.tar.gz was the HTML file. If you had opened it in a text editor, you could have seen what it said.

You are correct that MacPorts will not attempt to re-download a file of a particular name that is already there, even if the file that is already there is not the right one. Clearing out the distfiles manually, as you did, or running "sudo port clean --all <portname>", which does about the same thing, lets MacPorts try downloading the files again.

Note: See TracTickets for help on using tickets.