Originally posted by sylerner
View Post
That got me to thinking about pkcon (PackageKit CONsole client), since a lot of the info I saw referred to "pk-offline...", etc...
From "man pkcon":
offline-get-prepared
Print information about the prepared offline update. If no offline update is prepared, exit with an exit code of 1.
offline-trigger
Trigger an offline update.
offline-status
Print information about the result of the last offline update.
However, it gives no indication as to what pkg is responsible for adding the offline update option to System Settings. Still searching..EDIT: I believe Claydoh solved the problem in this post.
From his first link:
Starting today if you use Discover to update your KDE neon Unstable installation, instead of immediately applying the update it will download the package and notify you that you need to restart to complete the update. Upon starting the next time the update is finally applied.
...
Any other package management front end will not perform offline updates. This most notably also includes the terminal interfaces pkcon and apt-get. Application distribution systems such as flatpak and snap are equally unaffected by this because they generally are not able to break the same way as system software can.
You can still choose to prepare an offline update using pkcon if you prefer using the terminal:
pkcon update --only-download && pkcon offline-trigger
...
Any other package management front end will not perform offline updates. This most notably also includes the terminal interfaces pkcon and apt-get. Application distribution systems such as flatpak and snap are equally unaffected by this because they generally are not able to break the same way as system software can.
You can still choose to prepare an offline update using pkcon if you prefer using the terminal:
pkcon update --only-download && pkcon offline-trigger
Leave a comment: