Hi Andreas,
Andreas Cadhalpun wrote:
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 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.
I do trust in the fact that the API is stable, and if the API is well
specified and the implementation follows it, then there shouldn't be a
problem. But you know how it is, there can always be unexpected runtime
behaviors in the gray areas of the API, or implementations that don't
completely respect what is specified in the API. And since I depend on
sponsors, I'd like to make sure the update is complete.
But anyway, since you offered a sponsor for the upload (see below), I
don't mind uploading a version that is not yet tested with the new
FFmpeg 2.9, as long as it works with the current FFmpeg (which I tested).
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?
Sounds great. Please find the new version of the package in the
package's git repository:
https://github.com/martin-steghoefer/debian-karlyriceditor
Thanks again for the patch and for managing the transition.
Cheers,
Martin
