Repository navigation
Corresponding-source records for first-party Windows full CI build 37085543729 #18648
Unanswered
asrulnasirudin
asked this question in
Q&A
Replies: 2 comments 1 reply
|
All the information is there, like I said in another AI question, there is no summary currently. Patches welcome. Otherwise you can track things from logs and repo states like https://github.com/BtbN/FFmpeg-Builds. I won't do the work for you, sorry. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Hello,
Where can I obtain the complete corresponding-source and dependency/build records for this first-party Windows CI full mpv package?
mingw64-full (win64, gpl), ID111094948460mpv-v0.41.0-dev-g413ff0b1c-37085543729-x86_64-w64-mingw32-full.zip112612253713e492e47bfea0761924b7c6cc5509320fdb73a26f6c9e5590bac13dd6cd53997mpv.exeSHA-256:db36261c4ee2835a6e886f8ed154350228cba5c46622dab1a873c6e76b629b93413ff0b1cd4585294803308a1a14be2fad30cedegit-2026-10-02-98e9256; libplacebo:v7.374.0We are assessing redistribution with a Windows application and have retained the mpv source snapshot, GPL text and original CI log. We still need the matching statically linked dependency sources, applicable notices, local patches and relevant build material, rather than today's dependency checkouts.
The log records pulling
ghcr.io/btbn/ffmpeg-builds/win64-gpl:latestwith digest:The public registry currently returns HTTP 404 /
MANIFEST_UNKNOWNfor that digest, while the currentlatestmanifest is accessible. The recipe also makes shallow FFmpeg/LuaJIT/dependency checkouts; we do not assume current branch heads match the historical binary.Is there an archived corresponding-source bundle, build-time dependency manifest/download cache, or a documented way to obtain the matching material for this exact artifact? If another maintainer owns the container records, a pointer would help.
Thank you.
All reactions