-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sanity check fails with dnf5 #5820
Comments
So, F40 worked with 5.1.x, F41 with 5.2 doesn't... |
Oddly, it works when I manually run it too:
|
It just came to my mind that on F40 dnf4 was still used by default, wasn't it? So the problem is not between dnf5 5.1 and 5.2. The command syntax seems right, even if dnf5 could use different options (see #5821 ) it maintain backward compatibility. I've also tested that by cloning the above repository locally and ran the command both in my F41 workstation and in the bodhi development environment through bodhi-shell by using the bodhi.server.util.sanity_check_repodata_dnf method. The only way I can reproduce a failure on that part of code is by enabling the relevant tests during a real Koji build (I cannot see it in a local mockbuild). There I get some more details:
But I'm not sure it can be relevant. |
I have updated #5821 to catch the error thrown by subprocess and print it out, so, if you want, we can try to patch bodhi.server.util on bodhi-backend, reinstate dnf5 and fire a compose to better see what the error is. |
I've also set up #5822 which is a little more radical... instead of trying to load the repository by a dnf CLI call through subprocess, we can load it through libdnf5 python bindings. But I'd like a review by someone with more knowledge on dnf python bindings on the method I wrote to load the repository. I have the feeling it is not quite right about the settings changed on the base config, despite I've followed the official tutorial. In the end, I think the problem is that we run dnf5 in a subprocess started by a user without bash login. Using python bindings would solve that. |
Yeah, that seems a fine approach. I am not sure who knows those bindings and can review tho. |
This is with:
dnf5-5.2.7.0-1.fc41.x86_64
Switchking back to dnf-3 works.
The text was updated successfully, but these errors were encountered: