Ensure Debian package is up-to-date

Description

Ideally, this should be done before the trixie freeze dates, to make sure the latest Onionbalance is included and is in a good state. Timeline:

• 2025-03-15 - Milestone 1 - Transition and toolchain freeze
• 2025-04-15 - Milestone 2 - Soft Freeze
• 2025-05-15 - Milestone 3 - Hard Freeze - for key packages and packages without autopkgtests
• To be announced - Milestone 4 - Full Freeze

Tasks

• Preparation:
  • Run Onionbalance CI on Debian trixie.
• Packaging (!37 (merged)):
  • Consider to host the debian/ folder inside the main Onionbalance repository.
  • Consider to build a Debian package on CI.
  • Control file (and others) have old URLs.
  • Update the HTML documentation procedure. Needs to update debian/rules and debian/onionbalance.docs. Actually, the HTML documentation was removed from the package.
  • Produce new man pages, for onionbalance(1) and onionbalance-config(1). Needs to update debian/rules and debian/onionbalance.manpages.
  • Manually test the package. Done.
  • Test the package with piuparts. Done.
  • Review.
  • Make the 0.2.4 release.
• Contacting:
  • Send a message to the Debian package maintainer to check the current workflow, and whether it needs to be changed/updated. Source seems to be tracked here.
  • OpenReply a ticket in the Debian BTS:
    • Explaining the intention to ship the latest Onionbalance on trixie.
    • Telling that the maintainer was already contacted.
    • Setting a deadline and informing that we're considering to do a NMU if needed.
  • Try to reach another uploader, for the case of a NMU.
• Coordinating:
  • Confirm whether https://salsa.debian.org/debian/onionbalance is (still) the reference repository for packaging.
  • Consider to ship the HTML documentation in the Debian package (with dh_mkdocs).
  • Try to coordinate the new version upload.
  • Review changes done downstream.
• Workflowing:
  • Update the development workflow (#30 (closed)) as needed.
• Bonus (do or move to another ticket(s)) (all moved to #49):
  • Consider to offer the Debian package also through https://deb.torproject.org.
  • Debian bug #989926: purging fails when removing users.
  • Add the Debian package test procedure into the [development procedure](docs/development.md], perhaps generalized for the Debian package, the Python package and also for testing directly from source code. Perhaps this procedure could be integrated into a multi-step shell script.
  • Debian package should ship executables on /usr/bin not /usr/sbin.
  • Remove data folder away from the configurator module?

Time estimation

• Complexity: medium (3 days)
• Uncertainty: low (x1.1)
• Reference (adapted)