Using updater-test-22-10-31.xzm (my md5sum is the same as yours)
Code: Select all
Starting checks ...
[OK] Server: http://dl.porteus.org
[OK] Architecture: x86_64
[OK] User is root
[OK] Distro is Porteus
[OK] Base folder is writable
[OK] Internet connection confirmed
Downloading: update-porteus-live DONE
Downloading: updates.txt DONE
Checking base modules ...
Checking patch availability ...
#########################
Available core updates
001-core.xzm
002-xorg.xzm
Would you like to continue? [y/n]
Now it works.
Suggestion, is it possible for the script to tell the user what update that is?
E.g. by telling the user the YYYYMMDD folder the updates are in?
Just
is giving no info at all, but I presume the script knows what YYYYMMDD folder the modules are in?
Would the script overwrite my files in base?
Would it make a backup first?
I prefer older versions that work than new versions that fail e.g. due to a download error and wrong md5sums.
The core modules are quite essential to a working system after all.
Added in 7 minutes 49 seconds:
Some mirror servers still seem not to have the updates.
This one does:
https://linux.rz.rub.de/porteus/x86_64/ ... /20220924/
Code: Select all
Index of /porteus/x86_64/Porteus-v5.0/updates/core/20220924
Icon Name Last modified Size [PARENTDIR] Parent Directory -
[ ] 001-core.xzm 2022-10-09 12:48 121M
[ ] 002-xorg.xzm 2022-10-09 12:48 112M
I presume that's the ones the above is referring to?
Added in 5 minutes 27 seconds:
Update
It seems silly me manually downloaded the updates via wget recursive… but I forgot to change the symlinks in my $PORTDIR/base/ accordingly.
I now changed that, making the new md5sums appear like so:
Code: Select all
root@porteus:~# md5sum $PORTDIR/base/001-core.xzm $PORTDIR/base/002-xorg.xzm
087e196ed3e7a8750b32031e3221fc2b /mnt/sda1/Porteus_5.0/porteus/base/001-core.xzm
9a1afb69141822791d5a114909725431 /mnt/sda1/Porteus_5.0/porteus/base/002-xorg.xzm
According to
https://linux.rz.rub.de/porteus/x86_64/ ... pdates.txt both md5sums are accurate.
Added in 6 minutes 41 seconds:
Now all there is to do figure out how to accurately update my palemoon settings module to reflect the most recent changes how I want it to behave prior me rebooting the system…
Code: Select all
cd /home/guest/.moonchild productions/pale moon/*.default
# the above won't work, replace "*.default" with the real folder name of your setup
grep -E '"browser.sessionstore.cache_behavior", |"browser.startup.page", ' prefs.js
# should be:
#user_pref("browser.sessionstore.cache_behavior", 2);
#user_pref("browser.startup.page", 3);
The last manually updated settings module did have some kinks left, while it at least has the two settings as quoted above correct.
Added in 2 minutes 56 seconds:
So, working on that and then when I rebooted using the manually downloaded newest updates of core I will report back after again activating updater-test-22-10-31.xzm how that goes then. (It should report no updates available for me then… I presume it checks the updates via the md5sums of the modules in the base/ folder ?)