[Pkg-chromium-maint] Bug#580947: chromium-browser from experimental has included h.264 by default?

Andres Mejia mcitadel at gmail.com
Wed May 12 08:18:56 UTC 2010

On Wed, May 12, 2010 at 2:31 AM, Giuseppe Iuculano <giuseppe at iuculano.it> wrote:
> Il 12/05/2010 06:38, Reinhard Tartler ha scritto:
>> TBH, I'm very skeptical. While I'm not sure why google has decided to
>> choose astrange's branch/fork, I fear that there have been too many
>> changes to the external public API that this is not going to work out.
>> I'm basing this opinion on the Giuseppe's observation that Chromium does
>> not even compile against ffmpeg 0.5 (debian' system) ffmpeg.
>> It would be of course interesting to see how this works out with ffmpeg
>> 0.6 (currently in NEW), but for totally unrelated reasons to this one, I
>> fear it won't be processes as well, just like mplayer.
> I already tried to compile against the ffmpeg in NEW, and it compiles
> fine (and works fine). For this reason, waiting the new version in NEW,
> the ugly hack for the current version in unstable was a tentative to
> obtain a working chromium for users with and without debian-multimedia
> repository in sources.list.
>> For this reason, I think that chromium
>> upstream is providing excellent security support for its copy of ffmpeg!
> I full agree, I contacted the chromium security team some time ago
> asking an help to triage all security vulnerabilities in our sec
> tracker. I was impressed by their responsiveness and helpfulness.
> Cheers,
> Giuseppe.

Just so you know,  ffmpeg-0.6 which sits in NEW is meant for
experimental. Furthermore, there's currently no plans to move it into
unstable until after the release of Squeeze.

Here's a preliminary patch that allows chromium-browser to build with
system ffmpeg-0.5.1. This is a hard hack to drop back to functions
that were not deprecated until 0.6. Also, this patch shouldn't be
submitted upstream as is. It patches the packaging done in the bzr

Aside from allowing it to build with system ffmpeg 0.5.1, the
packaging is updated to make use of the shlib files for the ffmpeg
libs, to acquire proper entries for the Depends field.

I'm writing this email through gmail with the newly built
chromium-browser, although I'm still getting the 'Aw Snap' message
trying to view HTML5 content. I was getting that message with the
current chromium in experimental as well. I guess this patch is a
start to figuring out that issue at least : /

Andres Mejia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ffmpeg-0.5.1.patch
Type: text/x-patch
Size: 9586 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20100512/6f905403/attachment-0001.bin>

More information about the Pkg-chromium-maint mailing list