<!-- common, language independant entities -->
<!entity % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!entity cvs-rev "$Revision: 1.53 $">
+ <!entity cvs-rev "$Revision: 1.54 $">
<!-- if you are translating this document, please notate the RCS
revision of the developers reference here -->
following those bugs and try to help you each time they can. But if
you can't fix such bugs within 2 weeks, you should either ask for help
by sending a mail to the Quality Assurance (QA) group
-(&email-debian-qa;) or justify yourself and present your plan to fix
+&email-debian-qa;, or justify yourself and present your plan to fix
it by sending a mail to the bug concerned report. Otherwise people
from the QA group may want to do a Non-Maintainer Upload (see
<ref id="nmu">) after trying to contact you (they might not wait as long as
If you can no longer maintain a package, you need to inform the others
about that, and see that the package is marked as orphaned.
you should set the package maintainer to <tt>Debian QA Group
-<debian-qa@lists.debian.org></tt> and submit a bug report
-against the pseudo package <tt>wnpp</tt>. The bug report should be
+&orphan-address;</tt> and submit a bug report
+against the pseudo package <package>wnpp</package>. The bug report should be
titled <tt>O: <var>package</var> -- <var>short description</var></tt>
indicating that the package is now orphaned. The severity of the bug
should be set to <em>normal</em>. If the package is especially