Re: Bug#763148: Prevent migration to jessie
Hi Jonathan,
thanks for answering my question.
On 29.04.2015 16:52, Jonathan Wiltshire wrote:
> mysql-5.5 and mariadb-10.0 in Jessie is not exactly "no problem".
> There were extensive discussions before the freeze about which of
> the *four* forks of MySQL would ship in Jessie.
>
> Bear in mind that MySQL and Maria were both already in testing at
> this point.
When I asked Moritz about MySQL and MariaDB [1] in February 2014,
MariaDB 5.5 had been in testing for just two months, while
MariaDB 10.0 went to testing only in November 2014.
> The security team understandably want to support only
> one fork. The maintainers could not agree which it should be.
This is exactl
I don't think that's a fair criterion. FFmpeg would be in testing,
if it wasn't blocked.
Now the justification for the block is that it's not in testing.
That's kind of circular.
> andy how it was with FFmpeg/Libav before the freeze.
> We eventually arranged to ship two of those four forks in Jessie
> with a view to having only one in Stretch, easing the transition
> for users if it ends up being Maria. That aim has not changed.
> Jessie was a compromise situation.
I would have appreciated if there had been such a compromise solution
for FFmpeg/Libav as well.
> This isn't a good direct comparison with ffmpeg/libav since we do
> not have the situation of them both in testing at the moment,
I don't think that's a fair criterion. FFmpeg would be in testing,
if it wasn't blocked.
Now the justification for the block is that it's not in testing.
That's kind of circular.
> and
> I believe that should remain the case until one or the other
> becomes the obvious candidate. We do not want to end up with
> dependencies on both in testing that need to be untangled later.
That's understandable. But on the other hand, not having FFmpeg
in testing means more work elsewhere and less testing for it.
Best regards,
Andreas
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729203#420
Reply to: