On Qui, 2014-09-25 at 19:27 +0200, Julian Sikorski wrote:
> W dniu 25.09.2014 o 17:26, Sérgio Basto pisze:
>> On Qui, 2014-09-25 at 07:47 +0200, Julian Sikorski wrote:
>>> W dniu 21.09.2014 o 23:20, Sérgio Basto pisze:
>>>> On Dom, 2014-09-21 at 19:03 +0200, Julian Sikorski wrote:
>>>>> Dear all,
>>>>>
>>>>> ffmpeg-2.4 was released recently which means we have another rebuild
>>>>> coming up. I have done a test and only 4 packages have failed, which
is
>>>>> not bad given the extent of API changes:
>>>>> - alsa-plugins-freeworld: pcm_a52.c:101:45: error: 'struct
a52_ctx' has
>>>>> no member named 'frame'
>>>>> - dvbcut: lavfmuxer.cpp:63:57: error: 'av_new_stream' was not
declared
>>>>> in this scope
>>>>> - kmediafactory: videofile.cpp:74:45: error:
'av_find_stream_info' was
>>>>> not declared in this scope (mencoder needs to be rebuilt first)
>>>>> - vlc: configure: error: libavcodec versions 56 and later are not
>>>>> supported yet.
>>>>>
>>>>> Given that we are close to branching (?), what would be the good time
to
>>>>> do the rebuild?
>>>>
>>>> yes, I don't see any problem, I can do the mass rebuild of others
>>>> packages, no problem.
>>>>
>>>> My question if we ever put this updates on F20 ? I'd like put it at
>>>> least on update-testing. I can made a list of the packages, with
>>>> ffmpeg / x264 dependencies, that should stay on update-testing for more
>>>> time than usual, but is not my decision .
>>>>
>>>>
>>>> Best regards,
>>>>
>>> ffmpeg-2.4.1 has now been built. I will take care of rebuilding mplayer.
>>>
>>> Best regards,
>>> Julian
>>
>> Hi, please wait, let's wait to know if kwizart allow us to put ffmpeg
>> 2.3.3 in F20, we think it is better and we have strong reasons , like
>> explained in
>>
https://lists.rpmfusion.org/pipermail/rpmfusion-developers/2014-September...
>>
>> Kwizart , do you allow this exception ?
>>
>>
>> Thanks,
>>
> Just to be clear: I only pushed it to devel. F20 is still an open question.
yes , but I want copy from devel to F20, the state of art , before
upgrading to ffmpeg 2.4 , will be more easier , clean etc , and just
after this update (on F20), update devel to ffmpeg 2.4
Thanks,
Hi,
it seems like we had a bit of misunderstanding. I was under the
impression we are good to go with 2.4 in rawhide, and 2.2/2.3 for F20 is
what we were discussing.
I don't think it makes sense to roll back now, let's just rebuild the
dependencies to minimise breakage time.
I think I should apply for the ffmpeg deps commit access moving forward,
so that there are more people who can do the rebuild.
Best regards,
Julian