Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#63286 closed defect (fixed)

developer_cmds @63 conflicts with pywhat @3.2.0

Reported by: cooljeanius (Eric Gallager) Owned by: harens <harensdeveloper@…>
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: harens (Haren S)
Port: developer_cmds pywhat

Description

They both try to install an executable named what:

x ./opt/local/bin/what
x ./opt/local/bin/asa
x ./opt/local/bin/unifdefall
x ./opt/local/bin/lorder
Error: Failed to activate developer_cmds: Image error: /opt/local/bin/what is being used by the active pywhat port.  Please deactivate this port first, or use 'port -f activate developer_cmds' to force the activation.
DEBUG: Error code: registry::image-error
DEBUG: Backtrace: Image error: /opt/local/bin/what is being used by the active pywhat port.  Please deactivate this port first, or use 'port -f activate developer_cmds' to force the activation.
    invoked from within
"throw registry::image-error "Image error: $file is being used by the active [$owner name] port.  Please deactivate this port first, or use 'port -f ac..."
    ("foreach" body line 45)
    invoked from within
"foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to install links, we test if we can lst..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to instal..."
    invoked from within
"try {
        registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be ..."
    (procedure "_activate_contents" line 21)
    invoked from within
"_activate_contents $requested $rename_list"
    (procedure "portimage::activate" line 63)
    invoked from within
"registry_activate $subport $_inregistry_version $_inregistry_revision $_inregistry_variants $optionlist"
    (procedure "portactivate::activate_main" line 20)
    invoked from within
"$procedure $targetname"
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_developer_cmds/developer_cmds/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port developer_cmds failed

This conflict should either be marked, or fixed (for example, by renaming pywhat's executable from what to pywhat)

Change History (2)

comment:1 Changed 3 years ago by harens <harensdeveloper@…>

Owner: set to harens <harensdeveloper@…>
Resolution: fixed
Status: newclosed

In ba0fd327c0f816202565fa44e01efa602690edc0/macports-ports (master):

pywhat: remove what binary

pywhat binary still available, and does the same thing.

Closes: #63286

comment:2 Changed 3 years ago by harens (Haren S)

Thanks Eric for opening this ticket.

This conflict should either be marked, or fixed (for example, by renaming pywhat's executable from what to pywhat)

Funnily enough, both a pywhat and what executable are provided by default. Therefore, I just removed the what binary.

Thank you again Eric for raising this issue, as well as for your previous contributions. They're greatly appreciated.

Note: See TracTickets for help on using tickets.