Hi Maxwell,
This contains an update to dnf 5.2.0 which has breaking API changes. I did not
see these communicated anywhere and the Change Proposal did not mention that
the update would include a major version bump at the same time as the switch to
dnf5 as default.
You're right; we missed this. I'm sorry about that. Our initial intention wasn't to do a major version bump, but implementing the new functionality without breaking ABI and API would have required a lot of extra work.
Would it be possible to provide a testing Copr ...
... and a porting guide so API users can fix their software
before this is pushed to rawhide?
We'll add a section about the API changes between dnf5 versions 5.1 and 5.2, and we'll reach out to the several teams affected by this. We'll also ensure that the builds for our reverse dependencies are passing with this update. We definitely don't want to push this before these projects are fixed.
Still, I hope no harm has been done yet. That's actually the purpose of this side-tag, to identify any gaps we may have missed while working on the switch. The 5.2.0.0 API changes aren't significant, there are though many ABI-breaking changes.
Thanks,
Jan