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.
