The API does not change, only the deprecation warning is added. The test suite in the linked bug fails only because it treats all warnings as errors, not because of any API change.
I consider raising a new warning as a change of API, but I realize that it is probably disputable. Anyway, the update is in stable, probably to late to change anything, let's not bike shed then. I was surprised by this, and others might be as well. I'd consider an e-mail to dependent package maintainers as a reasonable thing to do.
This update has been submitted for testing by jeckersb.
This update has been pushed to testing.
works for me
Works great! LGTM! =)
no regressions noted
This update has been submitted for batched by bodhi.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Are we sure this is API compatible enough to go into stable Fedoras? See for example https://bugzilla.redhat.com/show_bug.cgi?id=1692172
The API does not change, only the deprecation warning is added. The test suite in the linked bug fails only because it treats all warnings as errors, not because of any API change.
I consider raising a new warning as a change of API, but I realize that it is probably disputable. Anyway, the update is in stable, probably to late to change anything, let's not bike shed then. I was surprised by this, and others might be as well. I'd consider an e-mail to dependent package maintainers as a reasonable thing to do.
(I'll send it.)