X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=developers-reference.sgml;h=af1aca2b1911645413d314b5c6f7c33ae64bd6ad;hb=be9ea81016073be70c312fd28af026fd2fa35224;hp=1a491c6db7fb95b49488a9a6e97837e42e5df0af;hpb=dcba6dbc63f59b6aafcfb848df0400666540b272;p=developers-reference.git diff --git a/developers-reference.sgml b/developers-reference.sgml index 1a491c6..af1aca2 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -5,7 +5,7 @@ %commondata; - + @@ -30,7 +30,7 @@ Adam Di Carlo, current maintainer aph@debian.org Christian Schwarz schwarz@debian.org Ian Jackson ijackson@gnu.ai.mit.edu - ver. &version;, &date; + ver. &version;, &date-en; @@ -317,20 +317,19 @@ to remove the ``on vacation'' flag when you come back. Coordination With Upstream Developers

A big part of your job as Debian maintainer will be to stay in contact -with the upstream developers since you'll have to share information that -you get from the Bug Tracking System. It's not your job to fix non-Debian -specific bugs. -Rather, you have to forward these bugs to the upstream developers. -(Of course, if you are able to do so, you may certainly fix them...) -This way, the bug will hopefully -be corrected when the next upstream version comes out. +with the upstream developers. Debian users will sometimes report bugs +to the Bug Tracking System that are not specific to Debian. You +must forward these bug reports to the upstream developers so that +they can be fixed in a future release. It's not your job to fix +non-Debian specific bugs. However, if you are able to do so, you are +encouraged to contribute to upstream development of the package by +providing a fix for the bug. Debian users and developers will often +submit patches to fix upstream bugs, and you should evaluate and +forward these patches upstream.

-From time to -time, you may get a patch attached to a bug report. You have to send the -patch upstream and make sure that it gets included (if the authors accept -the proposed fix). If you need to modify the upstream sources in order to -build a policy conformant package, then you should propose a nice fix -to the upstream developers which can be included there, so that you won't have to +If you need to modify the upstream sources in order to build a policy +conformant package, then you should propose a nice fix to the upstream +developers which can be included there, so that you won't have to modify the sources of the next upstream version. Whatever changes you need, always try not to fork from the upstream sources. @@ -346,7 +345,7 @@ id="&url-debian-qa;" name="Debian Quality Assurance"> effort are 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 ) after trying to contact you (they might not wait as long as @@ -1115,8 +1114,8 @@ consulting a lawyer. For packages in non-US main or contrib, developers should at least follow the . Maintainers of non-US/non-free packages should -further consult these of non-free software. +further consult these of non-free software.

This section is for information only and does not constitute legal advice. Again, it is strongly recommended that U.S. citizens and @@ -1542,7 +1541,7 @@ of things you should check or be aware of. Don't set architecture to a value other than ``all'' or ``any'' unless you really mean it. In too many cases, maintainers don't follow the -instructions in the . Setting your architecture to ``i386'' is usually incorrect. Make sure your source package is correct. Do dpkg-source -x @@ -1600,7 +1599,7 @@ NMU of the source package ``foo_1.3-1'' would be numbered ``foo_1.3-1.0.1''.

The way to invoke dpkg-buildpackage is as -dpkg-buildpackage -B -mporter-email. Of course, +dpkg-buildpackage -B -eporter-email. Of course, set porter-email to your email address. This will do a binary-only build of only the architecture-dependant portions of the package, using the `binary-arch' target in debian/rules. @@ -1784,8 +1783,8 @@ obsolete name. 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 Debian QA Group -<debian-qa@lists.debian.org> and submit a bug report -against the pseudo package wnpp. The bug report should be +&orphan-address; and submit a bug report +against the pseudo package wnpp. The bug report should be titled O: package -- short description indicating that the package is now orphaned. The severity of the bug should be set to normal. If the package is especially