Re: ffmpeg-2.4 released - kmediafactory patches

[Sérgio Basto]

Hi, I don't believe in myself , I call it ffmpeg-2.4.3 , to emphasize that
was a new ffmpeg release , not 2.4.0 and 2.4.1 , but in fact was a rebuild
for ffmpeg-2.4.2  , is the 3rd release of ffmpeg-2.4 (0, 1 and 2) but it is
ffmpeg-2.4.2 . I just notice this today .
Sorry about this confusion ...

Re: ffmpeg-2.4 released - kmediafactory patches

[David Timms]

On 23/10/14 09:15, Nicolas Chauvet wrote:
> 2014-10-22 14:26 GMT+02:00 David Timms  >:
> 
> On 22/10/14 23:23, David Timms wrote:
> > No testing of the binary package at all, but I think the changes seem
> > good. I don't have commit access so someone else will need sort that
> > side out, see attached.
> >
> > If no super-packager can commit, then I can make a bug to hold the
> > patches, just let me know.
> And just remembered that I commented out two requires, so here is the
> more correct spec file. (fully untested; couldn't work out the bunch of
> new ffmpeg related builds that could let me upgrade mlt/dvd-slideshow to
> suit kmediafactory.
>  
> I've added you to the package acl, you can commit it youslef.
OK, that's another way, I didn't want to step on the packager's toes...
Shall do.

Dave.

Re: ffmpeg-2.4 released - kmediafactory patches

[Nicolas Chauvet]

2014-10-22 14:26 GMT+02:00 David Timms :

> On 22/10/14 23:23, David Timms wrote:
> > No testing of the binary package at all, but I think the changes seem
> > good. I don't have commit access so someone else will need sort that
> > side out, see attached.
> >
> > If no super-packager can commit, then I can make a bug to hold the
> > patches, just let me know.
> And just remembered that I commented out two requires, so here is the
> more correct spec file. (fully untested; couldn't work out the bunch of
> new ffmpeg related builds that could let me upgrade mlt/dvd-slideshow to
> suit kmediafactory.
>


I've added you to the package acl, you can commit it youslef.

Thx

-- 
-

Nicolas (kwizart)

Re: ffmpeg-2.4 released - kmediafactory patches

[Sérgio Basto]

On Wed, Oct 22, 2014 at 1:26 PM, David Timms  wrote:

> On 22/10/14 23:23, David Timms wrote:
> > No testing of the binary package at all, but I think the changes seem
> > good. I don't have commit access so someone else will need sort that
> > side out, see attached.
> >
> > If no super-packager can commit, then I can make a bug to hold the
> > patches, just let me know.
> And just remembered that I commented out two requires, so here is the
> more correct spec file. (fully untested; couldn't work out the bunch of
> new ffmpeg related builds that could let me upgrade mlt/dvd-slideshow to
> suit kmediafactory.
>
> Again, needs testing.
>
> Dave.
>

Hi, I can do that and I will do that, but maybe just tomorrow night, until
then I'm too busy .

Sorry , thanks for the patches

Re: ffmpeg-2.4 released - kmediafactory patches

[David Timms]

On 22/10/14 23:23, David Timms wrote:
> No testing of the binary package at all, but I think the changes seem
> good. I don't have commit access so someone else will need sort that
> side out, see attached.
> 
> If no super-packager can commit, then I can make a bug to hold the
> patches, just let me know.
And just remembered that I commented out two requires, so here is the
more correct spec file. (fully untested; couldn't work out the bunch of
new ffmpeg related builds that could let me upgrade mlt/dvd-slideshow to
suit kmediafactory.

Again, needs testing.

Dave.
Name:   kmediafactory
Summary:A template based DVD authoring tool
Version:0.8.1
Release:18%{?dist}

License:GPLv2+
URL:http://code.google.com/p/kmediafactory/ 
Source0:http://kmediafactory.googlecode.com/files/kmediafactory-%{version}.tar.bz2

# rpmfusion's mlt binary is named mlt-melt:
Patch1: kmediafactory-0.8.0-mlt-melt.patch

## upstreamable patches
# http://code.google.com/p/kmediafactory/issues/detail?id=19
Patch50: kmediafactory-0.8.1-gcc47.patch
# http://code.google.com/p/kmediafactory/issues/detail?id=18
Patch51: kmediafactory-0.8.0-dso.patch
# fix for newer ffmpeg
Patch52: kmediafactory-0.8.1-ffmpeg.patch
# use kdelibs' FindFFMPEG.cmake instead of bundled FindFfmpeg.cmake here
Patch53: kmediafactory-0.8.1-FindFFmpeg.patch
# make kmediafactory.desktop pass desktop-file-validate
Patch54: kmediafactory-0.8.1-desktop_validate.patch
Patch55: kmediafactory-0.8.1-ffmpeg-2.4.3-compatibility.patch

BuildRequires:  desktop-file-utils
BuildRequires:  dvdauthor
BuildRequires:  dvd-slideshow
BuildRequires:  gettext
BuildRequires:  giflib-devel
BuildRequires:  kdelibs4-devel
BuildRequires:  libdvdread-devel 
BuildRequires:  mlt
BuildRequires:  mjpegtools 
BuildRequires:  pcre-devel
BuildRequires:  pkgconfig(QtWebKit)
## ffmpeg
BuildRequires:  pkgconfig(libavcodec) pkgconfig(libavformat) pkgconfig(libavutil) pkgconfig(libswscale)
BuildRequires:  pkgconfig(libkexiv2)
BuildRequires:  zip 

Requires: %{name}-libs%{?_isa} = %{version}-%{release}
Requires: kdebase-runtime%{?_kde4_version: >= %{_kde4_version}}

# needed for normal functionality
Requires: dvdauthor
Requires: dvd-slideshow
Requires: ffmpeg
Requires: mjpegtools
Requires: mplayer
# optional bits
#Requires(hint): mlt

%description
Kmediafactory is an easy to use template based dvd authoring tool. 
You can quickly create DVD menus for home videos and TV 
recordings in three simple steps.

%package libs
Summary: Runtime libraries for %{name}
Requires: %{name} = %{version}-%{release}
%description libs
%{summary}.

%package devel
Summary: Development files for %{name}
Requires: %{name}-libs%{?_isa} = %{version}-%{release}
%description devel
%{summary}.


%prep
%setup -q

%patch1 -p1 -b .mlt-melt
%patch50 -p1 -b .gcc47
%patch51 -p1 -b .dso
%patch52 -p1 -b .ffmpeg
%patch53 -p1 -b .FindFFmpeg
%patch54 -p1 -b .desktop_validate
%patch55 -p1 -b .ffmpeg243


%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%{cmake_kde4} ..
popd

make %{?_smp_mflags} -C %{_target_platform}


%install
make install/fast DESTDIR=%{buildroot} -C %{_target_platform}

# locale
%find_lang kmediafactory --with-kde
%find_lang kmediafactory_kstore
%find_lang kmediafactory_interface
%find_lang kmediafactory_output
%find_lang kmediafactory_slideshow
%find_lang kmediafactory_template
%find_lang kmediafactory_video
%find_lang libkmf
cat kmediafactory*.lang > kmediafactory-all.lang


%check
desktop-file-validate %{buildroot}%{_kde4_datadir}/applications/kde4/kmediafactory.desktop


%post
touch --no-create %{_kde4_iconsdir}/hicolor >& /dev/null || :
touch --no-create %{_datadir}/mime/packages &> /dev/null || :

%postun
if [ $1 -eq 0 ]; then
touch --no-create %{_kde4_iconsdir}/hicolor || :
gtk-update-icon-cache --quiet %{_kde4_iconsdir}/hicolor &> /dev/null || :
update-desktop-database &> /dev/null ||:
touch --no-create %{_datadir}/mime/packages &> /dev/null || :
update-mime-database %{?fedora:-n} %{_datadir}/mime &> /dev/null || :
fi

%posttrans
gtk-update-icon-cache --quiet %{_kde4_iconsdir}/hicolor &> /dev/null || :
update-desktop-database &> /dev/null ||:
update-mime-database %{?fedora:-n} %{_datadir}/mime &> /dev/null || :

%files -f kmediafactory-all.lang
%doc AUTHORS ChangeLog COPYING CREDITS NEWS README TODO
%{_kde4_bindir}/kmediafactory
%{_kde4_appsdir}/kmediafactory/
%{_kde4_appsdir}/kmediafactory_template/
%{_kde4_appsdir}/kmfwidgets/
%{_kde4_datadir}/config.kcfg/*
%{_kde4_datadir}/config/*
%{_kde4_datadir}/kde4/services/*
%{_kde4_datadir}/kde4/servicetypes/*
%{_kde4_iconsdir}/hicolor/*/*/*
%{_kde4_libdir}/kde4/kmediafactory_*
%{_kde4_libdir}/kde4/plugins/designer/kmfwidgets.so
%{_kde4_datadir}/applications/kde4/kmediafactory.desktop
%{_datadir}/mime/packages/kmediafactory.xml

%post libs -p /sbin/ldconfig
%postun libs -p /sbin/ldconfig

%files libs -f libkmf.lang
%{_kde4_libdir}/libkmediafactoryinterfaces.so.0*
%{_kde4_libdir}/libkmediafactorykstore.so.0*

Re: ffmpeg-2.4 released - kmediafactory patches

[David Timms]

On 21/10/14 01:22, Sérgio Basto wrote:
> On Sun, Oct 19, 2014 at 12:11 PM, Nicolas Chauvet  > wrote:
...
> Please lead the rebuild so everything can be done in one push.
> I may hold the rawhide push until everything get in.
> But I would also have everything not failing, so please someone to
> have a look on the two remaining failing packages.
> We are rather late in the Fedora 21 release process
> 
> At worst I will remove the two package from the f21 tree until fixed.
> 
> 
> Done , only package that fails to rebuild was kmediafactory ...
...
I've also taken a look at getting kmedifactory to compile on my F21 test
machine, but with some it's deps downloaded from the ffmpeg 2.4.2(3?)
builds, and have had compile success.

No testing of the binary package at all, but I think the changes seem
good. I don't have commit access so someone else will need sort that
side out, see attached.

If no super-packager can commit, then I can make a bug to hold the
patches, just let me know.

Dave.
Name:   kmediafactory
Summary:A template based DVD authoring tool
Version:0.8.1
Release:18%{?dist}

License:GPLv2+
URL:http://code.google.com/p/kmediafactory/ 
Source0:http://kmediafactory.googlecode.com/files/kmediafactory-%{version}.tar.bz2

# rpmfusion's mlt binary is named mlt-melt:
Patch1: kmediafactory-0.8.0-mlt-melt.patch

## upstreamable patches
# http://code.google.com/p/kmediafactory/issues/detail?id=19
Patch50: kmediafactory-0.8.1-gcc47.patch
# http://code.google.com/p/kmediafactory/issues/detail?id=18
Patch51: kmediafactory-0.8.0-dso.patch
# fix for newer ffmpeg
Patch52: kmediafactory-0.8.1-ffmpeg.patch
# use kdelibs' FindFFMPEG.cmake instead of bundled FindFfmpeg.cmake here
Patch53: kmediafactory-0.8.1-FindFFmpeg.patch
# make kmediafactory.desktop pass desktop-file-validate
Patch54: kmediafactory-0.8.1-desktop_validate.patch
Patch55: kmediafactory-0.8.1-ffmpeg-2.4.3-compatibility.patch

BuildRequires:  desktop-file-utils
BuildRequires:  dvdauthor
#B#uildRequires:  dvd-slideshow
BuildRequires:  gettext
BuildRequires:  giflib-devel
BuildRequires:  kdelibs4-devel
BuildRequires:  libdvdread-devel 
#B#uildRequires:  mlt
BuildRequires:  mjpegtools 
BuildRequires:  pcre-devel
BuildRequires:  pkgconfig(QtWebKit)
## ffmpeg
BuildRequires:  pkgconfig(libavcodec) pkgconfig(libavformat) pkgconfig(libavutil) pkgconfig(libswscale)
BuildRequires:  pkgconfig(libkexiv2)
BuildRequires:  zip 

Requires: %{name}-libs%{?_isa} = %{version}-%{release}
Requires: kdebase-runtime%{?_kde4_version: >= %{_kde4_version}}

# needed for normal functionality
Requires: dvdauthor
Requires: dvd-slideshow
Requires: ffmpeg
Requires: mjpegtools
Requires: mplayer
# optional bits
#Requires(hint): mlt

%description
Kmediafactory is an easy to use template based dvd authoring tool. 
You can quickly create DVD menus for home videos and TV 
recordings in three simple steps.

%package libs
Summary: Runtime libraries for %{name}
Requires: %{name} = %{version}-%{release}
%description libs
%{summary}.

%package devel
Summary: Development files for %{name}
Requires: %{name}-libs%{?_isa} = %{version}-%{release}
%description devel
%{summary}.


%prep
%setup -q

%patch1 -p1 -b .mlt-melt
%patch50 -p1 -b .gcc47
%patch51 -p1 -b .dso
%patch52 -p1 -b .ffmpeg
%patch53 -p1 -b .FindFFmpeg
%patch54 -p1 -b .desktop_validate
%patch55 -p1 -b .ffmpeg243


%build
mkdir -p %{_target_platform}
pushd %{_target_platform}
%{cmake_kde4} ..
popd

make %{?_smp_mflags} -C %{_target_platform}


%install
make install/fast DESTDIR=%{buildroot} -C %{_target_platform}

# locale
%find_lang kmediafactory --with-kde
%find_lang kmediafactory_kstore
%find_lang kmediafactory_interface
%find_lang kmediafactory_output
%find_lang kmediafactory_slideshow
%find_lang kmediafactory_template
%find_lang kmediafactory_video
%find_lang libkmf
cat kmediafactory*.lang > kmediafactory-all.lang


%check
desktop-file-validate %{buildroot}%{_kde4_datadir}/applications/kde4/kmediafactory.desktop


%post
touch --no-create %{_kde4_iconsdir}/hicolor >& /dev/null || :
touch --no-create %{_datadir}/mime/packages &> /dev/null || :

%postun
if [ $1 -eq 0 ]; then
touch --no-create %{_kde4_iconsdir}/hicolor || :
gtk-update-icon-cache --quiet %{_kde4_iconsdir}/hicolor &> /dev/null || :
update-desktop-database &> /dev/null ||:
touch --no-create %{_datadir}/mime/packages &> /dev/null || :
update-mime-database %{?fedora:-n} %{_datadir}/mime &> /dev/null || :
fi

%posttrans
gtk-update-icon-cache --quiet %{_kde4_iconsdir}/hicolor &> /dev/null || :
update-desktop-database &> /dev/null ||:
update-mime-database %{?fedora:-n} %{_datadir}/mime &> /dev/null || :

%files -f kmediafactory-all.lang
%doc AUTHORS ChangeLog COPYING CREDITS NEWS README TODO
%{_kde4_bindir}/kmediafactory
%{_kde4_appsdir}/kmediafactory/
%{_kde4_appsdir}/kmediafactory_template/
%{_kde4_appsdir}/kmfwidgets/
%{_kde4_datadir}/config.kcfg/*
%{_kde4_datadir}/con

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Sun, Oct 19, 2014 at 12:11 PM, Nicolas Chauvet  wrote:

> 2014-10-19 2:27 GMT+02:00 Sérgio Basto :
>
>> On Sex, 2014-10-17 at 07:37 +1100, David Timms wrote:
>> > I expect to have another look this weekend; however, don't hold up the
>> > update just due dvbcut...
>>
>> OK, so seems we don't have big issues , kwizart also agreed.
>> So if no impediments, I plan star mass rebuild for ffmpeg-2.4, tomorrow
>> Sunday, afternoon
>>
>> I'll follow this wikipage :
>>
>> http://rpmfusion.org/ImportantDependencyLists#only_ffmpeg_so_bump
>>
>>
>> in this order :
>> * build ffmpeg
>> * build gpac
>> * build x264 without bootstrap (depends on gpac and ffmpeg )
>> * build libquicktime (vlc, mjpegtools and mlt need it)
>> * build what requires ffmpeg-libs.
>>
>
> Please lead the rebuild so everything can be done in one push.
> I may hold the rawhide push until everything get in.
> But I would also have everything not failing, so please someone to have a
> look on the two remaining failing packages.
> We are rather late in the Fedora 21 release process
>
> At worst I will remove the two package from the f21 tree until fixed.
>

Done , only package that fails to rebuild was kmediafactory ...

I have updated wiki page section :
"some_other_deps_that_also_should_be_considered"  [1]


[1]
http://rpmfusion.org/ImportantDependencyLists#some_other_deps_that_also_should_be_considered


PS :
serjux.com have a hard disk failure with 100% data lost AFAIK and no
backup, so I'm using this mailbox  temporarily

Sérgio M. B.

Re: ffmpeg-2.4 released

[Nicolas Chauvet]

2014-10-19 2:27 GMT+02:00 Sérgio Basto :

> On Sex, 2014-10-17 at 07:37 +1100, David Timms wrote:
> > I expect to have another look this weekend; however, don't hold up the
> > update just due dvbcut...
>
> OK, so seems we don't have big issues , kwizart also agreed.
> So if no impediments, I plan star mass rebuild for ffmpeg-2.4, tomorrow
> Sunday, afternoon
>
> I'll follow this wikipage :
>
> http://rpmfusion.org/ImportantDependencyLists#only_ffmpeg_so_bump
>
>
> in this order :
> * build ffmpeg
> * build gpac
> * build x264 without bootstrap (depends on gpac and ffmpeg )
> * build libquicktime (vlc, mjpegtools and mlt need it)
> * build what requires ffmpeg-libs.
>

Please lead the rebuild so everything can be done in one push.
I may hold the rawhide push until everything get in.
But I would also have everything not failing, so please someone to have a
look on the two remaining failing packages.
We are rather late in the Fedora 21 release process

At worst I will remove the two package from the f21 tree until fixed.

Thx

-- 
-

Nicolas (kwizart)

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Sex, 2014-10-17 at 07:37 +1100, David Timms wrote:
> I expect to have another look this weekend; however, don't hold up the
> update just due dvbcut...

OK, so seems we don't have big issues , kwizart also agreed. 
So if no impediments, I plan star mass rebuild for ffmpeg-2.4, tomorrow
Sunday, afternoon

I'll follow this wikipage :

http://rpmfusion.org/ImportantDependencyLists#only_ffmpeg_so_bump


in this order : 
* build ffmpeg
* build gpac 
* build x264 without bootstrap (depends on gpac and ffmpeg ) 
* build libquicktime (vlc, mjpegtools and mlt need it)
* build what requires ffmpeg-libs. 

Best regards,
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[David Timms]

On 15/10/14 16:42, Julian Sikorski wrote:
...
> I don't think anything has changed since last time: dvbcut and
> kmediafactory fail to rebuild, vlc needs a patch, everything else builds
> fine. David Timms was working on making dvbcut work, but I have not
> heard from him regarding whether he was successful.
Hi, I currently don't have a dev/vm for F21, so haven't had much of a
look at dvbcut. Only got as far as making the net install CD.

However, in reality, dvbcut defaults to using it's own inbuilt demux,
with various ffmpeg output formats as options.

When I made changes to suit earlier ffmpeg, these followed the original
authors #if #end style checking for ffmpeg version. In some of these
areas, I hadn't worked out the details of what the new equivalent code
was going to be (and it was starting to look pretty messy), and hence
choosing some of the output types (ffmpeg) results in application fail.
 (help wanted from ffmpeg expert).

I expect to have another look this weekend; however, don't hold up the
update just due dvbcut...

Thanks, Dave.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 15.10.2014 o 00:38, Sérgio Basto pisze:
> Hi, 
> 
> On Ter, 2014-10-07 at 08:02 +0200, Julian Sikorski wrote: 
>>>
>> Please be advised that 2.3 was recently removed from the maintained
>> branches list:
>>
>> https://ffmpeg.org/pipermail/ffmpeg-devel/2014-September/162904.html
>>
>> Thus, if we ever rebase F-20, we should use 2.2 and not 2.3.
> 
> The mode I like to work and to coordinate the mass rebuild for a stable
> branch (F-20), is first be test in devel . We have packages in devel, we
> test it for some time and when we can say that are stable , so we could
> *copy* to F-20 , another point was: mass rebuild was for ffmpeg/x264 ,
> not only ffmpeg .
> So it is important have .specs for packages that compile in all Fedora
> releases. Having 2 trees, one for F20, other for devel , is just
> justified when is a very core package like udev or systemd  ... , but
> for rpmfusion the point is other, maintainers are not aware ... 
> So *theoretically* my solution was build ffmpeg 2.2 in devel, test it
> and copy to F-20 , but devel already have 2.3 so is not practical . 
> 
> Moving forward, just update "ffmpeg" on F20 seems to me acceptable ,
> like you wrote "only libavfilter has a soname bump (snip) This means
> that we really only need to rebuild dvdstyler, mpv and xbmc." but we
> miss the test phase, we need guarantee that ffmpeg version was tested ,
> any suggestion ?

ffmpeg-2.2 was in devel between March and August. Moreover, the reason
why upstream picked it over 2.3 was that it is used by more downstream
distros: OpenSUSE, SUSE Enterprise and ROSA [1]. If we let it sit in
-testing for a bit longer than usual, I believe this will be enough.

> 
> Saying that and giving up mass rebuild ffmpeg/x264 for F-20, no need
> preserve devel as is and we can do the mass rebuild for ffmpeg 2.4 on
> devel , anything pending ?

I don't think anything has changed since last time: dvbcut and
kmediafactory fail to rebuild, vlc needs a patch, everything else builds
fine. David Timms was working on making dvbcut work, but I have not
heard from him regarding whether he was successful.

> 
> BTW what packages (.spec) do you have ? that are different from stable
> branches to devel ?

Only ffmpeg and mplayer. ffmpeg due to its numerous dependencies, and
mplayer because it is highly dependent on ffmpeg.

> 
> Thanks and best regards,
> 

Thank you.

[1] https://trac.ffmpeg.org/wiki/Downstreams

Re: ffmpeg-2.4 released

[Sérgio Basto]

Hi, 

On Ter, 2014-10-07 at 08:02 +0200, Julian Sikorski wrote: 
> > 
> Please be advised that 2.3 was recently removed from the maintained
> branches list:
> 
> https://ffmpeg.org/pipermail/ffmpeg-devel/2014-September/162904.html
> 
> Thus, if we ever rebase F-20, we should use 2.2 and not 2.3.

The mode I like to work and to coordinate the mass rebuild for a stable
branch (F-20), is first be test in devel . We have packages in devel, we
test it for some time and when we can say that are stable , so we could
*copy* to F-20 , another point was: mass rebuild was for ffmpeg/x264 ,
not only ffmpeg .
So it is important have .specs for packages that compile in all Fedora
releases. Having 2 trees, one for F20, other for devel , is just
justified when is a very core package like udev or systemd  ... , but
for rpmfusion the point is other, maintainers are not aware ... 
So *theoretically* my solution was build ffmpeg 2.2 in devel, test it
and copy to F-20 , but devel already have 2.3 so is not practical . 

Moving forward, just update "ffmpeg" on F20 seems to me acceptable ,
like you wrote "only libavfilter has a soname bump (snip) This means
that we really only need to rebuild dvdstyler, mpv and xbmc." but we
miss the test phase, we need guarantee that ffmpeg version was tested ,
any suggestion ? 

Saying that and giving up mass rebuild ffmpeg/x264 for F-20, no need
preserve devel as is and we can do the mass rebuild for ffmpeg 2.4 on
devel , anything pending ? 

BTW what packages (.spec) do you have ? that are different from stable
branches to devel ?  

Thanks and best regards, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 07.10.2014 o 08:02, Julian Sikorski pisze:
> W dniu 04.10.2014 o 11:39, Julian Sikorski pisze:
>> W dniu 25.09.2014 o 21:04, Nicolas Chauvet pisze:
>>> 2014-09-25 20:44 GMT+02:00 Sérgio Basto
>>> >> >:
>>>
>>> On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote:
>>> > 2014-09-25 19:27 GMT+02:00 Julian Sikorski
>>> >> >:
>>> > 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.
>>> >
>>> >
>>> >
>>> > Can we care about rebuilding all dependencies at the same time ?
>>> >
>>> yes of course , I will take care ,
>>>
>>> but may I build all for new ffmpeg /x624 for F20 ?
>>>
>>>
>>> SO I NAK the ffmpeg update in F-20 because the way the update was done
>>> in Rawhide.
>>> I don't want to hear about it. This is not acceptable not to have
>>> coordinated the update.
>>> PERIOD.
>>>
>>>
>>> -- 
>>> -
>>>
>>> Nicolas (kwizart)
>>
>> In case this gets reconsidered at some point in the future: I have done
>> a test rebuild of F-20 dependecies against ffmpeg-2.3.4, and all 37 have
>> built correctly.
>> Moreover, only libavfilter has a soname bump (please find rpmsodiff
>> output attached). This means that we really only need to rebuild
>> dvdstyler, mpv and xbmc.
>>
>> Best regards,
>> Julian
>>
> Please be advised that 2.3 was recently removed from the maintained
> branches list:
> 
> https://ffmpeg.org/pipermail/ffmpeg-devel/2014-September/162904.html
> 
> Thus, if we ever rebase F-20, we should use 2.2 and not 2.3.
> 
> Best regards,
> Julian
> 
As expected, everything builds against ffmpeg-2.2.9 too. Relevant sodiff
attached.

Best regards,
Julian
	sonames only in ffmpeg-libs-2.1.5-1.fc20 [1]:
libavfilter.so.3	/usr/lib64/libavfilter.so.3.90.100

	sonames only in ffmpeg-libs-2.2.9-1.fc20 [2]:
libavfilter.so.4	/usr/lib64/libavfilter.so.4.2.100

	common sonames:
libavcodec.so.55	/usr/lib64/libavcodec.so.55.39.101	/usr/lib64/libavcodec.so.55.52.102
libavdevice.so.55	/usr/lib64/libavdevice.so.55.5.100	/usr/lib64/libavdevice.so.55.10.100
libavformat.so.55	/usr/lib64/libavformat.so.55.19.104	/usr/lib64/libavformat.so.55.33.100
libavresample.so.1	/usr/lib64/libavresample.so.1.1.0	/usr/lib64/libavresample.so.1.2.0
libavutil.so.52	/usr/lib64/libavutil.so.52.48.101	/usr/lib64/libavutil.so.52.66.100
libpostproc.so.52	/usr/lib64/libpostproc.so.52.3.100	/usr/lib64/libpostproc.so.52.3.100
libswresample.so.0	/usr/lib64/libswresample.so.0.17.104	/usr/lib64/libswresample.so.0.18.100
libswscale.so.2	/usr/lib64/libswscale.so.2.5.101	/usr/lib64/libswscale.so.2.5.102

--- ffmpeg-libs-2.1.5-1.fc20/libavcodec.so.55	2014-07-09 00:08:31.0 +0200
+++ ffmpeg-libs-2.2.9-1.fc20/libavcodec.so.55	2014-10-07 08:19:24.013645000 +0200
@@ -11,2 +11,3 @@
 av

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 04.10.2014 o 11:39, Julian Sikorski pisze:
> W dniu 25.09.2014 o 21:04, Nicolas Chauvet pisze:
>> 2014-09-25 20:44 GMT+02:00 Sérgio Basto
>> > >:
>>
>> On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote:
>> > 2014-09-25 19:27 GMT+02:00 Julian Sikorski
>> > >:
>> > 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.
>> >
>> >
>> >
>> > Can we care about rebuilding all dependencies at the same time ?
>> >
>> yes of course , I will take care ,
>>
>> but may I build all for new ffmpeg /x624 for F20 ?
>>
>>
>> SO I NAK the ffmpeg update in F-20 because the way the update was done
>> in Rawhide.
>> I don't want to hear about it. This is not acceptable not to have
>> coordinated the update.
>> PERIOD.
>>
>>
>> -- 
>> -
>>
>> Nicolas (kwizart)
> 
> In case this gets reconsidered at some point in the future: I have done
> a test rebuild of F-20 dependecies against ffmpeg-2.3.4, and all 37 have
> built correctly.
> Moreover, only libavfilter has a soname bump (please find rpmsodiff
> output attached). This means that we really only need to rebuild
> dvdstyler, mpv and xbmc.
> 
> Best regards,
> Julian
> 
Please be advised that 2.3 was recently removed from the maintained
branches list:

https://ffmpeg.org/pipermail/ffmpeg-devel/2014-September/162904.html

Thus, if we ever rebase F-20, we should use 2.2 and not 2.3.

Best regards,
Julian

Re: ffmpeg-2.4 released

[David Timms]

On 02/10/14 22:52, David Timms wrote:
> On 02/10/14 15:36, Julian Sikorski wrote:
..
>>> Which packages are remaining please ?
>>>
>> dvbcut and kmediafactory.
> I should have time this weekend to look at my dvbcut package.
> Any hints welcome...
> Dave.

I did a mock test build with:
mock -r fedora-rawhide-x86_64-rpmfusion_free --rebuild
/home/davidt/rpmbuild/SRPMS/dvbcut-0.6.1-17.svn179.fc20.src.rpm

This build completed.

So am wondering, what mock config to do the testing/changes that this
thread is discussing ?

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 25.09.2014 o 21:04, Nicolas Chauvet pisze:
> 2014-09-25 20:44 GMT+02:00 Sérgio Basto
>  >:
> 
> On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote:
> > 2014-09-25 19:27 GMT+02:00 Julian Sikorski
>  >:
> > 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.
> >
> >
> >
> > Can we care about rebuilding all dependencies at the same time ?
> >
> yes of course , I will take care ,
> 
> but may I build all for new ffmpeg /x624 for F20 ?
> 
> 
> SO I NAK the ffmpeg update in F-20 because the way the update was done
> in Rawhide.
> I don't want to hear about it. This is not acceptable not to have
> coordinated the update.
> PERIOD.
> 
> 
> -- 
> -
> 
> Nicolas (kwizart)

In case this gets reconsidered at some point in the future: I have done
a test rebuild of F-20 dependecies against ffmpeg-2.3.4, and all 37 have
built correctly.
Moreover, only libavfilter has a soname bump (please find rpmsodiff
output attached). This means that we really only need to rebuild
dvdstyler, mpv and xbmc.

Best regards,
Julian
	sonames only in ffmpeg-libs-2.1.5-1.fc20 [1]:
libavfilter.so.3	/usr/lib64/libavfilter.so.3.90.100

	sonames only in ffmpeg-libs-2.3.4-1.fc20 [2]:
libavfilter.so.4	/usr/lib64/libavfilter.so.4.11.100

	common sonames:
libavcodec.so.55	/usr/lib64/libavcodec.so.55.39.101	/usr/lib64/libavcodec.so.55.69.100
libavdevice.so.55	/usr/lib64/libavdevice.so.55.5.100	/usr/lib64/libavdevice.so.55.13.102
libavformat.so.55	/usr/lib64/libavformat.so.55.19.104	/usr/lib64/libavformat.so.55.48.100
libavresample.so.1	/usr/lib64/libavresample.so.1.1.0	/usr/lib64/libavresample.so.1.3.0
libavutil.so.52	/usr/lib64/libavutil.so.52.48.101	/usr/lib64/libavutil.so.52.92.100
libpostproc.so.52	/usr/lib64/libpostproc.so.52.3.100	/usr/lib64/libpostproc.so.52.3.100
libswresample.so.0	/usr/lib64/libswresample.so.0.17.104	/usr/lib64/libswresample.so.0.19.100
libswscale.so.2	/usr/lib64/libswscale.so.2.5.101	/usr/lib64/libswscale.so.2.6.100

--- ffmpeg-libs-2.1.5-1.fc20/libavcodec.so.55	2014-07-09 00:08:31.0 +0200
+++ ffmpeg-libs-2.3.4-1.fc20/libavcodec.so.55	2014-10-03 08:15:03.239106000 +0200
@@ -11,2 +11,3 @@
 av_bitstream_filter_next	T
+av_codec_get_chroma_intra_matrix	T
 av_codec_get_codec_descriptor	T
@@ -19,2 +20,3 @@
 av_codec_next	T
+av_codec_set_chroma_intra_matrix	T
 av_codec_set_codec_descriptor	T
@@ -30,2 +32,4 @@
 av_dup_packet	T
+av_dv_codec_profile	T
+av_dv_frame_profile	T
 av_fast_malloc	T
@@ -64,5 +68,8 @@
 av_packet_new_side_data	T
+av_packet_pack_dictionary	T
 av_packet_ref	T
+av_packet_rescale_ts	T
 av_packet_shrink_side_data	T
 av_packet_split_side_data	T
+av_packet_unpack_dictionary	T
 av_packet_unref	T
@@ -87,2 +94,4 @@
 av_shrink_packet	T
+av_vdpau_alloc_context	T
+av_vdpau_get_profile	T
 av_vdpau_hwaccel_get_render2	T

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qui, 2014-10-02 at 08:00 +0200, Julian Sikorski wrote:
> >> Hi , Julian , that is the point, this is cvs , we don't have
> "upgrading
> >> in parallel", I try rolling devel to branches and yes "overwrite
> the f20
> >> spec" and what is in f20 spec is discard. Is the only rule of
> >> organization that we have .
> > 
> > I was not aware we have that rule. Until now, I was maintaining
> seperate
> > branches for ffmpeg and mplayer. I still believe that upgrading F-20
> > independently is better as it preserves the history better.
> 
> Case in point: rawhide ffmpeg has celt support disabled by default
> because the package has been retired in fedora. There is no reason to
> drop it in F-20.
> I have compared the F-20 and devel spec files, and the following
> changes
> are required if we decide to upgrade:
> - version bump to 2.3.x
> - rename README to README.md in %doc
> Please do not overwrite the F20 ffmpeg spec file. I think only makes
> sense for packages where the branches were kept at the same version at
> all times, which is not the case here.

Hi, no, for me what make sense is doing one spec that can be compiled at
all versions and use scriplets like : %if 0%{?fedora} < 21.
see VirtualBox/devel/VirtualBox.spec we even have : 

%if 0%{?fedora} > 11 || 0%{?rhel} > 5 

I have to go 


BTW : I had rebuild yesterday xine-lib , 


k3b-extras-freeworld
and mplayer 

so or wait that Kwizart publish or enable needsign repo and I hope not
have more broken deps .

kwizart, also I think we need put VirtualBox-4_3_16-1_fc19 and his
akmods on stable , since new kernel has enter in stable of F19 

Best regards, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qui, 2014-10-02 at 07:41 +0200, Julian Sikorski wrote: 
> W dniu 02.10.2014 o 01:46, Sérgio Basto pisze:
> > On Qua, 2014-10-01 at 19:38 +0200, Julian Sikorski wrote: 
> >> W dniu 25.09.2014 o 20:51, Sérgio Basto pisze:
> >>> 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/017393.html
> >
> > 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 , and it is more easier , clean etc , if just
> >>> after this (update ffmpeg to 2.4) . ...
> >>>
> >>>
> >>> Thanks, 
> >>>
> >> If we ever decide to upgrade f20 (which I don't think we will given the
> >> current fiasco), please do not overwrite the f20 spec with f21 one. I
> >> suggest comparing the two and upgrading in parallel, something like git
> >> cherry-pick.
> > 
> > Hi , Julian , that is the point, this is cvs , we don't have "upgrading
> > in parallel", I try rolling devel to branches and yes "overwrite the f20
> > spec" and what is in f20 spec is discard. Is the only rule of
> > organization that we have .
> 
> I was not aware we have that rule. Until now, I was maintaining seperate
> branches for ffmpeg and mplayer. I still believe that upgrading F-20
> independently is better as it preserves the history better.
> 
> > 
> > But the main problem was and still is, lack of time , so I and kwizart
> > (writing off-list) haven't much time next days and he point to try again
> > (the mass rebuild) no this weekend but next weekend, meantime
> > ffmpeg-2.3.3 still on devel (I think) . 
> > 
> > This is an ancient system so it give much work do all mass rebuild, see
> > if we can make a new builder happen.
> > 
> > Kwizart roll back to ffmpeg-2.3 , because though we haven't patches for
> > vlc build against ffmpeg2-4 and lack of time of course . 
> 
> What was wrong with the vlc patch I linked to?

Kwizart was not aware , at the time , just that  . 

> > 
> > Please be patient ...
> > 
> Julian

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[David Timms]

On 02/10/14 15:36, Julian Sikorski wrote:
> W dniu 01.10.2014 o 23:03, David Timms pisze:
>> On 02/10/14 03:51, Julian Sikorski wrote:
>> ...
>>> Looks like we are almost there. The two remaining packages have not been
>>> touched by upstream in ages and maybe we should reconsider whether it is
>>> worth carrying them.
>>
>> Which packages are remaining please ?
>>
> dvbcut and kmediafactory.
I should have time this weekend to look at my dvbcut package.
Any hints welcome...
Dave.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 02.10.2014 o 07:41, Julian Sikorski pisze:
> W dniu 02.10.2014 o 01:46, Sérgio Basto pisze:
>> On Qua, 2014-10-01 at 19:38 +0200, Julian Sikorski wrote: 
>>> W dniu 25.09.2014 o 20:51, Sérgio Basto pisze:
 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/017393.html
>>
>> 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 , and it is more easier , clean etc , if just
 after this (update ffmpeg to 2.4) . ...


 Thanks, 

>>> If we ever decide to upgrade f20 (which I don't think we will given the
>>> current fiasco), please do not overwrite the f20 spec with f21 one. I
>>> suggest comparing the two and upgrading in parallel, something like git
>>> cherry-pick.
>>
>> Hi , Julian , that is the point, this is cvs , we don't have "upgrading
>> in parallel", I try rolling devel to branches and yes "overwrite the f20
>> spec" and what is in f20 spec is discard. Is the only rule of
>> organization that we have .
> 
> I was not aware we have that rule. Until now, I was maintaining seperate
> branches for ffmpeg and mplayer. I still believe that upgrading F-20
> independently is better as it preserves the history better.

Case in point: rawhide ffmpeg has celt support disabled by default
because the package has been retired in fedora. There is no reason to
drop it in F-20.
I have compared the F-20 and devel spec files, and the following changes
are required if we decide to upgrade:
- version bump to 2.3.x
- rename README to README.md in %doc
Please do not overwrite the F20 ffmpeg spec file. I think only makes
sense for packages where the branches were kept at the same version at
all times, which is not the case here.

Best regards,
Julian

> 
>>
>> But the main problem was and still is, lack of time , so I and kwizart
>> (writing off-list) haven't much time next days and he point to try again
>> (the mass rebuild) no this weekend but next weekend, meantime
>> ffmpeg-2.3.3 still on devel (I think) . 
>>
>> This is an ancient system so it give much work do all mass rebuild, see
>> if we can make a new builder happen.
>>
>> Kwizart roll back to ffmpeg-2.3 , because though we haven't patches for
>> vlc build against ffmpeg2-4 and lack of time of course . 
> 
> What was wrong with the vlc patch I linked to?
> 
>>
>> Please be patient ...
>>
> Julian
> 

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 02.10.2014 o 01:46, Sérgio Basto pisze:
> On Qua, 2014-10-01 at 19:38 +0200, Julian Sikorski wrote: 
>> W dniu 25.09.2014 o 20:51, Sérgio Basto pisze:
>>> 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/017393.html
>
> 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 , and it is more easier , clean etc , if just
>>> after this (update ffmpeg to 2.4) . ...
>>>
>>>
>>> Thanks, 
>>>
>> If we ever decide to upgrade f20 (which I don't think we will given the
>> current fiasco), please do not overwrite the f20 spec with f21 one. I
>> suggest comparing the two and upgrading in parallel, something like git
>> cherry-pick.
> 
> Hi , Julian , that is the point, this is cvs , we don't have "upgrading
> in parallel", I try rolling devel to branches and yes "overwrite the f20
> spec" and what is in f20 spec is discard. Is the only rule of
> organization that we have .

I was not aware we have that rule. Until now, I was maintaining seperate
branches for ffmpeg and mplayer. I still believe that upgrading F-20
independently is better as it preserves the history better.

> 
> But the main problem was and still is, lack of time , so I and kwizart
> (writing off-list) haven't much time next days and he point to try again
> (the mass rebuild) no this weekend but next weekend, meantime
> ffmpeg-2.3.3 still on devel (I think) . 
> 
> This is an ancient system so it give much work do all mass rebuild, see
> if we can make a new builder happen.
> 
> Kwizart roll back to ffmpeg-2.3 , because though we haven't patches for
> vlc build against ffmpeg2-4 and lack of time of course . 

What was wrong with the vlc patch I linked to?

> 
> Please be patient ...
> 
Julian

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 01.10.2014 o 19:43, Ankur Sinha pisze:
> On Wed, 2014-10-01 at 19:23 +0200, Julian Sikorski wrote:
>> t is related. Try doing
>> # yum downgrade ffmpeg\*
> 
> I only have 2.3.3 here:
> 
> [asinha@localhost  99_Current_papers]$ rpm -qa \*ffmpeg\*
> ffmpeg-libs-2.3.3-3.fc21.x86_64
> gstreamer-ffmpeg-0.10.13-13.fc21.x86_64
> ffmpeg-2.3.3-3.fc21.x86_64
> 
> Should I still attempt the downgrade?
> 
Actually, despite what the changelog says, this release of mplayer still
requires ffmpeg-2.4.1.
Can you try these packages in the meantime?
http://lesloueizeh.com/belegdol/ffmpeg-rebuild/

Best regards,
Julian

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 01.10.2014 o 23:03, David Timms pisze:
> On 02/10/14 03:51, Julian Sikorski wrote:
> ...
>> Looks like we are almost there. The two remaining packages have not been
>> touched by upstream in ages and maybe we should reconsider whether it is
>> worth carrying them.
> 
> Which packages are remaining please ?
> 
dvbcut and kmediafactory.

J

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qua, 2014-10-01 at 18:10 -0500, Michael Cronenworth wrote: 
> On 10/01/2014 12:43 PM, Ankur Sinha wrote:
> > Should I still attempt the downgrade?
> 
> No. You need to downgrade mplayer.
> 
> mplayer was built against ffmpeg 2.4, but you do not have ffmpeg 2.4 
> installed.

yes , 
The packages k3b-extras-freeworld , xine-lib , mplayer (jobs 21300,
21301 and 21302) have to be build again, because, at the time, builder
repos still had ffmepg 2.4 , we can check it on logs :  

http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_free/21300-mplayer-1.1-28.20140919svn.fc21/x86_64/root.log


but we roll back to ffmpeg 2.3, so I will bump a version and *rebuild*
it again , this time only with ffmpeg-2.3 in builder repos. 


-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qua, 2014-10-01 at 19:38 +0200, Julian Sikorski wrote: 
> W dniu 25.09.2014 o 20:51, Sérgio Basto pisze:
> > 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/017393.html
> >>>
> >>> 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 , and it is more easier , clean etc , if just
> > after this (update ffmpeg to 2.4) . ...
> > 
> > 
> > Thanks, 
> > 
> If we ever decide to upgrade f20 (which I don't think we will given the
> current fiasco), please do not overwrite the f20 spec with f21 one. I
> suggest comparing the two and upgrading in parallel, something like git
> cherry-pick.

Hi , Julian , that is the point, this is cvs , we don't have "upgrading
in parallel", I try rolling devel to branches and yes "overwrite the f20
spec" and what is in f20 spec is discard. Is the only rule of
organization that we have . 

But the main problem was and still is, lack of time , so I and kwizart
(writing off-list) haven't much time next days and he point to try again
(the mass rebuild) no this weekend but next weekend, meantime
ffmpeg-2.3.3 still on devel (I think) . 

This is an ancient system so it give much work do all mass rebuild, see
if we can make a new builder happen.

Kwizart roll back to ffmpeg-2.3 , because though we haven't patches for
vlc build against ffmpeg2-4 and lack of time of course . 

Please be patient ...

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Rahul Sundaram]

Hi

On Wed, Oct 1, 2014 at 7:10 PM, Michael Cronenworth wrote:

>
> mplayer was built against ffmpeg 2.4, but you do not have ffmpeg 2.4
> installed.
>

Well, ffmpeg 2.4 is not available in the repository yet for some reason

Rahul

Re: ffmpeg-2.4 released

[Michael Cronenworth]

On 10/01/2014 12:43 PM, Ankur Sinha wrote:

Should I still attempt the downgrade?


No. You need to downgrade mplayer.

mplayer was built against ffmpeg 2.4, but you do not have ffmpeg 2.4 installed.

Re: ffmpeg-2.4 released

[David Timms]

On 02/10/14 03:51, Julian Sikorski wrote:
...
> Looks like we are almost there. The two remaining packages have not been
> touched by upstream in ages and maybe we should reconsider whether it is
> worth carrying them.

Which packages are remaining please ?

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 21.09.2014 o 19:11, Julian Sikorski pisze:
> W dniu 21.09.2014 o 19:03, Julian Sikorski pisze:
>> 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?
>>
>> Best regards,
>> Julian
>>
> Please excuse my replying to myself. Some of the work seems already done:
> - alsa-plugins: looking at arch seems to indicate this can be fixed by
> updating to 1.0.28
> - vlc:
> https://projects.archlinux.org/svntogit/packages.git/tree/trunk/vlc-2.1.5-ffmpeg-2.4.patch?h=packages/vlc
> 
> Best regards,
> Julian
> 
May I ask what are we waiting for with rawhide? I have done a local
rebuilt, found fixes for 2 out of 4 failing packages and rebuilt ffmpeg.
This is how we have always done it in the past and it has always worked.
Looking at the buildsys.rpmfusion.org, Nicolas has attempted to rebuild
the dependencies, and some have failed:
- vlc needs the patch I linked to
- ffmpegthumbs needs vlc to be built first
- mlt needs vlc to be built first
- xbmc was already taken care of
- audacious-plugins-freeworld and acoustid-fingerprinter seem to be a
buildsys issue

Looks like we are almost there. The two remaining packages have not been
touched by upstream in ages and maybe we should reconsider whether it is
worth carrying them.

Best regards,
Julian

Re: ffmpeg-2.4 released

[Ankur Sinha]

On Wed, 2014-10-01 at 19:23 +0200, Julian Sikorski wrote:
> t is related. Try doing
> # yum downgrade ffmpeg\*

I only have 2.3.3 here:

[asinha@localhost  99_Current_papers]$ rpm -qa \*ffmpeg\*
ffmpeg-libs-2.3.3-3.fc21.x86_64
gstreamer-ffmpeg-0.10.13-13.fc21.x86_64
ffmpeg-2.3.3-3.fc21.x86_64

Should I still attempt the downgrade?
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 25.09.2014 o 20:51, Sérgio Basto pisze:
> 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/017393.html
>>>
>>> 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 , and it is more easier , clean etc , if just
> after this (update ffmpeg to 2.4) . ...
> 
> 
> Thanks, 
> 
If we ever decide to upgrade f20 (which I don't think we will given the
current fiasco), please do not overwrite the f20 spec with f21 one. I
suggest comparing the two and upgrading in parallel, something like git
cherry-pick.

Julian

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 01.10.2014 o 16:38, Ankur Sinha pisze:
> On Fri, 2014-09-26 at 14:29 +0200, Xavier Bachelot wrote:
>> mplayer
> 
> I'm still seeing this on my F21 up to date system:
> 
> Error: nothing provides libavutil.so.54()(64bit) needed by
> mplayer-1.1-28.20140919svn.fc21.x86_64. nothing provides
> libavutil.so.54()(64bit) needed by
> mplayer-1.1-28.20140919svn.fc21.x86_64
> 
> 
> Is this related to the rebuild, or is it another issue?
> 
It is related. Try doing
# yum downgrade ffmpeg\*

Best regards,
Julian

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qua, 2014-10-01 at 15:38 +0100, Ankur Sinha wrote: 
> On Fri, 2014-09-26 at 14:29 +0200, Xavier Bachelot wrote:
> > mplayer
> 
> I'm still seeing this on my F21 up to date system:
> 
> Error: nothing provides libavutil.so.54()(64bit) needed by
> mplayer-1.1-28.20140919svn.fc21.x86_64. nothing provides
> libavutil.so.54()(64bit) needed by
> mplayer-1.1-28.20140919svn.fc21.x86_64
> 
> 
> Is this related to the rebuild, or is it another issue?

I'm very busy right now , ffmpeg 2.4 postpone 2 weeks  I' ll try see
what I cant do in the evening 

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Ankur Sinha]

On Fri, 2014-09-26 at 14:29 +0200, Xavier Bachelot wrote:
> mplayer

I'm still seeing this on my F21 up to date system:

Error: nothing provides libavutil.so.54()(64bit) needed by
mplayer-1.1-28.20140919svn.fc21.x86_64. nothing provides
libavutil.so.54()(64bit) needed by
mplayer-1.1-28.20140919svn.fc21.x86_64


Is this related to the rebuild, or is it another issue?
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part

Re: ffmpeg-2.4 released

[Michael Cronenworth]

On 09/26/2014 07:29 AM, Xavier Bachelot wrote:

Ssome packages were published already :
ffmpeg
mplayer
xine-lib

Additionnaly, k3b-extras-freeworld was built earlier today but is not
pushed yet.

I'm not sure what remains to be rebuilt against ffmpeg 2.4, but at least
mplayer, xine-lib and k3b-extras-freeworld can be removed from the list.


xbmc has been rebuilt. I saw Nicholas attempted one but it failed due to what 
looks like a builder error. A resubmit of the job was all that was required.

Re: ffmpeg-2.4 released

[Xavier Bachelot]

On 26/09/2014 14:15, Sérgio Basto wrote:
> On Qui, 2014-09-25 at 21:18 +0100, Sérgio Basto wrote:
>>> SO I NAK the ffmpeg update in F-20 because the way the update was
>> done
>>> in Rawhide.
>>> I don't want to hear about it. This is not acceptable not to have
>>> coordinated the update.
>>
>> Sorry I'm in work and can't focus, I already sent incomplete emails
>> etc,
>> but you NACK because ffmpeg 2.4 was submit in devel ? we can roll back
>> it , it easy to roll back it. 
>>
>> I understand, how things should roll out , first commit in devel , and
>> copy along branches and that is the way that should be done . So yes
>> it
>> was forbidden commit on devel for not roll out to branch , am I the
>> coordinator ? , we can fix it, is not a big deal. I will take care of
>> everything 
>> Thanks, 
>>
>> I have to go now ,
> 
> I'll try catch kwizart on irc this weekend to see what we can do, and
> also plan do the mass rebuild this weekend until then, I'm busy . 
> If I am the coordinator, please don't submit more builds with 
> +- rebuild (ffmpeg-2.4) and disable needsign repo , since nothing was
> yet publish, moreover is more difficult to me do the mass rebuild
> correctly because I have to track down which packages already sent it to
> rebuild. 
>

Ssome packages were published already :
ffmpeg
mplayer
xine-lib

Additionnaly, k3b-extras-freeworld was built earlier today but is not
pushed yet.

I'm not sure what remains to be rebuilt against ffmpeg 2.4, but at least
mplayer, xine-lib and k3b-extras-freeworld can be removed from the list.

Regards,
Xavier

Re: ffmpeg-2.4 released

[Sérgio Basto]

Hi!, 

On Sex, 2014-09-26 at 07:24 +0200, Julian Sikorski wrote:
> 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.

yes , as we have cvs, to avoid confusions etc, we like first copy devel
to branch and after update devel, so devel keeps all story ... 

> I don't think it makes sense to roll back now, let's just rebuild the
> dependencies to minimise breakage time.

yes , I mean virtually roll back last commit and copy that to branch
F20 . 

Until packages are signed and publish , no breakage happens , if you
disable repo needsign. 

> I think I should apply for the ffmpeg deps commit access moving
> forward,
> so that there are more people who can do the rebuild.

sorry don't understand what you mean here , but no worries we do the
best we can . 

Meanwhile I'm very busy today, at least. 

Best regards, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qui, 2014-09-25 at 21:18 +0100, Sérgio Basto wrote:
> > SO I NAK the ffmpeg update in F-20 because the way the update was
> done
> > in Rawhide.
> > I don't want to hear about it. This is not acceptable not to have
> > coordinated the update.
> 
> Sorry I'm in work and can't focus, I already sent incomplete emails
> etc,
> but you NACK because ffmpeg 2.4 was submit in devel ? we can roll back
> it , it easy to roll back it. 
> 
> I understand, how things should roll out , first commit in devel , and
> copy along branches and that is the way that should be done . So yes
> it
> was forbidden commit on devel for not roll out to branch , am I the
> coordinator ? , we can fix it, is not a big deal. I will take care of
> everything 
> Thanks, 
> 
> I have to go now ,

I'll try catch kwizart on irc this weekend to see what we can do, and
also plan do the mass rebuild this weekend until then, I'm busy . 
If I am the coordinator, please don't submit more builds with 
+- rebuild (ffmpeg-2.4) and disable needsign repo , since nothing was
yet publish, moreover is more difficult to me do the mass rebuild
correctly because I have to track down which packages already sent it to
rebuild. 

Thanks
> 
> > PERIOD.

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 25.09.2014 o 20:56, Sérgio Basto pisze:
> 
> 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/017393.html
>>>
>>> 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

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qui, 2014-09-25 at 21:04 +0200, Nicolas Chauvet wrote: 
> 2014-09-25 20:44 GMT+02:00 Sérgio Basto :
> On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote:
> > 2014-09-25 19:27 GMT+02:00 Julian Sikorski
> :
> > 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.
> >
> >
> >
> > Can we care about rebuilding all dependencies at the same
> time ?
> >
> 
> yes of course , I will take care ,
> 
> but may I build all for new ffmpeg /x624 for F20 ? 
> 
> 
> 
> SO I NAK the ffmpeg update in F-20 because the way the update was done
> in Rawhide.
> I don't want to hear about it. This is not acceptable not to have
> coordinated the update.

Sorry I'm in work and can't focus, I already sent incomplete emails etc,
but you NACK because ffmpeg 2.4 was submit in devel ? we can roll back
it , it easy to roll back it. 

I understand, how things should roll out , first commit in devel , and
copy along branches and that is the way that should be done . So yes it
was forbidden commit on devel for not roll out to branch , am I the
coordinator ? , we can fix it, is not a big deal. I will take care of
everything 
Thanks, 

I have to go now ,

Best regards, 


> PERIOD.
> 
> 
> 
> -- 
> -
> 
> 
> Nicolas (kwizart)
> 

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Nicolas Chauvet]

2014-09-25 20:44 GMT+02:00 Sérgio Basto :

> On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote:
> > 2014-09-25 19:27 GMT+02:00 Julian Sikorski :
> > 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.
> >
> >
> >
> > Can we care about rebuilding all dependencies at the same time ?
> >
> yes of course , I will take care ,
>
> but may I build all for new ffmpeg /x624 for F20 ?
>
>
> SO I NAK the ffmpeg update in F-20 because the way the update was done in
Rawhide.
I don't want to hear about it. This is not acceptable not to have
coordinated the update.
PERIOD.


-- 
-

Nicolas (kwizart)

Re: ffmpeg-2.4 released

[Sérgio Basto]

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/017393.html
> > 
> > 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, 

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Sérgio Basto]

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/017393.html
> > 
> > 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 , and it is more easier , clean etc , if just
after this (update ffmpeg to 2.4) . ...


Thanks, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Qui, 2014-09-25 at 20:33 +0200, Nicolas Chauvet wrote: 
> 2014-09-25 19:27 GMT+02:00 Julian Sikorski :
> 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.
> 
> 
> 
> Can we care about rebuilding all dependencies at the same time ?
> 
yes of course , I will take care , 

but may I build all for new ffmpeg /x624 for F20 ?  

> I've no time to care...
> 
> 
> 
> Nicolas (kwizart)
> 
> 
> 
> 
> 
> 
> 
> 

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Nicolas Chauvet]

2014-09-25 19:27 GMT+02:00 Julian Sikorski :

> 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.
>

Can we care about rebuilding all dependencies at the same time ?
I've no time to care...

Nicolas (kwizart)

Re: ffmpeg-2.4 released

[Julian Sikorski]

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/017393.html
> 
> Kwizart , do you allow this exception ? 
> 
> 
> Thanks, 
> 
Just to be clear: I only pushed it to devel. F20 is still an open question.

Best regards,
Julian

Re: ffmpeg-2.4 released

[Sérgio Basto]

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/017393.html

Kwizart , do you allow this exception ? 


Thanks, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Ankur Sinha]

On Thu, 2014-09-25 at 10:06 +0200, Xavier Bachelot wrote:
> xine-lib passed a local rebuild and is now building in plague.

Hi,

I get this at the moment:

Error: package mpd-1:0.18.11-2.fc21.x86_64 requires
libavcodec.so.55()(64bit), but none of the providers can be installed.
package vlc-core-2.1.5-2.fc21.x86_64 requires libavcodec.so.55()(64bit),
but none of the providers can be installed. package
xbmc-13.2-1.fc21.x86_64 requires libavcodec.so.55()(64bit), but none of
the providers can be installed. package
mplayer-1.1-26.20140806svn.fc21.x86_64 requires mplayer-common =
1.1-26.20140806svn.fc21, but none of the providers can be installed


I'm assuming this will fix itself once the rebuild is over?
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG



signature.asc
Description: This is a digitally signed message part

Re: ffmpeg-2.4 released

[Xavier Bachelot]

On 25/09/2014 07:47, 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
> 
xine-lib passed a local rebuild and is now building in plague.

Regards,
Xavier

Re: ffmpeg-2.4 released

[Julian Sikorski]

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

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Seg, 2014-09-22 at 18:46 +0200, Julian Sikorski wrote:
> The upstream-tracker.org website reveals that no symbols were removed
> between ffmpeg-2.1 and ffmpeg-2.3. Conversely, ffmpeg-2.4 has 20
> symbols
> removed vs 2.3.3.
> Finally, the reason I was suggesting moving away from ffmpeg-2.1 is
> due
> to the top of the "Old releases" page [3]:
> These releases are not actively maintained and thus we discourage
> their use.

OK , thanks, so we put on table update F20 with ffmpeg-2.3.3 (version
which is in rpmfusion-devel).  
I can made a list of the packages, with ffmpeg / x264 dependencies, that
should stay on update-testing for more time than usual. 

Kwizart ? 

Best regards, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 22.09.2014 o 16:57, Sérgio Basto pisze:
> On Seg, 2014-09-22 at 06:50 +0200, Julian Sikorski wrote: 
>> W dniu 22.09.2014 o 05:35, Ralf Corsepius pisze:
>>> On 09/21/2014 11:20 PM, Sérgio Basto wrote:
 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 ?
>>>
>>> No. If I understand correctly, this is an API/ABI incompatible upgrade
>>> and not an ordinary update. This means, unless there are very good
>>> reasons (e.g. security critical bug fixes), which make such upgrades
>>> inevitably necessary, such upgrades are harmful and should not happen.
>>> Keep in mind, people might build other packages based on your packages,
>>> which might break because of your upgrade.
>>>
 I'd like put it at
 least on update-testing.
>>> Sorry, but this can't work.
>>>
>>> Ralf
>>>
>> I tend to agree with Ralf here. Having said that, I believe we should do
>> something about F-20. It is currently tracking ffmpeg-2.1 branch, which
>> seems to be unmaintained [1]. Looking at the API changes [2], updating
>> to 2.2/2.3 should be relatively painless.
> 
> Hi, as you may know, I have some difficulties in deal with foreigner
> language (English). IIUC , upgrade to ffmpeg-2.3 in F-20 , also have
> API/ABI incompatible.
> Of course I'm not saying put ffmpeg-2.4 in F-20 without testing ,  2.3
> is tested on F-21 Alpha , I have 2 machines and one vm , and don't found
> any bug . 
> For me is fine put ffmpeg-2.3 / x264-0.142 in F-20 updates-testing , but
> as Ralf point out, we are breaking some rules . 
> 
> 
>> Best regards,
>> Julian
>>
>> [1] http://ffmpeg.org/olddownload.html
>> [2] http://upstream-tracker.org/versions/ffmpeg.html
> 
Hello,

my apologies, I should have expressed myself more clearly. The reason I
was suggesting 2.3 as an alternative to 2.4 is that it is less
disruptive. Please have a look at the soname versions below:

- ffmpeg-2.1:
libavutil  52. 48.101
libavcodec 55. 39.101
libavformat55. 19.104
libavdevice55.  5.100
libavfilter 3. 90.100
libavresample   1.  1.  0
libswscale  2.  5.101
libswresample   0. 17.104
libpostproc52.  3.100

- ffmpeg-2.3:
libavutil  52. 92.100
libavcodec 55. 69.100
libavformat55. 48.100
libavdevice55. 13.102
libavfilter 4. 11.100
libavresample   1.  3.  0
libswscale  2.  6.100
libswresample   0. 19.100
libpostproc52.  3.100

As you can see, the major versions are all the same for everything
except libavfilter. In contrast, ffmpeg-2.4 has the following:

libavutil  54.  7.100
libavcodec 56.  1.100
libavformat56.  4.101
libavdevice56.  0.100
libavfilter 5.  1.100
libavresample   2.  1.  0
libswscale  3.  0.100
libswresample   1.  1.100
libpostproc53.  0.100

Every single library got a soname bump.
The upstream-tracker.org website reveals that no symbols were removed
between ffmpeg-2.1 and ffmpeg-2.3. Conversely, ffmpeg-2.4 has 20 symbols
removed vs 2.3.3.
Finally, the reason I was suggesting moving away from ffmpeg-2.1 is due
to the top of the "Old releases" page [3]:
These releases are not actively maintained and thus we discourage their use.

Best regards,
Julian

[1] http://ffmpeg.org/olddownload.html

Re: ffmpeg-2.4 released

[Sérgio Basto]

On Seg, 2014-09-22 at 06:50 +0200, Julian Sikorski wrote: 
> W dniu 22.09.2014 o 05:35, Ralf Corsepius pisze:
> > On 09/21/2014 11:20 PM, Sérgio Basto wrote:
> >> 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 ?
> > 
> > No. If I understand correctly, this is an API/ABI incompatible upgrade
> > and not an ordinary update. This means, unless there are very good
> > reasons (e.g. security critical bug fixes), which make such upgrades
> > inevitably necessary, such upgrades are harmful and should not happen.
> > Keep in mind, people might build other packages based on your packages,
> > which might break because of your upgrade.
> > 
> >> I'd like put it at
> >> least on update-testing.
> > Sorry, but this can't work.
> > 
> > Ralf
> > 
> I tend to agree with Ralf here. Having said that, I believe we should do
> something about F-20. It is currently tracking ffmpeg-2.1 branch, which
> seems to be unmaintained [1]. Looking at the API changes [2], updating
> to 2.2/2.3 should be relatively painless.

Hi, as you may know, I have some difficulties in deal with foreigner
language (English). IIUC , upgrade to ffmpeg-2.3 in F-20 , also have
API/ABI incompatible.
Of course I'm not saying put ffmpeg-2.4 in F-20 without testing ,  2.3
is tested on F-21 Alpha , I have 2 machines and one vm , and don't found
any bug . 
For me is fine put ffmpeg-2.3 / x264-0.142 in F-20 updates-testing , but
as Ralf point out, we are breaking some rules . 


> Best regards,
> Julian
> 
> [1] http://ffmpeg.org/olddownload.html
> [2] http://upstream-tracker.org/versions/ffmpeg.html

-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 22.09.2014 o 05:35, Ralf Corsepius pisze:
> On 09/21/2014 11:20 PM, Sérgio Basto wrote:
>> 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 ?
> 
> No. If I understand correctly, this is an API/ABI incompatible upgrade
> and not an ordinary update. This means, unless there are very good
> reasons (e.g. security critical bug fixes), which make such upgrades
> inevitably necessary, such upgrades are harmful and should not happen.
> Keep in mind, people might build other packages based on your packages,
> which might break because of your upgrade.
> 
>> I'd like put it at
>> least on update-testing.
> Sorry, but this can't work.
> 
> Ralf
> 
I tend to agree with Ralf here. Having said that, I believe we should do
something about F-20. It is currently tracking ffmpeg-2.1 branch, which
seems to be unmaintained [1]. Looking at the API changes [2], updating
to 2.2/2.3 should be relatively painless.

Best regards,
Julian

[1] http://ffmpeg.org/olddownload.html
[2] http://upstream-tracker.org/versions/ffmpeg.html

Re: ffmpeg-2.4 released

[Ralf Corsepius]

On 09/21/2014 11:20 PM, Sérgio Basto wrote:

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 ?


No. If I understand correctly, this is an API/ABI incompatible upgrade 
and not an ordinary update. This means, unless there are very good 
reasons (e.g. security critical bug fixes), which make such upgrades 
inevitably necessary, such upgrades are harmful and should not happen.
Keep in mind, people might build other packages based on your packages, 
which might break because of your upgrade.



I'd like put it at
least on update-testing.

Sorry, but this can't work.

Ralf

Re: ffmpeg-2.4 released

[Sérgio Basto]

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, 
-- 
Sérgio M. B.

Re: ffmpeg-2.4 released

[Julian Sikorski]

W dniu 21.09.2014 o 19:03, Julian Sikorski pisze:
> 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?
> 
> Best regards,
> Julian
> 
Please excuse my replying to myself. Some of the work seems already done:
- alsa-plugins: looking at arch seems to indicate this can be fixed by
updating to 1.0.28
- vlc:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/vlc-2.1.5-ffmpeg-2.4.patch?h=packages/vlc

Best regards,
Julian