Skip to content

Conversation

@jelly
Copy link
Member

@jelly jelly commented Dec 5, 2025

No description provided.

@jelly jelly added the no-test For doc/workflow changes, or experiments which don't need a full CI run, label Dec 5, 2025
@jelly jelly force-pushed the debug-rhel-8-packagekit branch 3 times, most recently from fbf4d91 to 19b2987 Compare December 5, 2025 10:30
jelly added 14 commits December 5, 2025 12:44
Introduce a `with_session` helper which creates the session, optionally a
subscription and cleans them up.
Implement `is_installed` for the appstream apps page and switch to the
packagemanager implementation. This also drops the progress callback as
it wasn't use in the PackageKit scenario and dnf5daemon doesn't give us
any useful progress information at all.
The confusingly named packagekit.js file will be empty after moving
everything to the packagemanager class and to where it is used.
Implement `install_packages` for the appstream apps page and switch to
the PacakgeManager implementation. This also drops the ProgressReporter
wrapper which isn't required as we have one progress event to watch.
With these two new methods we can replace the remove functionality in
the apps page with the packagemanager implementation.
Implement the last two functions needed to move the `refresh` method of
the apps page over to the packagemanager implementation.
This removes the confusingly named packagekit.js file and moves the
refresh function to where it is used.
These are no longer used via "packagekit" but only via the
PackageManager class.
Closing the single dbus client shared across all packagemanager
instances breaks multiple operations in parallel. Subscriptions will now
not be properly cleaned up as `remove-match` isn't implemented in the
Python bridge.
Everyone has moved to the PackageManager method.
Close the DBus client after checking if packagekit/dnf5daemon dbus's
services exist.
@jelly jelly force-pushed the debug-rhel-8-packagekit branch from ec212f8 to 70fea30 Compare December 5, 2025 11:44
jelly added 3 commits December 5, 2025 13:18
The kpatch code already uses the install_dialog which uses the
PackageManager class internally so there is no issue in moving this to
check_missing_packages. As kpatch only works on RHEL, this would use
PackageKit anyway.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-test For doc/workflow changes, or experiments which don't need a full CI run,

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant