Failure of "port upgrade outdated" after selfupdate

[LLLActive at GMX.Net]

On 21.01.13 20:18, Jeremy Lavergne wrote:
>> :debug:main Executing org.macports.main (ffmpeg)
>> :debug:main Skipping completed org.macports.archivefetch (ffmpeg)
>> :debug:main Skipping completed org.macports.fetch (ffmpeg)
>> :debug:main Skipping completed org.macports.checksum (ffmpeg)
>> :debug:main Skipping completed org.macports.extract (ffmpeg)
>> :debug:main Skipping completed org.macports.patch (ffmpeg)
>> :debug:main Skipping completed org.macports.configure (ffmpeg)
>> :debug:build build phase started at Mon Jan 21 18:28:20 CET 2013
>> :notice:build --->  Building ffmpeg
>> :debug:build Executing org.macports.build (ffmpeg)
> I'd recommend `sudo port clean ffmpeg` then run `sudo port -s install ffmpeg` to get a clean log of one attempt (`port logfile ffmpeg`). That log can then be attached to a ticket.
>
>
Thanks for the recommendation Jeremy. I did what you suggested.

A side question. Looking at the MacPorts for submitting tickets, there 
is a suggestion to run for "Is the problem with a 'port upgrade' 
operation?":

" ... try a 'port uninstall /|foo|/' and then reinstall. You might also 
want to run 'port -nR upgrade --force /|foo|/' to rebuild ports 
depending upon port /|foo|/". ( i.e. port -nR upgrade --force /|ffmpeg|/'//)

Is it OK in my case? I'm not sure if it will then provide the wrong info 
in the log file. In the mean time I will wade through Chapter 7.1 in 
"http://guide.macports.org/#project.tickets".


TIA

:-)

Dreiel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130121/562609c0/attachment.html>