Re: Bug#763148: Prevent migration to jessie
Hi,
On 05.10.2014 21:27, Cyril Brulebois wrote:
Andreas Cadhalpun <andreas.cadhalpun@googlemail.com> (2014-10-05):
The whole discussion we are having currently is about letting FFmpeg
migrate to jessie!
So this is no 'unavoidable issue'.
But as you seem to be willing to consider this in principle, I think
now the time has come for the release team to make an official
decision:
Is FFmpeg allowed to migrate to testing, so that chromium can use it?
Or is chromium allowed to continue to use it's embedded copy?
I'm not sure why one would think the decision still needs to be made.
That's because the last message from a release team member in this bug
said [1]:
'However (and please note that I'm not a member of the security team
and just speak for myself here as always when not otherwise marked) if
it would be possible to replace the internal code copy in chromium
by a reference to ffmpeg (but it's not possible with libav), that will
probably lead to a re-evalutation. (That doesn't necessarily mean
"sucess guranteed", but it looks to me as it will not make things
worse.)'
It is possible to replace the internal code copy in chromium
by a reference to ffmpeg [2], so I thought this would lead to a
re-evaluation.
Best regards,
Andreas
1: https://bugs.debian.org/763148#27
2: https://bugs.debian.org/763632
Reply to: