<p>Hello VideoLAN developers,</p>
<p>I maintain Random Multimedia Manager, an open-source Windows desktop application using LibVLCSharp and VideoLAN.LibVLC.Windows 3.0.23.1. We are reviewing the exact bundled binaries and corresponding source/build materials before publishing an end-user package.</p>
<p>Could you point us to the source/build materials used for VLC 3.0.23-2, commit <code>79128878ddb2c280bbb6c89c76a46b31a80ade1c</code>, particularly project 435 pipeline 674296 and Windows release jobs 2403066/2403067/2403068?</p>
<ul>
<li>Selected contrib versions/source archive checksums, applied patches, and the configuration/link inputs and scripts needed to build/install the shipped components, including any linked runtime license exceptions.</li>
<li>The source changes and build options corresponding to the shipped libbluray 1.4.0 Java JARs and compiled Lua files. We have inventoried the JAR classes and Lua headers against the retained upstream sources, but do not treat name/header matches as proof of source equivalence.</li>
<li>Where the applicable copyright/license notices for shipped support artwork/web resources and Java sources without individual headers can be found.</li>
</ul>
<p>During our earlier check, public release-job trace requests returned 401 and the win64 artifact returned 404. We have retained the revision-matched VLC source, contrib recipes/patches, libbluray source, and available original notices; pointers to existing corresponding materials would be welcome.</p>
<p>Our file-level hashes and review findings are available here:<br>
<a href="https://github.com/danhk0612/Random_Multimedia_Manager/blob/4c9ad0f769081c199001900f751387b9d4cc7b89/packaging/release-readiness/README.md">Review summary and remaining questions</a><br>
<a href="https://github.com/danhk0612/Random_Multimedia_Manager/blob/4c9ad0f769081c199001900f751387b9d4cc7b89/packaging/release-readiness/native-inventory.csv">Per-file SHA256 inventory</a></p>
<p>The review also records GPL FFmpeg strings/configuration in six avcodec/swscale plugin binaries across the three bundled architectures. We are checking the actual components rather than relying solely on NuGet metadata. This is a request for technical source/build provenance and notice locations, not a request to change licenses or provide a replacement bundle, and not an allegation of noncompliance.</p>
<p>If this belongs with the NuGet packaging maintainers or another contact, please direct us to the appropriate channel.</p>
<p>Thank you,<br>HAEKWANG DAN<br>danhk0612 / Random Multimedia Manager</p>