Advisory: -------------------------------------------------- This updates provides ffmpeg version 2.0.3, which fixes several bugs which were corrected upstream. References: http://git.videolan.org/?p=ffmpeg.git;a=log;h=n2.0.3 http://ffmpeg.org/olddownload.html -------------------------------------------------- Updated packages in {core,tainted}/updates_testing: -------------------------------------------------- ffmpeg-2.0.3-1.mga4 libavcodec55-2.0.3-1.mga4 libpostproc52-2.0.3-1.mga4 libavformat55-2.0.3-1.mga4 libavutil52-2.0.3-1.mga4 libswscaler2-2.0.3-1.mga4 libavfilter3-2.0.3-1.mga4 libswresample0-2.0.3-1.mga4 libffmpeg-devel-2.0.3-1.mga4 libffmpeg-static-devel-2.0.3-1.mga4 from ffmpeg-2.0.3-1.mga4.src.rpm Reproducible: Steps to Reproduce:
Version: Cauldron => 4
Basic testing procedure at https://bugs.mageia.org/show_bug.cgi?id=8065#c6 Don't forget to test packages from both core and tainted. Replace lib with lib64 for 64 bits systems.
CC: (none) => stormi
Whiteboard: (none) => has_procedure
There is a problem here with one of the included packages. That package is: libavcodec55 It appears that it is not, or a version(s) of it, in both the core and tainted repos. As a result of that apps like Openshot cannot deal with some/many codecs. I'll be putting time into this defining what and where this is in the next day(s). I was successfull to load M4 64-bit on my laptop a few weeks ago now this error appears. It works in M3 just fine.
CC: (none) => wilcal.int
This libavcodec55 issue may only occur in the x86-64 version.
Nope, it's there: http://mageia.c3sl.ufpr.br/distrib/4/x86_64/media/tainted/updates_testing/lib64avcodec55-2.0.3-1.mga4.tainted.x86_64.rpm
Did this just get put in today?
(In reply to William Kenney from comment #5) > Did this just get put in today? Of course not, all packages are built and uploaded together.
Gimme till the meeting tomorrow, 13 Feb. More testing here.
This is what I believe is happening here. Yes both the core and tainted versions of libavformat55 are in the M4 repos. If you MCC -> Software Management -> Install & Remove Software -> libavformat55 If you are using M4 i586 then you are presented with the tainted version of libavformat55. Installing that then Openshot is capable of exporting an Mpeg4 video, and many others. If you are using M4 x86_64 then you are presented with the core version of libavformat55. Installing that then Openshot is incapable of exporting an Mpeg4 video, and many others. So what I did to confirm this was to remove the core version of libavformat55 from the M4 x86_64 test install and using ftp downloaded from the M4 repo the tainted version of libavformat55 from the updates_testing repo. Installing that and now Openshot is capable of exporting Mpeg4 videos and many others.
You should be installing lib64avformat55 not libavformat55, shouldn't you? (to packagers, please try to list 64 bit name of libs too, with (64) in the name or any other way)
(In reply to Samuel VERSCHELDE from comment #9) > You should be installing lib64avformat55 not libavformat55, shouldn't you? > (to packagers, please try to list 64 bit name of libs too, with (64) in the > name or any other way) Somewhere along the line here that did get installed. Now that I've got this working I'll probably go back and do a complete install of M4 from ground up and note what's in and what's not. Do note that there was no problem at all with M4 i586. So this is only an x86_64 issue. I think this is a listing issue and not a problem with the package itself.
IMO, this lib(64)avformat/codec55 issue probably effects many other apps other then just Openshot.
(In reply to Samuel VERSCHELDE from comment #9) > (to packagers, please try to list 64 bit name of libs too, with (64) in the > name or any other way) That's not how we do things. We assume it's known that lib64 is the lib names on x86_64.
(In reply to William Kenney from comment #11) > IMO, this lib(64)avformat/codec55 issue probably effects > many other apps other then just Openshot. Unless there's a bug in MageiaUpdate, this shouldn't be an issue for users installing the final pushed update if they have the tainted repo enabled.
I'm comfortable now with where I'm at. I'll keep poke'n at this thing.
(In reply to David Walser from comment #12) > (In reply to Samuel VERSCHELDE from comment #9) > > (to packagers, please try to list 64 bit name of libs too, with (64) in the > > name or any other way) > > That's not how we do things. We assume it's known that lib64 is the lib > names on x86_64. And regularly we need to explain it to QA testers who don't find their libs or try to pick them from 32 bits media. Also, your "we" is not always true from what I know. A lot of packagers add that 64 part, or even better list both i586 and x86_64 packages. The updates policy says list ALL packages (with capital letters). Also, the example advisory shows that lib(64) thingy. Your advisories are great, I'm not denying it, but on this specific point marking the difference between 32 and 64 bits libs would be a plus.
I could stop listing them in the bugs and just refer people to madb if you'd prefer that.
We could stop testing them altogether if you prefer that. Making this kind of threat helps nobody, please rememeber we are all volunteers here.
As am I. What he's asking of me would be a lot more work and I do not agree that it would be better. The way I list them has been working fine for two years now. I'm not going to expend a lot more effort in the task of listing packages, which is already possibly the most annoying part of the process, for no obvious tangible gain.
Thanks for clarifying your position. This is much more productive. It's never been a big issue mainly as we've not had many new people. It is an occasional issue though so perhaps something we can improve in documentation. Either way, ffmpeg update is not the place for this discussion :)
Thanks Claire. I think documentation is the answer here, if one of our wiki pages doesn't already explain this, we can address it there. I do wonder what was up with MageiaUpdate though. It's enough of a pain having to cherry-pick all of the correct packages when QA testing, even more so when MageiaUpdate prevents you from doing so correctly. It'd be nice if we had a tool to make this easier.
In VirtualBox, M4, KDE, 32-bit Package(s) under test: ffmpeg, libavformat55 default install of ffmpeg, libavformat55 [root@localhost wilcal]# urpmi ffmpeg Package ffmpeg-2.0.2-2.mga4.tainted.i586 is already installed [root@localhost wilcal]# urpmi libavformat55 Package libavformat55-2.0.2-2.mga4.tainted.i586 is already installed OpenShot operates correctly. ffmpeg conversions operate correctly. install ffmpeg, libavformat55 from updates_testing [root@localhost wilcal]# urpmi ffmpeg Package ffmpeg-2.0.3-1.mga4.tainted.i586 is already installed [root@localhost wilcal]# urpmi libavformat55 Package libavformat55-2.0.3-1.mga4.tainted.i586 is already installed OpenShot operates correctly. ffmpeg conversions operate correctly. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
Whiteboard: has_procedure => has_procedure MGA4-32-OK
In VirtualBox, M4, KDE, 64-bit Package(s) under test: ffmpeg, lib64avformat55 default install of ffmpeg, lib64avformat55 [root@localhost wilcal]# urpmi ffmpeg Package ffmpeg-2.0.2-2.mga4.tainted.x86_64 is already installed [root@localhost wilcal]# urpmi lib64avformat55 Package lib64avformat55-2.0.2-2.mga4.tainted.x86_64 is already installed OpenShot operates correctly. ffmpeg conversions operate correctly. install ffmpeg, libavformat55 from updates_testing [root@localhost wilcal]# urpmi ffmpeg Package ffmpeg-2.0.3-1.mga4.tainted.x86_64 is already installed [root@localhost wilcal]# urpmi lib64avformat55 Package lib64avformat55-2.0.3-1.mga4.tainted.x86_64 is already installed OpenShot operates correctly. ffmpeg conversions operate correctly. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
I'm happy with this update. It took awhile for me to figure out how the codes work in M4 but for now, if everyone is comfortable with this, lets push this update.
Whiteboard: has_procedure MGA4-32-OK => has_procedure MGA4-32-OK MGA4-64-OK
Keywords: (none) => validated_updateWhiteboard: has_procedure MGA4-32-OK MGA4-64-OK => has_procedure MGA4-32-OK MGA4-64-OK advisoryCC: (none) => remi, sysadmin-bugs
Validated, advisory has been uploaded. Please push to 4 {core,tainted}/updates.
Update pushed: http://advisories.mageia.org/MGAA-2014-0048.html
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED