[MacPorts] #39113: 'port -f clean --all all' aborts with unintelligible error
#39113: 'port -f clean --all all' aborts with unintelligible error -----------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -----------------------+-------------------------------- I run 'port -f clean --all all' about once a week as part of my regular routine maintenance tasks. When I ran it today, it aborted after the cleaning drush msg: Cleaning druntime ---> Cleaning drupal5 ---> Cleaning drupal6 ---> Cleaning drupal7 ---> Cleaning drush Error: Unable to open port: invalid command name "}|̂}|oHoVcc¤´p" I tried twice and got the same unintelligible error each time. Running port rev-upgrade reports no broken files found. -- Ticket URL: <https://trac.macports.org/ticket/39113> MacPorts <http://www.macports.org/> Ports system for OS X
#39113: 'port -f clean --all all' aborts with unintelligible error ------------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Old description:
I run 'port -f clean --all all' about once a week as part of my regular routine maintenance tasks. When I ran it today, it aborted after the cleaning drush msg:
Cleaning druntime ---> Cleaning drupal5 ---> Cleaning drupal6 ---> Cleaning drupal7 ---> Cleaning drush Error: Unable to open port: invalid command name "}|̂}|oHoVcc¤´p"
I tried twice and got the same unintelligible error each time. Running port rev-upgrade reports no broken files found.
New description: I run 'port -f clean --all all' about once a week as part of my regular routine maintenance tasks. When I ran it today, it aborted after the cleaning drush msg: {{{ ---> Cleaning druntime ---> Cleaning drupal5 ---> Cleaning drupal6 ---> Cleaning drupal7 ---> Cleaning drush Error: Unable to open port: invalid command name "}|̂}|oHoVcc¤´p" }}} I tried twice and got the same unintelligible error each time. Running port rev-upgrade reports no broken files found. -- Comment (by larryv@…): I don’t see anything wrong with the portfile. Perhaps yours has been corrupted somehow. Try this: {{{ % sudo rm $(port file drush) % sudo port selfupdate % sudo port clean --all all }}} -- Ticket URL: <https://trac.macports.org/ticket/39113#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#39113: 'port -f clean --all all' aborts with unintelligible error ------------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: According to the output, drush was successfully cleaned; it would be the port after drush: drwright. Does the problem always happen at the same port? Are the flags `-f` and `--all` necessary to reproduce the problem? Does just `sudo port clean drwright` produce the same error? -- Ticket URL: <https://trac.macports.org/ticket/39113#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#39113: 'port -f clean --all all' aborts with unintelligible error ------------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by istlota@…): Replying to [comment:2 ryandesign@…]:
According to the output, drush was successfully cleaned; it would be the port after drush: drwright. Does the problem always happen at the same port? Are the flags `-f` and `--all` necessary to reproduce the problem? Does just `sudo port clean drwright` produce the same error?
Thanks. 'sudo port clean drwright' fixed the problem. For future reference, where can I find a list of ports in the order that 'port clean' cleans them? -- Ticket URL: <https://trac.macports.org/ticket/39113#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#39113: 'port -f clean --all all' aborts with unintelligible error ------------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: invalid | Keywords: Port: | ------------------------+-------------------------------- Changes (by larryv@…): * status: new => closed * resolution: => invalid Comment: Replying to [comment:3 istlota@…]:
For future reference, where can I find a list of ports in the order that 'port clean' cleans them?
{{{ % port echo all }}} -- Ticket URL: <https://trac.macports.org/ticket/39113#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#39113: 'port -f clean --all all' aborts with unintelligible error ------------------------+-------------------------------- Reporter: istlota@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: invalid | Keywords: Port: | ------------------------+-------------------------------- Comment (by ryandesign@…): MacPorts cleans ports in the order you specify; since you specified the pseudoport "all", that's the order it'll use. -- Ticket URL: <https://trac.macports.org/ticket/39113#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts