Starting a few weeks ago, the REPO_REVISIONS line in files like releases/amd64/binpackages/23.0/x86-64-v3/Packages stopped being updated when a new batch of binary packages is compiled and published to the mirrors.
On milou: 2024-11-07T16:24:48 >>> sys-apps/portage-3.0.66.1-r1: 1′22″ 2025-03-15T16:06:31 >>> sys-apps/portage-3.0.67: 34s 2025-03-28T19:39:09 >>> sys-apps/portage-3.0.67: 11s 2025-02-22T21:17:09 >>> dev-vcs/git-2.45.3: 4′55″ 2025-03-15T16:05:58 >>> dev-vcs/git-2.48.1: 33s 2025-03-28T19:37:04 >>> dev-vcs/git-2.48.1: 1′18″ 2025-03-29T17:58:32 >>> dev-vcs/git-2.49.0-r2: 19s Looking at https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64/Packages, I see: REPO_REVISIONS: {"gentoo": "36508f40390a65ca5d92409213664fc28ebd7a81"} TIMESTAMP: 1743691567 which is: commit 36508f40390a65ca5d92409213664fc28ebd7a81 Author: WANG Xuerui <xen0n@gentoo.org> Date: Thu Mar 6 15:54:44 2025 +0800 net-im/gajim: keyword 2.0.1 for ~loong, #950666 Signed-off-by: WANG Xuerui <xen0n@gentoo.org>
If it really stopped around ~6th March, neither Portage nor git seem like candidates to blame (at least not immediately obviously so).
The issue is likely that the binhost builders have a "volatile" configuration for the gentoo repo, which prevents REPO_REVISIONS from being recorded.
emerge --info has.. gentoo location: /var/db/repos/gentoo sync-type: git sync-uri: https://github.com/gentoo-mirror/gentoo.git priority: -1000 volatile: False sync-git-verify-commit-signature: yes on the host. I think we bind-mount that in. But do we need to enable history (so sync-depth & clone-depth = 0)?