On 10/13/26 11:34 AM, Aoife Moloney via devel-announce wrote:
* '''System Management & Diagnostics:''' `etckeeper`,
`fedora-easy-karma`, `fedrq`, `libreport`, `needrestart`,
`retrace-server`, `subscription-manager`, `system-config-language`

fedrq has already been ported to libdnf5, so it can be removed from this list. It supports python3-dnf OR python3-libdnf5, which causes it show up in repoqueries for dependents of python3-dnf.

== Upgrade/compatibility impact ==
* Packages belonging to the DNF4 stack and legacy modularity tools
will be retired from the Fedora 46 repositories. Unless explicitly
obsoleted, existing installs will remain on upgraded machines as
orphan packages until removed by the user.

After the dnf4 stack is retired, we will eventually (after the Python 3.16 rebuild in F47 or maybe sooner) have to obsolete it to prevent update path issues.

== Contingency Plan ==
* Contingency mechanism: If critical infrastructure or blocking
packages cannot finish migrating off `libdnf` v1 / `python3-dnf` or
dropping `libmodulemd` before freeze, keep the legacy `dnf4`,
`libdnf`, and `libmodulemd` packages in the repositories as standalone
compatibility packages for one additional release cycle.

I am happy to see that libmodulemd is going away and also the eventual removal of the old dnf stack, but I am little worried about this contingency plan. There are releng scripts that still depend on python3-dnf and so does pungi itself. I believe rpm-ostree also still uses the libdnf C library, not just libmodulemd. Is there a plan to complete that porting work by F46 (or F47 if we extend this "for one additional release cycle")? I'd prefer if the proposal identified the most critical components out of the list of dnf4's current dependencies that need to be ported away from dnf4 and then have the actual completion of those porting efforts be the blocker for dnf4 retirement.
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to