so 686 it hurts… I’m an old model, you know what I mean, and I use my little RAM on the mousemat; on the mousemat, yeah, on the mousemat; and I shake a little dust on the mousemat…
Hello everyone!
I’m very happy to announce the first full availability of the continuation of i686 support within Manjaro, using archlinux32 as upstream instead of Arch, and the standard Manjaro infrastructure for package delivery.
It has been two months in the making, so without further ado here’s the first x32-stable update for anyone running the i686 architecture.
Main changes
- Lots and lots of updates
- Updated kernels 3.16, 4.1, 4.4, 4.9
- Introduced kernel 4.14
- EOL kernels dropped
- All extramodules rebuilt
-
firefox-kde
dropped -
thunderbird-kde
dropped - Deepin dropped
- Cinnamon (partly) dropped
Kernels
- linux316 - 3.16.51
- linux41 - 4.1.48
- linux44 - 4.4.108
- linux49 - 4.9.73
- linux414 - 4.14.10
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?
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.
What about installer images?
I’ll be looking into creating an Xfce installer. but have no plans to offer a full set of editions. I hope once manjaro32 is completely off-the-ground and proven the current maintainers might spin a 32-bit iso of their editions, but as this represents doubling the amount of work to prepare an edition the demand would have to be quite high to justify 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.
After this point, x32-unstable should be regarded as untested and may break at any time, so should definitely be used by people who like finding and fixing problems.
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
Wayyy too long to post, so it’s 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