On Sat, Sep 24, 2022 at 08:01:45PM -0500, Maxwell G via devel wrote:
On Tue Sep 6, 2022, Ben Cotton wrote:
> == Upgrade/compatibility impact ==
> The new DNF5 will obsolete `dnf`, `yum`, `dnf-automatic`, `yum-utils`,
> and DNF plugins (core and extras). python3-dnf and LIBDNF (`libdnf`,
> `python3-hawkey`) will be obsoleted by `fedora-obsolete-packages`.
I am worried about removing python3-dnf this early. As far as I can
tell, the new Python libdnf bindings are very much not a drop in
replacement. There are a fair amount of tools and scripts that depend on
python3-dnf. The change proposal listed some of them, but Ansible's dnf
I'm worried about replacing it at all. I'd like to see them coexist
until we can get things rewritten, but it also says their databases are
separate which will possibly cause other issues so that's also likely to
lead to different problems.
I took a stab at converting my test-dnf-transaction script yesterday,
and the changes so far are not anywhere near compatible with dnf v4, and
I didn't manage to get it working yet.
https://github.com/bcl/test-dnf-transaction/pull/1
https://github.com/rpm-software-management/dnf5/issues/66
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart