archlinux-s390x/scripts
Mathieu Benoit 51384a64af [ADD] stage 2 is complete: 164 of 164, and it resolves, is clean, and runs
Every package in the list has been rebuilt inside the chroot by the compiler,
linker and libc it produced. The verification, run against repo2 rather than
asserted:

  RESOLVE   resolver satisfied (101 packages), --nodeps OFF
  ARTEFACT  no multiarch, no lib64, no dist-packages, no usr/local
  SONAME    every requested soname has a provider in the repository
  RUN       102 packages installed; bash 5.3.15, uname s390x, glibc 2.44,
            ls, tar, find, sed and pacman all execute

SONAME is the one that matters most. Stage 1 shipped nine sonames at the host's
version and three with no provider at all, and the whole premise of a second
stage was that rebuilding inside the result dissolves them. It did: zero of
either.

python was the last holdout and the most instructive: POSIX_SEMAPHORES_NOT_ENABLED
is now 0. It had been 1 for days because `mount --bind /dev` does not carry
submounts, so the chroot saw an empty 0755 /dev/shm, CPython's configure got
EACCES from sem_open, and _multiprocessing was compiled without SemLock -- a
package that installed cleanly, imported cleanly, and was wrong.

--- FR ---

Chaque paquet de la liste a été rebâti dans le chroot par le compilateur, le lieur
et la libc qu'il a produits. La vérification, passée sur repo2 plutôt
qu'affirmée :

  RESOLVE   résolveur satisfait (101 paquets), --nodeps éteint
  ARTEFACT  ni multiarch, ni lib64, ni dist-packages, ni usr/local
  SONAME    chaque soname demandé a un fournisseur dans le dépôt
  RUN       102 paquets installés ; bash 5.3.15, uname s390x, glibc 2.44,
            ls, tar, find, sed et pacman s'exécutent tous

SONAME est le contrôle qui compte. L'étage 1 livrait neuf sonames à la version de
l'hôte et trois sans aucun fournisseur, et toute la raison d'être d'un second
étage était que rebâtir dans le résultat les dissout. C'est fait : zéro des deux.

python fut le dernier et le plus instructif : POSIX_SEMAPHORES_NOT_ENABLED vaut
désormais 0. Il valait 1 depuis des jours parce que `mount --bind /dev` ne porte
pas les sous-montages : le chroot voyait un /dev/shm vide en 0755, le configure de
CPython recevait EACCES de sem_open, et _multiprocessing était compilé sans
SemLock — un paquet qui s'installait proprement, s'importait proprement, et était
faux.

Assisted-by: Claude Opus 5
2026-08-24 01:35:16 -04:00
..
devtools [FIX] libdir: the Debian host hid the libraries from Arch 2026-08-17 01:33:41 -04:00
bootstrap-pacman.sh [FIX] a hook's scope belongs to its sections, not to its filename 2026-08-23 17:23:30 -04:00
build-arch-kernel.sh making the house a home 2026-01-27 23:26:31 +01:00
build-busybox-zvm.sh making the house a home 2026-01-27 23:26:31 +01:00
build-container.sh making the house a home 2026-01-27 23:26:31 +01:00
build-initramfs-final.sh making the house a home 2026-01-27 23:26:31 +01:00
build-stage1.sh [FIX] stage 2: the build tools the host was providing silently 2026-08-20 01:34:41 -04:00
build-stage2.sh [FIX] rm -rf followed a bind mount into the host's /dev 2026-08-24 01:14:35 -04:00
build-systemd-zvm.sh making the house a home 2026-01-27 23:26:31 +01:00
check-private.sh [ADD] upstream.lock, and keep the machine out of the repository 2026-08-22 22:52:04 -04:00
common.sh cleaned up scripts to be more DRY 2025-06-05 20:48:16 +02:00
create-rootfs.sh making the house a home 2026-01-27 23:26:31 +01:00
deploy-and-build-systemd-zvm.sh cleaned up scripts to be more DRY 2025-06-05 20:48:16 +02:00
lib-watch.sh [FIX] stage 2: the build tools the host was providing silently 2026-08-20 01:34:41 -04:00
packages.sh [ADD] gyp for nss, and jsoncpp's doxygen output 2026-08-24 00:03:26 -04:00
prepare-boot.sh making the house a home 2026-01-27 23:26:31 +01:00
test-chroot.sh [FIX] ARTEFACT condemned two correct packages 2026-08-24 00:46:33 -04:00
test-qemu.sh cleaned up scripts to be more DRY 2025-06-05 20:48:16 +02:00
upstream-lock.sh [ADD] upstream.lock, and keep the machine out of the repository 2026-08-22 22:52:04 -04:00
upstream.lock [ADD] stage 2 is complete: 164 of 164, and it resolves, is clean, and runs 2026-08-24 01:35:16 -04:00
zvm-utils.sh cleaned up scripts to be more DRY 2025-06-05 20:48:16 +02:00