Hello i686ers!
This set of updates bumps kernels 4.4, 4.9 and 4.14 to include the current KPTI fixes. More is sure to come with the next kernel updates.
However, the main thing of note is the number of upstream changes with a huge number of core packages updated, and another load of packages rebuilt due to MESA, Xorg, Python, Ruby, Qt5 and Haskell updates.
This is a large set of updates.
Main changes
- Updated kernels, extramodules rebuilt as necessary
- Firefox and Thunderbird updates
- Many, many upstream changes, including:
- systemd
- xorg-server
- mesa
- KDE
- LibreOffice
Available kernels
| Series | Version |
|---|---|
| linux316 | 3.16.52 |
| linux41 | 4.1.48 |
| linux44 | 4.4.110 |
| linux49 | 4.9.75 |
| linux414 | 4.14.12 |
archlinux32
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.
How do I get it?
These steps should no longer be necessary
If you’re already running a 32-bit installation, and haven’t already migrated, you should shortly get a manjaro-system update which will transition you to the new setup (it should automate the following steps).
Otherwise, edit your /etc/pacman-mirrors.conf and change (or set):
Branch = x32-stable
making sure there is no comment marker (#) at the start of the line. Then, update your mirror list, install the keyring package, and update:
pacman-mirrors -c all
pacman -Sy archlinux32-keyring-transition
pacman -S archlinux32-keyring
pacman -Syu
archlinux32-keyring-transition is signed by the Arch devs and allows you to install archlinux32-keyring which contains the keys that sign all archlinux32 packages.
archlinux32-keyring replaces archlinux32-keyring-transition.
What about package updates?
Manjaro-specific packages may lag behind x86_64 because there aren’t as many packagers. I may also trim the supported package list to save effort, depending on frequency of updates to packages and packagers who volunteer to help out. 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 spun some preview installer images:
This stable update set will form the basis for the 17.1.1 release once I work out how to do it. 
What about x32-testing and x32-unstable?
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.
The update announcement process will look something like:
| Unstable | Testing | Stable | Announcement threads |
|---|---|---|---|
| Sync | New unstable | ||
| Sync | Snap | New testing, update unstable | |
| Sync | Update unstable | ||
| … | … | ||
| Sync | Snap | New testing, update unstable | |
| … | … | … | |
| Snap | New stable, close testing and unstable | ||
| Sync | New unstable | ||
| Sync | Snap | New testing, update unstable | |
| etc. | etc. | etc. | etc. |
Full list of changes
The list of changes is once again too long to post, so is available here.
Any problems?
- 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)
0 voters
