Problems installing ffmpeg 1.2.1

John King johnk at media.berkeley.edu
Fri May 24 09:55:38 PDT 2013


Thanks for your help guys.

What worked was to
1) "sudo port selfupdate"
2) "sudo port upgrade outdated"

During step 2, the 1.2.1 version of ffmpeg was built and installed 
successfully. probably because I had already tried to in install it as 
per my email.

Maybe  step 2 installed some newer dependencies that the 1.2.1 port file 
called for but were somehow not installed during the first ffmpeg 
install attempt?

In any event I now have a working ffmpeg 1.2.1

Appreciate the quick responses.

John K


On 5/23/13 9:03 PM, Ryan Schmidt wrote:
> On May 23, 2013, at 18:39, Brandon Allbery wrote:
>> On Thu, May 23, 2013 at 7:11 PM, John King wrote:
>>> Having a problem getting the 1.2.1 version installed.  When I search for ffmpeg in available ports, the result I see is ffmpeg 1.2.1 and the associated Portfile also lists 1.2.1 as the version.
>>>
>>> However, when I run "sudo port install ffmpeg +nonfree", I get version 1.1.2 installed.
>> At a guess, it's getting installed and then immediately deactivated and replaced with the older version because of dependencies broken by the new one.
> I'm not aware of any feature in MacPorts that would cause that to happen—aside from explicitly requesting that (e.g. "sudo port activate ffmpeg @1.1.2_0+gpl2"), but John isn't doing that.
>
>> Use "upgrade" instead of "install" to make sure those dependencies are also updated to use the new version;
> "install" and "upgrade" both upgrade dependencies first—unless you explicitly request for that not to happen, by using the "-n" flag, but John isn't doing that.
>
>> or if that also ends up re-downgrading you in the rev-upgrade step following the upgrade, then make a note of the ports which were noted as broken in rev-upgrade and file Trac tickets against them, as that would indicate they have dependencies they are not declaring properly.
> John, have you run "sudo port selfupdate" to make sure your ports and MacPorts base are up to date? If so, and this is still happening, is it possible you have deliberately set up a local portfile repository, which contains this older ffmpeg 1.1.2 port? Check your sources.conf file for unusual entries.
>
>


-- 
John King
Applications Programmer
Learning Systems Group
Educational Technology Services
9 Dwinelle Hall - Mail
117 Dwinelle Hall - Office
University of California
Berkeley, CA 94720-2535
Phone: 510-529-5074
Email: johnk at media.berkeley.edu



More information about the macports-users mailing list