Hi Brad (and Erwan),
* Brad Rogers <b...@fineby.me.uk> [2022-02-27 20:22]:
On Sun, 27 Feb 2022 16:47:25 +0100
Erwan David <er...@rail.eu.org> wrote:
Hello Erwan,
I know wether all plasma packages will upgrade or not ?
Whenever I see a large number of plasma packages arrive in testing, I
check versions.
If they go from 5.14.something to 5.14.somethingelse, then I upgrade
without too many worries.
If the packages go from 5.14.something to 5.15.something, then I wait a
day or two, to make sure everything has come through - in the mean time
checking as best I can that there aren't any known issues (here, Debian
packages, DDG search, etc).
If packages were to go from 5.14.5 to 6.something, I'd again hold on a
day or two to make sure everything's in sync.
For doing these mega updates, everyone has his/her particular way of
doing stuff, but some things can help quite a lot:
1. Try having a system installation with filesystem snapshots; thin
snapshots work quite well. If everything becomes completely messed up
you can easily revert to the initial state. This can be automated (e.g.,
before and after apt runs), and you can keep a few images with automatic
rotation, just in case (consider snapper for this).
2. Try using aptitude interactively. This way all packages will end up
in a consistent state; possible different forms of conflict resolution
can be selected manually, you can also look/select different package
versions, as also suggested installs.
3. After the major update is finished, you can check which packages did
not yet upgrade to a target version number, with aptitude. These might
not have migrated to testing yet. Just use something like:
aptitude search '?narrow(~i,~V4.12)'
aptitude search '?narrow(~i,~ncuda)'
aptitude search '~V5.5' -F "%c %p %d %V" |sort |more
If you feel safe, just update the packages that are identified (e.g.,
interactively again in aptitude). This way you'll be able to do a
complete upgrade without waiting too long.
Hope this can help. Regards,
Nuno.