A RomM row printed the served copy's sha1 under the same SHA1 it
had just declared, 313 times on the page. The note stays where the
copy is not one the row declares.
With found_by content the openMSX entries read as labels, and two of
them, COLECO.ROM and fmpac.rom, are names other profiles give another
dump. openMSX's own machine XMLs name both (ColecoVision_SGM.xml:56,
Boosted_MSX2_EN.xml:83) and try them beside the XML, so they are code
names, not labels.
POM2 v1.1.0 ships no firmware dump in any package, so the 26 Apple II files dropped in ef8b37281 return byte for byte, with the DAN ][ slot EPROM from ThorstenBr/Apple2Card. The profile is re-read at de86e8e3: bundled false on the firmware, 8 entries for the new cards, refs re-anchored. (#86)
A bulk advance moved fheroes2, supertux and supermariowar past the
revision EmuELEC compiles, and nothing stopped it: bump_commit refused
built_by only. It now leaves a profile a single registered platform ships
until it carries pin_frozen or the new pin_follows, which says that
platform builds the branch tip.
hode, bermuda, bennugd-monolithic and ccleste are held on the
PKG_VERSION of their EmuELEC v4.8 package.mk, equal to their pins.
rigelengine was one commit past it (README.md only) and goes back to
f05996f9.
In a fork's clone origin/main is the fork: once pushed it is HEAD, and
profile_sync --changed --strict checked nothing and passed while the PR's
CI then failed. The default base is now the line validate_pr.py reads:
upstream/main or origin/main when that remote is the project, the
project's main fetched otherwise.
openMSX reaches a ROM in share/systemroms through its file pool by SHA1
alone. A filename is only looked up beside the machine's XML
(src/memory/Rom.cc:121-170, HardwareConfig.cc:279-280,
FileContext.cc:152-156 at a557de7b). The labels read as names the core
opens, and the export added 15 of them to KNULLI and 2 to Batocera.
DEV9 opens eeprom.dat and flash.dat by bare name (pcsx2/DEV9/DEV9.cpp:144
at f0523f8a, AetherSX2 DEV9/flash.cpp:89, PCSX2 1.6 dev9ghzdrk/flash.cpp:73),
so the process working directory answers, never the BIOS folder. Only
yaps2 said so: the other PCSX2 profiles had the file packed into the BIOS
folder and the RetroDECK export add it there.
PCSX2 and its forks keep the first 4 to 8 MB image with a romdir in
the BIOS folder (pcsx2/ps2/BiosTools.cpp:258-282, 317-332 at f0523f8a),
and PCSX2 1.6 lists the same test in its BIOS picker
(BiosSelectorPanel.cpp:151-177). The names are labels. Without found_by
the truth model read ps2-0230a-20080220.bin as a name the core opens, and
the RetroDECK export added it as a required file.
Notes compared a core with another profile of this directory (unlike
beetle_pce, unlike the other engines in this directory), which means
nothing once a profile is read alone, and shouted NOT, ALL and MUST. The
facts stay, the comparisons and capitals go. Comparisons with a core's
own upstream remain.
The profile declared libretro/redream, which answers 404, with no pin and
no source_ref: profile_sync skipped it and the boot.bin md5 came from the
libretro docs. It now reads inolen/redream at ffb73022, the last public
tree, whose libretro core opens dc/boot.bin and dc/flash.bin in the system
directory. boot.bin is checked against four md5 and the flash against its
size, and both fall back to the high level BIOS, so neither is required.
needs_review counts an orphaned pin and a moved repository, but the
triage line only added stale prose and unchecked refs, so pcem read
"1 to review" for an upstream_commit outside its branch history.
idtech4a++ cites xash3d-fwgs filesystem/filesystem.c, starship and
ghostship Torch src/Companion.cpp: files of submodules of the declared
repository. No blob of the declared tree answers, so the parts stayed
external and a bump moved the submodule commit with nothing checked.
A project word now also resolves to the one submodule named after it,
and a file under a submodule is read in the repository .gitmodules
names, at the commit the declared revision pins it to.
The integrity check let a platform file the frontend's hash refuses
hold its path, so the core file the builder ships there was never
compared (finding 3).
core_version went null although doc/CHANGES.html at the pin opens on
Version 0.16.0. ti99sim cites v0.16.0 and v0.0.11 parts side by side,
and with no documented version every part read as another program:
profile_sync reported 6 external, 0 to review, nothing checked. The v0.16.0
parts are anchored at the pin again, the v0.0.11 parts stay external.
XRoar reads the Dragon 200-E and Alice ROMs for those machine configs
(src/xroar.c:437-444, 552-558 at 1.12.1), and VICE the Japanese kernal
and chargen for the C64 JAP and VIC-1001 models: a (Japan) file name
selects the NTSC model (libretro-core.c:2018-2034). No code branches on a
territory for these files, so region: is removed, as profiling.md rules
for a model enum.
A keep line gave every emulator the file of the first profile claim:
Recalbox's neocdz.zip line said geolith reads the archive fbneo reads.
The JSON 'expected' lists each file with its emulators (finding 4).
install.py took --list-platforms, generate_pack.py --list and verify.py
nothing. Both tools now take --list-platforms and print the same list
from common.py. generate_pack.py keeps --list (finding 80).
Abdessamad Derraz
VERHILLE Arnaud