severity 803828 minor
thanks
Hi Andreas,
There was no update on this bug report because I found any upload on
this matter premature. When this bug was reported, there was no
transition yet [1] and the FFmpeg version you wanted to upgrade to
hadn't even been release by upstream [2]. Nothing of this has changed so
far, so I keep waiting.
I thank you for your patch and your initiative and hope you understand
that I can't very well upload anything before the version we are
upgrading to is actually released and I can test its compatibility.
When you first posted this report, I checked out your patch and
confirmed that it doesn't break anything. But I can't be sure that it
will fix all compatibility issues with FFmpeg 2.9/3.0 - because it
doesn't exist yet. Since I am not a DD or DM, all my uploads have to go
through sponsors, so I really want to get it right the first time.
Cheers,
Martin
[1] https://release.debian.org/transitions/
[2] https://www.ffmpeg.org/download.html#releases
Andreas Cadhalpun wrote:
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an upload soon?
* Is upstream aware of the problem?
If this bug isn't fixed soon, it will become release critical and
thus the package will either get NMUed or removed from testing.
Also there is a new upstream version (2.1) available, which
could be uploaded together with this patch.
Best regards,
Andreas
