Opened 13 years ago

Closed 13 years ago

#31135 closed defect (duplicate)

Can't install slime

Reported by: hans.vonkaraman@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.2
Keywords: Cc:
Port: slime

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Trying to run:

$sudo port install slime
--->  Computing dependencies for slime
--->  Verifying checksum(s) for slime
Error: Target org.macports.checksum returned:  does not exist in /opt/local/var/macports/distfiles/slime
Log for slime is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_slime/slime/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Log file:

<snip>

:msg:main 
:debug:main Executing org.macports.main (slime)
:debug:main Skipping completed org.macports.archivefetch (slime)
:debug:main Skipping completed org.macports.fetch (slime)
:debug:checksum checksum phase started at Tue Sep  6 19:30:30 NZST 2011
:notice:checksum --->  Verifying checksum(s) for slime
:debug:checksum Executing org.macports.checksum (slime)
:info:checksum --->  Checksumming 
:error:checksum Target org.macports.checksum returned:  does not exist in /opt/local/var/macports/distfiles/slime
:debug:checksum Backtrace:  does not exist in /opt/local/var/macports/distfiles/slime
    while executing
"$procedure $targetname"
:info:checksum Warning: the following items did not execute (for slime): org.macports.activate org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install
:notice:checksum Log for slime is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_slime/slime/main.log

Change History (1)

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

Description: modified (diff)
Port: slime added
Resolution: duplicate
Status: newclosed

Duplicate of #31073.

Note: See TracTickets for help on using tickets.