Skip to content
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

Open
edpil02 opened this issue Nov 29, 2024 · 8 comments
Open

Yumex-updater fake updates #112

edpil02 opened this issue Nov 29, 2024 · 8 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request reproduced

Comments

@edpil02
Copy link

edpil02 commented Nov 29, 2024

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."

@edpil02 edpil02 added the bug Something isn't working label Nov 29, 2024
@edpil02
Copy link
Author

edpil02 commented Nov 29, 2024

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) - show_message : No match for argument: akmods-0:0.6.0-6.fc42.noarch
No match for argument: binutils-0:2.43.50-9.fc42.x86_64
No match for argument: bluedevil-0:6.2.4-1.fc42.x86_64
No match for argument: breeze-cursor-theme-0:6.2.4-1.fc42.noarch
No match for argument: breeze-gtk-0:6.2.4-1.fc42.noarch
No match for argument: breeze-gtk-common-0:6.2.4-1.fc42.noarch
No match for argument: breeze-gtk-gtk2-0:6.2.4-1.fc42.noarch
No match for argument: breeze-gtk-gtk3-0:6.2.4-1.fc42.noarch
No match for argument: breeze-gtk-gtk4-0:6.2.4-1.fc42.noarch
No match for argument: chrony-0:4.6.1-1.fc42.x86_64
No match for argument: crypto-policies-0:20241126-1.gitbb3f7dc.fc42.noarch
No match for argument: crypto-policies-scripts-0:20241126-1.gitbb3f7dc.fc42.noarch
No match for argument: debugedit-0:5.1-2.fc42.x86_64
No match for argument: edk2-ovmf-0:20241117-5.fc42.n

08:45:22 DEBUG : (yumex.ui.window) - Transaction execution ended : False
08:45:22 DEBUG : (yumex.ui.package_view) - Reset Package View
08:45:22 DEBUG : (yumex.ui.package_settings) - SIGNAL: emit package-filter-changed: installed
08:45:22 DEBUG : (yumex.ui.window) - SIGNAL: package filter changed : installed
08:45:22 DEBUG : (yumex.ui.package_view) - Loading packages : installed
08:45:22 DEBUG : (yumex.utils) - >> Running async job : get_packages_by_filter.
08:45:23 DEBUG : (yumex.utils) - << Completed async job : get_packages_by_filter.
08:45:23 DEBUG : (yumex.utils) - >> starting add_packages_to_store
08:45:23 DEBUG : (yumex.ui.package_view) - Adding packages to store
08:45:23 DEBUG : (yumex.ui.package_view) - --> sorting by : name
08:45:23 DEBUG : (yumex.ui.package_view) - --> number of packages : 2350
08:45:23 DEBUG : (yumex.utils) - << add_packages_to_store took 0.0531 sec
08:45:23 DEBUG : (yumex.ui.package_view) - SIGNAL: emit selection_changed: a2jmidid-0:9-14.fc41.x86_64
08:45:23 DEBUG : (yumex.ui.window) - Window: package selection changed : a2jmidid-0:9-14.fc41.x86_64
08:45:23 DEBUG : (yumex.utils) - >> Running async job : get_package_info.
08:45:23 DEBUG : (yumex.utils) - << Completed async job : get_package_info.

@GloriousEggroll
Copy link
Contributor

GloriousEggroll commented Jan 13, 2025

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.
what happens is say f41 repo and f42 repo provide the same package. if theres no priority set for one of the repos then it's going to offer the package version that is newest between the two, and of course that may fail if you have both f41 and f42 repos mix matched.

@nick-pt
Copy link

nick-pt commented Jan 23, 2025

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.

@timlau
Copy link
Owner

timlau commented Jan 24, 2025

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

dnf clean expire-cache ; sudo dnf clean expire-cache

solve it i most cases

@timlau timlau self-assigned this Jan 24, 2025
@timlau
Copy link
Owner

timlau commented Jan 24, 2025

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.

@timlau timlau added enhancement New feature or request reproduced labels Jan 24, 2025
@timlau
Copy link
Owner

timlau commented Jan 24, 2025

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

@timlau
Copy link
Owner

timlau commented Jan 24, 2025

#116

@nick-pt
Copy link

nick-pt commented Jan 25, 2025

Thank you for your help! Ill report back if it breaks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request reproduced
Projects
None yet
Development

No branches or pull requests

4 participants