Re: Bug#763148: Prevent migration to jessie
On 29/04/15 10:41, Bálint Réczey wrote:
> 2015-04-29 9:44 GMT+02:00 Emilio Pozuelo Monfort <pochu@debian.org>:
>> On 27/04/15 00:30, Andreas Cadhalpun wrote:
>>> On 27.04.2015 00:01, Emilio Pozuelo Monfort wrote:
>>>> On 26/04/15 19:06, Andreas Cadhalpun wrote:
>>>>> Dear release team,
>>>>>
>>>>> as you undoubtedly know: jessie has been released! \o/
>>>>>
>>>>> Thus this bug is now obsolete and I'm closing it.
>>>>>
>>>>> Please remove the testing migration block of ffmpeg.
>>>>
>>>> I don't think you understand the problem.
>>>>
>>>> Having both ffmpeg and libav in the same release is the problem.
>>>
>>> But having mysql-5.5 and mariadb-10.0 in jessie is apparently no
>>> problem, despite previous claims. What's the difference?
>>>
>>>> So at this moment, that "block" hint is not going to be removed.
>>>
>>> When will it be removed, if not now?
>>>
>>> Previously Moritz Mühlenhoff wrote [1]:
>>> "After the jessie release a decision between libav and ffmpeg will need
>>> to be made. It certainly possible to have them co-exist for a year or
>>> so, but the decision needs to be made before the jessie+1 freeze."
>>>
>>> How do you think this should go forward?
>>
>> You could ask the TC to decide between the two. As it happened with #717076 for
>> example.
> There is no need to ask TC (yet), it is blocked by Julien:
> https://release.debian.org/britney/hints/jcristau
>
> Dear Julien,
>
> Could you please lift the unblock now since Jessie has been released
> and we generally don't ban packages from entering testing based on
> duplicate functionality?
Sigh. This has been said multiple times, but I'll explain it again.
We do block stuff based on security concerns.
Since there are concerns on shipping both libav and ffmpeg, we won't allow
ffmpeg unless it is chosen to be the default and there is a clear transition
plan, so that we can switch from one to the other. Only then will the block hint
be removed.
Hope that is clear.
Cheers,
Emilio
Reply to: