Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#39113 closed defect (invalid)

'port -f clean --all all' aborts with unintelligible error

Reported by: istlota@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port:

Description (last modified by larryv (Lawrence Velázquez))

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 "}|̂}|͹oH͹oVcc¤´­p"

I tried twice and got the same unintelligible error each time. Running port rev-upgrade reports no broken files found.

Attachments (1)

051713 port clean error (24.4 KB) - added by istlota@… 11 years ago.
scrollback buffer from terminal session

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by istlota@…

Attachment: 051713 port clean error added

scrollback buffer from terminal session

comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)

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

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

Cc: ryandesign@… added

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?

comment:3 in reply to:  2 ; Changed 11 years ago by istlota@…

Replying to 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?

comment:4 in reply to:  3 Changed 11 years ago by larryv (Lawrence Velázquez)

Resolution: invalid
Status: newclosed

Replying to istlota@…:

For future reference, where can I find a list of ports in the order that 'port clean' cleans them?

% port echo all

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

MacPorts cleans ports in the order you specify; since you specified the pseudoport "all", that's the order it'll use.

Note: See TracTickets for help on using tickets.