1 # Debian Developer's Reference (Japanese)
2 # Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2008.
6 "Project-Id-Version: developers-reference 3.4.0\n"
7 "POT-Creation-Date: 2010-01-04 00:20+0100\n"
8 "PO-Revision-Date: 2008-03-05 18:30+0900\n"
9 "Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
10 "Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
12 "Content-Type: text/plain; charset=UTF-8\n"
13 "Content-Transfer-Encoding: 8bit\n"
15 # type: Content of: <chapter><title>
16 #. type: Content of: <chapter><title>
18 msgid "Managing Packages"
21 # type: Content of: <chapter><para>
22 #. type: Content of: <chapter><para>
25 "This chapter contains information related to creating, uploading, "
26 "maintaining, and porting packages."
28 "この章では、パッケージの作成、アップロード、メンテナンス、移植についての情報"
31 # type: Content of: <chapter><section><title>
32 #. type: Content of: <chapter><section><title>
37 # type: Content of: <chapter><section><para>
38 #. type: Content of: <chapter><section><para>
41 "If you want to create a new package for the Debian distribution, you should "
42 "first check the <ulink url=\"&url-wnpp;\">Work-Needing and Prospective "
43 "Packages (WNPP)</ulink> list. Checking the WNPP list ensures that no one is "
44 "already working on packaging that software, and that effort is not "
45 "duplicated. Read the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink> for "
49 # type: Content of: <chapter><section><para>
50 #. type: Content of: <chapter><section><para>
53 "Assuming no one else is already working on your prospective package, you "
54 "must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the "
55 "pseudo-package <systemitem role=\"package\">wnpp</systemitem> describing "
56 "your plan to create a new package, including, but not limiting yourself to, "
57 "a description of the package, the license of the prospective package, and "
58 "the current URL where it can be downloaded from."
61 # type: Content of: <chapter><section><para>
62 #. type: Content of: <chapter><section><para>
65 "You should set the subject of the bug to <literal>ITP: <replaceable>foo</"
66 "replaceable> -- <replaceable>short description</replaceable></literal>, "
67 "substituting the name of the new package for <replaceable>foo</"
68 "replaceable>. The severity of the bug report must be set to "
69 "<literal>wishlist</literal>. Please send a copy to &email-debian-devel; by "
70 "using the X-Debbugs-CC header (don't use CC:, because that way the message's "
71 "subject won't indicate the bug number). If you are packaging so many new "
72 "packages (>10) that notifying the mailing list in seperate messages is too "
73 "disruptive, do send a summary after filing the bugs to the debian-devel list "
74 "instead. This will inform the other developers about upcoming packages and "
75 "will allow a review of your description and package name."
78 # type: Content of: <chapter><section><para>
79 #. type: Content of: <chapter><section><para>
82 "Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></"
83 "literal> entry in the changelog of the new package in order for the bug "
84 "report to be automatically closed once the new package is installed in the "
85 "archive (see <xref linkend=\"upload-bugfix\"/> )."
88 #. type: Content of: <chapter><section><para>
91 "If you think your package needs some explanations for the administrators of "
92 "the NEW package queue, include them in your changelog, send to "
93 "ftpmaster@debian.org a reply to the email you receive as a maintainer after "
94 "your upload, or reply to the rejection email in case you are already re-"
98 # type: Content of: <chapter><section><para>
99 #. type: Content of: <chapter><section><para>
102 "When closing security bugs include CVE numbers as well as the Closes: "
103 "#nnnnn. This is useful for the security team to track vulnerabilities. If "
104 "an upload is made to fix the bug before the advisory ID is known, it is "
105 "encouraged to modify the historical changelog entry with the next upload. "
106 "Even in this case, please include all available pointers to background "
107 "information in the original changelog entry."
110 # type: Content of: <chapter><section><para>
111 #. type: Content of: <chapter><section><para>
114 "There are a number of reasons why we ask maintainers to announce their "
118 # type: Content of: <chapter><section><itemizedlist><listitem><para>
119 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
122 "It helps the (potentially new) maintainer to tap into the experience of "
123 "people on the list, and lets them know if anyone else is working on it "
127 # type: Content of: <chapter><section><itemizedlist><listitem><para>
128 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
131 "It lets other people thinking about working on the package know that there "
132 "already is a volunteer, so efforts may be shared."
135 # type: Content of: <chapter><section><itemizedlist><listitem><para>
136 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
139 "It lets the rest of the maintainers know more about the package than the one "
140 "line description and the usual changelog entry ``Initial release'' that gets "
141 "posted to &email-debian-devel-changes;."
144 # type: Content of: <chapter><section><itemizedlist><listitem><para>
145 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
148 "It is helpful to the people who live off <literal>unstable</literal> (and "
149 "form our first line of testers). We should encourage these people."
152 # type: Content of: <chapter><section><itemizedlist><listitem><para>
153 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
156 "The announcements give maintainers and other interested parties a better "
157 "feel of what is going on, and what is new, in the project."
160 # type: Content of: <chapter><section><para>
161 #. type: Content of: <chapter><section><para>
164 "Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> "
165 "for common rejection reasons for a new package."
168 # type: Content of: <chapter><section><title>
169 #. type: Content of: <chapter><section><title>
171 msgid "Recording changes in the package"
172 msgstr "パッケージの変更を記録する"
174 # type: Content of: <chapter><section><para>
175 #. type: Content of: <chapter><section><para>
178 "Changes that you make to the package need to be recorded in the "
179 "<filename>debian/changelog</filename>. These changes should provide a "
180 "concise description of what was changed, why (if it's in doubt), and note if "
181 "any bugs were closed. They also record when the package was completed. "
182 "This file will be installed in <filename>/usr/share/doc/"
183 "<replaceable>package</replaceable>/changelog.Debian.gz</filename>, or "
184 "<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</"
185 "filename> for native packages."
188 # type: Content of: <chapter><section><para>
189 #. type: Content of: <chapter><section><para>
192 "The <filename>debian/changelog</filename> file conforms to a certain "
193 "structure, with a number of different fields. One field of note, the "
194 "<literal>distribution</literal>, is described in <xref linkend=\"distribution"
195 "\"/> . More information about the structure of this file can be found in "
196 "the Debian Policy section titled <filename>debian/changelog</filename>."
199 # type: Content of: <chapter><section><para>
200 #. type: Content of: <chapter><section><para>
203 "Changelog entries can be used to automatically close Debian bugs when the "
204 "package is installed into the archive. See <xref linkend=\"upload-bugfix\"/"
208 # type: Content of: <chapter><section><para>
209 #. type: Content of: <chapter><section><para>
212 "It is conventional that the changelog entry of a package that contains a new "
213 "upstream version of the software looks like this:"
216 # type: Content of: <chapter><section><screen>
217 #. type: Content of: <chapter><section><screen>
220 msgid " * new upstream version\n"
221 msgstr "* new upstream version"
223 # type: Content of: <chapter><section><para>
224 #. type: Content of: <chapter><section><para>
227 "There are tools to help you create entries and finalize the "
228 "<filename>changelog</filename> for release — see <xref linkend=\"devscripts"
229 "\"/> and <xref linkend=\"dpkg-dev-el\"/> ."
232 # type: Content of: <chapter><section><para>
233 #. type: Content of: <chapter><section><para>
235 msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ."
236 msgstr "<xref linkend=\"bpp-debian-changelog\"/> も参照してください。"
238 # type: Content of: <chapter><section><title>
239 #. type: Content of: <chapter><section><title>
241 msgid "Testing the package"
244 # type: Content of: <chapter><section><para>
245 #. type: Content of: <chapter><section><para>
248 "Before you upload your package, you should do basic testing on it. At a "
249 "minimum, you should try the following activities (you'll need to have an "
250 "older version of the same Debian package around):"
253 # type: Content of: <chapter><section><itemizedlist><listitem><para>
254 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
257 "Install the package and make sure the software works, or upgrade the package "
258 "from an older version to your new version if a Debian package for it already "
262 # type: Content of: <chapter><section><itemizedlist><listitem><para>
263 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
266 "Run <command>lintian</command> over the package. You can run "
267 "<command>lintian</command> as follows: <literal>lintian -v "
268 "<replaceable>package-version</replaceable>.changes</literal>. This will "
269 "check the source package as well as the binary package. If you don't "
270 "understand the output that <command>lintian</command> generates, try adding "
271 "the <literal>-i</literal> switch, which will cause <command>lintian</"
272 "command> to output a very verbose description of the problem."
275 # type: Content of: <chapter><section><itemizedlist><listitem><para>
276 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
279 "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes "
280 "lintian to emit errors (they will start with <literal>E</literal>)."
283 # type: Content of: <chapter><section><itemizedlist><listitem><para>
284 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
287 "For more information on <command>lintian</command>, see <xref linkend="
291 # type: Content of: <chapter><section><itemizedlist><listitem><para>
292 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
295 "Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older "
296 "version, if one exists."
299 # type: Content of: <chapter><section><itemizedlist><listitem><para>
300 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
303 "Downgrade the package to the previous version (if one exists) — this tests "
304 "the <filename>postrm</filename> and <filename>prerm</filename> scripts."
307 # type: Content of: <chapter><section><itemizedlist><listitem><para>
308 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
311 msgid "Remove the package, then reinstall it."
312 msgstr "パッケージを削除して、再インストールしてください。"
314 # type: Content of: <chapter><section><itemizedlist><listitem><para>
315 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
318 "Copy the source package in a different directory and try unpacking it and "
319 "rebuilding it. This tests if the package relies on existing files outside "
320 "of it, or if it relies on permissions being preserved on the files shipped "
321 "inside the .diff.gz file."
324 # type: Content of: <chapter><section><title>
325 #. type: Content of: <chapter><section><title>
328 msgid "Layout of the source package"
331 # type: Content of: <chapter><section><para>
332 #. type: Content of: <chapter><section><para>
334 msgid "There are two types of Debian source packages:"
335 msgstr "Debian のソースパッケージには 2 種類あります:"
337 # type: Content of: <chapter><section><itemizedlist><listitem><para>
338 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
341 "the so-called <literal>native</literal> packages, where there is no "
342 "distinction between the original sources and the patches applied for Debian"
345 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
348 "the (more common) packages where there's an original source tarball file "
349 "accompanied by another file that contains the changes made by Debian"
352 #. type: Content of: <chapter><section><para>
355 "For the native packages, the source package includes a Debian source control "
356 "file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.{gz,bz2,"
357 "lzma}</literal>). A source package of a non-native package includes a Debian "
358 "source control file, the original source tarball (<literal>.orig.tar.{gz,bz2,"
359 "lzma}</literal>) and the Debian changes (<literal>.diff.gz</literal> for the "
360 "source format “1.0” or <literal>.debian.tar.{gz,bz2,lzma}</literal> for the "
361 "source format “3.0 (quilt)”)."
364 #. type: Content of: <chapter><section><para>
367 "With source format “1.0”, whether a package is native or not was determined "
368 "by <command>dpkg-source</command> at build time. Nowadays it is recommended "
369 "to be explicit about the desired source format by putting either “3.0 "
370 "(quilt)” or “3.0 (native)” in <filename>debian/source/format</filename>. "
371 "The rest of this section relates only to non-native packages."
374 # type: Content of: <chapter><section><para>
375 #. type: Content of: <chapter><section><para>
378 "The first time a version is uploaded which corresponds to a particular "
379 "upstream version, the original source tar file should be uploaded and "
380 "included in the <filename>.changes</filename> file. Subsequently, this very "
381 "same tar file should be used to build the new diffs and <filename>.dsc</"
382 "filename> files, and will not need to be re-uploaded."
385 #. type: Content of: <chapter><section><para>
388 "By default, <command>dpkg-genchanges</command> and <command>dpkg-"
389 "buildpackage</command> will include the original source tar file if and only "
390 "if the current changelog entry has a different upstream version from the "
391 "preceding entry. This behavior may be modified by using <literal>-sa</"
392 "literal> to always include it or <literal>-sd</literal> to always leave it "
396 # type: Content of: <chapter><section><para>
397 #. type: Content of: <chapter><section><para>
400 "If no original source is included in the upload, the original source tar-"
401 "file used by <command>dpkg-source</command> when constructing the <filename>."
402 "dsc</filename> file and diff to be uploaded <emphasis>must</emphasis> be "
403 "byte-for-byte identical with the one already in the archive."
406 #. type: Content of: <chapter><section><para>
409 "Please notice that, in non-native packages, permissions on files that are "
410 "not present in the .orig.tar.{gz,bz2} will not be preserved, as diff does "
411 "not store file permissions in the patch. However when using source format "
412 "“3.0 (quilt)”, permissions of files inside the <filename>debian</filename> "
413 "directory are preserved since they are stored in a tar archive."
416 # type: Content of: <chapter><section><title>
417 #. type: Content of: <chapter><section><title>
419 msgid "Picking a distribution"
422 # type: Content of: <chapter><section><para>
423 #. type: Content of: <chapter><section><para>
426 "Each upload needs to specify which distribution the package is intended "
427 "for. The package build process extracts this information from the first "
428 "line of the <filename>debian/changelog</filename> file and places it in the "
429 "<literal>Distribution</literal> field of the <literal>.changes</literal> "
433 # type: Content of: <chapter><section><para>
434 #. type: Content of: <chapter><section><para>
437 "There are several possible values for this field: <literal>stable</literal>, "
438 "<literal>unstable</literal>, <literal>testing-proposed-updates</literal> and "
439 "<literal>experimental</literal>. Normally, packages are uploaded into "
440 "<literal>unstable</literal>."
443 # type: Content of: <chapter><section><para>
444 #. type: Content of: <chapter><section><para>
447 "Actually, there are two other possible distributions: <literal>stable-"
448 "security </literal> and <literal>testing-security</literal>, but read <xref "
449 "linkend=\"bug-security\"/> for more information on those."
452 # type: Content of: <chapter><section><para>
453 #. type: Content of: <chapter><section><para>
456 "It is not possible to upload a package into several distributions at the "
460 # type: Content of: <chapter><section><section><title>
461 #. type: Content of: <chapter><section><section><title>
464 "Special case: uploads to the <literal>stable</literal> and "
465 "<literal>oldstable</literal> distributions"
468 #. type: Content of: <chapter><section><section><para>
471 "Uploading to <literal>stable</literal> means that the package will "
472 "transferred to the <literal>proposed-updates-new</literal> queue for review "
473 "by the stable release managers, and if approved will be installed in "
474 "<filename>stable-proposed-updates</filename> directory of the Debian "
475 "archive. From there, it will be included in <literal>stable</literal> with "
476 "the next point release."
479 # type: Content of: <chapter><section><section><para>
480 #. type: Content of: <chapter><section><section><para>
483 "To ensure that your upload will be accepted, you should discuss the changes "
484 "with the stable release team before you upload. For that, send a mail to the "
485 "&email-debian-release; mailing list, including the patch you want to apply "
486 "to the package version currently in <literal>stable</literal>. Always be "
487 "verbose and detailed in your changelog entries for uploads to the "
488 "<literal>stable</literal> distribution."
491 # type: Content of: <chapter><section><section><para>
492 #. type: Content of: <chapter><section><section><para>
495 "Extra care should be taken when uploading to <literal>stable</literal>. "
496 "Basically, a package should only be uploaded to <literal>stable</literal> if "
497 "one of the following happens:"
500 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
501 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
503 msgid "a truly critical functionality problem"
506 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
507 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
509 msgid "the package becomes uninstallable"
512 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
513 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
515 msgid "a released architecture lacks the package"
518 # type: Content of: <chapter><section><section><para>
519 #. type: Content of: <chapter><section><section><para>
522 "In the past, uploads to <literal>stable</literal> were used to address "
523 "security problems as well. However, this practice is deprecated, as uploads "
524 "used for Debian security advisories are automatically copied to the "
525 "appropriate <filename>proposed-updates</filename> archive when the advisory "
526 "is released. See <xref linkend=\"bug-security\"/> for detailed information "
527 "on handling security problems. If the security teams deems the problem to be "
528 "too benign to be fixed through a <literal>DSA</literal>, the stable release "
529 "managers are usually willing to include your fix nonetheless in a regular "
530 "upload to <literal>stable</literal>."
533 # type: Content of: <chapter><section><section><para>
534 #. type: Content of: <chapter><section><section><para>
537 "Changing anything else in the package that isn't important is discouraged, "
538 "because even trivial fixes can cause bugs later on."
541 # type: Content of: <chapter><section><section><para>
542 #. type: Content of: <chapter><section><section><para>
545 "Packages uploaded to <literal>stable</literal> need to be compiled on "
546 "systems running <literal>stable</literal>, so that their dependencies are "
547 "limited to the libraries (and other packages) available in <literal>stable</"
548 "literal>; for example, a package uploaded to <literal>stable</literal> that "
549 "depends on a library package that only exists in <literal>unstable</literal> "
550 "will be rejected. Making changes to dependencies of other packages (by "
551 "messing with <literal>Provides</literal> or <literal>shlibs</literal> "
552 "files), possibly making those other packages uninstallable, is strongly "
556 # type: Content of: <chapter><section><section><para>
557 #. type: Content of: <chapter><section><section><para>
560 "Uploads to the <literal>oldstable</literal> distributions are possible as "
561 "long as it hasn't been archived. The same rules as for <literal>stable </"
565 # type: Content of: <chapter><section><section><title>
566 #. type: Content of: <chapter><section><section><title>
569 "Special case: uploads to <literal>testing/testing-proposed-updates</literal>"
572 # type: Content of: <chapter><section><section><para>
573 #. type: Content of: <chapter><section><section><para>
576 "Please see the information in the <link linkend=\"t-p-u\">testing section</"
580 # type: Content of: <chapter><section><title>
581 #. type: Content of: <chapter><section><title>
583 msgid "Uploading a package"
584 msgstr "パッケージをアップロードする"
586 # type: Content of: <chapter><section><section><title>
587 #. type: Content of: <chapter><section><section><title>
589 msgid "Uploading to <literal>ftp-master</literal>"
590 msgstr "<literal>ftp-master</literal> にアップロードする"
592 #. type: Content of: <chapter><section><section><para>
595 "To upload a package, you should upload the files (including the signed "
596 "changes and dsc-file) with anonymous ftp to <literal>&ftp-upload-host;</"
597 "literal> in the directory <ulink url=\"ftp://&ftp-upload-host;&upload-queue;"
598 "\">&upload-queue;</ulink>. To get the files processed there, they need to "
599 "be signed with a key in the Debian Developers keyring or the Debian "
600 "Maintainers keyring (see <ulink url=\"&url-wiki-dm;\"></ulink>)."
603 # type: Content of: <chapter><section><section><para>
604 #. type: Content of: <chapter><section><section><para>
607 "Please note that you should transfer the changes file last. Otherwise, your "
608 "upload may be rejected because the archive maintenance software will parse "
609 "the changes file and see that not all files have been uploaded."
612 # type: Content of: <chapter><section><section><para>
613 #. type: Content of: <chapter><section><section><para>
616 "You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref "
617 "linkend=\"dput\"/> useful when uploading packages. These handy programs "
618 "help automate the process of uploading packages into Debian."
621 #. type: Content of: <chapter><section><section><para>
624 "For removing packages, please see <ulink url=\"ftp://&ftp-upload-host;"
625 "&upload-queue;/README\"/> and the Debian package <xref linkend=\"dcut\"/> ."
628 # type: Content of: <chapter><section><section><title>
629 #. type: Content of: <chapter><section><section><title>
631 msgid "Delayed uploads"
634 #. type: Content of: <chapter><section><section><para>
637 "It is sometimes useful to upload a package immediately, but to want this "
638 "package to arrive in the archive only a few days later. For example, when "
639 "preparing a <link linkend=\"nmu\">Non-maintainer Upload</link>, you might "
640 "want to give the maintainer a few days to react."
643 #. type: Content of: <chapter><section><section><para>
646 "An upload to the delayed directory keeps the package in <ulink url=\"http://"
647 "ftp-master.debian.org/deferred.html\"> the deferred uploads queue\"</"
648 "ulink>. When the specified waiting time is over, the package is moved into "
649 "the regular incoming directory for processing. This is done through "
650 "automatic uploading to <literal>&ftp-upload-host;</literal> in upload-"
651 "directory <literal>DELAYED/[012345678]-day</literal>. 0-day is uploaded "
652 "multiple times per day to <literal>&ftp-upload-host;</literal>."
655 #. type: Content of: <chapter><section><section><para>
658 "With dput, you can use the <literal>--delayed <replaceable>DELAY</"
659 "replaceable></literal> parameter to put the package into one of the queues."
662 # type: Content of: <chapter><section><section><title>
663 #. type: Content of: <chapter><section><section><title>
665 msgid "Security uploads"
666 msgstr "セキュリティアップロード"
668 # type: Content of: <chapter><section><section><para>
669 #. type: Content of: <chapter><section><section><para>
672 "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
673 "upload queue (<literal>oldstable-security</literal>, <literal>stable-"
674 "security </literal>, etc.) without prior authorization from the security "
675 "team. If the package does not exactly meet the team's requirements, it will "
676 "cause many problems and delays in dealing with the unwanted upload. For "
677 "details, please see section <xref linkend=\"bug-security\"/> ."
680 # type: Content of: <chapter><section><section><title>
681 #. type: Content of: <chapter><section><section><title>
683 msgid "Other upload queues"
686 #. type: Content of: <chapter><section><section><para>
689 "There is an alternative upload queue in Europe at <ulink url=\"ftp://&ftp-eu-"
690 "upload-host;&upload-queue;\"/>. It operates in the same way as <literal>&ftp-"
691 "upload-host;</literal>, but should be faster for European developers."
694 #. type: Content of: <chapter><section><section><para>
697 "Packages can also be uploaded via ssh to <literal>&ssh-upload-host;</"
698 "literal>; files should be put <literal>/srv/upload.debian.org/UploadQueue</"
699 "literal>. This queue does not support <xref linkend=\"delayed-incoming"
700 "\">delayed uploads</xref>."
703 # type: Content of: <chapter><section><section><title>
704 #. type: Content of: <chapter><section><section><title>
706 msgid "Notification that a new package has been installed"
709 # type: Content of: <chapter><section><section><para>
710 #. type: Content of: <chapter><section><section><para>
713 "The Debian archive maintainers are responsible for handling package "
714 "uploads. For the most part, uploads are automatically handled on a daily "
715 "basis by the archive maintenance tools, <command>katie</command>. "
716 "Specifically, updates to existing packages to the <literal>unstable</"
717 "literal> distribution are handled automatically. In other cases, notably "
718 "new packages, placing the uploaded package into the distribution is handled "
719 "manually. When uploads are handled manually, the change to the archive may "
720 "take up to a month to occur. Please be patient."
723 # type: Content of: <chapter><section><section><para>
724 #. type: Content of: <chapter><section><section><para>
727 "In any case, you will receive an email notification indicating that the "
728 "package has been added to the archive, which also indicates which bugs will "
729 "be closed by the upload. Please examine this notification carefully, "
730 "checking if any bugs you meant to close didn't get triggered."
733 # type: Content of: <chapter><section><section><para>
734 #. type: Content of: <chapter><section><section><para>
737 "The installation notification also includes information on what section the "
738 "package was inserted into. If there is a disparity, you will receive a "
739 "separate email notifying you of that. Read on below."
742 # type: Content of: <chapter><section><section><para>
743 #. type: Content of: <chapter><section><section><para>
746 "Note that if you upload via queues, the queue daemon software will also send "
747 "you a notification by email."
750 # type: Content of: <chapter><section><title>
751 #. type: Content of: <chapter><section><title>
753 msgid "Specifying the package section, subsection and priority"
756 # type: Content of: <chapter><section><para>
757 #. type: Content of: <chapter><section><para>
760 "The <filename>debian/control</filename> file's <literal>Section</literal> "
761 "and <literal>Priority</literal> fields do not actually specify where the "
762 "file will be placed in the archive, nor its priority. In order to retain "
763 "the overall integrity of the archive, it is the archive maintainers who have "
764 "control over these fields. The values in the <filename>debian/control</"
765 "filename> file are actually just hints."
768 # type: Content of: <chapter><section><para>
769 #. type: Content of: <chapter><section><para>
772 "The archive maintainers keep track of the canonical sections and priorities "
773 "for packages in the <literal>override file</literal>. If there is a "
774 "disparity between the <literal>override file</literal> and the package's "
775 "fields as indicated in <filename>debian/control</filename>, then you will "
776 "receive an email noting the divergence when the package is installed into "
777 "the archive. You can either correct your <filename>debian/control</"
778 "filename> file for your next upload, or else you may wish to make a change "
779 "in the <literal>override file</literal>."
782 #. type: Content of: <chapter><section><para>
785 "To alter the actual section that a package is put in, you need to first make "
786 "sure that the <filename>debian/control</filename> file in your package is "
787 "accurate. Next, submit a bug against <systemitem role=\"package\">ftp."
788 "debian.org</systemitem> requesting that the section or priority for your "
789 "package be changed from the old section or priority to the new one. Use a "
790 "Subject like <literal>override: PACKAGE1:section/priority, [...], PACKAGEX:"
791 "section/priority</literal>, and include the justification for the change in "
792 "the body of the bug report."
795 # type: Content of: <chapter><section><para>
796 #. type: Content of: <chapter><section><para>
799 "For more information about <literal>override files</literal>, see "
800 "<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> "
801 "<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;"
802 "#maintincorrect\"></ulink>."
805 # type: Content of: <chapter><section><para>
806 #. type: Content of: <chapter><section><para>
809 "Note that the <literal>Section</literal> field describes both the section as "
810 "well as the subsection, which are described in <xref linkend=\"archive-"
811 "sections\"/> . If the section is main, it should be omitted. The list of "
812 "allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-"
813 "archive.html#s-subsections\"></ulink>."
816 # type: Content of: <chapter><section><title>
817 #. type: Content of: <chapter><section><title>
819 msgid "Handling bugs"
822 # type: Content of: <chapter><section><para>
823 #. type: Content of: <chapter><section><para>
826 "Every developer has to be able to work with the Debian <ulink url=\"&url-bts;"
827 "\">bug tracking system</ulink>. This includes knowing how to file bug "
828 "reports properly (see <xref linkend=\"submit-bug\"/> ), how to update them "
829 "and reorder them, and how to process and close them."
832 # type: Content of: <chapter><section><para>
833 #. type: Content of: <chapter><section><para>
836 "The bug tracking system's features are described in the <ulink url=\"&url-"
837 "bts-devel;\">BTS documentation for developers</ulink>. This includes "
838 "closing bugs, sending followup messages, assigning severities and tags, "
839 "marking bugs as forwarded, and other issues."
842 # type: Content of: <chapter><section><para>
843 #. type: Content of: <chapter><section><para>
846 "Operations such as reassigning bugs to other packages, merging separate bug "
847 "reports about the same issue, or reopening bugs when they are prematurely "
848 "closed, are handled using the so-called control mail server. All of the "
849 "commands available on this server are described in the <ulink url=\"&url-bts-"
850 "control;\">BTS control server documentation</ulink>."
853 # type: Content of: <chapter><section><section><title>
854 #. type: Content of: <chapter><section><section><title>
856 msgid "Monitoring bugs"
859 # type: Content of: <chapter><section><section><para>
860 #. type: Content of: <chapter><section><section><para>
863 "If you want to be a good maintainer, you should periodically check the "
864 "<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your "
865 "packages. The BTS contains all the open bugs against your packages. You "
866 "can check them by browsing this page: <literal>http://&bugs-host;/"
867 "<replaceable>yourlogin</replaceable>@debian.org</literal>."
870 # type: Content of: <chapter><section><section><para>
871 #. type: Content of: <chapter><section><section><para>
874 "Maintainers interact with the BTS via email addresses at <literal>&bugs-host;"
875 "</literal>. Documentation on available commands can be found at <ulink url="
876 "\"&url-bts;\"></ulink>, or, if you have installed the <systemitem role="
877 "\"package\">doc-debian</systemitem> package, you can look at the local files "
881 # type: Content of: <chapter><section><section><para>
882 #. type: Content of: <chapter><section><section><para>
885 "Some find it useful to get periodic reports on open bugs. You can add a "
886 "cron job such as the following if you want to get a weekly email outlining "
887 "all the open bugs against your packages:"
890 #. type: Content of: <chapter><section><section><screen>
894 "# ask for weekly reports of bugs in my packages\n"
895 "&cron-bug-report;\n"
898 # type: Content of: <chapter><section><section><para>
899 #. type: Content of: <chapter><section><section><para>
902 "Replace <replaceable>address</replaceable> with your official Debian "
903 "maintainer address."
906 # type: Content of: <chapter><section><section><title>
907 #. type: Content of: <chapter><section><section><title>
909 msgid "Responding to bugs"
912 # type: Content of: <chapter><section><section><para>
913 #. type: Content of: <chapter><section><section><para>
916 "When responding to bugs, make sure that any discussion you have about bugs "
917 "is sent both to the original submitter of the bug, and to the bug itself (e."
918 "g., <email>123@&bugs-host;</email>). If you're writing a new mail and you "
919 "don't remember the submitter email address, you can use the <email>123-"
920 "submitter@&bugs-host;</email> email to contact the submitter <emphasis>and</"
921 "emphasis> to record your mail within the bug log (that means you don't need "
922 "to send a copy of the mail to <email>123@&bugs-host;</email>)."
925 # type: Content of: <chapter><section><section><para>
926 #. type: Content of: <chapter><section><section><para>
929 "If you get a bug which mentions FTBFS, this means Fails to build from "
930 "source. Porters frequently use this acronym."
933 # type: Content of: <chapter><section><section><para>
934 #. type: Content of: <chapter><section><section><para>
937 "Once you've dealt with a bug report (e.g. fixed it), mark it as "
938 "<literal>done</literal> (close it) by sending an explanation message to "
939 "<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and "
940 "uploading the package, you can automate bug closing as described in <xref "
941 "linkend=\"upload-bugfix\"/> ."
944 # type: Content of: <chapter><section><section><para>
945 #. type: Content of: <chapter><section><section><para>
948 "You should <emphasis>never</emphasis> close bugs via the bug server "
949 "<literal>close</literal> command sent to &email-bts-control;. If you do so, "
950 "the original submitter will not receive any information about why the bug "
954 # type: Content of: <chapter><section><section><title>
955 #. type: Content of: <chapter><section><section><title>
957 msgid "Bug housekeeping"
960 # type: Content of: <chapter><section><section><para>
961 #. type: Content of: <chapter><section><section><para>
964 "As a package maintainer, you will often find bugs in other packages or have "
965 "bugs reported against your packages which are actually bugs in other "
966 "packages. The bug tracking system's features are described in the <ulink "
967 "url=\"&url-bts-devel;\">BTS documentation for Debian developers</ulink>. "
968 "Operations such as reassigning, merging, and tagging bug reports are "
969 "described in the <ulink url=\"&url-bts-control;\">BTS control server "
970 "documentation</ulink>. This section contains some guidelines for managing "
971 "your own bugs, based on the collective Debian developer experience."
974 # type: Content of: <chapter><section><section><para>
975 #. type: Content of: <chapter><section><section><para>
978 "Filing bugs for problems that you find in other packages is one of the civic "
979 "obligations of maintainership, see <xref linkend=\"submit-bug\"/> for "
980 "details. However, handling the bugs in your own packages is even more "
984 # type: Content of: <chapter><section><section><para>
985 #. type: Content of: <chapter><section><section><para>
987 msgid "Here's a list of steps that you may follow to handle a bug report:"
990 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
991 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
994 "Decide whether the report corresponds to a real bug or not. Sometimes users "
995 "are just calling a program in the wrong way because they haven't read the "
996 "documentation. If you diagnose this, just close the bug with enough "
997 "information to let the user correct their problem (give pointers to the good "
998 "documentation and so on). If the same report comes up again and again you "
999 "may ask yourself if the documentation is good enough or if the program "
1000 "shouldn't detect its misuse in order to give an informative error message. "
1001 "This is an issue that may need to be brought up with the upstream author."
1004 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1005 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1008 "If the bug submitter disagrees with your decision to close the bug, they may "
1009 "reopen it until you find an agreement on how to handle it. If you don't "
1010 "find any, you may want to tag the bug <literal>wontfix</literal> to let "
1011 "people know that the bug exists but that it won't be corrected. If this "
1012 "situation is unacceptable, you (or the submitter) may want to require a "
1013 "decision of the technical committee by reassigning the bug to <systemitem "
1014 "role=\"package\">tech-ctte</systemitem> (you may use the clone command of "
1015 "the BTS if you wish to keep it reported against your package). Before doing "
1016 "so, please read the <ulink url=\"&url-tech-ctte;\">recommended procedure</"
1020 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1021 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1024 "If the bug is real but it's caused by another package, just reassign the bug "
1025 "to the right package. If you don't know which package it should be "
1026 "reassigned to, you should ask for help on <link linkend=\"irc-channels"
1027 "\">IRC</link> or on &email-debian-devel;. Please inform the maintainer(s) "
1028 "of the package you reassign the bug to, for example by Cc:ing the message "
1029 "that does the reassign to <email>packagename@packages.debian.org</email> and "
1030 "explaining your reasons in that mail. Please note that a simple reassignment "
1031 "is <emphasis>not</emphasis> e-mailed to the maintainers of the package being "
1032 "reassigned to, so they won't know about it until they look at a bug overview "
1033 "for their packages."
1036 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1037 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1040 "If the bug affects the operation of your package, please consider cloning "
1041 "the bug and reassigning the clone to the package that really causes the "
1042 "behavior. Otherwise, the bug will not be shown in your package's bug list, "
1043 "possibly causing users to report the same bug over and over again. You "
1044 "should block \"your\" bug with the reassigned, cloned bug to document the "
1048 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1049 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1052 "Sometimes you also have to adjust the severity of the bug so that it matches "
1053 "our definition of the severity. That's because people tend to inflate the "
1054 "severity of bugs to make sure their bugs are fixed quickly. Some bugs may "
1055 "even be dropped to wishlist severity when the requested change is just "
1059 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1060 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1063 "If the bug is real but the same problem has already been reported by someone "
1064 "else, then the two relevant bug reports should be merged into one using the "
1065 "merge command of the BTS. In this way, when the bug is fixed, all of the "
1066 "submitters will be informed of this. (Note, however, that emails sent to "
1067 "one bug report's submitter won't automatically be sent to the other report's "
1068 "submitter.) For more details on the technicalities of the merge command and "
1069 "its relative, the unmerge command, see the BTS control server documentation."
1072 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1073 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1076 "The bug submitter may have forgotten to provide some information, in which "
1077 "case you have to ask them for the required information. You may use the "
1078 "<literal>moreinfo</literal> tag to mark the bug as such. Moreover if you "
1079 "can't reproduce the bug, you tag it <literal>unreproducible</literal>. "
1080 "Anyone who can reproduce the bug is then invited to provide more information "
1081 "on how to reproduce it. After a few months, if this information has not "
1082 "been sent by someone, the bug may be closed."
1085 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1086 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1089 "If the bug is related to the packaging, you just fix it. If you are not "
1090 "able to fix it yourself, then tag the bug as <literal>help</literal>. You "
1091 "can also ask for help on &email-debian-devel; or &email-debian-qa;. If it's "
1092 "an upstream problem, you have to forward it to the upstream author. "
1093 "Forwarding a bug is not enough, you have to check at each release if the bug "
1094 "has been fixed or not. If it has, you just close it, otherwise you have to "
1095 "remind the author about it. If you have the required skills you can prepare "
1096 "a patch that fixes the bug and send it to the author at the same time. Make "
1097 "sure to send the patch to the BTS and to tag the bug as <literal>patch</"
1101 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1102 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1105 "If you have fixed a bug in your local copy, or if a fix has been committed "
1106 "to the CVS repository, you may tag the bug as <literal>pending</literal> to "
1107 "let people know that the bug is corrected and that it will be closed with "
1108 "the next upload (add the <literal>closes:</literal> in the "
1109 "<filename>changelog</filename>). This is particularly useful if you are "
1110 "several developers working on the same package."
1113 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
1114 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
1117 "Once a corrected package is available in the archive, the bug should be "
1118 "closed indicating the version in which it was fixed. This can be done "
1119 "automatically, read <xref linkend=\"upload-bugfix\"/>."
1122 # type: Content of: <chapter><section><section><title>
1123 #. type: Content of: <chapter><section><section><title>
1125 msgid "When bugs are closed by new uploads"
1126 msgstr "新規アップロードでバグがクローズされる時"
1128 # type: Content of: <chapter><section><section><para>
1129 #. type: Content of: <chapter><section><section><para>
1132 "As bugs and problems are fixed in your packages, it is your responsibility "
1133 "as the package maintainer to close these bugs. However, you should not "
1134 "close a bug until the package which fixes the bug has been accepted into the "
1135 "Debian archive. Therefore, once you get notification that your updated "
1136 "package has been installed into the archive, you can and should close the "
1137 "bug in the BTS. Also, the bug should be closed with the correct version."
1140 # type: Content of: <chapter><section><section><para>
1141 #. type: Content of: <chapter><section><section><para>
1144 "However, it's possible to avoid having to manually close bugs after the "
1145 "upload — just list the fixed bugs in your <filename>debian/changelog</"
1146 "filename> file, following a certain syntax, and the archive maintenance "
1147 "software will close the bugs for you. For example:"
1150 # type: Content of: <chapter><section><section><screen>
1151 #. type: Content of: <chapter><section><section><screen>
1155 "acme-cannon (3.1415) unstable; urgency=low\n"
1157 " * Frobbed with options (closes: Bug#98339)\n"
1158 " * Added safety to prevent operator dismemberment, closes: bug#98765,\n"
1159 " bug#98713, #98714.\n"
1160 " * Added man page. Closes: #98725.\n"
1162 "acme-cannon (3.1415) unstable; urgency=low\n"
1164 " * Frobbed with options (closes: Bug#98339)\n"
1165 " * Added safety to prevent operator dismemberment, closes: bug#98765,\n"
1166 " bug#98713, #98714.\n"
1167 " * Added man page. Closes: #98725."
1169 # type: Content of: <chapter><section><section><para>
1170 #. type: Content of: <chapter><section><section><para>
1173 "Technically speaking, the following Perl regular expression describes how "
1174 "bug closing changelogs are identified:"
1177 # type: Content of: <chapter><section><section><screen>
1178 #. type: Content of: <chapter><section><section><screen>
1181 msgid " /closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig\n"
1182 msgstr "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig"
1184 # type: Content of: <chapter><section><section><para>
1185 #. type: Content of: <chapter><section><section><para>
1188 "We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> "
1189 "syntax, as it is the most concise entry and the easiest to integrate with "
1190 "the text of the <filename>changelog</filename>. Unless specified different "
1191 "by the <replaceable>-v</replaceable>-switch to <command>dpkg-buildpackage</"
1192 "command>, only the bugs closed in the most recent changelog entry are closed "
1193 "(basically, exactly the bugs mentioned in the changelog-part in the "
1194 "<filename>.changes</filename> file are closed)."
1197 # type: Content of: <chapter><section><section><para>
1198 #. type: Content of: <chapter><section><section><para>
1201 "Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer "
1202 "upload (NMU)</link> were tagged <literal>fixed</literal> instead of being "
1203 "closed, but that practice was ceased with the advent of version-tracking. "
1204 "The same applied to the tag <literal>fixed-in-experimental</literal>."
1207 # type: Content of: <chapter><section><section><para>
1208 #. type: Content of: <chapter><section><section><para>
1211 "If you happen to mistype a bug number or forget a bug in the changelog "
1212 "entries, don't hesitate to undo any damage the error caused. To reopen "
1213 "wrongly closed bugs, send a <literal>reopen <replaceable>XXX</replaceable></"
1214 "literal> command to the bug tracking system's control address, &email-bts-"
1215 "control;. To close any remaining bugs that were fixed by your upload, email "
1216 "the <filename>.changes</filename> file to <email>XXX-done@&bugs-host;</"
1217 "email>, where <replaceable>XXX</replaceable> is the bug number, and put "
1218 "Version: YYY and an empty line as the first two lines of the body of the "
1219 "email, where <replaceable>YYY</replaceable> is the first version where the "
1220 "bug has been fixed."
1223 # type: Content of: <chapter><section><section><para>
1224 #. type: Content of: <chapter><section><section><para>
1227 "Bear in mind that it is not obligatory to close bugs using the changelog as "
1228 "described above. If you simply want to close bugs that don't have anything "
1229 "to do with an upload you made, do it by emailing an explanation to "
1230 "<email>XXX-done@&bugs-host;</email>. Do <emphasis role=\"strong\">not</"
1231 "emphasis> close bugs in the changelog entry of a version if the changes in "
1232 "that version of the package don't have any bearing on the bug."
1235 # type: Content of: <chapter><section><section><para>
1236 #. type: Content of: <chapter><section><section><para>
1239 "For general information on how to write your changelog entries, see <xref "
1240 "linkend=\"bpp-debian-changelog\"/> ."
1243 # type: Content of: <chapter><section><section><title>
1244 #. type: Content of: <chapter><section><section><title>
1246 msgid "Handling security-related bugs"
1247 msgstr "セキュリティ関連バグの取扱い"
1249 # type: Content of: <chapter><section><section><para>
1250 #. type: Content of: <chapter><section><section><para>
1253 "Due to their sensitive nature, security-related bugs must be handled "
1254 "carefully. The Debian Security Team exists to coordinate this activity, "
1255 "keeping track of outstanding security problems, helping maintainers with "
1256 "security problems or fixing them themselves, sending security advisories, "
1257 "and maintaining <literal>security.debian.org</literal>."
1260 #. type: Content of: <chapter><section><section><para>
1263 "When you become aware of a security-related bug in a Debian package, whether "
1264 "or not you are the maintainer, collect pertinent information about the "
1265 "problem, and promptly contact the security team at &email-security-team; as "
1266 "soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any "
1267 "packages for <literal>stable</literal> without contacting the team. Useful "
1268 "information includes, for example:"
1271 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1272 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1275 "Which versions of the package are known to be affected by the bug. Check "
1276 "each version that is present in a supported Debian release, as well as "
1277 "<literal>testing</literal> and <literal>unstable</literal>."
1280 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1281 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1284 "The nature of the fix, if any is available (patches are especially helpful)"
1287 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1288 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1291 "Any fixed packages that you have prepared yourself (send only the <literal>."
1292 "diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend="
1293 "\"bug-security-building\"/> first)"
1296 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1297 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1300 "Any assistance you can provide to help with testing (exploits, regression "
1304 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1305 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
1308 "Any information needed for the advisory (see <xref linkend=\"bug-security-"
1312 #. type: Content of: <chapter><section><section><para>
1315 "As the maintainer of the package, you have the responsibility to maintain "
1316 "it, even in the stable release. You are in the best position to evaluate "
1317 "patches and test updated packages, so please see the sections below on how "
1318 "to prepare packages for the Security Team to handle."
1321 #. type: Content of: <chapter><section><section><section><title>
1323 msgid "The Security Tracker"
1326 #. type: Content of: <chapter><section><section><section><para>
1329 "The security team maintains a central database, the <ulink url=\"http://"
1330 "security-tracker.debian.org/\">Debian Security Tracker</ulink>. This "
1331 "contains all public information that is known about security issues: which "
1332 "packages and versions are affected or fixed, and thus whether stable, "
1333 "testing and/or unstable are vulnerable. Information that is still "
1334 "confidential is not added to the tracker."
1337 #. type: Content of: <chapter><section><section><section><para>
1340 "You can search it for a specific issue, but also on package name. Look for "
1341 "your package to see which issues are still open. If you can, please provide "
1342 "more information about those issues, or help to address them in your "
1343 "package. Instructions are on the tracker web pages."
1346 # type: Content of: <chapter><section><section><section><title>
1347 #. type: Content of: <chapter><section><section><section><title>
1349 msgid "Confidentiality"
1352 # type: Content of: <chapter><section><section><section><para>
1353 #. type: Content of: <chapter><section><section><section><para>
1356 "Unlike most other activities within Debian, information about security "
1357 "issues must sometimes be kept private for a time. This allows software "
1358 "distributors to coordinate their disclosure in order to minimize their "
1359 "users' exposure. Whether this is the case depends on the nature of the "
1360 "problem and corresponding fix, and whether it is already a matter of public "
1364 # type: Content of: <chapter><section><section><section><para>
1365 #. type: Content of: <chapter><section><section><section><para>
1367 msgid "There are several ways developers can learn of a security problem:"
1370 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1371 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1373 msgid "they notice it on a public forum (mailing list, web site, etc.)"
1376 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1377 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1379 msgid "someone files a bug report"
1382 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1383 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1385 msgid "someone informs them via private email"
1388 # type: Content of: <chapter><section><section><section><para>
1389 #. type: Content of: <chapter><section><section><section><para>
1392 "In the first two cases, the information is public and it is important to "
1393 "have a fix as soon as possible. In the last case, however, it might not be "
1394 "public information. In that case there are a few possible options for "
1395 "dealing with the problem:"
1398 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1399 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1402 "If the security exposure is minor, there is sometimes no need to keep the "
1403 "problem a secret and a fix should be made and released."
1406 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1407 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1410 "If the problem is severe, it is preferable to share the information with "
1411 "other vendors and coordinate a release. The security team keeps in contact "
1412 "with the various organizations and individuals and can take care of that."
1415 # type: Content of: <chapter><section><section><section><para>
1416 #. type: Content of: <chapter><section><section><section><para>
1419 "In all cases if the person who reports the problem asks that it not be "
1420 "disclosed, such requests should be honored, with the obvious exception of "
1421 "informing the security team in order that a fix may be produced for a stable "
1422 "release of Debian. When sending confidential information to the security "
1423 "team, be sure to mention this fact."
1426 # type: Content of: <chapter><section><section><section><para>
1427 #. type: Content of: <chapter><section><section><section><para>
1430 "Please note that if secrecy is needed you may not upload a fix to "
1431 "<literal>unstable</literal> (or anywhere else, such as a public CVS "
1432 "repository). It is not sufficient to obfuscate the details of the change, "
1433 "as the code itself is public, and can (and will) be examined by the general "
1437 # type: Content of: <chapter><section><section><section><para>
1438 #. type: Content of: <chapter><section><section><section><para>
1441 "There are two reasons for releasing information even though secrecy is "
1442 "requested: the problem has been known for a while, or the problem or exploit "
1443 "has become public."
1446 #. type: Content of: <chapter><section><section><section><para>
1449 "The Security Team has a PGP-key to enable encrypted communication about "
1450 "sensitive issues. See the <ulink url=\"http://www.debian.org/security/faq.en."
1451 "html#contact\">Security Team FAQ</ulink> for details."
1454 # type: Content of: <chapter><section><section><section><title>
1455 #. type: Content of: <chapter><section><section><section><title>
1457 msgid "Security Advisories"
1460 # type: Content of: <chapter><section><section><section><para>
1461 #. type: Content of: <chapter><section><section><section><para>
1464 "Security advisories are only issued for the current, released stable "
1465 "distribution, and <emphasis>not</emphasis> for <literal>testing</literal> or "
1466 "<literal>unstable</literal>. When released, advisories are sent to the "
1467 "&email-debian-security-announce; mailing list and posted on <ulink url="
1468 "\"&url-debian-security-advisories;\">the security web page</ulink>. "
1469 "Security advisories are written and posted by the security team. However "
1470 "they certainly do not mind if a maintainer can supply some of the "
1471 "information for them, or write part of the text. Information that should be "
1472 "in an advisory includes:"
1475 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1476 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1478 msgid "A description of the problem and its scope, including:"
1481 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1482 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1484 msgid "The type of problem (privilege escalation, denial of service, etc.)"
1487 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1488 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1490 msgid "What privileges may be gained, and by whom (if any)"
1493 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1494 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1496 msgid "How it can be exploited"
1497 msgstr "どのようにして攻撃が可能なのか"
1499 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1500 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1502 msgid "Whether it is remotely or locally exploitable"
1503 msgstr "攻撃はリモートから可能なのかそれともローカルから可能なのか"
1505 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1506 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para>
1508 msgid "How the problem was fixed"
1509 msgstr "どのようにして問題が修正されたのか"
1511 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1512 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1514 msgid "This information allows users to assess the threat to their systems."
1517 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1518 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1520 msgid "Version numbers of affected packages"
1521 msgstr "影響を受けるパッケージのバージョン番号"
1523 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1524 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1526 msgid "Version numbers of fixed packages"
1527 msgstr "修正されたパッケージのバージョン番号"
1529 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1530 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1533 "Information on where to obtain the updated packages (usually from the Debian "
1537 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1538 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1541 "References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</"
1542 "ulink> identifiers, and any other information useful in cross-referencing "
1546 # type: Content of: <chapter><section><section><section><title>
1547 #. type: Content of: <chapter><section><section><section><title>
1549 msgid "Preparing packages to address security issues"
1552 # type: Content of: <chapter><section><section><section><para>
1553 #. type: Content of: <chapter><section><section><section><para>
1556 "One way that you can assist the security team in their duties is to provide "
1557 "them with fixed packages suitable for a security advisory for the stable "
1561 # type: Content of: <chapter><section><section><section><para>
1562 #. type: Content of: <chapter><section><section><section><para>
1565 "When an update is made to the stable release, care must be taken to avoid "
1566 "changing system behavior or introducing new bugs. In order to do this, make "
1567 "as few changes as possible to fix the bug. Users and administrators rely on "
1568 "the exact behavior of a release once it is made, so any change that is made "
1569 "might break someone's system. This is especially true of libraries: make "
1570 "sure you never change the API or ABI, no matter how small the change."
1573 # type: Content of: <chapter><section><section><section><para>
1574 #. type: Content of: <chapter><section><section><section><para>
1577 "This means that moving to a new upstream version is not a good solution. "
1578 "Instead, the relevant changes should be back-ported to the version present "
1579 "in the current stable Debian release. Generally, upstream maintainers are "
1580 "willing to help if needed. If not, the Debian security team may be able to "
1584 # type: Content of: <chapter><section><section><section><para>
1585 #. type: Content of: <chapter><section><section><section><para>
1588 "In some cases, it is not possible to back-port a security fix, for example "
1589 "when large amounts of source code need to be modified or rewritten. If this "
1590 "happens, it may be necessary to move to a new upstream version. However, "
1591 "this is only done in extreme situations, and you must always coordinate that "
1592 "with the security team beforehand."
1595 # type: Content of: <chapter><section><section><section><para>
1596 #. type: Content of: <chapter><section><section><section><para>
1599 "Related to this is another important guideline: always test your changes. "
1600 "If you have an exploit available, try it and see if it indeed succeeds on "
1601 "the unpatched package and fails on the fixed package. Test other, normal "
1602 "actions as well, as sometimes a security fix can break seemingly unrelated "
1603 "features in subtle ways."
1606 # type: Content of: <chapter><section><section><section><para>
1607 #. type: Content of: <chapter><section><section><section><para>
1610 "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your "
1611 "package which are not directly related to fixing the vulnerability. These "
1612 "will only need to be reverted, and this wastes time. If there are other "
1613 "bugs in your package that you would like to fix, make an upload to proposed-"
1614 "updates in the usual way, after the security advisory is issued. The "
1615 "security update mechanism is not a means for introducing changes to your "
1616 "package which would otherwise be rejected from the stable release, so please "
1617 "do not attempt to do this."
1620 # type: Content of: <chapter><section><section><section><para>
1621 #. type: Content of: <chapter><section><section><section><para>
1624 "Review and test your changes as much as possible. Check the differences "
1625 "from the previous version repeatedly (<command>interdiff</command> from the "
1626 "<systemitem role=\"package\">patchutils</systemitem> package and "
1627 "<command>debdiff</command> from <systemitem role=\"package\">devscripts</"
1628 "systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/> )."
1631 # type: Content of: <chapter><section><section><section><para>
1632 #. type: Content of: <chapter><section><section><section><para>
1634 msgid "Be sure to verify the following items:"
1637 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1640 "<emphasis role=\"strong\">Target the right distribution</emphasis> in your "
1641 "<filename>debian/changelog</filename>. For <literal>stable</literal> this "
1642 "is <literal>stable-security</literal> and for testing this is "
1643 "<literal>testing-security</literal>, and for the previous stable release, "
1644 "this is <literal>oldstable-security</literal>. Do not target "
1645 "<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
1646 "or <literal>stable</literal>!"
1649 # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1650 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1654 "The upload should have <emphasis role=\"strong\">urgency=high</emphasis>."
1655 msgstr "アップロードは urgency=high で行う必要があります。"
1657 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1660 "Make descriptive, meaningful changelog entries. Others will rely on them to "
1661 "determine whether a particular bug was fixed. Add <literal>closes:</"
1662 "literal> statements for any <emphasis role=\"strong\">Debian bugs</emphasis> "
1663 "filed. Always include an external reference, preferably a <emphasis role="
1664 "\"strong\">CVE identifier</emphasis>, so that it can be cross-referenced. "
1665 "However, if a CVE identifier has not yet been assigned, do not wait for it "
1666 "but continue the process. The identifier can be cross-referenced later."
1669 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1672 "Make sure the <emphasis role=\"strong\">version number</emphasis> is "
1673 "proper. It must be greater than the current package, but less than package "
1674 "versions in later distributions. If in doubt, test it with <literal>dpkg --"
1675 "compare-versions</literal>. Be careful not to re-use a version number that "
1676 "you have already used for a previous upload, or one that conflicts with a "
1677 "binNMU. The convention is to append <literal>+</"
1678 "literal><replaceable>codename</replaceable><literal>1</literal>, e.g. "
1679 "<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any "
1680 "subsequent uploads."
1683 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1686 "Unless the upstream source has been uploaded to <literal>security.debian.org "
1687 "</literal> before (by a previous security update), build the upload "
1688 "<emphasis role=\"strong\">with full upstream source</emphasis> "
1689 "(<literal>dpkg-buildpackage -sa</literal>). If there has been a previous "
1690 "upload to <literal>security.debian.org</literal> with the same upstream "
1691 "version, you may upload without upstream source (<literal> dpkg-buildpackage "
1695 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1698 "Be sure to use the <emphasis role=\"strong\">exact same <filename>*.orig.tar."
1699 "{gz,bz2}</filename></emphasis> as used in the normal archive, otherwise it "
1700 "is not possible to move the security fix into the main archives later."
1703 #. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
1706 "Build the package on a <emphasis role=\"strong\">clean system</emphasis> "
1707 "which only has packages installed from the distribution you are building "
1708 "for. If you do not have such a system yourself, you can use a debian.org "
1709 "machine (see <xref linkend=\"server-machines\"/> ) or setup a chroot (see "
1710 "<xref linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )."
1713 # type: Content of: <chapter><section><section><section><title>
1714 #. type: Content of: <chapter><section><section><section><title>
1716 msgid "Uploading the fixed package"
1719 # type: Content of: <chapter><section><section><section><para>
1720 #. type: Content of: <chapter><section><section><section><para>
1723 "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security "
1724 "upload queue (<literal>oldstable-security</literal>, <literal>stable-"
1725 "security </literal>, etc.) without prior authorization from the security "
1726 "team. If the package does not exactly meet the team's requirements, it will "
1727 "cause many problems and delays in dealing with the unwanted upload."
1730 # type: Content of: <chapter><section><section><section><para>
1731 #. type: Content of: <chapter><section><section><section><para>
1734 "Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to <literal> "
1735 "proposed-updates</literal> without coordinating with the security team. "
1736 "Packages from <literal>security.debian.org</literal> will be copied into the "
1737 "<literal>proposed-updates</literal> directory automatically. If a package "
1738 "with the same or a higher version number is already installed into the "
1739 "archive, the security update will be rejected by the archive system. That "
1740 "way, the stable distribution will end up without a security update for this "
1744 # type: Content of: <chapter><section><section><section><para>
1745 #. type: Content of: <chapter><section><section><section><para>
1748 "Once you have created and tested the new package and it has been approved by "
1749 "the security team, it needs to be uploaded so that it can be installed in "
1750 "the archives. For security uploads, the place to upload to is "
1751 "<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</"
1755 #. type: Content of: <chapter><section><section><section><para>
1758 "Once an upload to the security queue has been accepted, the package will "
1759 "automatically be built for all architectures and stored for verification by "
1760 "the security team."
1763 # type: Content of: <chapter><section><section><section><para>
1764 #. type: Content of: <chapter><section><section><section><para>
1767 "Uploads which are waiting for acceptance or verification are only accessible "
1768 "by the security team. This is necessary since there might be fixes for "
1769 "security problems that cannot be disclosed yet."
1772 # type: Content of: <chapter><section><section><section><para>
1773 #. type: Content of: <chapter><section><section><section><para>
1776 "If a member of the security team accepts a package, it will be installed on "
1777 "<literal>security.debian.org</literal> as well as proposed for the proper "
1778 "<replaceable>distribution</replaceable><literal>-proposed-updates</literal> "
1779 "on <literal>&ftp-master-host;</literal>."
1782 # type: Content of: <chapter><section><title>
1783 #. type: Content of: <chapter><section><title>
1785 msgid "Moving, removing, renaming, adopting, and orphaning packages"
1786 msgstr "パッケージの移動、削除、リネーム、変更、みなしご化"
1788 # type: Content of: <chapter><section><para>
1789 #. type: Content of: <chapter><section><para>
1792 "Some archive manipulation operations are not automated in the Debian upload "
1793 "process. These procedures should be manually followed by maintainers. This "
1794 "chapter gives guidelines on what to do in these cases."
1797 # type: Content of: <chapter><section><section><title>
1798 #. type: Content of: <chapter><section><section><title>
1800 msgid "Moving packages"
1803 # type: Content of: <chapter><section><section><para><footnote><para>
1804 #. type: Content of: <chapter><section><section><para><footnote><para>
1807 "See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
1808 "guidelines on what section a package belongs in."
1811 #. type: Content of: <chapter><section><section><para>
1814 "Sometimes a package will change its section. For instance, a package from "
1815 "the `non-free' section might be GPL'd in a later version, in which case the "
1816 "package should be moved to `main' or `contrib'.<placeholder type=\"footnote"
1820 #. type: Content of: <chapter><section><section><para>
1823 "If you need to change the section for one of your packages, change the "
1824 "package control information to place the package in the desired section, and "
1825 "re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian "
1826 "Policy Manual</ulink> for details). You must ensure that you include the "
1827 "<filename>.orig.tar.{gz,bz2}</filename> in your upload (even if you are not "
1828 "uploading a new upstream version), or it will not appear in the new section "
1829 "together with the rest of the package. If your new section is valid, it "
1830 "will be moved automatically. If it does not, then contact the ftpmasters in "
1831 "order to understand what happened."
1834 # type: Content of: <chapter><section><section><para>
1835 #. type: Content of: <chapter><section><section><para>
1838 "If, on the other hand, you need to change the <literal>subsection</literal> "
1839 "of one of your packages (e.g., ``devel'', ``admin''), the procedure is "
1840 "slightly different. Correct the subsection as found in the control file of "
1841 "the package, and re-upload that. Also, you'll need to get the override file "
1842 "updated, as described in <xref linkend=\"override-file\"/> ."
1845 # type: Content of: <chapter><section><section><title>
1846 #. type: Content of: <chapter><section><section><title>
1848 msgid "Removing packages"
1851 # type: Content of: <chapter><section><section><para>
1852 #. type: Content of: <chapter><section><section><para>
1855 "If for some reason you want to completely remove a package (say, if it is an "
1856 "old compatibility library which is no longer required), you need to file a "
1857 "bug against <literal>ftp.debian.org</literal> asking that the package be "
1858 "removed; as all bugs, this bug should normally have normal severity. The "
1859 "bug title should be in the form <literal>RM: <replaceable>package </"
1860 "replaceable> <replaceable>[architecture list]</replaceable> -- "
1861 "<replaceable>reason</replaceable></literal>, where <replaceable>package</"
1862 "replaceable> is the package to be removed and <replaceable>reason</"
1863 "replaceable> is a short summary of the reason for the removal request. "
1864 "<replaceable>[architecture list]</replaceable> is optional and only needed "
1865 "if the removal request only applies to some architectures, not all. Note "
1866 "that the <command>reportbug</command> will create a title conforming to "
1867 "these rules when you use it to report a bug against the <literal> ftp.debian."
1868 "org</literal> pseudo-package."
1871 # type: Content of: <chapter><section><section><para>
1872 #. type: Content of: <chapter><section><section><para>
1875 "If you want to remove a package you maintain, you should note this in the "
1876 "bug title by prepending <literal>ROM</literal> (Request Of Maintainer). "
1877 "There are several other standard acronyms used in the reasoning for a "
1878 "package removal, see <ulink url=\"http://&ftp-master-host;/removals.html\"></"
1879 "ulink> for a complete list. That page also provides a convenient overview of "
1880 "pending removal requests."
1883 # type: Content of: <chapter><section><section><para>
1884 #. type: Content of: <chapter><section><section><para>
1887 "Note that removals can only be done for the <literal>unstable </literal>, "
1888 "<literal>experimental</literal> and <literal>stable </literal> "
1889 "distribution. Packages are not removed from <literal>testing</literal> "
1890 "directly. Rather, they will be removed automatically after the package has "
1891 "been removed from <literal>unstable</literal> and no package in "
1892 "<literal>testing </literal> depends on it."
1895 # type: Content of: <chapter><section><section><para>
1896 #. type: Content of: <chapter><section><section><para>
1899 "There is one exception when an explicit removal request is not necessary: If "
1900 "a (source or binary) package is an orphan, it will be removed semi-"
1901 "automatically. For a binary-package, this means if there is no longer any "
1902 "source package producing this binary package; if the binary package is just "
1903 "no longer produced on some architectures, a removal request is still "
1904 "necessary. For a source-package, this means that all binary packages it "
1905 "refers to have been taken over by another source package."
1908 # type: Content of: <chapter><section><section><para>
1909 #. type: Content of: <chapter><section><section><para>
1912 "In your removal request, you have to detail the reasons justifying the "
1913 "request. This is to avoid unwanted removals and to keep a trace of why a "
1914 "package has been removed. For example, you can provide the name of the "
1915 "package that supersedes the one to be removed."
1918 # type: Content of: <chapter><section><section><para>
1919 #. type: Content of: <chapter><section><section><para>
1922 "Usually you only ask for the removal of a package maintained by yourself. "
1923 "If you want to remove another package, you have to get the approval of its "
1924 "maintainer. Should the package be orphaned and thus have no maintainer, you "
1925 "should first discuss the removal request on &email-debian-qa;. If there is a "
1926 "consensus that the package should be removed, you should reassign and "
1927 "retitle the <literal>O:</literal> bug filed against the <literal>wnpp</"
1928 "literal> package instead of filing a new bug as removal request."
1931 # type: Content of: <chapter><section><section><para>
1932 #. type: Content of: <chapter><section><section><para>
1935 "Further information relating to these and other package removal related "
1936 "topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals"
1937 "\"></ulink> and <ulink url=\"&url-debian-qa;howto-remove.html\"></ulink>."
1940 # type: Content of: <chapter><section><section><para>
1941 #. type: Content of: <chapter><section><section><para>
1944 "If in doubt concerning whether a package is disposable, email &email-debian-"
1945 "devel; asking for opinions. Also of interest is the <command>apt-cache</"
1946 "command> program from the <systemitem role=\"package\">apt</systemitem> "
1947 "package. When invoked as <literal>apt-cache showpkg <replaceable>package</"
1948 "replaceable></literal>, the program will show details for "
1949 "<replaceable>package</replaceable>, including reverse depends. Other useful "
1950 "programs include <literal>apt-cache rdepends</literal>, <command>apt-"
1951 "rdepends</command>, <command>build-rdeps</command> (in the <systemitem role="
1952 "\"package\">devscripts</systemitem> package) and <command>grep-dctrl</"
1953 "command>. Removal of orphaned packages is discussed on &email-debian-qa;."
1956 #. type: Content of: <chapter><section><section><para>
1959 "Once the package has been removed, the package's bugs should be handled. "
1960 "They should either be reassigned to another package in the case where the "
1961 "actual code has evolved into another package (e.g. <literal>libfoo12</"
1962 "literal> was removed because <literal>libfoo13</literal> supersedes it) or "
1963 "closed if the software is simply no longer part of Debian. When closing the "
1964 "bugs, to avoid marking the bugs as fixed in versions of the packages in "
1965 "previous Debian releases, they should be marked as fixed in the version "
1966 "<literal><most-recent-version-ever-in-Debian>+rm</literal>."
1969 # type: Content of: <chapter><section><section><section><title>
1970 #. type: Content of: <chapter><section><section><section><title>
1972 msgid "Removing packages from <filename>Incoming</filename>"
1973 msgstr "<filename>Incoming</filename> からパッケージを削除する"
1975 # type: Content of: <chapter><section><section><section><para>
1976 #. type: Content of: <chapter><section><section><section><para>
1979 "In the past, it was possible to remove packages from <filename>incoming</"
1980 "filename>. However, with the introduction of the new incoming system, this "
1981 "is no longer possible. Instead, you have to upload a new revision of your "
1982 "package with a higher version than the package you want to replace. Both "
1983 "versions will be installed in the archive but only the higher version will "
1984 "actually be available in <literal>unstable</literal> since the previous "
1985 "version will immediately be replaced by the higher. However, if you do "
1986 "proper testing of your packages, the need to replace a package should not "
1987 "occur too often anyway."
1990 # type: Content of: <chapter><section><section><title>
1991 #. type: Content of: <chapter><section><section><title>
1993 msgid "Replacing or renaming packages"
1994 msgstr "パッケージをリプレースあるいはリネームする"
1996 # type: Content of: <chapter><section><section><para>
1997 #. type: Content of: <chapter><section><section><para>
2000 "When the upstream maintainers for one of your packages chose to rename their "
2001 "software (or you made a mistake naming your package), you should follow a "
2002 "two-step process to rename it. In the first step, change the "
2003 "<filename>debian/control</filename> file to reflect the new name and to "
2004 "replace, provide and conflict with the obsolete package name (see the <ulink "
2005 "url=\"&url-debian-policy;\"> Debian Policy Manual</ulink> for details). "
2006 "Please note that you should only add a <literal>Provides</literal> relation "
2007 "if all packages depending on the obsolete package name continue to work "
2008 "after the renaming. Once you've uploaded the package and the package has "
2009 "moved into the archive, file a bug against <literal> ftp.debian.org</"
2010 "literal> asking to remove the package with the obsolete name (see <xref "
2011 "linkend=\"removing-pkgs\"/>). Do not forget to properly reassign the "
2012 "package's bugs at the same time."
2015 #. type: Content of: <chapter><section><section><para>
2018 "At other times, you may make a mistake in constructing your package and wish "
2019 "to replace it. The only way to do this is to increase the version number "
2020 "and upload a new version. The old version will be expired in the usual "
2021 "manner. Note that this applies to each part of your package, including the "
2022 "sources: if you wish to replace the upstream source tarball of your package, "
2023 "you will need to upload it with a different version. An easy possibility is "
2024 "to replace <filename>foo_1.00.orig.tar.gz</filename> with <filename>foo_1.00"
2025 "+0.orig.tar.gz</filename> or <filename>foo_1.00.orig.tar.bz2</filename>. "
2026 "This restriction gives each file on the ftp site a unique name, which helps "
2027 "to ensure consistency across the mirror network."
2030 # type: Content of: <chapter><section><section><title>
2031 #. type: Content of: <chapter><section><section><title>
2033 msgid "Orphaning a package"
2034 msgstr "パッケージをみなしご化する"
2036 # type: Content of: <chapter><section><section><para>
2037 #. type: Content of: <chapter><section><section><para>
2040 "If you can no longer maintain a package, you need to inform others, and see "
2041 "that the package is marked as orphaned. You should set the package "
2042 "maintainer to <literal>Debian QA Group &orphan-address;</literal> and submit "
2043 "a bug report against the pseudo package <systemitem role=\"package\">wnpp</"
2044 "systemitem>. The bug report should be titled <literal>O: "
2045 "<replaceable>package</replaceable> -- <replaceable>short description</"
2046 "replaceable></literal> indicating that the package is now orphaned. The "
2047 "severity of the bug should be set to <literal>normal</literal>; if the "
2048 "package has a priority of standard or higher, it should be set to "
2049 "important. If you feel it's necessary, send a copy to &email-debian-devel; "
2050 "by putting the address in the X-Debbugs-CC: header of the message (no, don't "
2051 "use CC:, because that way the message's subject won't indicate the bug "
2055 # type: Content of: <chapter><section><section><para>
2056 #. type: Content of: <chapter><section><section><para>
2059 "If you just intend to give the package away, but you can keep maintainership "
2060 "for the moment, then you should instead submit a bug against <systemitem "
2061 "role=\"package\">wnpp</systemitem> and title it <literal>RFA: "
2062 "<replaceable>package</replaceable> -- <replaceable>short description</"
2063 "replaceable></literal>. <literal>RFA</literal> stands for <literal>Request "
2064 "For Adoption</literal>."
2067 # type: Content of: <chapter><section><section><para>
2068 #. type: Content of: <chapter><section><section><para>
2071 "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>."
2073 "より詳細な情報は <ulink url=\"&url-wnpp;\">WNPP ウェブページ</ulink>にありま"
2076 # type: Content of: <chapter><section><section><title>
2077 #. type: Content of: <chapter><section><section><title>
2079 msgid "Adopting a package"
2080 msgstr "パッケージに変更を加える"
2082 # type: Content of: <chapter><section><section><para>
2083 #. type: Content of: <chapter><section><section><para>
2086 "A list of packages in need of a new maintainer is available in the <ulink "
2087 "url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</"
2088 "ulink>. If you wish to take over maintenance of any of the packages listed "
2089 "in the WNPP, please take a look at the aforementioned page for information "
2093 # type: Content of: <chapter><section><section><para>
2094 #. type: Content of: <chapter><section><section><para>
2097 "It is not OK to simply take over a package that you feel is neglected — that "
2098 "would be package hijacking. You can, of course, contact the current "
2099 "maintainer and ask them if you may take over the package. If you have "
2100 "reason to believe a maintainer has gone AWOL (absent without leave), see "
2101 "<xref linkend=\"mia-qa\"/> ."
2104 # type: Content of: <chapter><section><section><para>
2105 #. type: Content of: <chapter><section><section><para>
2108 "Generally, you may not take over the package without the assent of the "
2109 "current maintainer. Even if they ignore you, that is still not grounds to "
2110 "take over a package. Complaints about maintainers should be brought up on "
2111 "the developers' mailing list. If the discussion doesn't end with a positive "
2112 "conclusion, and the issue is of a technical nature, consider bringing it to "
2113 "the attention of the technical committee (see the <ulink url=\"&url-tech-"
2114 "ctte;\">technical committee web page</ulink> for more information)."
2117 # type: Content of: <chapter><section><section><para>
2118 #. type: Content of: <chapter><section><section><para>
2121 "If you take over an old package, you probably want to be listed as the "
2122 "package's official maintainer in the bug system. This will happen "
2123 "automatically once you upload a new version with an updated "
2124 "<literal>Maintainer:</literal> field, although it can take a few hours after "
2125 "the upload is done. If you do not expect to upload a new version for a "
2126 "while, you can use <xref linkend=\"pkg-tracking-system\"/> to get the bug "
2127 "reports. However, make sure that the old maintainer has no problem with the "
2128 "fact that they will continue to receive the bugs during that time."
2131 # type: Content of: <chapter><section><title>
2132 #. type: Content of: <chapter><section><title>
2134 msgid "Porting and being ported"
2137 # type: Content of: <chapter><section><para>
2138 #. type: Content of: <chapter><section><para>
2141 "Debian supports an ever-increasing number of architectures. Even if you are "
2142 "not a porter, and you don't use any architecture but one, it is part of your "
2143 "duty as a maintainer to be aware of issues of portability. Therefore, even "
2144 "if you are not a porter, you should read most of this chapter."
2147 # type: Content of: <chapter><section><para>
2148 #. type: Content of: <chapter><section><para>
2151 "Porting is the act of building Debian packages for architectures that are "
2152 "different from the original architecture of the package maintainer's binary "
2153 "package. It is a unique and essential activity. In fact, porters do most "
2154 "of the actual compiling of Debian packages. For instance, when a maintainer "
2155 "uploads a (portable) source packages with binaries for the <literal>i386 </"
2156 "literal> architecture, it will be built for each of the other architectures, "
2157 "amounting to &number-of-arches; more builds."
2160 # type: Content of: <chapter><section><section><title>
2161 #. type: Content of: <chapter><section><section><title>
2163 msgid "Being kind to porters"
2166 # type: Content of: <chapter><section><section><para>
2167 #. type: Content of: <chapter><section><section><para>
2170 "Porters have a difficult and unique task, since they are required to deal "
2171 "with a large volume of packages. Ideally, every source package should build "
2172 "right out of the box. Unfortunately, this is often not the case. This "
2173 "section contains a checklist of ``gotchas'' often committed by Debian "
2174 "maintainers — common problems which often stymie porters, and make their "
2175 "jobs unnecessarily difficult."
2178 # type: Content of: <chapter><section><section><para>
2179 #. type: Content of: <chapter><section><section><para>
2182 "The first and most important thing is to respond quickly to bug or issues "
2183 "raised by porters. Please treat porters with courtesy, as if they were in "
2184 "fact co-maintainers of your package (which, in a way, they are). Please be "
2185 "tolerant of succinct or even unclear bug reports; do your best to hunt down "
2186 "whatever the problem is."
2189 # type: Content of: <chapter><section><section><para>
2190 #. type: Content of: <chapter><section><section><para>
2193 "By far, most of the problems encountered by porters are caused by "
2194 "<emphasis>packaging bugs</emphasis> in the source packages. Here is a "
2195 "checklist of things you should check or be aware of."
2198 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2199 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2202 "Make sure that your <literal>Build-Depends</literal> and <literal>Build-"
2203 "Depends-Indep</literal> settings in <filename>debian/control</filename> are "
2204 "set properly. The best way to validate this is to use the <systemitem role="
2205 "\"package\">debootstrap</systemitem> package to create an <literal>unstable</"
2206 "literal> chroot environment (see <xref linkend=\"debootstrap\"/> ). Within "
2207 "that chrooted environment, install the <systemitem role=\"package\">build-"
2208 "essential</systemitem> package and any package dependencies mentioned in "
2209 "<literal>Build-Depends</literal> and/or <literal>Build-Depends-Indep</"
2210 "literal>. Finally, try building your package within that chrooted "
2211 "environment. These steps can be automated by the use of the "
2212 "<command>pbuilder</command> program which is provided by the package of the "
2213 "same name (see <xref linkend=\"pbuilder\"/> )."
2216 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2217 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2220 "If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
2221 "of assistance (see <xref linkend=\"dpkg-depcheck\"/> )."
2224 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2225 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2228 "See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
2229 "instructions on setting build dependencies."
2232 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2233 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2236 "Don't set architecture to a value other than <literal>all</literal> or "
2237 "<literal>any</literal> unless you really mean it. In too many cases, "
2238 "maintainers don't follow the instructions in the <ulink url=\"&url-debian-"
2239 "policy;\">Debian Policy Manual</ulink>. Setting your architecture to only "
2240 "one architecture (such as <literal>i386</literal> or <literal>amd64</"
2241 "literal>) is usually incorrect."
2244 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2245 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2248 "Make sure your source package is correct. Do <literal>dpkg-source -x "
2249 "<replaceable>package</replaceable>.dsc</literal> to make sure your source "
2250 "package unpacks properly. Then, in there, try building your package from "
2251 "scratch with <command>dpkg-buildpackage</command>."
2254 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2255 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2258 "Make sure you don't ship your source package with the <filename>debian/"
2259 "files</filename> or <filename>debian/substvars</filename> files. They "
2260 "should be removed by the <literal>clean</literal> target of <filename>debian/"
2264 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2265 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2268 "Make sure you don't rely on locally installed or hacked configurations or "
2269 "programs. For instance, you should never be calling programs in <filename>/"
2270 "usr/local/bin</filename> or the like. Try not to rely on programs being "
2271 "setup in a special way. Try building your package on another machine, even "
2272 "if it's the same architecture."
2275 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2276 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2279 "Don't depend on the package you're building being installed already (a sub-"
2280 "case of the above issue). There are, of course, exceptions to this rule, but "
2281 "be aware that any case like this needs manual bootstrapping and cannot be "
2282 "done by automated package builders."
2285 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2286 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2289 "Don't rely on the compiler being a certain version, if possible. If not, "
2290 "then make sure your build dependencies reflect the restrictions, although "
2291 "you are probably asking for trouble, since different architectures sometimes "
2292 "standardize on different compilers."
2295 # type: Content of: <chapter><section><section><orderedlist><listitem><para>
2296 #. type: Content of: <chapter><section><section><orderedlist><listitem><para>
2299 "Make sure your debian/rules contains separate <literal>binary-arch</literal> "
2300 "and <literal>binary-indep</literal> targets, as the Debian Policy Manual "
2301 "requires. Make sure that both targets work independently, that is, that you "
2302 "can call the target without having called the other before. To test this, "
2303 "try to run <command>dpkg-buildpackage -B</command>."
2306 # type: Content of: <chapter><section><section><title>
2307 #. type: Content of: <chapter><section><section><title>
2309 msgid "Guidelines for porter uploads"
2312 # type: Content of: <chapter><section><section><para>
2313 #. type: Content of: <chapter><section><section><para>
2316 "If the package builds out of the box for the architecture to be ported to, "
2317 "you are in luck and your job is easy. This section applies to that case; it "
2318 "describes how to build and upload your binary package so that it is properly "
2319 "installed into the archive. If you do have to patch the package in order to "
2320 "get it to compile for the other architecture, you are actually doing a "
2321 "source NMU, so consult <xref linkend=\"nmu-guidelines\"/> instead."
2324 # type: Content of: <chapter><section><section><para>
2325 #. type: Content of: <chapter><section><section><para>
2328 "For a porter upload, no changes are being made to the source. You do not "
2329 "need to touch any of the files in the source package. This includes "
2330 "<filename>debian/changelog</filename>."
2333 # type: Content of: <chapter><section><section><para>
2334 #. type: Content of: <chapter><section><section><para>
2337 "The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-"
2338 "buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of "
2339 "course, set <replaceable>porter-email</replaceable> to your email address. "
2340 "This will do a binary-only build of only the architecture-dependent portions "
2341 "of the package, using the <literal>binary-arch</literal> target in "
2342 "<filename>debian/rules </filename>."
2345 # type: Content of: <chapter><section><section><para>
2346 #. type: Content of: <chapter><section><section><para>
2349 "If you are working on a Debian machine for your porting efforts and you need "
2350 "to sign your upload locally for its acceptance in the archive, you can run "
2351 "<command>debsign</command> on your <filename>.changes</filename> file to "
2352 "have it signed conveniently, or use the remote signing mode of <command>dpkg-"
2356 # type: Content of: <chapter><section><section><section><title>
2357 #. type: Content of: <chapter><section><section><section><title>
2359 msgid "Recompilation or binary-only NMU"
2362 # type: Content of: <chapter><section><section><section><para>
2363 #. type: Content of: <chapter><section><section><section><para>
2366 "Sometimes the initial porter upload is problematic because the environment "
2367 "in which the package was built was not good enough (outdated or obsolete "
2368 "library, bad compiler, ...). Then you may just need to recompile it in an "
2369 "updated environment. However, you have to bump the version number in this "
2370 "case, so that the old bad package can be replaced in the Debian archive "
2371 "(<command>dak</command> refuses to install new packages if they don't have a "
2372 "version number greater than the currently available one)."
2375 # type: Content of: <chapter><section><section><section><para>
2376 #. type: Content of: <chapter><section><section><section><para>
2379 "You have to make sure that your binary-only NMU doesn't render the package "
2380 "uninstallable. This could happen when a source package generates arch-"
2381 "dependent and arch-independent packages that have inter-dependencies "
2382 "generated using dpkg's substitution variable <literal>$(Source-Version) </"
2386 # type: Content of: <chapter><section><section><section><para>
2387 #. type: Content of: <chapter><section><section><section><para>
2390 "Despite the required modification of the changelog, these are called binary-"
2391 "only NMUs — there is no need in this case to trigger all other architectures "
2392 "to consider themselves out of date or requiring recompilation."
2395 # type: Content of: <chapter><section><section><section><para>
2396 #. type: Content of: <chapter><section><section><section><para>
2399 "Such recompilations require special ``magic'' version numbering, so that the "
2400 "archive maintenance tools recognize that, even though there is a new Debian "
2401 "version, there is no corresponding source update. If you get this wrong, "
2402 "the archive maintainers will reject your upload (due to lack of "
2403 "corresponding source code)."
2406 # type: Content of: <chapter><section><section><section><para><footnote><para>
2407 #. type: Content of: <chapter><section><section><section><para><footnote><para>
2410 "In the past, such NMUs used the third-level number on the Debian part of the "
2411 "revision to denote their recompilation-only status; however, this syntax was "
2412 "ambiguous with native packages and did not allow proper ordering of "
2413 "recompile-only NMUs, source NMUs, and security NMUs on the same package, and "
2414 "has therefore been abandoned in favor of this new syntax."
2417 #. type: Content of: <chapter><section><section><section><para>
2420 "The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
2421 "appended to the package version number, following the form <literal> "
2422 "b<replaceable>number</replaceable></literal>. For instance, if the latest "
2423 "version you are recompiling against was version <literal>2.9-3</literal>, "
2424 "your binary-only NMU should carry a version of <literal>2.9-3+b1</literal>. "
2425 "If the latest version was <literal>3.4+b1 </literal> (i.e, a native package "
2426 "with a previous recompilation NMU), your binary-only NMU should have a "
2427 "version number of <literal>3.4+b2</literal>. <placeholder type=\"footnote\" "
2431 # type: Content of: <chapter><section><section><section><para>
2432 #. type: Content of: <chapter><section><section><section><para>
2435 "Similar to initial porter uploads, the correct way of invoking <command>dpkg-"
2436 "buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only "
2437 "build the architecture-dependent parts of the package."
2440 # type: Content of: <chapter><section><section><section><title>
2441 #. type: Content of: <chapter><section><section><section><title>
2443 msgid "When to do a source NMU if you are a porter"
2446 # type: Content of: <chapter><section><section><section><para>
2447 #. type: Content of: <chapter><section><section><section><para>
2450 "Porters doing a source NMU generally follow the guidelines found in <xref "
2451 "linkend=\"nmu\"/> , just like non-porters. However, it is expected that the "
2452 "wait cycle for a porter's source NMU is smaller than for a non-porter, since "
2453 "porters have to cope with a large quantity of packages. Again, the "
2454 "situation varies depending on the distribution they are uploading to. It "
2455 "also varies whether the architecture is a candidate for inclusion into the "
2456 "next stable release; the release managers decide and announce which "
2457 "architectures are candidates."
2460 # type: Content of: <chapter><section><section><section><para>
2461 #. type: Content of: <chapter><section><section><section><para>
2464 "If you are a porter doing an NMU for <literal>unstable</literal>, the above "
2465 "guidelines for porting should be followed, with two variations. Firstly, "
2466 "the acceptable waiting period — the time between when the bug is submitted "
2467 "to the BTS and when it is OK to do an NMU — is seven days for porters "
2468 "working on the <literal>unstable</literal> distribution. This period can be "
2469 "shortened if the problem is critical and imposes hardship on the porting "
2470 "effort, at the discretion of the porter group. (Remember, none of this is "
2471 "Policy, just mutually agreed upon guidelines.) For uploads to "
2472 "<literal>stable</literal> or <literal>testing </literal>, please coordinate "
2473 "with the appropriate release team first."
2476 # type: Content of: <chapter><section><section><section><para>
2477 #. type: Content of: <chapter><section><section><section><para>
2480 "Secondly, porters doing source NMUs should make sure that the bug they "
2481 "submit to the BTS should be of severity <literal>serious</literal> or "
2482 "greater. This ensures that a single source package can be used to compile "
2483 "every supported Debian architecture by release time. It is very important "
2484 "that we have one version of the binary and source package for all "
2485 "architectures in order to comply with many licenses."
2488 # type: Content of: <chapter><section><section><section><para>
2489 #. type: Content of: <chapter><section><section><section><para>
2492 "Porters should try to avoid patches which simply kludge around bugs in the "
2493 "current version of the compile environment, kernel, or libc. Sometimes such "
2494 "kludges can't be helped. If you have to kludge around compiler bugs and the "
2495 "like, make sure you <literal>#ifdef</literal> your work properly; also, "
2496 "document your kludge so that people know to remove it once the external "
2497 "problems have been fixed."
2500 # type: Content of: <chapter><section><section><section><para>
2501 #. type: Content of: <chapter><section><section><section><para>
2504 "Porters may also have an unofficial location where they can put the results "
2505 "of their work during the waiting period. This helps others running the port "
2506 "have the benefit of the porter's work, even during the waiting period. Of "
2507 "course, such locations have no official blessing or status, so buyer beware."
2510 # type: Content of: <chapter><section><section><title>
2511 #. type: Content of: <chapter><section><section><title>
2513 msgid "Porting infrastructure and automation"
2516 # type: Content of: <chapter><section><section><para>
2517 #. type: Content of: <chapter><section><section><para>
2520 "There is infrastructure and several tools to help automate package porting. "
2521 "This section contains a brief overview of this automation and porting to "
2522 "these tools; see the package documentation or references for full "
2526 # type: Content of: <chapter><section><section><section><title>
2527 #. type: Content of: <chapter><section><section><section><title>
2529 msgid "Mailing lists and web pages"
2530 msgstr "メーリングリストとウェブページ"
2532 # type: Content of: <chapter><section><section><section><para>
2533 #. type: Content of: <chapter><section><section><section><para>
2536 "Web pages containing the status of each port can be found at <ulink url="
2537 "\"&url-debian-ports;\"></ulink>."
2540 # type: Content of: <chapter><section><section><section><para>
2541 #. type: Content of: <chapter><section><section><section><para>
2544 "Each port of Debian has a mailing list. The list of porting mailing lists "
2545 "can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These "
2546 "lists are used to coordinate porters, and to connect the users of a given "
2547 "port with the porters."
2550 # type: Content of: <chapter><section><section><section><title>
2551 #. type: Content of: <chapter><section><section><section><title>
2553 msgid "Porter tools"
2556 # type: Content of: <chapter><section><section><section><para>
2557 #. type: Content of: <chapter><section><section><section><para>
2560 "Descriptions of several porting tools can be found in <xref linkend=\"tools-"
2564 # type: Content of: <chapter><section><section><section><title>
2565 #. type: Content of: <chapter><section><section><section><title>
2567 msgid "<systemitem role=\"package\">wanna-build</systemitem>"
2570 # type: Content of: <chapter><section><section><section><para>
2571 #. type: Content of: <chapter><section><section><section><para>
2574 "The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
2575 "a distributed, client-server build distribution system. It is usually used "
2576 "in conjunction with build daemons running the <systemitem role=\"package"
2577 "\">buildd </systemitem> program. <literal>Build daemons</literal> are "
2578 "``slave'' hosts which contact the central <systemitem role=\"package\"> "
2579 "wanna-build</systemitem> system to receive a list of packages that need to "
2583 # type: Content of: <chapter><section><section><section><para>
2584 #. type: Content of: <chapter><section><section><section><para>
2587 "<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
2588 "as a package; however, all Debian porting efforts are using it for automated "
2589 "package building. The tool used to do the actual package builds, "
2590 "<systemitem role=\"package\">sbuild</systemitem> is available as a package, "
2591 "see its description in <xref linkend=\"sbuild\"/> . Please note that the "
2592 "packaged version is not the same as the one used on build daemons, but it is "
2593 "close enough to reproduce problems."
2596 # type: Content of: <chapter><section><section><section><para>
2597 #. type: Content of: <chapter><section><section><section><para>
2600 "Most of the data produced by <systemitem role=\"package\">wanna-build </"
2601 "systemitem> which is generally useful to porters is available on the web at "
2602 "<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated "
2603 "statistics, queueing information and logs for build attempts."
2606 # type: Content of: <chapter><section><section><section><para>
2607 #. type: Content of: <chapter><section><section><section><para>
2610 "We are quite proud of this system, since it has so many possible uses. "
2611 "Independent development groups can use the system for different sub-flavors "
2612 "of Debian, which may or may not really be of general interest (for instance, "
2613 "a flavor of Debian built with <command>gcc</command> bounds checking). It "
2614 "will also enable Debian to recompile entire distributions quickly."
2617 #. type: Content of: <chapter><section><section><section><para>
2620 "The wanna-build team, in charge of the buildds, can be reached at "
2621 "<literal>debian-wb-team@lists.debian.org</literal>. To determine who (wanna-"
2622 "build team, release team) and how (mail, BTS) to contact, refer to <ulink "
2623 "url=\"&url-wb-team;\"></ulink>."
2626 #. type: Content of: <chapter><section><section><section><para>
2629 "When requesting binNMUs or give-backs (retries after a failed build), please "
2630 "use the format described at <ulink url=\"&url-release-wb;\"/>."
2633 # type: Content of: <chapter><section><section><title>
2634 #. type: Content of: <chapter><section><section><title>
2636 msgid "When your package is <emphasis>not</emphasis> portable"
2639 # type: Content of: <chapter><section><section><para>
2640 #. type: Content of: <chapter><section><section><para>
2643 "Some packages still have issues with building and/or working on some of the "
2644 "architectures supported by Debian, and cannot be ported at all, or not "
2645 "within a reasonable amount of time. An example is a package that is SVGA-"
2646 "specific (only available for <literal>i386</literal> and <literal>amd64</"
2647 "literal>), or uses other hardware-specific features not supported on all "
2651 # type: Content of: <chapter><section><section><para>
2652 #. type: Content of: <chapter><section><section><para>
2655 "In order to prevent broken packages from being uploaded to the archive, and "
2656 "wasting buildd time, you need to do a few things:"
2659 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2660 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2663 "First, make sure your package <emphasis>does</emphasis> fail to build on "
2664 "architectures that it cannot support. There are a few ways to achieve "
2665 "this. The preferred way is to have a small testsuite during build time that "
2666 "will test the functionality, and fail if it doesn't work. This is a good "
2667 "idea anyway, as this will prevent (some) broken uploads on all "
2668 "architectures, and also will allow the package to build as soon as the "
2669 "required functionality is available."
2672 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2673 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2676 "Additionally, if you believe the list of supported architectures is pretty "
2677 "constant, you should change <literal>any</literal> to a list of supported "
2678 "architectures in <filename>debian/control</filename>. This way, the build "
2679 "will fail also, and indicate this to a human reader without actually trying."
2682 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2685 "In order to prevent autobuilders from needlessly trying to build your "
2686 "package, it must be included in <filename>packages-arch-specific</filename>, "
2687 "a list used by the <command>wanna-build</command> script. The current "
2688 "version is available as <ulink url=\"&url-buildd-p-a-s;\"/>; please see the "
2689 "top of the file for whom to contact for changes."
2692 # type: Content of: <chapter><section><section><para>
2693 #. type: Content of: <chapter><section><section><para>
2696 "Please note that it is insufficient to only add your package to Packages-"
2697 "arch-specific without making it fail to build on unsupported architectures: "
2698 "A porter or any other person trying to build your package might accidently "
2699 "upload it without noticing it doesn't work. If in the past some binary "
2700 "packages were uploaded on unsupported architectures, request their removal "
2701 "by filing a bug against <systemitem role=\"package\">ftp.debian.org</"
2705 # type: Content of: <chapter><section><title>
2706 #. type: Content of: <chapter><section><title>
2708 msgid "Non-Maintainer Uploads (NMUs)"
2711 #. type: Content of: <chapter><section><para>
2714 "Every package has one or more maintainers. Normally, these are the people "
2715 "who work on and upload new versions of the package. In some situations, it "
2716 "is useful that other developers can upload a new version as well, for "
2717 "example if they want to fix a bug in a package they don't maintain, when the "
2718 "maintainer needs help to respond to issues. Such uploads are called "
2719 "<emphasis>Non-Maintainer Uploads (NMU)</emphasis>."
2722 # type: Content of: <chapter><section><section><title>
2723 #. type: Content of: <chapter><section><section><title>
2726 msgid "When and how to do an NMU"
2727 msgstr "誰が NMU 可能なのか"
2729 #. type: Content of: <chapter><section><section><para>
2731 msgid "Before doing an NMU, consider the following questions:"
2734 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2737 "Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
2738 "packaging style in NMUs is discouraged."
2741 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2744 "Did you give enough time to the maintainer? When was the bug reported to the "
2745 "BTS? Being busy for a week or two isn't unusual. Is the bug so severe that "
2746 "it needs to be fixed right now, or can it wait a few more days?"
2749 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2752 "How confident are you about your changes? Please remember the Hippocratic "
2753 "Oath: \"Above all, do no harm.\" It is better to leave a package with an "
2754 "open grave bug than applying a non-functional patch, or one that hides the "
2755 "bug instead of resolving it. If you are not 100% sure of what you did, it "
2756 "might be a good idea to seek advice from others. Remember that if you break "
2757 "something in your NMU, many people will be very unhappy about it."
2760 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2763 "Have you clearly expressed your intention to NMU, at least in the BTS? It is "
2764 "also a good idea to try to contact the maintainer by other means (private "
2768 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2771 "If the maintainer is usually active and responsive, have you tried to "
2772 "contact him? In general it should be considered preferable that a maintainer "
2773 "takes care of an issue himself and that he is given the chance to review and "
2774 "correct your patch, because he can be expected to be more aware of potential "
2775 "issues which an NMUer might miss. It is often a better use of everyone's "
2776 "time if the maintainer is given an opportunity to upload a fix on their own."
2779 #. type: Content of: <chapter><section><section><para>
2782 "When doing an NMU, you must first make sure that your intention to NMU is "
2783 "clear. Then, you must send a patch with the differences between the current "
2784 "package and your proposed NMU to the BTS. The <literal>nmudiff</literal> "
2785 "script in the <literal>devscripts</literal> package might be helpful."
2788 #. type: Content of: <chapter><section><section><para>
2791 "While preparing the patch, you should better be aware of any package-"
2792 "specific practices that the maintainer might be using. Taking them into "
2793 "account reduces the burden of getting your changes integrated back in the "
2794 "normal package workflow and thus increases the possibilities that that will "
2795 "happen. A good place where to look for for possible package-specific "
2796 "practices is <ulink url=\"&url-debian-policy;ch-source.html#s-readmesource"
2797 "\"><literal>debian/README.source</literal></ulink>."
2800 #. type: Content of: <chapter><section><section><para>
2803 "Unless you have an excellent reason not to do so, you must then give some "
2804 "time to the maintainer to react (for example, by uploading to the "
2805 "<literal>DELAYED</literal> queue). Here are some recommended values to use "
2809 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2811 msgid "Upload fixing only release-critical bugs older than 7 days: 2 days"
2814 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2816 msgid "Upload fixing only release-critical and important bugs: 5 days"
2819 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
2821 msgid "Other NMUs: 10 days"
2824 #. type: Content of: <chapter><section><section><para>
2827 "Those delays are only examples. In some cases, such as uploads fixing "
2828 "security issues, or fixes for trivial bugs that blocking a transition, it is "
2829 "desirable that the fixed package reaches <literal>unstable</literal> sooner."
2832 #. type: Content of: <chapter><section><section><para>
2835 "Sometimes, release managers decide to allow NMUs with shorter delays for a "
2836 "subset of bugs (e.g release-critical bugs older than 7 days). Also, some "
2837 "maintainers list themselves in the <ulink url=\"&url-low-threshold-nmu;"
2838 "\">Low Threshold NMU list</ulink>, and accept that NMUs are uploaded without "
2839 "delay. But even in those cases, it's still a good idea to give the "
2840 "maintainer a few days to react before you upload, especially if the patch "
2841 "wasn't available in the BTS before, or if you know that the maintainer is "
2845 #. type: Content of: <chapter><section><section><para>
2848 "After you upload an NMU, you are responsible for the possible problems that "
2849 "you might have introduced. You must keep an eye on the package (subscribing "
2850 "to the package on the PTS is a good way to achieve this)."
2853 #. type: Content of: <chapter><section><section><para>
2856 "This is not a license to perform NMUs thoughtlessly. If you NMU when it is "
2857 "clear that the maintainers are active and would have acknowledged a patch in "
2858 "a timely manner, or if you ignore the recommendations of this document, your "
2859 "upload might be a cause of conflict with the maintainer. You should always "
2860 "be prepared to defend the wisdom of any NMU you perform on its own merits."
2863 #. type: Content of: <chapter><section><section><title>
2865 msgid "NMUs and debian/changelog"
2868 #. type: Content of: <chapter><section><section><para>
2871 "Just like any other (source) upload, NMUs must add an entry to "
2872 "<literal>debian/changelog</literal>, telling what has changed with this "
2873 "upload. The first line of this entry must explicitely mention that this "
2874 "upload is an NMU, e.g.:"
2877 # type: Content of: <chapter><section><section><screen>
2878 #. type: Content of: <chapter><section><section><screen>
2881 msgid " * Non-maintainer upload.\n"
2882 msgstr "* Non-maintainer upload"
2884 #. type: Content of: <chapter><section><section><para>
2886 msgid "The way to version NMUs differs for native and non-native packages."
2889 #. type: Content of: <chapter><section><section><para>
2892 "If the package is a native package (without a debian revision in the version "
2893 "number), the version must be the version of the last maintainer upload, plus "
2894 "<literal>+nmu<replaceable>X</replaceable></literal>, where <replaceable>X</"
2895 "replaceable> is a counter starting at <literal>1</literal>. If the last "
2896 "upload was also an NMU, the counter should be increased. For example, if "
2897 "the current version is <literal>1.5</literal>, then an NMU would get version "
2898 "<literal>1.5+nmu1</literal>."
2901 #. type: Content of: <chapter><section><section><para>
2904 "If the package is a not a native package, you should add a minor version "
2905 "number to the debian revision part of the version number (the portion after "
2906 "the last hyphen). This extra number must start at 1. For example, if the "
2907 "current version is <literal>1.5-2</literal>, then an NMU would get version "
2908 "<literal>1.5-2.1</literal>. If a new upstream version is packaged in the "
2909 "NMU, the debian revision is set to <literal>0</literal>, for example "
2910 "<literal>1.6-0.1</literal>."
2913 #. type: Content of: <chapter><section><section><para>
2916 "In both cases, if the last upload was also an NMU, the counter should be "
2917 "increased. For example, if the current version is <literal>1.5+nmu3</"
2918 "literal> (a native package which has already been NMUed), the NMU would get "
2919 "version <literal>1.5+nmu4</literal>. ."
2922 #. type: Content of: <chapter><section><section><para>
2925 "A special versioning scheme is needed to avoid disrupting the maintainer's "
2926 "work, since using an integer for the Debian revision will potentially "
2927 "conflict with a maintainer upload already in preparation at the time of an "
2928 "NMU, or even one sitting in the ftp NEW queue. It also has the benefit of "
2929 "making it visually clear that a package in the archive was not made by the "
2930 "official maintainer."
2933 #. type: Content of: <chapter><section><section><para>
2936 "If you upload a package to testing or stable, you sometimes need to \"fork\" "
2937 "the version number tree. This is the case for security uploads, for "
2938 "example. For this, a version of the form <literal>+deb<replaceable>XY</"
2939 "replaceable>u<replaceable>Z</replaceable></literal> should be used, where "
2940 "<replaceable>X</replaceable> and <replaceable>Y</replaceable> are the major "
2941 "and minor release numbers, and <replaceable>Z</replaceable> is a counter "
2942 "starting at <literal>1</literal>. When the release number is not yet known "
2943 "(often the case for <literal>testing</literal>, at the beginning of release "
2944 "cycles), the lowest release number higher than the last stable release "
2945 "number must be used. For example, while Etch (Debian 4.0) is stable, a "
2946 "security NMU to stable for a package at version <literal>1.5-3</literal> "
2947 "would have version <literal>1.5-3+deb40u1</literal>, whereas a security NMU "
2948 "to Lenny would get version <literal>1.5-3+deb50u1</literal>. After the "
2949 "release of Lenny, security uploads to the <literal>testing</literal> "
2950 "distribution will be versioned <literal>+deb51uZ</literal>, until it is "
2951 "known whether that release will be Debian 5.1 or Debian 6.0 (if that becomes "
2952 "the case, uploads will be versioned as <literal>+deb60uZ</literal>."
2955 # type: Content of: <chapter><section><section><title>
2956 #. type: Content of: <chapter><section><section><title>
2959 msgid "Using the <literal>DELAYED/</literal> queue"
2960 msgstr "<literal>ftp-master</literal> にアップロードする"
2962 #. type: Content of: <chapter><section><section><para>
2965 "Having to wait for a response after you request permission to NMU is "
2966 "inefficient, because it costs the NMUer a context switch to come back to the "
2967 "issue. The <literal>DELAYED</literal> queue (see <xref linkend=\"delayed-"
2968 "incoming\"/>) allows the developer doing the NMU to perform all the "
2969 "necessary tasks at the same time. For instance, instead of telling the "
2970 "maintainer that you will upload the updated package in 7 days, you should "
2971 "upload the package to <literal>DELAYED/7</literal> and tell the maintainer "
2972 "that he has 7 days to react. During this time, the maintainer can ask you "
2973 "to delay the upload some more, or cancel your upload."
2976 #. type: Content of: <chapter><section><section><para>
2979 "The <literal>DELAYED</literal> queue should not be used to put additional "
2980 "pressure on the maintainer. In particular, it's important that you are "
2981 "available to cancel or delay the upload before the delay expires since the "
2982 "maintainer cannot cancel the upload himself."
2985 #. type: Content of: <chapter><section><section><para>
2988 "If you make an NMU to <literal>DELAYED</literal> and the maintainer updates "
2989 "his package before the delay expires, your upload will be rejected because a "
2990 "newer version is already available in the archive. Ideally, the maintainer "
2991 "will take care to include your proposed changes (or at least a solution for "
2992 "the problems they address) in that upload."
2995 #. type: Content of: <chapter><section><section><title>
2997 msgid "NMUs from the maintainer's point of view"
3000 #. type: Content of: <chapter><section><section><para>
3003 "When someone NMUs your package, this means they want to help you to keep it "
3004 "in good shape. This gives users fixed packages faster. You can consider "
3005 "asking the NMUer to become a co-maintainer of the package. Receiving an NMU "
3006 "on a package is not a bad thing; it just means that the package is "
3007 "interesting enough for other people to work on it."
3010 #. type: Content of: <chapter><section><section><para>
3013 "To acknowledge an NMU, include its changes and changelog entry in your next "
3014 "maintainer upload. If you do not acknowledge the NMU by including the NMU "
3015 "changelog entry in your changelog, the bugs will remain closed in the BTS "
3016 "but will be listed as affecting your maintainer version of the package."
3019 #. type: Content of: <chapter><section><section><title>
3021 msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
3024 #. type: Content of: <chapter><section><section><para>
3027 "The full name of an NMU is <emphasis>source NMU</emphasis>. There is also "
3028 "another type, namely the <emphasis>binary-only NMU</emphasis>, or "
3029 "<emphasis>binNMU</emphasis>. A binNMU is also a package upload by someone "
3030 "other than the package's maintainer. However, it is a binary-only upload."
3033 #. type: Content of: <chapter><section><section><para>
3036 "When a library (or other dependency) is updated, the packages using it may "
3037 "need to be rebuilt. Since no changes to the source are needed, the same "
3038 "source package is used."
3041 #. type: Content of: <chapter><section><section><para>
3044 "BinNMUs are usually triggered on the buildds by wanna-build. An entry is "
3045 "added to debian/changelog, explaining why the upload was needed and "
3046 "increasing the version number as described in <xref linkend=\"binary-only-nmu"
3047 "\"/>. This entry should not be included in the next upload."
3050 #. type: Content of: <chapter><section><section><para>
3053 "Buildds upload packages for their architecture to the archive as binary-only "
3054 "uploads. Strictly speaking, these are binNMUs. However, they are not "
3055 "normally called NMU, and they don't add an entry to debian/changelog."
3058 #. type: Content of: <chapter><section><section><title>
3060 msgid "NMUs vs QA uploads"
3063 #. type: Content of: <chapter><section><section><para>
3066 "NMUs are uploads of packages by somebody else than their assigned "
3067 "maintainer. There is another type of upload where the uploaded package is "
3068 "not yours: QA uploads. QA uploads are uploads of orphaned packages."
3071 #. type: Content of: <chapter><section><section><para>
3074 "QA uploads are very much like normal maintainer uploads: they may fix "
3075 "anything, even minor issues; the version numbering is normal, and there is "
3076 "no need to use a delayed upload. The difference is that you are not listed "
3077 "as the Maintainer or Uploader for the package. Also, the changelog entry of "
3078 "a QA upload has a special first line:"
3081 #. type: Content of: <chapter><section><section><screen>
3084 msgid " * QA upload.\n"
3087 #. type: Content of: <chapter><section><section><para>
3090 "If you want to do an NMU, and it seems that the maintainer is not active, it "
3091 "is wise to check if the package is orphaned (this information is displayed "
3092 "on the package's Package Tracking System page). When doing the first QA "
3093 "upload to an orphaned package, the maintainer should be set to "
3094 "<literal>Debian QA Group <packages@qa.debian.org></literal>. Orphaned "
3095 "packages which did not yet have a QA upload still have their old maintainer "
3096 "set. There is a list of them at <ulink url=\"&url-orphaned-not-qa;\"/>."
3099 #. type: Content of: <chapter><section><section><para>
3102 "Instead of doing a QA upload, you can also consider adopting the package by "
3103 "making yourself the maintainer. You don't need permission from anybody to "
3104 "adopt an orphaned package, you can just set yourself as maintainer and "
3105 "upload the new version (see <xref linkend=\"adopting\"/>)."
3108 # type: Content of: <chapter><section><title>
3109 #. type: Content of: <chapter><section><title>
3111 msgid "Collaborative maintenance"
3114 # type: Content of: <chapter><section><para>
3115 #. type: Content of: <chapter><section><para>
3118 "Collaborative maintenance is a term describing the sharing of Debian package "
3119 "maintenance duties by several people. This collaboration is almost always a "
3120 "good idea, since it generally results in higher quality and faster bug fix "
3121 "turnaround times. It is strongly recommended that packages with a priority "
3122 "of <literal>Standard</literal> or which are part of the base set have co-"
3126 # type: Content of: <chapter><section><para>
3127 #. type: Content of: <chapter><section><para>
3130 "Generally there is a primary maintainer and one or more co-maintainers. The "
3131 "primary maintainer is the person whose name is listed in the "
3132 "<literal>Maintainer</literal> field of the <filename>debian/control</"
3133 "filename> file. Co-maintainers are all the other maintainers, usually "
3134 "listed in the <literal>Uploaders</literal> field of the <filename>debian/"
3135 "control</filename> file."
3138 # type: Content of: <chapter><section><para>
3139 #. type: Content of: <chapter><section><para>
3142 "In its most basic form, the process of adding a new co-maintainer is quite "
3146 # type: Content of: <chapter><section><itemizedlist><listitem><para>
3147 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
3150 "Setup the co-maintainer with access to the sources you build the package "
3151 "from. Generally this implies you are using a network-capable version "
3152 "control system, such as <command>CVS</command> or <command>Subversion</"
3153 "command>. Alioth (see <xref linkend=\"alioth\"/> ) provides such tools, "
3157 # type: Content of: <chapter><section><itemizedlist><listitem><para>
3158 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
3161 "Add the co-maintainer's correct maintainer name and address to the "
3162 "<literal>Uploaders</literal> field in the first paragraph of the "
3163 "<filename>debian/control</filename> file."
3166 # type: Content of: <chapter><section><itemizedlist><listitem><screen>
3167 #. type: Content of: <chapter><section><itemizedlist><listitem><screen>
3170 msgid "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>\n"
3171 msgstr "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>"
3173 # type: Content of: <chapter><section><itemizedlist><listitem><para>
3174 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
3177 "Using the PTS (<xref linkend=\"pkg-tracking-system\"/> ), the co-maintainers "
3178 "should subscribe themselves to the appropriate source package."
3181 # type: Content of: <chapter><section><para>
3182 #. type: Content of: <chapter><section><para>
3185 "Another form of collaborative maintenance is team maintenance, which is "
3186 "recommended if you maintain several packages with the same group of "
3187 "developers. In that case, the Maintainer and Uploaders field of each "
3188 "package must be managed with care. It is recommended to choose between one "
3189 "of the two following schemes:"
3192 # type: Content of: <chapter><section><orderedlist><listitem><para>
3193 #. type: Content of: <chapter><section><orderedlist><listitem><para>
3196 "Put the team member mainly responsible for the package in the Maintainer "
3197 "field. In the Uploaders, put the mailing list address, and the team members "
3198 "who care for the package."
3201 # type: Content of: <chapter><section><orderedlist><listitem><para>
3202 #. type: Content of: <chapter><section><orderedlist><listitem><para>
3205 "Put the mailing list address in the Maintainer field. In the Uploaders "
3206 "field, put the team members who care for the package. In this case, you "
3207 "must make sure the mailing list accept bug reports without any human "
3208 "interaction (like moderation for non-subscribers)."
3211 # type: Content of: <chapter><section><para>
3212 #. type: Content of: <chapter><section><para>
3215 "In any case, it is a bad idea to automatically put all team members in the "
3216 "Uploaders field. It clutters the Developer's Package Overview listing (see "
3217 "<xref linkend=\"ddpo\"/> ) with packages one doesn't really care for, and "
3218 "creates a false sense of good maintenance."
3221 # type: Content of: <chapter><section><title>
3222 #. type: Content of: <chapter><section><title>
3224 msgid "The testing distribution"
3225 msgstr "テスト版ディストリビューション"
3227 # type: Content of: <chapter><section><section><title>
3228 #. type: Content of: <chapter><section><section><title>
3233 # type: Content of: <chapter><section><section><para>
3234 #. type: Content of: <chapter><section><section><para>
3237 "Packages are usually installed into the <literal>testing</literal> "
3238 "distribution after they have undergone some degree of <literal>testing</"
3239 "literal> in <literal>unstable</literal>."
3242 # type: Content of: <chapter><section><section><para>
3243 #. type: Content of: <chapter><section><section><para>
3246 "They must be in sync on all architectures and mustn't have dependencies that "
3247 "make them uninstallable; they also have to have generally no known release-"
3248 "critical bugs at the time they're installed into <literal>testing </"
3249 "literal>. This way, <literal>testing</literal> should always be close to "
3250 "being a release candidate. Please see below for details."
3253 # type: Content of: <chapter><section><section><title>
3254 #. type: Content of: <chapter><section><section><title>
3256 msgid "Updates from unstable"
3259 # type: Content of: <chapter><section><section><para>
3260 #. type: Content of: <chapter><section><section><para>
3263 "The scripts that update the <literal>testing</literal> distribution are run "
3264 "twice each day, right after the installation of the updated packages; these "
3265 "scripts are called <literal>britney</literal>. They generate the "
3266 "<filename>Packages</filename> files for the <literal>testing</literal> "
3267 "distribution, but they do so in an intelligent manner; they try to avoid any "
3268 "inconsistency and to use only non-buggy packages."
3271 # type: Content of: <chapter><section><section><para>
3272 #. type: Content of: <chapter><section><section><para>
3275 "The inclusion of a package from <literal>unstable</literal> is conditional "
3279 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3280 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3283 "The package must have been available in <literal>unstable</literal> for 2, 5 "
3284 "or 10 days, depending on the urgency (high, medium or low). Please note "
3285 "that the urgency is sticky, meaning that the highest urgency uploaded since "
3286 "the previous <literal>testing</literal> transition is taken into account. "
3287 "Those delays may be doubled during a freeze, or <literal>testing</literal> "
3288 "transitions may be switched off altogether;"
3291 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3292 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3295 "It must not have new release-critical bugs (RC bugs affecting the version "
3296 "available in <literal>unstable</literal>, but not affecting the version in "
3297 "<literal>testing</literal>);"
3300 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3301 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3304 "It must be available on all architectures on which it has previously been "
3305 "built in <literal>unstable</literal>. <xref linkend=\"dak-ls\"/> may be of "
3306 "interest to check that information;"
3309 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3310 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3313 "It must not break any dependency of a package which is already available in "
3314 "<literal>testing</literal>;"
3317 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3318 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3321 "The packages on which it depends must either be available in "
3322 "<literal>testing</literal> or they must be accepted into <literal>testing</"
3323 "literal> at the same time (and they will be if they fulfill all the "
3324 "necessary criteria);"
3327 # type: Content of: <chapter><section><section><para>
3328 #. type: Content of: <chapter><section><section><para>
3331 "To find out whether a package is progressing into <literal>testing</literal> "
3332 "or not, see the <literal>testing</literal> script output on the <ulink url="
3333 "\"&url-testing-maint;\">web page of the testing distribution</ulink>, or use "
3334 "the program <command>grep-excuses</command> which is in the <systemitem role="
3335 "\"package\">devscripts</systemitem> package. This utility can easily be "
3336 "used in a <citerefentry> <refentrytitle>crontab</refentrytitle> "
3337 "<manvolnum>5</manvolnum> </citerefentry> to keep yourself informed of the "
3338 "progression of your packages into <literal>testing</literal>."
3341 # type: Content of: <chapter><section><section><para>
3342 #. type: Content of: <chapter><section><section><para>
3345 "The <filename>update_excuses</filename> file does not always give the "
3346 "precise reason why the package is refused; you may have to find it on your "
3347 "own by looking for what would break with the inclusion of the package. The "
3348 "<ulink url=\"&url-testing-maint;\">testing web page</ulink> gives some more "
3349 "information about the usual problems which may be causing such troubles."
3352 # type: Content of: <chapter><section><section><para>
3353 #. type: Content of: <chapter><section><section><para>
3356 "Sometimes, some packages never enter <literal>testing</literal> because the "
3357 "set of inter-relationship is too complicated and cannot be sorted out by the "
3358 "scripts. See below for details."
3361 # type: Content of: <chapter><section><section><para>
3362 #. type: Content of: <chapter><section><section><para>
3365 "Some further dependency analysis is shown on <ulink url=\"http://release."
3366 "debian.org/migration/\"></ulink> — but be warned, this page also shows build "
3367 "dependencies which are not considered by britney."
3370 # type: Content of: <chapter><section><section><section><title>
3371 #. type: Content of: <chapter><section><section><section><title>
3376 # type: Content of: <chapter><section><section><section><para>
3377 #. FIXME: better rename this file than document rampant professionalism?
3378 #. type: Content of: <chapter><section><section><section><para>
3381 "For the <literal>testing</literal> migration script, outdated means: There "
3382 "are different versions in <literal>unstable</literal> for the release "
3383 "architectures (except for the architectures in fuckedarches; fuckedarches is "
3384 "a list of architectures that don't keep up (in <filename>update_out.py</"
3385 "filename>), but currently, it's empty). outdated has nothing whatsoever to "
3386 "do with the architectures this package has in <literal>testing</literal>."
3389 # type: Content of: <chapter><section><section><section><para>
3390 #. type: Content of: <chapter><section><section><section><para>
3392 msgid "Consider this example:"
3395 # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3396 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3397 #: pkgs.dbk:2398 pkgs.dbk:2431
3401 # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3402 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3403 #: pkgs.dbk:2399 pkgs.dbk:2432
3407 # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3408 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3409 #: pkgs.dbk:2404 pkgs.dbk:2438 pkgs.dbk:2500
3413 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3414 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3415 #: pkgs.dbk:2405 pkgs.dbk:2410 pkgs.dbk:2439 pkgs.dbk:2440 pkgs.dbk:2447
3419 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3420 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3421 #: pkgs.dbk:2406 pkgs.dbk:2441 pkgs.dbk:2446
3425 # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3426 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3427 #: pkgs.dbk:2409 pkgs.dbk:2444 pkgs.dbk:2501
3431 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3432 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3433 #: pkgs.dbk:2411 pkgs.dbk:2445
3437 # type: Content of: <chapter><section><section><section><para>
3438 #. type: Content of: <chapter><section><section><section><para>
3441 "The package is out of date on alpha in <literal>unstable</literal>, and will "
3442 "not go to <literal>testing</literal>. Removing the package would not help at "
3443 "all, the package is still out of date on <literal>alpha</literal>, and will "
3444 "not propagate to testing."
3447 # type: Content of: <chapter><section><section><section><para>
3448 #. type: Content of: <chapter><section><section><section><para>
3451 "However, if ftp-master removes a package in <literal>unstable</literal> "
3452 "(here on <literal>arm</literal>):"
3455 # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3456 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
3461 # type: Content of: <chapter><section><section><section><para>
3462 #. type: Content of: <chapter><section><section><section><para>
3465 "In this case, the package is up to date on all release architectures in "
3466 "<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
3467 "doesn't matter, as it's not a release architecture)."
3470 # type: Content of: <chapter><section><section><section><para>
3471 #. type: Content of: <chapter><section><section><section><para>
3474 "Sometimes, the question is raised if it is possible to allow packages in "
3475 "that are not yet built on all architectures: No. Just plainly no. (Except "
3476 "if you maintain glibc or so.)"
3479 # type: Content of: <chapter><section><section><section><title>
3480 #. type: Content of: <chapter><section><section><section><title>
3482 msgid "Removals from testing"
3485 # type: Content of: <chapter><section><section><section><para>
3486 #. type: Content of: <chapter><section><section><section><para>
3489 "Sometimes, a package is removed to allow another package in: This happens "
3490 "only to allow <emphasis>another</emphasis> package to go in if it's ready in "
3491 "every other sense. Suppose e.g. that <literal>a</literal> cannot be "
3492 "installed with the new version of <literal>b</literal>; then <literal>a</"
3493 "literal> may be removed to allow <literal>b</literal> in."
3496 # type: Content of: <chapter><section><section><section><para>
3497 #. type: Content of: <chapter><section><section><section><para>
3500 "Of course, there is another reason to remove a package from <literal>testing "
3501 "</literal>: It's just too buggy (and having a single RC-bug is enough to be "
3505 # type: Content of: <chapter><section><section><section><para>
3506 #. type: Content of: <chapter><section><section><section><para>
3509 "Furthermore, if a package has been removed from <literal>unstable</literal>, "
3510 "and no package in <literal>testing</literal> depends on it any more, then it "
3511 "will automatically be removed."
3514 # type: Content of: <chapter><section><section><section><title>
3515 #. type: Content of: <chapter><section><section><section><title>
3517 msgid "circular dependencies"
3520 # type: Content of: <chapter><section><section><section><para>
3521 #. type: Content of: <chapter><section><section><section><para>
3524 "A situation which is not handled very well by britney is if package "
3525 "<literal>a</literal> depends on the new version of package <literal>b</"
3526 "literal>, and vice versa."
3529 # type: Content of: <chapter><section><section><section><para>
3530 #. type: Content of: <chapter><section><section><section><para>
3532 msgid "An example of this is:"
3535 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3536 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3541 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3542 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3544 msgid "1; depends: b=1"
3545 msgstr "1; depends: b=1"
3547 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3548 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3550 msgid "2; depends: b=2"
3551 msgstr "2; depends: b=2"
3553 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3554 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3559 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3560 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3562 msgid "1; depends: a=1"
3563 msgstr "1; depends: a=1"
3565 # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3566 #. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
3568 msgid "2; depends: a=2"
3569 msgstr "2; depends: a=2"
3571 # type: Content of: <chapter><section><section><section><para>
3572 #. type: Content of: <chapter><section><section><section><para>
3575 "Neither package <literal>a</literal> nor package <literal>b</literal> is "
3576 "considered for update."
3579 # type: Content of: <chapter><section><section><section><para>
3580 #. type: Content of: <chapter><section><section><section><para>
3583 "Currently, this requires some manual hinting from the release team. Please "
3584 "contact them by sending mail to &email-debian-release; if this happens to "
3585 "one of your packages."
3588 # type: Content of: <chapter><section><section><section><title>
3589 #. type: Content of: <chapter><section><section><section><title>
3591 msgid "influence of package in testing"
3592 msgstr "テスト版パッケージへの影響"
3594 # type: Content of: <chapter><section><section><section><para>
3595 #. type: Content of: <chapter><section><section><section><para>
3598 "Generally, there is nothing that the status of a package in <literal>testing "
3599 "</literal> means for transition of the next version from <literal>unstable </"
3600 "literal> to <literal>testing</literal>, with two exceptions: If the RC-"
3601 "bugginess of the package goes down, it may go in even if it is still RC-"
3602 "buggy. The second exception is if the version of the package in <literal> "
3603 "testing</literal> is out of sync on the different arches: Then any arch "
3604 "might just upgrade to the version of the source package; however, this can "
3605 "happen only if the package was previously forced through, the arch is in "
3606 "fuckedarches, or there was no binary package of that arch present in "
3607 "<literal>unstable </literal> at all during the <literal>testing</literal> "
3611 # type: Content of: <chapter><section><section><section><para>
3612 #. type: Content of: <chapter><section><section><section><para>
3615 "In summary this means: The only influence that a package being in <literal> "
3616 "testing</literal> has on a new version of the same package is that the new "
3617 "version might go in easier."
3620 # type: Content of: <chapter><section><section><section><title>
3621 #. type: Content of: <chapter><section><section><section><title>
3626 # type: Content of: <chapter><section><section><section><para>
3627 #. type: Content of: <chapter><section><section><section><para>
3629 msgid "If you are interested in details, this is how britney works:"
3632 # type: Content of: <chapter><section><section><section><para>
3633 #. type: Content of: <chapter><section><section><section><para>
3636 "The packages are looked at to determine whether they are valid candidates. "
3637 "This gives the update excuses. The most common reasons why a package is not "
3638 "considered are too young, RC-bugginess, and out of date on some arches. For "
3639 "this part of britney, the release managers have hammers of various sizes to "
3640 "force britney to consider a package. (Also, the base freeze is coded in "
3641 "that part of britney.) (There is a similar thing for binary-only updates, "
3642 "but this is not described here. If you're interested in that, please peruse "
3646 # type: Content of: <chapter><section><section><section><para>
3647 #. type: Content of: <chapter><section><section><section><para>
3650 "Now, the more complex part happens: Britney tries to update <literal>testing "
3651 "</literal> with the valid candidates. For that, britney tries to add each "
3652 "valid candidate to the testing distribution. If the number of uninstallable "
3653 "packages in <literal>testing</literal> doesn't increase, the package is "
3654 "accepted. From that point on, the accepted package is considered to be part "
3655 "of <literal>testing</literal>, such that all subsequent installability tests "
3656 "include this package. Hints from the release team are processed before or "
3657 "after this main run, depending on the exact type."
3660 # type: Content of: <chapter><section><section><section><para>
3661 #. type: Content of: <chapter><section><section><section><para>
3664 "If you want to see more details, you can look it up on <filename>merkel:/org/"
3665 "&ftp-debian-org;/testing/update_out/</filename> (or in <filename>merkel:~aba/"
3666 "testing/update_out</filename> to see a setup with a smaller packages file). "
3667 "Via web, it's at <ulink url=\"http://&ftp-master-host;/testing/"
3668 "update_out_code/\"></ulink>"
3671 # type: Content of: <chapter><section><section><section><para>
3672 #. type: Content of: <chapter><section><section><section><para>
3675 "The hints are available via <ulink url=\"http://&ftp-master-host;/testing/"
3676 "hints/\"></ulink>."
3679 # type: Content of: <chapter><section><section><title>
3680 #. type: Content of: <chapter><section><section><title>
3682 msgid "Direct updates to testing"
3683 msgstr "直接テスト版を更新する"
3685 # type: Content of: <chapter><section><section><para>
3686 #. type: Content of: <chapter><section><section><para>
3689 "The <literal>testing</literal> distribution is fed with packages from "
3690 "<literal>unstable</literal> according to the rules explained above. "
3691 "However, in some cases, it is necessary to upload packages built only for "
3692 "<literal> testing</literal>. For that, you may want to upload to <literal> "
3693 "testing-proposed-updates</literal>."
3696 # type: Content of: <chapter><section><section><para>
3697 #. type: Content of: <chapter><section><section><para>
3700 "Keep in mind that packages uploaded there are not automatically processed, "
3701 "they have to go through the hands of the release manager. So you'd better "
3702 "have a good reason to upload there. In order to know what a good reason is "
3703 "in the release managers' eyes, you should read the instructions that they "
3704 "regularly give on &email-debian-devel-announce;."
3707 # type: Content of: <chapter><section><section><para>
3708 #. type: Content of: <chapter><section><section><para>
3711 "You should not upload to <literal>testing-proposed-updates</literal> when "
3712 "you can update your packages through <literal>unstable</literal>. If you "
3713 "can't (for example because you have a newer development version in "
3714 "<literal>unstable </literal>), you may use this facility, but it is "
3715 "recommended that you ask for authorization from the release manager first. "
3716 "Even if a package is frozen, updates through <literal>unstable</literal> are "
3717 "possible, if the upload via <literal>unstable</literal> does not pull in any "
3721 # type: Content of: <chapter><section><section><para>
3722 #. type: Content of: <chapter><section><section><para>
3725 "Version numbers are usually selected by adding the codename of the "
3726 "<literal>testing</literal> distribution and a running number, like "
3727 "<literal>1.2sarge1</literal> for the first upload through <literal>testing-"
3728 "proposed-updates</literal> of package version <literal>1.2</literal>."
3731 # type: Content of: <chapter><section><section><para>
3732 #. type: Content of: <chapter><section><section><para>
3734 msgid "Please make sure you didn't miss any of these items in your upload:"
3737 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3738 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3741 "Make sure that your package really needs to go through <literal>testing-"
3742 "proposed-updates</literal>, and can't go through <literal> unstable</"
3746 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3747 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3749 msgid "Make sure that you included only the minimal amount of changes;"
3752 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3753 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3756 "Make sure that you included an appropriate explanation in the changelog;"
3759 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3760 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3763 "Make sure that you've written <literal>testing</literal> or <literal>testing-"
3764 "proposed-updates</literal> into your target distribution;"
3767 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3768 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3771 "Make sure that you've built and tested your package in <literal>testing</"
3772 "literal>, not in <literal>unstable</literal>;"
3775 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3776 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3779 "Make sure that your version number is higher than the version in "
3780 "<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
3781 "and lower than in <literal>unstable</literal>;"
3784 # type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3785 #. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
3788 "After uploading and successful build on all platforms, contact the release "
3789 "team at &email-debian-release; and ask them to approve your upload."
3792 # type: Content of: <chapter><section><section><title>
3793 #. type: Content of: <chapter><section><section><title>
3795 msgid "Frequently asked questions"
3798 # type: Content of: <chapter><section><section><section><title>
3799 #. type: Content of: <chapter><section><section><section><title>
3801 msgid "What are release-critical bugs, and how do they get counted?"
3804 # type: Content of: <chapter><section><section><section><para>
3805 #. type: Content of: <chapter><section><section><section><para>
3808 "All bugs of some higher severities are by default considered release-"
3809 "critical; currently, these are <literal>critical</literal>, <literal>grave</"
3810 "literal> and <literal>serious</literal> bugs."
3813 # type: Content of: <chapter><section><section><section><para>
3814 #. type: Content of: <chapter><section><section><section><para>
3817 "Such bugs are presumed to have an impact on the chances that the package "
3818 "will be released with the <literal>stable</literal> release of Debian: in "
3819 "general, if a package has open release-critical bugs filed on it, it won't "
3820 "get into <literal>testing</literal>, and consequently won't be released in "
3821 "<literal> stable</literal>."
3824 # type: Content of: <chapter><section><section><section><para>
3825 #. type: Content of: <chapter><section><section><section><para>
3828 "The <literal>unstable</literal> bug count are all release-critical bugs "
3829 "which are marked to apply to <replaceable>package</replaceable>/"
3830 "<replaceable>version </replaceable> combinations that are available in "
3831 "unstable for a release architecture. The <literal>testing</literal> bug "
3832 "count is defined analogously."
3835 # type: Content of: <chapter><section><section><section><title>
3836 #. type: Content of: <chapter><section><section><section><title>
3839 "How could installing a package into <literal>testing</literal> possibly "
3840 "break other packages?"
3843 # type: Content of: <chapter><section><section><section><para>
3844 #. type: Content of: <chapter><section><section><section><para>
3847 "The structure of the distribution archives is such that they can only "
3848 "contain one version of a package; a package is defined by its name. So when "
3849 "the source package <literal>acmefoo</literal> is installed into "
3850 "<literal>testing</literal>, along with its binary packages <literal>acme-foo-"
3851 "bin</literal>, <literal> acme-bar-bin</literal>, <literal>libacme-foo1</"
3852 "literal> and <literal> libacme-foo-dev</literal>, the old version is removed."
3855 # type: Content of: <chapter><section><section><section><para>
3856 #. type: Content of: <chapter><section><section><section><para>
3859 "However, the old version may have provided a binary package with an old "
3860 "soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
3861 "old <literal>acmefoo</literal> will remove <literal>libacme-foo0</literal>, "
3862 "which will break any packages which depend on it."
3865 # type: Content of: <chapter><section><section><section><para>
3866 #. type: Content of: <chapter><section><section><section><para>
3869 "Evidently, this mainly affects packages which provide changing sets of "
3870 "binary packages in different versions (in turn, mainly libraries). However, "
3871 "it will also affect packages upon which versioned dependencies have been "
3872 "declared of the ==, <=, or << varieties."
3875 # type: Content of: <chapter><section><section><section><para>
3876 #. type: Content of: <chapter><section><section><section><para>
3879 "When the set of binary packages provided by a source package change in this "
3880 "way, all the packages that depended on the old binaries will have to be "
3881 "updated to depend on the new binaries instead. Because installing such a "
3882 "source package into <literal>testing</literal> breaks all the packages that "
3883 "depended on it in <literal>testing</literal>, some care has to be taken now: "
3884 "all the depending packages must be updated and ready to be installed "
3885 "themselves so that they won't be broken, and, once everything is ready, "
3886 "manual intervention by the release manager or an assistant is normally "
3890 # type: Content of: <chapter><section><section><section><para>
3891 #. type: Content of: <chapter><section><section><section><para>
3894 "If you are having problems with complicated groups of packages like this, "
3895 "contact &email-debian-devel; or &email-debian-release; for help."
3898 # type: Content of: <chapter><section><section><screen>
3902 #~ "[tfheen_delayed]\n"
3904 #~ "fqdn = gluck.debian.org\n"
3905 #~ "incoming = ~tfheen\n"
3907 #~ "[tfheen_delayed]\n"
3909 #~ "fqdn = gluck.debian.org\n"
3910 #~ "incoming = ~tfheen"
3912 # type: Content of: <chapter><section><section><title>
3913 #~ msgid "How to do a NMU"
3914 #~ msgstr "NMU のやり方"