Arch Linux

sneakernets

Member

Registered: 2023-05-12

Posts: 2

The Big Rebuild Saga

Hello all,

I've been noticing that there is a lot of issues and footguns when innocently running Pacman -S in the past month. I understand there's a giant problem with backlogged packages waiting to be built, and some packages being misconfigured. Some examples that I ran into over the past 6 weeks:

python 3.11.3-2.0 : Has a LOT of issues with python module packages, too many to list. I had to roll back all my python related packages to the version prior that was thankfully, still in cache (3.10). This also included any modules.

sdl2 2.28.0-1.0 : Doesn't work at all, any invocation of the library crashes with illegal instruction. I had to roll back to 2.26. I attempted to build sdl2-git from the AUR, only to find that the same issue popped up, so it's likely a code/build change.

icu : Many, many problems, thankfully worked around by installing a versioned shim. Trying to pull up the icu package in the database causes an HTTP 500.

sweethome3d 7.1-2.0 : Doesn't work. Checked the logs, and the program hangs on locating 64-bit java packages, instead of the native 32-bit ones. I wonder if this ever worked?

firefox 114.0.2-1.0 : Many unexplainable WASM hangs. I believe FF's implementation requires SIMD extensions, and fixed-width SIMD seems to be disabled for all arches. But this should work fine on pentium4 builds, correct? This might be a firefox bug.

So I ask: Should we still be upgrading packages, or should we wait until things clear up on the build side? As it stands, I don't think a fresh from ISO install would be working properly!

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 990

Website

Re: The Big Rebuild Saga

About icu, this works quite nicely:

pacman -Rd --nodeps icu
pacman -Syy icu icu72
pacman -Syyu

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 990

Website

Re: The Big Rebuild Saga

About the rebuild. It does not work as planned. Tons of things are stuck, most notably python.
The build system is not made for doing manual packages, get-package-updates in a fast way, I'm afraid, I
cannot bootstrap python in the current state.

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 990

Website

Re: The Big Rebuild Saga

/var/cache/pacman/pkg/alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zsterror: alsa-ucm-conf: signature from "Andreas Baumann (sign) <mail@andreasbaumann.cc>" is invalid
:: File /var/cache/pacman/pkg/alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

This is also annoying, now keys are failing again.

One nice way would be to have something to resign all packages. I'm not confident we can rebuild all of them.

ITzTravelInTime

Member

Registered: 2023-07-14

Posts: 2

Re: The Big Rebuild Saga

Any news on this?

I have been trying to get a desktop environemt working on my athlon xp but i culdn't because anyone of those has 'alsa-ucm-conf-1.2.9-1.0-any.pkg' as a dependancy and that's so annoying.

UPDATE: i managed to go forward by installing the yay aur helper and then installing the git versin of `alsa-ucm-conf` that allowed me to get some DEs installed.

Last edited by ITzTravelInTime (2023-07-14 06:05:03)

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 990

Website

Re: The Big Rebuild Saga

The alsa-ucm-conf package is quite new:

-rw-r--r-- 1 http mirror 78288 May 14 18:34 alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst
-rw-r--r-- 1 http mirror   310 May 14 18:34 alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst.sig

The keyring was recently updated.

My PGP says:

pub   rsa2048 2017-11-02 [SC] [expires: 2024-01-29]
      16194A82231E9EF823562181C8E8F5A0AF9BA7E7
uid           [ultimate] Andreas Baumann (sign) <mail@andreasbaumann.cc>
sub   rsa2048 2017-11-02 [E] [expires: 2024-01-29]

So, I don't quite get, why the key is deeme expired by pacman.

BTW. Just disabling the package sign check mechanism (SigLevel=Never) is easier than to rebuild the software (which might not work).

ITzTravelInTime

Member

Registered: 2023-07-14

Posts: 2

Re: The Big Rebuild Saga

After disabling the signing check and attempting a reinstall of the library there is a checksum fail, which is also why the signing error might have appen, simply the repositories might have a corrupt package, so for now i have to go with the git versin compiled from aur i guess

abaumann

Administrator

From: Zurich

Registered: 2019-11-14

Posts: 990

Website

Re: The Big Rebuild Saga

Indeed, thanks spotting that one, it's a wrong checksum:

:: File /var/cache/pacman/pkg/alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
debug: found cached pkg: /var/cache/pacman/pkg/alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst
debug: sha256sum: 4919fcfb5003886aa8036024f07335d282595759bb3b2fff04996c386d762ea1
debug: checking sha256sum for /var/cache/pacman/pkg/alsa-ucm-conf-1.2.9-1.0-any.pkg.tar.zst
debug: returning error 36 from _alpm_pkg_validate_internal (../lib/libalpm/be_package.c: 329) : invalid or corrupted package (checksum)

So this means the sha256 checksum in the package and in the database file don't match. I recreated
that with repo-remove, repo-add now for this file, but this means something is out of sync when updating
repos.. This sort of reminds of the incident, when 50 packages were just left in 'pool' and the package
files and the database not up-to-date (those I moved to archive).