crosvm - Debian Package Tracker

action needed

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit f360b5b3224daec1716a08c1017e608f5798464a
Author: Yunseong Kim <yunseong.kim@est.tech>
Date:   Tue Oct 20 15:06:28 2026 +0200

    Add Debian packaging
    
    Package crosvm for Debian (ITP #1026126), Linux/KVM hypervisor built with
    --no-default-features --features qcow,balloon,net,usb,audio.
    
    Source:
     - The upstream git history is used unmodified; this commit only adds
       debian/. The orig tarball is a +ds repack of upstream c917be82d that
       leaves out hypervisor/src/whpx/whpx_sys/WinHv*.h (Files-Excluded):
       Microsoft headers with no licence grant, Windows-only. It is made
       with mk-origtargz and stored with pristine-tar; dpkg-source ignores
       the three files in the packaging tree.
     - The git submodules are empty in the tarball and nothing is taken from
       them.
    
    Build:
     - Built with the Debian cargo wrapper against the system crate
       registry; every direct crate dependency is in Build-Depends.
     - minijail comes from src:minijail, 2026.05.18+git20261016.8787d1a-2
       or later: libminijail-dev, librust-minijail-dev (the Rust crates,
       which are not on crates.io) and python3-minijail
       (compile_seccomp_policy, run by jail/build.rs to compile the seccomp
       policies).
     - crosvm makes no releases, so watch HEAD in git mode and name snapshots
       0.1.0~git<date>.<hash>, as debian/changelog does. Clone in full, since a
       shallow clone abbreviates the hash to 7 characters. Repack with
       Files-Excluded (+ds); the result is bit-identical to the git archive +
       mk-origtargz procedure in README.source, which now documents both.
     - Patches: trim the workspace to what the Debian feature set uses
       (generated by debian/trim-workspace.py), move libc, rand, lz4_flex,
       indexmap and which to the versions in unstable, and drop upstream's
       [patch.crates-io] override so minijail comes from the registry.
     - Install the seccomp policy sources under /usr/share/policy/crosvm and
       a crosvm(1) manual page; fill Built-Using/Static-Built-Using.
    
    Salsa CI is configured in debian/salsa-ci.yml; i386 is disabled.
    
    Signed-off-by: Yunseong Kim <yunseong.kim@est.tech>

Created: 2026-11-02 Last update: 2026-11-02 21:01

testing migrations

excuses:
- Migration status for crosvm (- to 0.1.0~git20261022.c917be82d+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ crosvm has no binaries on any arch
- ∙ ∙ Autopkgtest deferred: missing builds
- ∙ ∙ Lintian check deferred: missing builds
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts can't test crosvm (not a blocker) - (no link yet)
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[2026-11-02] Accepted crosvm 0.1.0~git20261022.c917be82d+ds-1 (source amd64) into unstable (Debian FTP Masters) (signed by: Ying-Chun Liu)