This is definitely worth doing - maybe if dnf5 is detected then use that by default, but offer the user the chance to override?

A bit busy with other things now, but if you or @ngompa or @daandemeyer want to send a PR that would be great!

I don't have an issue with that either, but I'm a bit busy at the moment.

The incompatibility between dnf4 and dnf5 repoquery is tracked here: https://github.com/rpm-software-management/dnf5/issues/709

maybe if dnf5 is detected then use that by default

I'm not a big fan of this because the interface is not identical, and it randomly switching depending on which dnf is installed would surprise the user and most importantly the scripts. Maybe just pick one default and allow switching manually

This is now a general problem on Fedora 41+, where dnf == dnf5.

Note that the rpmdistro-repoquery command currently doesn't work at all there - it needs to be passed the --use-host-config option to use the repo definitions from the "host" and not from the specified (empty) installroot.

see also https://github.com/rpm-software-management/dnf5/issues/1756

Is that something new? I'm pretty sure I've used rpmdistro-repoquery in rawhide recently

Possibly. I tried rpmdistro-repoquery epel 9 --whatrequires foo on Fedora 41 today and it gave up.

Ah. Doesn't seem to be a problem for repoquerying other fedora versions specifically

We'll need to implement this soon-ish, as we can no longer track rpmdistro-repoquery in ELN Extras now that CentOS 11 is slated to have DNF 5

https://github.com/minimization/content-resolver-input/commit/3412737297dd9489449104422b23d7ceed1e81b0