Oh sorry, you understood (and I too). So, let's redo the story. (= This is a little strange. Recently, you changed the package to add protobuf dependency. This is a major change, isn't it? In the last year, you moved Chromium to Packman because of FFMpeg. At that time, Chromium was shipped without FFMpeg. Some days after doing this, you moved these packages back to openSUSE after discovering a method to compile Chromium's FFMpeg only with free codecs support. Then was born the chromium-ffmpegsumo package. Support to the the proprietary codecs weren't in openSUSE's package beacause as we know, these formats has issues with patents in some countries. Right? People, now this isn't working properly, because chromium-ffmpegsumo is reproducing MP3/MP4. The chromium.spec has these two lines: -Dproprietary_codecs=1 -Dffmpeg_branding=Chrome According to the Chromium's wiki ( www.chromium.org/audio-video ) the use of these 2 build flags activates the support for the proprietary formats. I think the way to fix this is changing these values to 0 and Chromium, respectively. Any other idea? Regards, Ignacio PS: Raymond, I forgot to subscribing to the list, so I can't reply your email directly. PS2: sorry for the 6th paragraph in the comment 1 of the bug. I used the wrong words.
Thanks for making me look stupid and that I do not understand the issue. The reason why I asked you to write to this mailinglist was your statement that Chromium should be build without the proprietary-codec and branding=chrome options. This would mean that Chromium no longer would support H.264, MP4, etc codecs that normally are supported by Chrome. As that this is a major change, I asked you to validate this on this mailinglist. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org