-
Notifications
You must be signed in to change notification settings - Fork 2
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
Yumex-updater fake updates #112
Comments
A part of the konsole output after performing the update of 174 packages 8:45:22 DEBUG : (yumex.backend.dnf5daemon.client) - Close Dnf5Daemon session: /org/rpm/dnf/v0/e8c2ece66aadcf6c1bb31d0ced341bd2 08:45:22 DEBUG : (yumex.ui.window) - Transaction execution ended : False |
It seems you have both fedora 41 (fc41) and fedora 42 (rawhide fc42) packages installed. my guess is maybe you enabled rawhide repos somewhere? anyway if so you should go into the repo file and set priority. |
hey so i have the same problem. I just updated 524 packages and after the update 234 packages remained. I tried installing them again and the transaction failed. Its been happening for a really long time though, i just learned to ignore it.n I checked and i dont have rawhide installed pretty sure. |
The problem is that i use dnf in non-root mode for speed to show packages, but when i apply a transaction, i use a dnf dbus deamon there is working on dnf in root mode, and these don't have the same cache, so they can be out of sync close yumex and run this
solve it i most cases |
I plan to test the speed of the dnf5 dbus api is fast enough to do all the work, some time in the future, when dnf4 is not used any more and i don't have to maintain support for both dnf4/dnf-daemon & dnf5/dnf5-daemon. It will fix these issues. |
The problem is there is no API in dnf5-daemon to force and update of the metadata cache, so I can't force a refresh, but i can do that in dnf5 API when using it directly in non-root mode |
Thank you for your help! Ill report back if it breaks again |
Yumex updater often proposes invalid updates.
I have another example right now; it tells me that there are 174 packets to update but when I perform the update, the transaction fails.
And dnf update answers "there is nothing to do."
The text was updated successfully, but these errors were encountered: