Marek Blaha

This version prints installation size per package: ``` #!/usr/bin/python3 import libdnf5 # initialize libdnf5 base = libdnf5.base.Base() base.load_config() base.setup() # read all repositories repo_sack = base.get_repo_sack() repo_sack.create_repos_from_system_configuration() repo_sack.load_repos() for pkgspec...

Well, Rocky Linux 9 is exactly why you need the dnf4 API. RHEL 8, 9, and 10 all ship with dnf4, and dnf5 isn’t available there. So your issue is...

Here is the version of the script, that uses dnf4 API: ``` #!/usr/bin/python3 import dnf base = dnf.Base() base.read_all_repos() base.fill_sack(load_system_repo=True) for pkgspec in ["vim-enhanced", "powerline-fonts", "fzf", "python3-virtualenv", "ruff"]: base.install(pkgspec) base.resolve()...

Let me clarify it. 1. there is "dnf4 stack", package manager used in Fedora till version 40, and in RHEL 8, 9, and 10. It consists of - the python...

Given that the failing changelog entry was autogenerated - shouldn't there be a check for such errors in the generator?

I've bisected the problem to the commit d2a3098a86356b65182d4112a13e1c70ccacbe47

Upstream Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2350483

`transaction_action_*` signals are equivalent to the rpm transaction callbacks `(un)install_*`. See their documentation here: https://dnf5.readthedocs.io/en/latest/api/c%2B%2B/libdnf5_rpm_transaction_callbacks.html. In this context, `total` refers to the `installed size` of the package being installed or...

/packit test

This is valid request. Currently the metadata types libdnf5 knows about are hardcoded (see include/libdnf5/conf/const.hpp). We should think of more flexible way how distributions (or API users) can define their...