No description
Mathieu Benoit
3d2a1485af
python-packaging's PKGBUILD says pkgver=26.3 and the installed module reported 25.0. The vendored builder selected by _bootstrap=1 carries its OWN copy of each project, older than the release the PKGBUILD names. Nothing about the package looked wrong; only `packaging.__version__` disagreed with its own name, and the mismatch surfaced two packages later: python-vcs-versioning: packaging>=26.2 a floor our own package met on paper and not in fact. _bootstrap is now a probe evaluated by makepkg, in the build environment: if `build` and `installer` import, the real path works and the vendored copies are not wanted. A hook could not decide this -- hooks run on the HOST even for stage 2, so a probe written there cannot answer for the chroot. The license install then had to handle both layouts, since the source tree is a git clone under $pkgname when bootstrapping and a release tarball otherwise. Hardcoding either breaks the other, and this hook had hardcoded the clone -- right only while _bootstrap was always 1. --- FR --- Le PKGBUILD de python-packaging annonce pkgver=26.3 et le module installé rapportait 25.0. Le constructeur embarqué que sélectionne _bootstrap=1 porte ses PROPRES copies de chaque projet, plus anciennes que la version nommée. Rien dans le paquet n'avait l'air faux ; seul `packaging.__version__` contredisait son propre nom, et l'écart est apparu deux paquets plus loin : python-vcs-versioning: packaging>=26.2 un plancher que notre paquet satisfaisait sur le papier et non en fait. _bootstrap est désormais une sonde évaluée par makepkg, dans l'environnement de construction : si `build` et `installer` s'importent, la voie normale fonctionne et les copies embarquées ne sont pas voulues. Un hook ne pouvait pas trancher — les hooks tournent sur l'HÔTE même pour l'étage 2, donc une sonde écrite là ne peut pas répondre pour le chroot. L'installation de la licence devait alors gérer les deux dispositions, l'arbre source étant un clone git sous $pkgname en mode bootstrap et une archive sinon. Écrire l'une en dur casse l'autre, et ce hook avait écrit le clone en dur — juste seulement tant que _bootstrap valait toujours 1. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .github/workflows | ||
| arch-kernel | ||
| boot | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| CODEOWNERS | ||
| Containerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| RELAIS.md | ||
| TODO.md | ||
Arch Linux s390x
A port of Arch Linux to IBM s390x mainframe architecture with systemd support.
Boots a full Arch Linux system on IBM mainframes (or QEMU s390x emulation) using a hybrid build: cross-compilation for the kernel, native s390x compilation on z/VM for userspace.
Quick Start
make container # build dev container (first time)
cp .env.example .env # configure z/VM access
make all # build kernel + initramfs + systemd
make test-systemd # boot it
What Works
- Arch Linux kernel 6.18.6-arch1 with Arch patches, cross-compiled
- Initramfs via modified mkinitcpio
- Static busybox built natively on z/VM, 2.3MB
- Root filesystem with ext4, switch_root to real rootfs
- Systemd as PID 1
Pacman, bash, and GNU coreutils are not yet ported.
Build System
The build uses two tiers:
Cross-compilation (x86_64 host): Kernel is built in a Fedora 43 container with s390x-linux-gnu-gcc. Initramfs is generated with a patched mkinitcpio that handles cross-architecture binary injection.
Native compilation (s390x z/VM): Busybox and systemd must be built on real s390x hardware. The z/VM system runs RHEL 9.6 with GCC 11.5.0. Scripts handle SSH deployment and retrieval automatically via .env configuration.