two characters, one Debian bug, and a slower process

dev · 2026-10-28 · 3 min

it started with two letters

i was using a Debian package, and i read a sentence that did not hold together. not a crash, not a security problem: two letters in the wrong place, enough to make the sentence read strangely.

my first reaction was: does this matter? the second was: it is a typo, i use this package, i saw it. why not report it? most people close the tab there. i kept it open, because i wanted to know what sits between seeing a typo and the fix reaching the package.

Debian is not a pull request

on GitHub the path is short: fork, edit, pull request, merge.

Debian works differently. it is a distribution with thousands of packages, a policy, maintainers responsible for what ships, and a bug tracker that has been the front door for decades. there is no single repository where you push a fix and go home: there are a package, a version, a maintainer, and a place to report what you found.

the procedure, without decoration

i read the sentence again before writing anything. i was not going to waste a maintainer's time on something i had misread. then i found where the package's bugs are reported and wrote what i saw, which version, and what it should say instead. short, specific, no story about my day.

i did not choose the timeline. the report enters a queue, a maintainer reads it, agrees or asks, and the fix follows the release process. i waited. that waiting is not a delay invented to annoy me: it is what review looks like when the reviewer is responsible for a distribution and not for a folder.

it is all documented, and the Debian bug system is the place to start. less friendly than a green merge button, and clearer about what is expected of you.

what two characters teach

a fix can be small and the path to it long. confusing the two is how people conclude that contributing is either trivial or impossible.

Debian does not ask for talent. it asks for procedure and attention: find the package, describe the problem, respect the channel, wait. if you can do that, two characters are a real contribution.

and a system with thousands of packages is held together by people who report small things properly. not by heroes, by people who noticed and wrote it down where it belonged.

faq

do i need to be a developer to report a Debian bug?

no. a clear report with what you saw, where, and which version is already useful. a patch helps, but the report starts everything.

is a typo worth a bug report?

if it is in a package you use and it makes the text wrong, yes. it is small, but it is also cheap to describe and easy to verify.

why not just open a pull request on GitHub?

because that is not how Debian accepts changes. every package has its own maintainer and its own report channel, and the fix follows the distribution's process.