2018-06-07 - pacman 5.1, kernels, Chromium, Qt5 [Stable Update i686]

Frische News und Updates zu Manjaro Linux finden sich zeitnah hier ein!
Antworten
Benutzeravatar

Themen Author
Blueriver
Moderator
Moderator
Beiträge: 2343
Registriert: Donnerstag 19. Mai 2016, 15:49
CPU: AMD Quad Core A8 3,6GHz
GPU: AMD/ATI Radeon R7
Kernel: 6.1
Desktop-Variante: XFCE und KDE Stable, Testing, Unstable
GPU Treiber: Free
Hat sich bedankt: 28 Mal
Danksagung erhalten: 149 Mal

2018-06-07 - pacman 5.1, kernels, Chromium, Qt5 [Stable Update i686]

#1

Beitrag von Blueriver »


Hello i686ers!
This update set introduces pacman 5.1. All other package management tools should now be rebuilt and work with the new library version.

There’s an update to archlinux32-keyring. Please update that first to ensure the rest of the packages validate correctly.

There are plenty of updates for other software. Good news is that Chromium builds again on i686 without any changes from the Arch PKGBUILD, so we should get more regular builds now.

There’s the normal set of Haskell, Perl, and Python module updates.

Also, kernels.

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
linux316 3.16.56
linux41 4.1.51
linux44 4.4.135
linux49 4.9.105
linux414 4.14.47

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:

Using manjaro32 and spotted an out-of-date Manjaro package? First, check the Manjaro GitHub sources for core, extra, and community. If it’s in the GitHub sources, it’s a Manjaro package. You can check whether the package is in the archlinux32 repos directly: https://mirror.archlinux32.org/i686/ Alternatively, check the Arch package list to see whether the package is one likely to be built by archlinux32. If it’s a Manjaro package, and it’s out-of-date, report here.
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:

https://forum.manjaro.org/clicks/track? ... c_id=49198


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.

Full list of changes
Full list is available here.
Quelle
Manjaro LXQT und XFCE Stable, Testing, Unstable
CPU: AMD Quad Core A8 3,6GHz
Graka: AMD/ATI Radeon R7
Treiber: Free
Kernel: 4.20
Antworten