TODO:
- bugs in upstream versions should be reported upstream!
- add information on how to get accounts on different architectures
- - talk about CVS access
+ - talk about CVS access, other ways to submit problems
+ - add information on how you can contribute w/o being an official
+ developer
-->
<book>
<title>Debian Developer's Reference
- <author>Adam P. Harris, current maintainer <email/aph@debian.org/
+ <author>Adam Di Carlo, current maintainer <email/aph@debian.org/
<author>Christian Schwarz <email/schwarz@debian.org/
<author>Ian Jackson <email/ijackson@gnu.ai.mit.edu/
<version>ver. &version;, &date;
<copyright>
<copyrightsummary><!-- this tag not working right -->
-copyright ©1998 Adam P. Harris, ©1997,1998
+copyright ©1998 Adam Di Carlo, ©1997,1998
Christian Schwarz</copyrightsummary>
<p>
This manual is free software; you may redistribute it and/or modify it
<p>
Only an official Debian developers can do an NMU.
<!-- TODO: link to section talking about how non-maintainers can still
-contribute -->
+ contribute -->
<sect id="nmu-when">When to do an NMU
<p>
switch to force the build system to pick up the new source package
(normally it only looks for Debian revisions of '0' or '1').
<p>
-<!--- HERE --->
+<!-- HERE -->
Maintainers other than the usual package maintainer should make as few
changes to the package as possible, and they should always send a
unified context diff (<tt/diff -u/) detailing their changes to the bug
~ianmdlvl / developers-reference.git / blobdiff