I never would have guessed just how many things I'm missing. It looks
like it even worked out that there is both a binary and a library, which
is not something I had considered. Neat.
I credited Johannes Schauer Marin Rodrigues <josch@debian.org> with the
original debian/rules way back at the start of the packaging branch. It
seemed like good traceability, at the very least.
Now, the rules file is just a bit of boilerplate. I don't think anyone
needs particular credit for this thing, so I'm dropping the explicit
mention.
These don't do anything. I've compared against some other Rust packages
(some ProxmoxVE stuff) and the output of debcargo against this crate
(from crates.io, now that it's up). Neither contain these targets. I'm
fairly confident I don't need them at all.
See "https://wiki.debian.org/Teams/RustPackaging/Policy"
In section "Library package structure", the policy manual explains that
this file is meant to exist in the Debian package (i.e.: it's not
generated during the build) and should contain the SHA256 checksum of
the upstream crate.
The crate's internal arrangement can change depending on which version
of Cargo was used to create it. This checksum is from Rust 1.93, the
current stable at time of writing. Debian 13's Rust 1.85 produces a
different file with a different sum. I'm not sure what to do about that
right now.
I should have done this before publishing the build, but it's too late
now. Instead, I'll update it here and continue forward with gbp-dch to
help generate more correct changelogs.
I'm switching to use nested tags for the packaging branches. I want to
have a deb/bookworm and a deb/experimental branch. The gbp-pq tool
already seems to do this, so I'll follow it's lead.
