Re: Bug#763148: Prevent migration to jessie
Hi Moritz,
On 29.04.2015 20:22, Moritz Mühlenhoff wrote:
> Andreas Cadhalpun wrote:
>
>> But having mysql-5.5 and mariadb-10.0 in jessie is apparently no
>> problem, despite previous claims. What's the difference?
>
> To properly migrate over a daemon they need to co-exist for a stable
> release, while a lib does not. Stretch will only have one of them.
That makes sense, thanks for explaining.
>> How do you think this should go forward?
>
> When someone made a strawpoll amongst the multimedia maintainers
> last year it boiled down to "libav for jessie, since it's now to late".
> You should revisit that decision now that the release cycle has started.
> (Beside pkg-multimedia-maintainers, this certainly also includes
> maintainers like Balint which maintain relevant multimedia apps outside of
> pkg-multimedia-maintainers.)
>
> If no convinging/clear majority can be reached, let the CTTE decide.
That was my plan.
> Having both for a year along each other will only waste people's time. Now
> at the beginning of the release cycle is the time to make a decision,
> not by dragging things into a year as of today. Picking one of the two
> won't be any simpler in 12 months.
I just fear that the decision making process will take long, especially
if the TC has to get involved. (The libjpeg-turbo TC decision took 1 year.)
Having ffmpeg in testing during this time would be nice, e.g. so that people
using testing can easily compare them.
Was that not what you meant with [1]:
"It certainly possible to have them co-exist for a year or so"
Best regards,
Andreas
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763148#134
Reply to: