pin_frozen was prose, and no tool read the build file it cites, so a platform building another revision left the profile holding one nobody ships. pin_build records the platform, its repository, the revision read, the file, the variable and its value. check_freshness reads the file again where the platform's YAML now stands and reports STALE when the value moved. 36 of the 46 held profiles carry it, each value read from the build file at the platform's scraped revision. The other ten name no build file and are counted on one row: six RetroBat binary packages and four holds not tied to a platform build.
Each standalone profile records where its version is read: the source
at its pin (clk 2026-07-23-136-g9020107, shadps4 0.20.1 WIP, eden
v0.2.0-401-g26a03d2), the APK, binary or archive read (kind package),
or, where no reading can be made, kind unverified with the reason: a
host the tools cannot read, a forge gone or not answering, no build
recorded as read, a pin on another branch. Those keep their value,
unconfirmed.
The buildbot's azahar_libretro is built from azahar-emu/azahar: the
2026-10-22 nightly carries g_scm_rev f570b53f (master, 2026-10-16) and
the key blob of src/core/hw/default_keys.h byte for byte. The profile
now reads that repository at tag 2126.2, whose file-loading code matches
f570b53f apart from licence headers.
The libretro core keeps its user directory under <save_dir>/Azahar/,
falling back to <system_dir>/Azahar/, so path: carries the Azahar/
prefix and standalone_path: the user directory layout. The embedded
keys.txt is the 2126.2 blob (sha1 5288772b). azahar-sa is ROCKNIX's
name for the same standalone.
KNULLI builds the SDL2 frontend of johndoe6345789/azahar_libretro at
c8d39853 as its azahar binary, so that fork moves to azahar-sdl.yml
with built_by: [knulli].
Abdessamad Derraz