You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have spec files written for RPM packages for Fedora and openSUSE, and there's community support for Arch in AUR, but we don't have anything for the .deb ecosystem for Debian/Ubuntu
It would be great if we could get this working for that ecosystem. We need to get it done before the Ubuntu feature freeze in February if we want to make it into the next release.
The released packages would probably wind up being built in openSUSE Build Service next to our other packages, but creating the package definition would be very helpful as starting point.
Some open questions:
We will need the build to support vendoring. Our build system does that already, but I don't know how different build systems integrate that for deb files.
I also don't know if there's any other rules we need to follow to get into the Debian or Ubuntu repositories.
My plan is to start from the existing spec files in the OBS project and write a debian/ package definition that builds offline from the vendored crates (the dist-vendor.sh tarball), so it can be built on OBS next to the RPMs. I'll test-build it with sbuild against current Debian unstable and Ubuntu, and open a PR with what I find on the open questions (vendoring and Debian/Ubuntu archive rules).
I've opened #272 with packaging in distrib/debian/. It builds from the vendored meson dist tarball, which works for OBS but not for the Debian archive.
For the archive, every crate has to be packaged as librust-*-dev. Here is where Cargo.lock stands against Debian sid. In total there are 388 crates: 336 are in sid at a compatible version, 31 only at an incompatible version, and 21 aren't packaged at all.
Most of the missing crates belong to libwebauthn's stack (CTAP types, BlueZ, NFC). The incompatible ones are mostly older versions pulled in by dependencies, which bumps on our side or in libwebauthn could fix.
So the archive route needs, roughly:
packaging the 21 missing crates through the Debian Rust team (debcargo);
moving the incompatible ones to the versions in sid where we can;
an ITP bug, and a sponsor for the uploads.
Until then, OBS Debian/Ubuntu targets can use the vendored build in #272.
Activity
kpanuragh commentedon Nov 13, 2026
I'd like to take this one.
My plan is to start from the existing spec files in the OBS project and write a
debian/package definition that builds offline from the vendored crates (thedist-vendor.shtarball), so it can be built on OBS next to the RPMs. I'll test-build it withsbuildagainst current Debian unstable and Ubuntu, and open a PR with what I find on the open questions (vendoring and Debian/Ubuntu archive rules).kpanuragh commentedon Nov 14, 2026
I've opened #272 with packaging in
distrib/debian/. It builds from the vendoredmeson disttarball, which works for OBS but not for the Debian archive.For the archive, every crate has to be packaged as
librust-*-dev. Here is whereCargo.lockstands against Debian sid. In total there are 388 crates: 336 are in sid at a compatible version, 31 only at an incompatible version, and 21 aren't packaged at all.Not in Debian (21)
apdu 0.4.0, apdu-core 0.4.0, apdu-derive 0.4.0, bluer 0.17.4, bluez-async 0.8.2, bluez-generated 0.4.0, btleplug 0.11.8, cbor-smol 0.5.1, cosey 0.4.0, ctap-types 0.5.0, dbus-tokio 0.7.6, delog 0.1.8, heapless-bytes 0.5.0, iso7816 0.2.2, libwebauthn 0.11.0, nfc1 0.7.1, nfc1-sys 0.3.13, pxp 0.1.0, serde-indexed 0.1.1 and 0.2.0, text_io 0.1.13
Debian has an incompatible version (31)
Most of the missing crates belong to libwebauthn's stack (CTAP types, BlueZ, NFC). The incompatible ones are mostly older versions pulled in by dependencies, which bumps on our side or in libwebauthn could fix.
So the archive route needs, roughly:
Until then, OBS Debian/Ubuntu targets can use the vendored build in #272.