Opened 20 months ago

Last modified 20 months ago

#67184 closed defect

optool: no such file or directory — at Version 1

Reported by: cbitterfield (Colin Bitterfield) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc:
Port: optool

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

Error: Failed to extract optool: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_optool/optool/work/ArgumentParser-2802076f2351303c182b43efb583616750474f38" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_optool/optool/work/optool-0.1/optool/FSArgumentParser": no such file or directory
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_optool/optool/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port optool failed

Change History (2)

Changed 20 months ago by cbitterfield (Colin Bitterfield)

Attachment: main.log​ added

Log File

comment:1 Changed 20 months ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Owner: set to raimue
Status: new → assigned
Summary: Problem installing → optool: no such file or directory
Version: → 2.8.1

Confirmed. Probably just wrong worksrcdir.

Note: See TracTickets for help on using tickets.