This is a ridiculously large update set so get ready…
First off, this set brings in GCC 8.1.0 so there are many, many package rebuilds.
Next, Xorg 1.20. This will work fine for everything other than NVIDIA 304xx and 340xx driver series. If you’re running either of those you’ll need to switch to
nouveau as per the previous announcement. There’s nothing that can be done about this - NVIDIA are dropping 32-bit OS support for drivers, and that’s that. 390xx will stay working for “some time” but is likely to break at some point. If nouveau does not work for you then it’s time for a hardware upgrade…
KDE and Plasma packages also get an update.
Firefox and Chromium also see updates as I’ve found workarounds for their associated build issues.
FFMPEG is up to version 4.0. VLC is up to 3.0.2.
There’s a big set of Python and Haskell module updates.
Also, kernel updates!
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?
Phil very kindly updated the preview installer images:
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 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)