On 08/10/2010 09:25 PM, Adam D. Barratt wrote:
Chromium isn't meant to be released with Squeeze. We'll reevaluate for
Squeeze+1.
Is that still the case?
No, it isn't. Please see #581265 and in particular message #32, #37 and #44
Cheers,
Giuseppe.
signature.asc
Description: OpenPGP
On Tue, 2010-05-11 at 20:55 +0200, Moritz Muehlenhoff wrote:
On 2010-05-11, Reinhard Tartler siret...@debian.org wrote:
Surely not. Chromium ships a *private* copy of ffmpeg, more precisely, a
fork of ffmpeg called ffmpeg-mt. Debian does not include ffmpeg-mt
because of bug #575600 (tagged
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
On Wed, May 12, 2010 at 05:43:37AM +, Sune Vuorela wrote:
It is the 3rd copy of webkit code in the archive, again most likely
from a different branch point. (webkit source package building the gtk
frontend to webkit, qt4-x11 building qtwebkit and now chrome)
Right, but it's no more the
On Wed, May 12, 2010 at 2:31 AM, Giuseppe Iuculano giuse...@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
What I could imagine is to seperate out the ffmpeg module into a
seperate source package, and ship it in a 3rd party repository outside
of debian squeeze.
Wouldn't this be a perfect candidate for debimedia? And since it's the source
code only that we distribute with the package it shouldn't
On Thu, May 13, 2010 at 03:34:06 (CEST), Andreas Marschke wrote:
What I could imagine is to seperate out the ffmpeg module into a
seperate source package, and ship it in a 3rd party repository outside
of debian squeeze.
Wouldn't this be a perfect candidate for debimedia?
Probably yes.
severity 580947 serious
stop
On Tue, May 11, 2010 at 07:39:12 (CEST), Joey Hess wrote:
Reinhard Tartler wrote:
Surely not. Chromium ships a *private* copy of ffmpeg, more precisely, a
fork of ffmpeg called ffmpeg-mt. Debian does not include ffmpeg-mt
because of bug #575600 (tagged wontfix).
On 2010-05-11, Reinhard Tartler siret...@debian.org wrote:
[1] http://experimental.ftbfs.de/chromium-browser (unavailable at time
of writing)
experimental.ftbfs.de is down for good. I guess you meant [0] or similar.
Kind regards,
Philipp Kern
[0]
Hi,
On 11/05/10 10:13, Reinhard Tartler wrote:
[1] http://experimental.ftbfs.de/chromium-browser (unavailable at time
of writing)
Experimental is now on buildd.d.o, see
https://buildd.debian.org/status/package.php?p=chromium-browsersuite=experimental
Cheers,
Emilio
--
To UNSUBSCRIBE,
On Tue, May 11, 2010 at 10:22:02 (CEST), Philipp Kern wrote:
On 2010-05-11, Reinhard Tartler siret...@debian.org wrote:
[1] http://experimental.ftbfs.de/chromium-browser (unavailable at time
of writing)
experimental.ftbfs.de is down for good. I guess you meant [0] or similar.
Kind
severity 580947 important
thanks
Il 11/05/2010 10:44, Reinhard Tartler ha scritto:
checking [2], reveals that I'm partly wrong. There is an in-source copy
of ffmpeg, that there is an option 'use_system_ffmpeg=1' passed to the
buildscript. This indicates that I indeed missed that upstream now
On Tue, May 11, 2010 at 05:27:31PM +0200, Giuseppe Iuculano wrote:
[...]
chromium doesn't compile with the current version of ffmpeg in unstable
because it is too outdated, this means I had three choices:
- compile with use_system_ffmpeg=0 and build_ffmpegsumo=0 (this means
drop ffmpeg
On Tue, May 11, 2010 at 17:27:31 +0200, Giuseppe Iuculano wrote:
There was another solution, and this is now adopted in the latest
experimental package, Compile with use_system_ffmpeg=1 and
build_ffmpegsumo=0, but use the in-sources include path for headers, see
[1] and [2].
In this way,
On Tue, May 11, 2010 at 17:27:31 (CEST), Giuseppe Iuculano wrote:
severity 580947 important
thanks
For the record, after reading your latest mail, I still disagree with
this assessment, but won't play BTW ping pong.
Il 11/05/2010 10:44, Reinhard Tartler ha scritto:
I can only assume that
On 2010-05-11, Reinhard Tartler siret...@debian.org wrote:
On Mon, May 10, 2010 at 22:36:00 (CEST), Giuseppe Iuculano wrote:
Chromium in Debian is built against the system FFmpeg headers via
pkg-config. This means when Chromium is launched it will assume that
FFmpeg is present in the system
Il 11/05/2010 17:35, Ben Hutchings ha scritto:
How can you expect this to work? The ABI of the system ffmpeg libraries
is not going to match the ABI defined by the bundled headers. You must
patch chromium to work with the system ffmpeg headers.
chromium doesn't link against the ffmpeg
On Tue, May 11, 2010 at 08:55:17PM +0200, Moritz Muehlenhoff wrote:
Surely not. Chromium ships a *private* copy of ffmpeg, more precisely, a
fork of ffmpeg called ffmpeg-mt. Debian does not include ffmpeg-mt
because of bug #575600 (tagged wontfix). Moreover, Debian's copy of
ffmpeg will
On Tue, May 11, 2010 at 23:53:51 +0200, Giuseppe Iuculano wrote:
Il 11/05/2010 17:35, Ben Hutchings ha scritto:
How can you expect this to work? The ABI of the system ffmpeg libraries
is not going to match the ABI defined by the bundled headers. You must
patch chromium to work with the
On Wed, May 12, 2010 at 00:29:02 (CEST), Stefano Zacchiroli wrote:
On Tue, May 11, 2010 at 08:55:17PM +0200, Moritz Muehlenhoff wrote:
Surely not. Chromium ships a *private* copy of ffmpeg, more precisely, a
fork of ffmpeg called ffmpeg-mt. Debian does not include ffmpeg-mt
because of bug
On 2010-05-11, Stefano Zacchiroli z...@debian.org wrote:
I understand that the security team might be skeptical about security
support, but IIRC past vetoes from the security team came from software
with bad _history_ of security support, while in this case it would seem
a preemptive move,
Hi, i didn't know where or how to report this, but i have readed in a forum
that an user has tried chromium-browser from experimental and seems that it
includes by default those privative codecs. I have tried by myself and i
agree with him, but maybe i am wrong.
this is the process. Adding ubuntu
Hi,
Il 10/05/2010 22:15, Iker Salmón San Millán ha scritto:
Hi, i didn't know where or how to report this, but i have readed in a
forum that an user has tried |chromium-browser from experimental and
seems that it includes by default those privative codecs. I have tried
by myself and i agree
El 10 de mayo de 2010 22:36, Giuseppe Iuculano giuse...@iuculano.itescribió:
No, it doesn't contain those, see below
Chromium in Debian is built against the system FFmpeg headers via
pkg-config. This means when Chromium is launched it will assume that
FFmpeg is present in the system
On 05/10/2010 10:44 PM, Iker Salmón San Millán wrote:
I didn't report as a bug because there wasn't anything wrong with the
usability, i tought it was something that goes against debian social
contract.
Which would still be a bug, with a a release critical severity.
Best thing to do in such
On Mon, 2010-05-10 at 22:36 +0200, Giuseppe Iuculano wrote:
If you can watch youtube html5 video, probably you have installaed
libavcodec52, libavformat52 and libavutil50 from debian-multimedia[1] or
other third repositories.
Why? Debian ships decoders for H264, so it should work out of the
Giuseppe Iuculano giuse...@iuculano.it writes:
If you can watch youtube html5 video, probably you have installaed
libavcodec52, libavformat52 and libavutil50 from debian-multimedia[1] or
other third repositories.
Hmm? Mplayer in debian unstable plays youtube h.264 just fine. No
non-free stuff
On Monday 10 May 2010 17:36:59 Sven Arvidsson wrote:
On Mon, 2010-05-10 at 22:36 +0200, Giuseppe Iuculano wrote:
If you can watch youtube html5 video, probably you have installaed
libavcodec52, libavformat52 and libavutil50 from debian-multimedia[1] or
other third repositories.
Why?
On Mon, May 10, 2010 at 22:36:00 (CEST), Giuseppe Iuculano wrote:
Chromium in Debian is built against the system FFmpeg headers via
pkg-config. This means when Chromium is launched it will assume that
FFmpeg is present in the system library path. In this way you can
decide which codecs
On Mon, May 10, 2010 at 22:15:28 (CEST), Iker Salmón San Millán wrote:
Hi, i didn't know where or how to report this, but i have readed in a forum
that an user has tried chromium-browser from experimental and seems that it
includes by default those privative codecs.
As others have noted in
Reinhard Tartler wrote:
Surely not. Chromium ships a *private* copy of ffmpeg, more precisely, a
fork of ffmpeg called ffmpeg-mt. Debian does not include ffmpeg-mt
because of bug #575600 (tagged wontfix). Moreover, Debian's copy of
ffmpeg will always be out-of-date.
I wonder why the
31 matches
Mail list logo
