Hi Martin, On 08.01.2016 11:31, Martin Steghöfer wrote: > severity 803828 minor
This is certainly not a minor bug, as it will be release critical in a few weeks. So please change the severity back to important. > 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 think there is a misunderstanding here. The deprecation of the APIs this patch is about happened several years ago, so fixing the code is certainly not premature, rather the contrary. The goal is that all Debian packages are ready for the new upstream release, where these long deprecated APIs have been removed, when it gets released. Otherwise the transition will be (a lot) less smooth. So please don't 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. I don't really understand this as you can test the replacement APIs with any release of the recent years. The only thing you can't test (without compiling from upstream git) is whether it will build with the new version of ffmpeg. But you don't have to test that, because I (compile-)tested my patch with upstream git. Also I could (runtime-)test a package you prepared with upstream git, if you let me know how to do that. ;-) > When you first posted this report, I checked out your patch and confirmed > that it > doesn't break anything. That's great, because it means that it will work fine with the next FFmpeg version. > 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. However, you can be reasonably sure, because I tested with upstream git and the time for API breakage is over for this cycle (and was already over two months ago). > 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. I'm sure Felipe Sateler (who kindly offered to help with uploads for this transition) would be willing to sponsor this upload, like he did for dvbcut [1]. So as a way forward I suggest: * You prepare a package with this fix. * Optionally let me know how to test it, and I'll test with upstream git. * We ask Felipe to sponsor the upload. Does that sound good to you? Best regards, Andreas 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803809#20
