This is a very large update set which updates kernels 3.16, 4.4, 4.9, and 4.14 (with extramodules), KDE, LibreOffice, Haskell packages, Python modules, MATE, Palemoon, … it’s pretty massive.
This set is based on a custom “combined source” repo that combines packages from the archlinux32 stable and testing repos. This means we get packages more quickly, and can help with testing packages as they move through our branches. I’m hoping there will be no issues once they hit x32-stable but only time will tell.
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)
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?
Phil very kindly updated the preview installer images:
There will be a new release as soon as I refresh myself on how to do it.
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
The full list is far, far, faaaaar too long and 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)