``` >>> Running pre-merge checks for sys-apps/portage-3.0.65-r1 --2024-07-19 08:13:40-- https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/23.0/x86-64/sys-apps/portage/portage-3.0.65-r1-1.gpkg.tar Resolving mirror.bytemark.co.uk... 2001:41c8:20:5fc::13, 2001:41c8:20:5e6::150, 212.110.163.13, ... Connecting to mirror.bytemark.co.uk|2001:41c8:20:5fc::13|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2024-07-19 08:13:41 ERROR 404: Not Found. ``` But the Packages index _does_ have it: ``` $ wget -q https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/23.0/x86-64/Packages -O- | grep CPV.*sys-apps/portage -C 5 REPO: gentoo BDEPEND: dev-lang/python:3.12[bzip2(+),threads(+)] >=app-arch/tar-1.27 >=dev-build/meson-1.2.1-r1 || ( >=dev-build/meson-1.3.0-r1 <dev-build/meson-1.3.0 ) dev-python/setuptools[python_targets_python3_12(-)] >=sys-apps/sed-4.0.5 sys-devel/patch dev-lang/python:3.12[ssl(+)] >=dev-build/meson-1.2.3 app-alternatives/ninja dev-build/meson-format-array BUILD_ID: 1 BUILD_TIME: 1720343550 CPV: sys-apps/portage-3.0.65-r1 DEFINED_PHASES: compile configure install postinst preinst prepare pretend setup test EAPI: 7 IUSE: apidoc build doc gentoo-dev +ipc +native-extensions +rsync-verify selinux test xattr python_targets_pypy3 python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 KEYWORDS: ~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 LICENSE: GPL-2 ``` I think this might be distinct from bug 936288 (which I intended to be for bouncer/the gentoo infra CDN) and is instead either an issue in our binpkg syncing scripts or eclean-pkg/emaint binhost doing something wrong?
(I'm assuming here that bytemark is just one mirror and it's internally consistent.)
What I find really suspicious is, https://mirror.bytemark.co.uk/gentoo/releases/amd64/binpackages/23.0/x86-64/sys-apps/ has no portage *at all*. So it can't even really be just a delay -- it has to be the upload script going wrong, or eclean-pkg going wrong.
Nope: bytemark's mirror is misconfigured. It's excluding every directory named exactly "portage" in the ::gentoo mirror! I compared it with a listing from another mirror - it applies to every binpackage profile
(In reply to Robin Johnson from comment #3) Thank you for investigating!
No response from sponsor so far
As implied by bug 936287 comment 4, a useful mitigation is to set frozen = true in binrepos.conf just before you begin the bulk of your dependency calculations, but after a recent copy of the Packages index has been downloaded to /var/cache/edb/binhost/ using a command like `emerge -pG --nodeps portage`.
