Hi, Apologies for the gap in communication here. I have been in the middle of an intercontinental move and am only now catching up on all the packaging channels. The Salsa repo has seen a lot of work since Tobias's review, and I wanted to give a proper update rather than piecemeal replies.
All three items from Tobias's review have been addressed, along with feedback from Fabio Fantoni on Salsa and several CI issues discovered along the way: Salsa repo: https://salsa.debian.org/glamberson/lamco-rdp-server Latest CI pipeline: https://salsa.debian.org/glamberson/lamco-rdp-server/-/pipelines/1030254 Changes since 1.3.1-2: 1. d/copyright: fully regenerated as machine-readable DEP-5 with per-crate license and copyright enumeration (630 lines). BUSL-1.1 text included verbatim. 466 vendor paths corrected to match actual Cargo vendor directory layout. 2. FTBFS fix: d/rules clears vendor checksums before build, handling dpkg-source .orig file removal. 3. FTBFS fix: quilt patch for cros-libva VP9 struct compatibility with libva >= 2.22 (Debian sid ships 2.22). Adds ..Default::default() to handle new VAEncPictureParameterBufferVP9 fields. 4. d/changelog squashed to single 1.3.1-1 entry per Fabio Fantoni's guidance. Premature tags removed from Salsa. 5. Salsa CI pipeline fully configured: build, lintian, wrap-and-sort, piuparts all passing. blhc disabled (standard for Rust/cargo packages that don't expose gcc command lines). Lintian false positives for vendored test artifacts suppressed. 6. Build resource optimization: d/rules now uses thin LTO instead of fat (via CARGO_PROFILE_RELEASE_LTO=thin). Reduces peak memory from ~10GB to ~4GB and build time from ~55min to ~30min, with no effect on features or capabilities. This is the same approach Firefox and Chromium use for distro builds. 7. Standards-Version bumped to 4.7.3. The vendoring question raised by Tobias: I emailed [email protected] on Feb 16 asking for guidance, but haven't received a response. The package vendors 883 crates (including git fork dependencies that aren't on crates.io), so the standard debcargo workflow doesn't apply directly. Happy to discuss alternative approaches if the Rust team has suggestions. I'm actively looking for a sponsor comfortable with Rust packaging. Tobias kindly declined due to language unfamiliarity. I've reached out to Mike Gabriel (debian-remote-team) but haven't heard back. If anyone on this list knows a DD with Rust experience who might be willing to review, I'd appreciate the pointer. The package is ready for review on Salsa with CI green. I'll upload an updated source package to mentors once I have a sponsor lined up. Regards, Greg Lamberson
