Mathieu Benoit
09aa24c46a
python-build, python-wheel and python-pyproject-hooks were built on the host, reported OK, and installed everything under usr/lib/python3/dist-packages -- Debian's name for site-packages. Our python 3.14 never looks there, so every module in them was unreachable. Nothing about them looked wrong. Their package() computes install paths from the RUNNING python: local site_packages=$(python -c "import site; print(site.getsitepackages()[0])") rm "$pkgdir/$site_packages/$_name"/*.exe which is why the other three in the same batch FAILED -- on `rm` finding nothing. Those failures were protective. All six are built by stage 2 now, where python is ours; a stage-1 run is expected to report them as failed, like libxslt. The ARTEFACT check said the repository was clean throughout, truthfully: it only ever asked about C library directories. It now also counts dist-packages and usr/local paths, so the next time this happens it says so. --- FR --- python-build, python-wheel et python-pyproject-hooks ont été bâtis sur l'hôte, déclarés OK, et ont tout installé sous usr/lib/python3/dist-packages — le nom Debian de site-packages. Notre python 3.14 n'y regarde jamais : chaque module était inatteignable. Rien en eux n'avait l'air faux. Leur package() calcule les chemins depuis le python COURANT : local site_packages=$(python -c "import site; print(site.getsitepackages()[0])") rm "$pkgdir/$site_packages/$_name"/*.exe d'où l'échec des trois autres du même lot — sur un `rm` qui ne trouvait rien. Ces échecs étaient protecteurs. Les six sont désormais bâtis par l'étage 2, où le python est le nôtre ; une passe d'étage 1 doit les déclarer en échec, comme libxslt. Le test ARTEFACT affirmait un dépôt propre, véridiquement : il n'interrogeait que les répertoires de bibliothèques C. Il compte maintenant aussi dist-packages et usr/local, pour le dire la prochaine fois. Assisted-by: Claude Opus 5
32 lines
1.5 KiB
Bash
Executable file
32 lines
1.5 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
# One of the six packages in the Python packaging cycle. The reasoning, and the
|
|
# edit, are shared -- see lib-python-bootstrap.sh.
|
|
set -euo pipefail
|
|
source "$(dirname "$0")/lib-python-bootstrap.sh"
|
|
|
|
# The license install assumes the NON-bootstrap layout, unconditionally.
|
|
#
|
|
# install -vDm644 -t "$pkgdir/usr/share/licenses/$pkgname" \
|
|
# $srcdir/$_name-$pkgver/LICENSE*
|
|
#
|
|
# sits outside the `if (( _bootstrap == 0 ))`, but with _bootstrap=1 the source
|
|
# array is a set of git clones and there is no packaging-26.3 directory at all:
|
|
#
|
|
# install: cannot stat '.../src/packaging-26.3/LICENSE*'
|
|
#
|
|
# The clone is at $srcdir/python-packaging, and it carries LICENSE,
|
|
# LICENSE.APACHE and LICENSE.BSD. The other five PKGBUILDs handle this by
|
|
# naming a bootstrap-specific path in their else branch; this one just misses
|
|
# it, so the fix follows their shape rather than inventing one.
|
|
python3 - <<'ZZPY'
|
|
import io, re
|
|
lines = io.open("PKGBUILD", encoding="utf-8").read().split("\n")
|
|
hit = [i for i, l in enumerate(lines) if "LICENSE*" in l and "$_name-$pkgver" in l]
|
|
assert len(hit) == 1, "python-packaging: expected one license install, got %d" % len(hit)
|
|
lines[hit[0]] = lines[hit[0]].replace("$srcdir/$_name-$pkgver/LICENSE*",
|
|
"$srcdir/$pkgname/LICENSE*")
|
|
io.open("PKGBUILD", "w", encoding="utf-8").write("\n".join(lines))
|
|
ZZPY
|
|
grep -q 'srcdir/\$pkgname/LICENSE\*' PKGBUILD || {
|
|
echo "python-packaging: the license path was not redirected" >&2; exit 1; }
|
|
echo "python-packaging: license taken from the bootstrap clone"
|