Open an issue on apt. Before you do, check the three things that decide it, because a request that fails any of them will be declined:
- Debian does not already ship it, in trixie or in sid. If it is in Debian, use Debian's. Packages here are retired when Debian catches up.
- Upstream does not publish a working
.debyou could install directly. - No maintained third-party apt repository already carries it.
Say which upstream project, and what you checked. If it clears those, the
remaining question is whether it can be built from source at an upstream
release tag on amd64 and arm64, and whether its function can be proven
automatically rather than by someone squinting at --version.
Open an issue on packages, naming the package, unless the archive itself is at fault. What helps:
apt policy <package> # which version, from which suite
dpkg -l <package> # what is actually installed
cat /etc/os-release # which Debian
dpkg --print-architecture # amd64 or arm64If the failure is an apt update error rather than the software
misbehaving, that is an archive problem and belongs on apt.
Do not open an issue. See SECURITY.md; the address is security@pkg.haus.
Pull requests are welcome on any package's debian/ directory in
packages. Two things to know:
- Version bumps are opened automatically every six hours, already built
and tested across every suite, so a pull request that only edits
package.confis usually already there. Merging one is not a release: the archive publishes on a signed tag, which stays manual. A bump needing packaging changes shows up as a failed verification rather than as a pull request, so those are the ones worth a contribution. - Every published version is immutable. Once a version is in the pool it is never rebuilt with different bytes; a fix ships as a new Debian revision.
Commits are signed. If yours are not, they can still be merged, but the merge commit is what carries the signature.