http://bugzilla.suse.com/show_bug.cgi?id=939530 http://bugzilla.suse.com/show_bug.cgi?id=939530#c1 --- Comment #1 from Raymond Wooninck --- Well, we have the chicken and the egg story here. With Chromium v44, Google decided to change the way that they are building the ffmpeg libraries and it got renamed from libffmpegsumo.so to lib/libffmpeg.so. Chromium itself has a dependency on any package that provides ffmpegsumo (as a provides). In principle these are two packages. The first one is chromium-ffmpegsumo, which is build on openSUSE OBS and contains a limited ffmpeg. Limited in the sense that only opensource codecs are support. The full ffmpeg package for chromium is build on Packman and is called chromium-ffmpeg. This package is linked to the chromium sources on Factory. Unfortunately the Chromium package has not been accepted yet into Factory itself and therefore Packman still has the older version (v43). Due to change, it was inevitable to happen and could have not been avoided. Upgrading first Packman, would have caused the same thing to happen, that chromium would not have been able to find libffmpegsumo.so. Hopefully this would be resolved soon once Chromium v44 gets accepted into Factory. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=939530 http://bugzilla.suse.com/show_bug.cgi?id=939530#c3 --- Comment #3 from Raymond Wooninck --- And what would you wanted me to put in the changelog ?? Looking from a pure openSUSE perspective, then we have a single chromium source package that delivers a chromium and chromium-ffmpegsumo rpm package. Those two together will always deliver a working Chromium web browser, however with a limited ffmpeg functionality as that openSUSE does not have all build requirements for this and also from a legal perspective it wouldn't be allowed. That is why packman is building this separated ffmpeg package (called chromium-ffmpeg) which would deliver a libffmpeg that fully supports all codecs. As far as I know openSUSE can not be associated with packman (nor provide links, etc), so for openSUSE the chromium-ffmpeg package does not exist. People who just used the openSUSE delivered packages, do not have any problems as that the chromium-ffmpegsumo package delivers the correct libffmpeg.so Packman is building based on the source in openSUSE:Factory and this time (this single time) Factory was delayed with checkin of the chromium package due to all kind of reasons. This caused the situation that packman still had v43 and the update repo's got v44. I don't think that many people are reading the changelog and I am really wondering what idea that you have that the changelog can push people to do something ? And in this case do what ? Not to install the update ? Switch back to the ffmpegsumo package and then raise bugs that not all codecs are supported ?? In the meantime I have splitted the chromium package on packman in one version tracking openSUSE:Factory and another one that is tracking openSUSE:13.2:Update -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=939530 http://bugzilla.suse.com/show_bug.cgi?id=939530#c5 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |astieger@suse.com Resolution|--- |WORKSFORME --- Comment #5 from Andreas Stieger --- One time transition event I guess, no longer current on 48.0.2564.82, closing. -- You are receiving this mail because: You are on the CC list for the bug.