[Future request] Avoiding partial system updates

sirlucjan commented

2022-06-21 16:43:10 +02:00

@anonfunc
Currently, only the Plasma 5.25.1 partial update is available in ALHP.

lucjan at archlinux ~ 16:41:15    
❯ checkupdates
breeze-gtk 5.25.0-1 -> 5.25.1-1
drkonqi 5.25.0-1.1 -> 5.25.1-1.1
kactivitymanagerd 5.25.0-1.1 -> 5.25.1-1.1
kdecoration 5.25.0-1.1 -> 5.25.1-1.1
kmenuedit 5.25.0-1.1 -> 5.25.1-1.1
ksshaskpass 5.25.0-1.1 -> 5.25.1-1.1
kwallet-pam 5.25.0-1.1 -> 5.25.1-1.1
kwayland-integration 5.25.0-1.1 -> 5.25.1-1.1
layer-shell-qt 5.25.0-1.1 -> 5.25.1-1.1
libkscreen 5.25.0-1.1 -> 5.25.1-1.1
libksysguard 5.25.0-1.1 -> 5.25.1-1.1
milou 5.25.0-1.1 -> 5.25.1-1.1
oxygen-sounds 5.25.0-1 -> 5.25.1-1
plasma-sdk 5.25.0-1.1 -> 5.25.1-1.1
plasma-workspace-wallpapers 5.25.0-1 -> 5.25.1-1
polkit-kde-agent 5.25.0-1.1 -> 5.25.1-1.1
xdg-desktop-portal-kde 5.25.0-1.1 -> 5.25.1-1.1

Would it be technically possible to upload full updates? Installing the above update would almost certainly end up crashing Plasma.

@anonfunc Currently, only the Plasma 5.25.1 partial update is available in ALHP. ``` lucjan at archlinux ~ 16:41:15 ❯ checkupdates breeze-gtk 5.25.0-1 -> 5.25.1-1 drkonqi 5.25.0-1.1 -> 5.25.1-1.1 kactivitymanagerd 5.25.0-1.1 -> 5.25.1-1.1 kdecoration 5.25.0-1.1 -> 5.25.1-1.1 kmenuedit 5.25.0-1.1 -> 5.25.1-1.1 ksshaskpass 5.25.0-1.1 -> 5.25.1-1.1 kwallet-pam 5.25.0-1.1 -> 5.25.1-1.1 kwayland-integration 5.25.0-1.1 -> 5.25.1-1.1 layer-shell-qt 5.25.0-1.1 -> 5.25.1-1.1 libkscreen 5.25.0-1.1 -> 5.25.1-1.1 libksysguard 5.25.0-1.1 -> 5.25.1-1.1 milou 5.25.0-1.1 -> 5.25.1-1.1 oxygen-sounds 5.25.0-1 -> 5.25.1-1 plasma-sdk 5.25.0-1.1 -> 5.25.1-1.1 plasma-workspace-wallpapers 5.25.0-1 -> 5.25.1-1 polkit-kde-agent 5.25.0-1.1 -> 5.25.1-1.1 xdg-desktop-portal-kde 5.25.0-1.1 -> 5.25.1-1.1 ``` Would it be technically possible to upload full updates? Installing the above update would almost certainly end up crashing Plasma.

anonfunc commented

2022-06-22 12:50:24 +02:00

Owner

ALHP builds the Archlinux source repo in a snapshot-like mode. It updates the repo-source, then builds whatever there is to build, then repeats. So technically there should be no partial updates assuming upstream moves its packages in a 'non-partial-update'-like manner (which they do).

anonfunc added the question label 2022-06-22 12:51:46 +02:00

sirlucjan commented

2022-06-22 13:11:26 +02:00

Author

I try to review the packages that will be updated and if I see that a dozen or so are missing, I wait for them to appear. However, this situation surprised me a bit - some of the Plasma 5.25.1 appeared in the repo immediately and the rest after a few hours. This could lead to a Plasma crash hence the thought.

anonfunc commented

2022-06-22 13:31:43 +02:00

Owner

Like I said, this should not happen, at least not under normal circumstances. ALHP only builds packages in a batch like manner, same as they are released upstream. What you describe may happen if Arch would have released a part of plasma earlier than the rest. Not sure if that is the case here. You can look that up in their svn2git repo if you want to, maybe you can reconstruct the timeline.
Even if we assume above mentioned happens somewhat infrequently, ALHP would have a hard time checking for that sort of thing.

Like I said, this should not happen, at least not under normal circumstances. ALHP only builds packages in a batch like manner, same as they are released upstream. What you describe may happen if Arch would have released a part of plasma earlier than the rest. Not sure if that is the case here. You can look that up in their svn2git repo if you want to, maybe you can reconstruct the timeline. Even if we assume above mentioned happens somewhat infrequently, ALHP would have a hard time checking for that sort of thing.

sirlucjan commented

2022-06-22 15:01:44 +02:00

Author

In that case, the topic can be considered non-existent. Thanks for the explanation.

sirlucjan closed this issue

2022-06-22 15:01:46 +02:00

[Future request] Avoiding partial system updates #130