devscripts

specifically: nmudiff, tagpending, dch

Marco d'Itri: "I also think it could be interesting to notice how new features in dch are reflected in the actual changelogs."

NathanaelNerode: dch lets me get the changelog entry (time format, spacing) formatted correctly, something which many tools are very persnickety about. I always use it for that reason and that reason alone.

Marga: I have the sensation many DDs and NMs don't know some of these, and it would be important to publicize them a little bit more. Have a "Debian tool of the month" or something like that, that explains one goodie at a time. dch is particularyly nice, but dch --close sucks, and I've seen a number of people abuse it horribly.

dpkg-dev-el

?AaronUcko: debian-changelog-mode is an excellent alternative to dch for those of us with permanent Emacs sessions running.

schroot

?ReinhardTartler: schroot is another very very useful tool. It gives me more or less instant access to clean chroots on lvm snapshots for experimenting, building, developing and testing.

debootstrap

snapshot.debian.org

Steinar: Binary searching for what version some bug surfaced in; reproduction of upgrade bugs.

LarsWirzenius: Note that source code version control does not always make it easy to re-create the exact same binary package. If, for example, the package uses debhelper, and the binary package that actually exist{s,ed} in Debian was built with an older version of debhelper, re-building the package from source now with a newer debhelper might not result in a package that behaves in the same way. For example, the old version might have not called an init.d script via invoke-rc.d, but the new one does. This may make things more difficult to debug.

PTS

ddpo