Hi,
I started working on packaging `siomon` to the official Debian repositories.
It’s a long process, and it takes some time for this package to be available for users.
But it will get there.
I wanted to ask what would be the preferred “upstream contact” listed in the package.
In Debian, we usually list the authors name and email, but I also found the “packaging email” you guys listed in the PPA.
Thanks,
This siomon, GitHub - level1techs/siomon · GitHub ?? Has reqs for Rust 1.88+ and will need rustc and cargo from trixie-backports.
From the Debian packaging guide, I think you will have to find a mentor to upload to the Debian archive, but I’d like to see this tool in the archive for sure. In the mean time, is there any way to add the .deb build to the L1T github to build on release?
Yes! This siomon.
I’m not sure if it will land on backports or only in the next release.
I will keep this thread up-to-date when news come.
The package archive is not in any way locked down, and you’d probably want a build matched to Trixie-Backports’ rust/cargo as well as a build matched to (Debian 14) Forky’s rust/cargo. The archives are updated regularly, packages can appear between releases, they pop up in the archive as soon as they’re approved by the Debian FTP Team (the name for the volunteers who manage the package archives).
Been a while since I tried to build a deb package. I think you need to lock down and commit to a specific version, 15 years ago it required the use of .tar.gz files, these days it is .txz I think.
The reason for this is that git tags change, archives do not. But yeah, get a mentor and kudos for stepping up 
If you want a .deb directly from the release workflows, there is the cargo-deb command.
It’s easy to use, and I have it working on a personal project.
This is not the same as having an upstremable package, but it’s nice.
My example in a personal rust project:
Alien to convert the .deb to a .rpm