This is a pretty obscene update. Pretty much every package in the repos has been updated - there are nearly 8,000 updated packages in total. Therefore,
I recommend that you:
- Make a backup before performing this update
- Prepare a boot medium in case you need to chroot in
- Make absolutely certain your mirror is up to date
- Make sure you’re on AC power
- Run the update from a text console using
The update set has been reported to work fine from within Pamac or Octopi but for this number of updates I really wouldn’t risk it. As @sueridgepipe observed in the x32-testing thread you’re essentially reinstalling the entire OS. Running from a text console should prevent any issues (possibly even better, from runmode 3, e.g. tag a “3” to the end of your GRUB boot line then boot direct to a text console).
As far as I, and all the other people who have tested so far, can tell, there shouldn’t be any major issues. However - I still wish you luck with this one.
Anyone who would like to help out testing the upstream packages, please read the archlinux32 thread for details about how they automate their testing process and how to get involved:
(running this in an archlinux32 VM would be fine, there will hopefully be a way of doing this directly from within manjaro32 in the future)
If you find manjaro32 useful please consider donating to, or helping out with, archlinux32. It’s a small team taking on a huge project and any help will no doubt be very much appreciated.
Why aren’t the available packages/package versions the same as x86_64?
archlinux32 packages are based on Arch packages but may need editing to build correctly. Builds of less-popular packages are lower priority.
Manjaro-specific packages may lag behind x86_64 because there aren’t as many packagers. If you notice an important package is lagging please report it; at the moment it’s only me packaging for i686:
I’m only packaging current LTS kernels. Any marked as EOL are dropped. I’ll not be building the mainline kernel.
What about security updates?
I cannot guarantee timely security updates on x32-stable. If this is critical for you I recommend you switch to x32-testing or cherry-pick those packages from x32-testing or x32-unstable as they become available.
Something broke. Isn’t this meant to be stable?
“Stable” means “infrequently changing”, not “everything will work perfectly all the time”. If you want it to mean everything works, you need to help test the things you’re interested in.
What about installer images?
There’s a rapidly ageing image over here:
A new image will arrive when I find the time, which may be never.
These are already available, and I recommend you use
x32-testing if you can to make sure testing is done.
x32-unstable should be used by anyone who wants to try and find any issues before they impact other people. If you have multiple/many machines you really should run one of those on x32-unstable.
Full list of changes
Full list of changes is available here.
- No issues, everything went smoothly
- Yes there was an issue. I was able to resolve it myself. (Please post your solution)
- Yes I am currently experiencing an issue due to the update. (Please post about it)