fedora-eln / eln

Main repository and issue tracker

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

TASK: dnf5 timeline for ELN/c10s/RHEL10

yselkowitz opened this issue · comments

What does the ELN SIG need to do?

  • Right now, dnf (the python-based 4.y version) is still the default, and microdnf the minimal alternative, in ELN, while dnf5 just became the default and replacement for both in rawhide (f39). This is due to how the conditionals in each package were written.
  • It sounds like dnf5 isn't quite at feature parity with dnf (4.y) yet, but I'm not familiar with the plans and schedules here. FWIW dnf and microdnf are still listed in CR, with dnf5 currently only a BuildRequires of supermin.
  • If dnf5 is supposed to be the package manager in c10s/RHEL10, then when it's considered "ready enough" for that, then we'll need coordinated changes to dnf, dnf5, and content-resolver-input.

Looks like this is still up in the air even for F39: https://pagure.io/fesco/issue/3039

Postponed until Fedora 41.