[Stable Update i686] 2019-06-16 - Chromium, Thunderbird, Palemoon, Kernels

Hello i686ers!

This is another small update set which brings in updates and fixes for Chromium, Thunderbird, and Palemoon.

Also, kernels.

Note that kernel 3.18 is now actually EOL and won't be receiving any further updates. Please switch to another kernel if you're still running on 3.18. It will be removed from the repos "soon" in the next stable set.


Available kernels

Series Version PAE
linux316 3.16.68 No
linux318 3.18.140 EOL No
linux44 4.4.181 No
linux49 4.9.181 No
linux414 4.14.125 No
linux419 4.19.51 Yes

Full list of changes

The full list is available here. ~200 updated packages.


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:

https://bbs.archlinux32.org/viewtopic.php?id=171

(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)


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.

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?

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 the adventurous who want 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. However: expect breakage.


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


2 Likes

Known issues and solutions


signature from "Erich Eckner (just to sign arch packages) <arch@eckner.net>" is marginal trust

Either follow Issues with "signature is marginal trust" or "invalid or corrupted package" replacing "archlinux" with "archlinux32", or more trivially:

sudo pacman -U /var/cache/pacman/pkg/archlinux32-keyring-20190108-1.0-any.pkg.tar.xz

Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version)

This happens every so often when there's a kernel ABI change. As far as I know it's harmless and can be ignored.


Perfect. Thanks jonathon. :+1:

1 Like

Perfect, no forget of make a ranking mirrors.

sudo pacman-mirrors -g

Thanks @jonathon!

The following should be added to the known issues again:


Incompatible libdevmapper 1.02.156 (2019-03-22) and kernel driver (unknown version)

This happens every so often when there's a kernel ABI change. As far as I know it's harmless and can be ignored.


1 Like