Hi! Even if gst-plugins-libav is compatible with ffmpeg-2.2 and newer, upstream is testing it with ffmpeg-2.8 branch and, then, maybe it would be interesting to start to work on trying to get it stabilized if possible :) What is needed for that? Is there any tracker bug we need to take care? Should I try to rebuild the reverse deps to ensure they are still ok with that ffmpeg version? Thanks for the info
it's always safer to run a tinderbox, but the 2.6.x -> 2.8.y upgrade should be smooth; otherwise, I was thinking about stabilising 2.8.2 but I added it only a few days ago (even if it is only a bugfix release from the 2.8 branch)
2.8.2 would be nice for sure :) I was doing a rebuilding of reverse deps but I have hit the unrelated bug 566328 and then I am unable to rebuild some of them because of that problem. Well, maybe we could ping Toralf if a tinderbox run over stable is needed for this :/
would 2.8.3 be a proper candidate for stabilization then? ;)
go for 2.8.4, its just bugfixes anyway will someone run a tinderbox or can we just cc arches ?
Not in my case (well, I need to be able to use my laptop a bit this days :(, maybe toralf could be CCed here :/)
@Toralf: would you be able to run a stable tinderbox with ffmpeg 2.8.4 stable, in addition ?
(In reply to Alexis Ballier from comment #6) > @Toralf: would you be able to run a stable tinderbox with ffmpeg 2.8.4 > stable, in addition ? ofc. Any other package which should be keyworded at that image too ? To avoid waiting time (there're 18,000 packages), are there any packages which should be tested first / before all others ?
(In reply to Toralf Förster from comment #7) > (In reply to Alexis Ballier from comment #6) > > @Toralf: would you be able to run a stable tinderbox with ffmpeg 2.8.4 > > stable, in addition ? > > ofc. thanks! > Any other package which should be keyworded at that image too ? Apart from those needed by ffmpeg itself (if any), none: the point is also to catch those that just need to be stabilized. > To avoid waiting time (there're 18,000 packages), are there any packages > which should be tested first / before all others ? complete list should be the union of these two lists, and testing only the latest stable (and enabling relevant flags if any, but that tends to be quite messy for some packages): https://qa-reports.gentoo.org/output/genrdeps/rindex/virtual/ffmpeg https://qa-reports.gentoo.org/output/genrdeps/rindex/media-video/ffmpeg
FWIW media-libs/x265would need to be stabilized too : The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by media-video/vlc-2.2.1-r1::gentoo[x265] # required by media-libs/phonon-vlc-0.7.2::gentoo # required by media-libs/phonon-4.7.2::gentoo[vlc] # required by kde-base/kdelibs-4.14.8::gentoo # required by kde-base/khelpcenter-4.14.3::gentoo =media-libs/x265-1.8-r3 ~amd64
@toralf: how did the run go ? I haven't noticed any bug related to this, is it all ok ? (see also bug #571868)
(In reply to Alexis Ballier from comment #10) I got no issues here related to ffmpeg and friends a t 3 different stable chroot images (disclaimer: for the tested USE flag combinations)
According to https://bugs.gentoo.org/show_bug.cgi?id=571868 2.8.5 should be stabilized at least.
Action is being taken at bug 571868 finally *** This bug has been marked as a duplicate of bug 571868 ***
