Hi,
On 23-10-15 13:57, Sérgio Basto wrote:
> Hello mates
>
> On Qui, 2015-10-22 at 22:27 +0200, Nicolas Chauvet wrote:
>
>> 2015-10-12 8:30 GMT+02:00 Hans de Goede <j.w.r.degoede(a)gmail.com>:
>> Hi All,
>>
>> I'm getting requests to update the gstreamer packages to 1.6.x
>> for Fedora-23:
>>
>>
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3794
>>
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3795
>>
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3796
>>
>> But AFAIK we are not building any packages for F-23 yet. What
>> are the
>> plans here ?
>> Sorry for the lake for answear,
>>
>>
>> The development/23 repository layout will probably stay some time
>> after fedora 23 GA, which means the repository won't be frozen.
>>
>> development/23 is basically f22 packaged resigned with the f23 key,
>> updates-testing will be f23 specifics packages
>> (x264/ffmpeg/gst/others)
>>
>>
>> Once everything got more into shape, we merge them into releases/23
>> later, but at least, the plan is still to have usable state from
>> end-user point of view at GA time.(1 week delay!)
>>
>> As we can see/deduce, kwizart open a window to update F23 with
> x264/ffmpeg/gst/mplayer/others , which means a mass rebuild ! and I'd
> like try do it in oneshot ...
>
> Following ImportantDependencyLists [1] I have submit x264-0.148
> yesterday for F23 .
>
> I think is important show to others mates what is going on so, I had
> publish a copy of what was submit in github [2] (and is only a copy!) ,
> I don't know if Julian is available , but I'd like see some coordination
> to update ffmpeg to latest (2.8.1) , update mplayer as Dominik suggest
> and check if there is more packages to update that imply soname bump .
>
Having some definite plans what to do with ffmpeg for rpmfusion would
be great. I plan to update the gstreamer10-* packages to 1.6.x for
F-23 and gstreamer1-libav now is using ffmpeg rather then libav despite
its name, so I hope that I can build it against the system ffmpeg.
We will probably be using the lastest ffmpeg-2.8.1 altought it's not
completely well known for the amount of work to make that very recent
version fit.
Right now x265 and xvidcore are failing.
Thx
--
-
Nicolas (kwizart)