Bug#1154067: How to make your Debian bug reports more helpful (e.g. #1154067)
Tobias Frost
tobi at frost.de
Mon Nov 16 06:30:19 GMT 2026
Hi onders,
Thanks for trying to help improve Debian, and for looking into packages like alure (#1154067). However, the way these reports are currently written creates a lot of extra work for maintainers instead of helping them.
To make your contributions actually helpful and actionable, please keep the following points in mind:
State the actual issue and your goal clearly: A one-liner like "this seems legit: " or "unmaintained in Debian and original" is not enough context. Explain what is wrong in the package right now (e.g., "The Homepage field in debian/control points to a dead URL, whereas <URL> appears to be the active upstream repository") and what concrete change you are asking for.
Provide patches or Merge Requests directly: For straightforward metadata fixes (such as updating Homepage or Vcs-* fields in debian/control), submitting a ready-to-apply fix saves maintainers a lot of time:
Via Salsa Merge Request: If the package is hosted on salsa.debian.org (check the Vcs-Git / Vcs-Browser fields), you can fork the repository, make the change, and open a Merge Request (MR) directly.
Via Patch in the BTS: Alternatively, attach a git diff / debdiff patch to your bug report and add the patch tag (by including Tags: patch in the pseudo-header).
Being "unmaintained upstream" is not a bug by itself: Many libraries in Debian are feature-complete and stable even without recent upstream commits. Unless a package is broken, causes build/dependency issues, has unfixed security bugs, or blocks transitions, low upstream activity alone does not warrant a bug report or removal.
Avoid mass-filing low-effort reports: Filing large numbers of brief, ambiguous bugs forces maintainers to spend time guessing what you mean and triaging noise. Please take the time to write complete, self-contained reports, and if you plan to file similar issues across many packages, discuss it on debian-devel at lists.debian.org first as required by the Mass Bug Filing guidelines (debian.org).
Thanks for your understanding and cooperation.
More information about the Pkg-games-devel
mailing list