Opened 2 years ago

Last modified 17 months ago

#65312 closed defect

bowtie v 1.2.3 — at Version 2

Reported by: Minhas61 Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: bowtie

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

I am trying to install bowtie v 1.2.3 on MacOS Monterey version 12.2.1, However, I am getting the following error.

Error: Failed to build bowtie: command execution failed  
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_bowtie/bowtie/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port bowtie failed
--->  Some of the ports you installed have notes:
  python27 has the following notes:
    To make this the default Python or Python 2 (i.e., the version run by the
    'python' or 'python2' commands), run one or both of:
    
        sudo port select --set python python27
        sudo port select --set python2 python27

Could you please guide how can I address this issue

Change History (2)

comment:1 Changed 2 years ago by Minhas61

Error: Failed to build bowtie: command execution failed  
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_bowtie/bowtie/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port bowtie failed
--->  Some of the ports you installed have notes:
  python27 has the following notes:
    To make this the default Python or Python 2 (i.e., the version run by the
    'python' or 'python2' commands), run one or both of:
    
        sudo port select --set python python27
        sudo port select --set python2 python27
Last edited 2 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

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

Description: modified (diff)

Please attach the main.log file so that we can see what happened.

Note: See TracTickets for help on using tickets.