Petr Pisar

autocheck_running_kernel option is not yet implemented in DNF5. See dnf5.conf-todo(5) manual page. Currently, the option is parsed from a configuration file, but it has no effect.

I see why you see that debug message. DNF5 by default protects a currently running kernel from a removal. To do that it maps the running kernel to an RPM...

"repolist" and "repoinfo" and aliases. Now, we do not provide manual pages for aliases as aliases are usually deprecated forms of invocation. Though I recognize that changes page should list...

Then handle librpm output as informational. E.g. Fedora packaging guidelines require packages to always return exit code 0. I.e. never to fail.

In general, I like your patch, but please address the different semantics I pointed in-line.

I'm not aware about any mechanism you want on the repository level. Repository can have an updateinfo file which can deliver messages to the users, but they are always tied...

I will move this request to librepo project as it the piece of code which downloads repository metadata.

Delivering a new location or the end-of-life notice on HTTP layer (Status 301, 500) would have a problem with mirrors and that a repository locator can contain DNF variables ($basearch,...

The same happens with pull requests against rhel-9.4 branch.

Thanks for the reply. I've just sent an e-mail to Kevin Mulholland.