[Stable Update i686] 2019-01-25 - The Pretty Much Everything™ 2 Update

update
stable
manjaro32

#1

Hello i686ers!

This is another massive update. There were a lot of issues identified during its time in x32-testing which are, as far as I can tell, all now resolved. I don’t like this sort of time period between updates, but sometimes… :man_shrugging:

There is no single highlight of this set. With about 4900 updated packages almost everything is updated. Again.

As with the last update of this size,

I recommend that you:

  1. Make a backup before performing this update
  2. Prepare a boot medium in case you need to chroot in
  3. Make absolutely certain your mirror is up to date
  4. Make sure you’re on AC power
  5. Run the update from a text console using pacman -Syu

Take it slowly, and good luck. :slight_smile:


Full list of changes

Is once again massive, so is available here.


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)


Available kernels

Series Version PAE
linux316 3.16.62 No
linux318 3.18.133 No
linux44 4.4.166 No
linux49 4.9.151 No
linux414 4.14.94 No
linux419 4.19.16 Yes

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?

There’s a “new” image here:

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.


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



[Testing Update i686] 2018-12-19 to 2019-01-25 - Systemd, Kernels, LibreOffice Fresh, Readline, Firefox
[Testing Update] 2019-02-10 - KDE Apps, Gambas, Qt5, VirtualBox, LibreOffice, Wine, Firefox
#2

Known issues and solutions

This is a wiki post; please edit as necessary.


I want a new installer image

Keep your hair on. I’ll create one this coming week Go here:



#3

Updated my system a couple of hours by following the intructions and everything went smoothly


#4

Is there a valid current i686 ISO to do this with?

I’ve tried using the older manjaro-kde-17.0.6-stable-i686 to chroot with, which afaik was the last one built before i686 was officially dropped.

Being a very old package base, with an old version of pacman, I think it corrupted my pacman database, multiple times.


#5

Once again, no problems :slight_smile:


#6

There’s an 18.0.0 image linked in the OP. That should work OK.


#7

no problems


#8

Thanks I was hunting around OSDN looking for a KDE image … tl’dr on the image OP link unfortunately … :blush:


#9

How safe it is to do this last update now on the testing branch? Is there any risk if I am using linux414 (I did not understood that table of the available kernels)?


#10

that kernel is still supported so it’s as safe as any other update. this is not a testing branch announcement though so you should check the latest announcement for that unless you want to change from testing to stable.


#11

Update on 1 System without Problems.
1 VB Freezed during Update but can fix it.

DK3


#12

I have two vbox VMs using the testing branch, both updated without issue.

As always though if you are not confident take a backup first, better to have it and not need it than … you know.


#13

No gui start, just blinking cursor. Satellite A135-S4427 with Intel T2250. Tried downgrading mate-desktop, xorg-server. Don’t know how to troubleshoot.


#14

Read this thread:

then start a new thread.


#15

Probably its the same issue which left unresolved on testing branch.

Please check the journalctl of your faulty boot (journalctl -b-1 for previous boot) and refer there which causes this blank screen.

One possible solution is to disable plymouth and see how your system boots then.

PS. Mine blank screen problem was gone after last full upgrade today on testing branch. So probably you will need to wait until this solution reaches to stable branch.


#16