msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2012-08-08 21:41-0400\n"
+"POT-Creation-Date: 2013-05-14 15:27-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"helper, to learn its expectations and behavior."
msgstr ""
-#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:79
-msgid ""
-"Some people feel that vanilla <filename>debian/rules</filename> files are "
-"better, since you don't have to learn the intricacies of any helper system. "
-"This decision is completely up to you. Use what works for you. Many "
-"examples of vanilla <filename>debian/rules</filename> files are available at "
-"<ulink url=\"&url-rules-files;\"></ulink>."
-msgstr ""
-
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:88
+#: best-pkging-practices.dbk:81
msgid "Separating your patches into multiple files"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:90
+#: best-pkging-practices.dbk:83
msgid ""
"Big, complex packages may have many bugs that you need to deal with. If you "
"correct a number of bugs directly in the source, and you're not careful, it "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:99
+#: best-pkging-practices.dbk:92
msgid ""
"Fortunately, with the source format “3.0 (quilt)” it is now possible to keep "
"patches separate without having to modify <filename>debian/rules</filename> "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:107
+#: best-pkging-practices.dbk:100
msgid ""
"When using the older source “1.0”, it's also possible to separate patches "
"but a dedicated patch system must be used: the patch files are shipped "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:119
+#: best-pkging-practices.dbk:112
msgid ""
"<command>quilt</command> is the recommended tool for this. It does all of "
"the above, and also allows to manage patch series. See the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:125
+#: best-pkging-practices.dbk:118
msgid ""
"There are other tools to manage patches, like <command>dpatch</command>, and "
"the patch system integrated with <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:132
+#: best-pkging-practices.dbk:125
msgid "Multiple binary packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:134
+#: best-pkging-practices.dbk:127
msgid ""
"A single source package will often build several binary packages, either to "
"provide several flavors of the same software (e.g., the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:141
+#: best-pkging-practices.dbk:134
msgid ""
"The second case can be easily managed in <filename>debian/rules</filename>. "
"You just need to move the appropriate files from the build directory into "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:150
+#: best-pkging-practices.dbk:143
msgid ""
"The first case is a bit more difficult since it involves multiple recompiles "
"of the same software but with different configuration options. The "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:162
+#: best-pkging-practices.dbk:155
msgid "Best practices for <filename>debian/control</filename>"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:164
+#: best-pkging-practices.dbk:157
msgid ""
"The following practices are relevant to the "
"<filename>debian/control</filename> file. They supplement the <ulink "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:170
+#: best-pkging-practices.dbk:163
msgid ""
"The description of the package, as defined by the corresponding field in the "
"<filename>control</filename> file, contains both the package synopsis and "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:179
+#: best-pkging-practices.dbk:172
msgid "General guidelines for package descriptions"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:181
+#: best-pkging-practices.dbk:174
msgid ""
"The package description should be written for the average likely user, the "
"average person who will use and benefit from the package. For instance, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:188
+#: best-pkging-practices.dbk:181
msgid ""
"Our review of package descriptions lead us to conclude that most package "
"descriptions are technical, that is, are not written to make sense for "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:194
+#: best-pkging-practices.dbk:187
msgid ""
"How do you write for non-technical users? Avoid jargon. Avoid referring to "
"other applications or frameworks that the user might not be familiar with — "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:201
+#: best-pkging-practices.dbk:194
msgid ""
"Be objective. Package descriptions are not the place for advocating your "
"package, no matter how much you love it. Remember that the reader may not "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:206
+#: best-pkging-practices.dbk:199
msgid ""
"References to the names of any other software packages, protocol names, "
"standards, or specifications should use their canonical forms, if one "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:213
+#: best-pkging-practices.dbk:206
msgid ""
"If you are having problems writing your description, you may wish to send it "
"along to &email-debian-l10n-english; and request feedback."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:219
+#: best-pkging-practices.dbk:212
msgid "The package synopsis, or short description"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:221
+#: best-pkging-practices.dbk:214
msgid ""
"Policy says the synopsis line (the short description) must be concise, not "
"repeating the package name, but also informative."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:225
+#: best-pkging-practices.dbk:218
msgid ""
"The synopsis functions as a phrase describing the package, not a complete "
"sentence, so sentential punctuation is inappropriate: it does not need extra "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:231
+#: best-pkging-practices.dbk:224
#, no-wrap
msgid ""
"Package: libeg0\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:235
+#: best-pkging-practices.dbk:228
msgid ""
"Technically this is a noun phrase minus articles, as opposed to a verb "
"phrase. A good heuristic is that it should be possible to substitute the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:240
+#: best-pkging-practices.dbk:233
msgid ""
"The package <replaceable>name</replaceable> provides {a,an,the,some} "
"<replaceable>synopsis</replaceable>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:244
+#: best-pkging-practices.dbk:237
msgid ""
"Sets of related packages may use an alternative scheme that divides the "
"synopsis into two parts, the first a description of the whole suite and the "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:249
+#: best-pkging-practices.dbk:242
#, no-wrap
msgid ""
"Package: eg-tools\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:256
+#: best-pkging-practices.dbk:249
msgid ""
"These synopses follow a modified formula. Where a package "
"\"<replaceable>name</replaceable>\" has a synopsis "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:263
+#: best-pkging-practices.dbk:256
msgid ""
"The package <replaceable>name</replaceable> provides {a,an,the} "
"<replaceable>role</replaceable> for the <replaceable>suite</replaceable>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:269
+#: best-pkging-practices.dbk:262
msgid "The long description"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:271
+#: best-pkging-practices.dbk:264
msgid ""
"The long description is the primary information available to the user about "
"a package before they install it. It should provide all the information "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:277
+#: best-pkging-practices.dbk:270
msgid "The long description should consist of full and complete sentences."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:280
+#: best-pkging-practices.dbk:273
msgid ""
"The first paragraph of the long description should answer the following "
"questions: what does the package do? what task does it help the user "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:286
+#: best-pkging-practices.dbk:279
msgid ""
"The following paragraphs should answer the following questions: Why do I as "
"a user need this package? What other features does the package have? What "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:294
+#: best-pkging-practices.dbk:287
msgid ""
"Be careful to avoid spelling and grammar mistakes. Ensure that you "
"spell-check it. Both <command>ispell</command> and "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:299
+#: best-pkging-practices.dbk:292
#, no-wrap
msgid "ispell -d american -g debian/control\n"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:302
+#: best-pkging-practices.dbk:295
#, no-wrap
msgid "aspell -d en -D -c debian/control\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:305
+#: best-pkging-practices.dbk:298
msgid ""
"Users usually expect these questions to be answered in the package "
"description:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:310
+#: best-pkging-practices.dbk:303
msgid ""
"What does the package do? If it is an add-on to another package, then the "
"short description of the package we are an add-on to should be put in here."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:316
+#: best-pkging-practices.dbk:309
msgid ""
"Why should I want this package? This is related to the above, but not the "
"same (this is a mail user agent; this is cool, fast, interfaces with PGP and "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:323
+#: best-pkging-practices.dbk:316
msgid ""
"If this package should not be installed directly, but is pulled in by "
"another package, this should be mentioned."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:329
+#: best-pkging-practices.dbk:322
msgid ""
"If the package is <literal>experimental</literal>, or there are other "
"reasons it should not be used, if there are other packages that should be "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:336
+#: best-pkging-practices.dbk:329
msgid ""
"How is this package different from the competition? Is it a better "
"implementation? more features? different features? Why should I choose this "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:349
+#: best-pkging-practices.dbk:342
msgid "Upstream home page"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:351
+#: best-pkging-practices.dbk:344
msgid ""
"We recommend that you add the URL for the package's home page in the "
"<literal>Homepage</literal> field of the <literal>Source</literal> section "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:359
+#: best-pkging-practices.dbk:352
msgid "Version Control System location"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:361
+#: best-pkging-practices.dbk:354
msgid ""
"There are additional fields for the location of the Version Control System "
"in <filename>debian/control</filename>."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:365
+#: best-pkging-practices.dbk:358
msgid "Vcs-Browser"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:367
+#: best-pkging-practices.dbk:360
msgid ""
"Value of this field should be a <literal>http://</literal> URL pointing to a "
"web-browsable copy of the Version Control System repository used to maintain "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:372
+#: best-pkging-practices.dbk:365
msgid ""
"The information is meant to be useful for the final user, willing to browse "
"the latest work done on the package (e.g. when looking for the patch fixing "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:379
+#: best-pkging-practices.dbk:372
msgid "Vcs-*"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:381
+#: best-pkging-practices.dbk:374
msgid ""
"Value of this field should be a string identifying unequivocally the "
"location of the Version Control System repository used to maintain the given "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:392
+#: best-pkging-practices.dbk:385
msgid ""
"The information is meant to be useful for a user knowledgeable in the given "
"Version Control System and willing to build the current version of a package "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:403
+#: best-pkging-practices.dbk:396
msgid ""
"In the following example, an instance of the field for a Subversion "
"repository of the <systemitem role=\"package\">vim</systemitem> package is "
msgstr ""
#. type: Content of: <chapter><section><section><section><screen>
-#: best-pkging-practices.dbk:412
+#: best-pkging-practices.dbk:405
#, no-wrap
msgid ""
" Source: vim\n"
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:427
+#: best-pkging-practices.dbk:420
msgid "Best practices for <filename>debian/changelog</filename>"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:429
+#: best-pkging-practices.dbk:422
msgid ""
"The following practices supplement the <ulink "
"url=\"&url-debian-policy;ch-docs.html#s-changelogs\">Policy on changelog "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:434
+#: best-pkging-practices.dbk:427
msgid "Writing useful changelog entries"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:436
+#: best-pkging-practices.dbk:429
msgid ""
"The changelog entry for a package revision documents changes in that "
"revision, and only them. Concentrate on describing significant and "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:441
+#: best-pkging-practices.dbk:434
msgid ""
"Focus on <emphasis>what</emphasis> was changed — who, how and when are "
"usually less important. Having said that, remember to politely attribute "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:447
+#: best-pkging-practices.dbk:440
msgid ""
"There's no need to elaborate the trivial and obvious changes. You can also "
"aggregate several changes in one entry. On the other hand, don't be overly "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:454
+#: best-pkging-practices.dbk:447
msgid ""
"Use common English so that the majority of readers can comprehend it. Avoid "
"abbreviations, tech-speak and jargon when explaining changes that close "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:460
+#: best-pkging-practices.dbk:453
msgid ""
"It is sometimes desirable to prefix changelog entries with the names of the "
"files that were changed. However, there's no need to explicitly list each "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:466
+#: best-pkging-practices.dbk:459
msgid ""
"When referring to bugs, don't assume anything. Say what the problem was, "
"how it was fixed, and append the closes: #nnnnn string. See <xref "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:473
+#: best-pkging-practices.dbk:466
msgid "Common misconceptions about changelog entries"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:475
+#: best-pkging-practices.dbk:468
msgid ""
"The changelog entries should <emphasis role=\"strong\">not</emphasis> "
"document generic packaging issues (Hey, if you're looking for foo.conf, it's "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:483
+#: best-pkging-practices.dbk:476
msgid ""
"The only bugs closed with a changelog entry should be those that are "
"actually fixed in the same package revision. Closing unrelated bugs in the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:488
+#: best-pkging-practices.dbk:481
msgid ""
"The changelog entries should <emphasis role=\"strong\">not</emphasis> be "
"used for random discussion with bug reporters (I don't see segfaults when "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:499
+#: best-pkging-practices.dbk:492
msgid ""
"It is an old tradition to acknowledge bugs fixed in non-maintainer uploads "
"in the first changelog entry of the proper maintainer upload. As we have "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:507
+#: best-pkging-practices.dbk:500
msgid "Common errors in changelog entries"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:509
+#: best-pkging-practices.dbk:502
msgid ""
"The following examples demonstrate some common errors or examples of bad "
"style in changelog entries."
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:513
+#: best-pkging-practices.dbk:506
#, no-wrap
msgid " * Fixed all outstanding bugs.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:516
+#: best-pkging-practices.dbk:509
msgid "This doesn't tell readers anything too useful, obviously."
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:519
+#: best-pkging-practices.dbk:512
#, no-wrap
msgid " * Applied patch from Jane Random.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:522
+#: best-pkging-practices.dbk:515
msgid "What was the patch about?"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:525
+#: best-pkging-practices.dbk:518
#, no-wrap
msgid " * Late night install target overhaul.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:528
+#: best-pkging-practices.dbk:521
msgid ""
"Overhaul which accomplished what? Is the mention of late night supposed to "
"remind us that we shouldn't trust that code?"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:532
+#: best-pkging-practices.dbk:525
#, no-wrap
msgid " * Fix vsync FU w/ ancient CRTs.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:535
+#: best-pkging-practices.dbk:528
msgid ""
"Too many acronyms, and it's not overly clear what the, uh, fsckup (oops, a "
"curse word!) was actually about, or how it was fixed."
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:539
+#: best-pkging-practices.dbk:532
#, no-wrap
msgid " * This is not a bug, closes: #nnnnnn.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:542
+#: best-pkging-practices.dbk:535
msgid ""
"First of all, there's absolutely no need to upload the package to convey "
"this information; instead, use the bug tracking system. Secondly, there's "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:547
+#: best-pkging-practices.dbk:540
#, no-wrap
msgid " * Has been fixed for ages, but I forgot to close; closes: #54321.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:550
+#: best-pkging-practices.dbk:543
msgid ""
"If for some reason you didn't mention the bug number in a previous changelog "
"entry, there's no problem, just close the bug normally in the BTS. There's "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:557
+#: best-pkging-practices.dbk:550
#, no-wrap
msgid " * Closes: #12345, #12346, #15432\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:560
+#: best-pkging-practices.dbk:553
msgid ""
"Where's the description? If you can't think of a descriptive message, start "
"by inserting the title of each different bug."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:566
+#: best-pkging-practices.dbk:559
msgid "Supplementing changelogs with <filename>NEWS.Debian</filename> files"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:568
+#: best-pkging-practices.dbk:561
msgid ""
"Important news about changes in a package can also be put in "
"<filename>NEWS.Debian</filename> files. The news will be displayed by tools "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:579
+#: best-pkging-practices.dbk:572
msgid ""
"The file format is the same as a debian changelog file, but leave off the "
"asterisks and describe each news item with a full paragraph when necessary "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:588
+#: best-pkging-practices.dbk:581
#, no-wrap
msgid ""
"cron (3.0pl1-74) unstable; urgency=low\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:598
+#: best-pkging-practices.dbk:591
msgid ""
"The <filename>NEWS.Debian</filename> file is installed as "
"<filename>/usr/share/doc/<replaceable>package</replaceable>/NEWS.Debian.gz</filename>. "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:605
+#: best-pkging-practices.dbk:598
msgid ""
"Unlike changelog files, you need not update <filename>NEWS.Debian</filename> "
"files with every release. Only update them if you have something "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:627
+#: best-pkging-practices.dbk:620
msgid "Best practices for maintainer scripts"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:629
+#: best-pkging-practices.dbk:622
msgid ""
"Maintainer scripts include the files <filename>debian/postinst</filename>, "
"<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:637
+#: best-pkging-practices.dbk:630
msgid ""
"Maintainer scripts must be idempotent. That means that you need to make "
"sure nothing bad will happen if the script is called twice where it would "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:642
+#: best-pkging-practices.dbk:635
msgid ""
"Standard input and output may be redirected (e.g. into pipes) for logging "
"purposes, so don't rely on them being a tty."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:646
+#: best-pkging-practices.dbk:639
msgid ""
"All prompting or interactive configuration should be kept to a minimum. "
"When it is necessary, you should use the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:653
+#: best-pkging-practices.dbk:646
msgid ""
"Keep the maintainer scripts as simple as possible. We suggest you use pure "
"POSIX shell scripts. Remember, if you do need any bash features, the "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:660
+#: best-pkging-practices.dbk:653
msgid ""
"If you change your maintainer scripts, be sure to test package removal, "
"double installation, and purging. Be sure that a purged package is "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:666
+#: best-pkging-practices.dbk:659
msgid ""
"If you need to check for the existence of a command, you should use "
"something like"
msgstr ""
#. type: Content of: <chapter><section><programlisting>
-#: best-pkging-practices.dbk:669
+#: best-pkging-practices.dbk:662
#, no-wrap
msgid "if [ -x /usr/sbin/install-docs ]; then ..."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:671
+#: best-pkging-practices.dbk:664
msgid ""
"If you don't wish to hard-code the path of a command in your maintainer "
"script, the following POSIX-compliant shell function may help:"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:676
+#: best-pkging-practices.dbk:669
msgid ""
"You can use this function to search <varname>$PATH</varname> for a command "
"name, passed as an argument. It returns true (zero) if the command was "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:683
+#: best-pkging-practices.dbk:676
msgid ""
"While <command>which</command> is an acceptable alternative, since it is "
"from the required <systemitem role=\"package\">debianutils</systemitem> "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:693
+#: best-pkging-practices.dbk:686
msgid ""
"Configuration management with <systemitem "
"role=\"package\">debconf</systemitem>"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:695
+#: best-pkging-practices.dbk:688
msgid ""
"<systemitem role=\"package\">Debconf</systemitem> is a configuration "
"management system which can be used by all the various packaging scripts "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:703
+#: best-pkging-practices.dbk:696
msgid ""
"Debconf is a great tool but it is often poorly used. Many common mistakes "
"are listed in the <citerefentry> "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:710
+#: best-pkging-practices.dbk:703
msgid ""
"These guidelines include some writing style and typography recommendations, "
"general considerations about debconf usage as well as more specific "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:716
+#: best-pkging-practices.dbk:709
msgid "Do not abuse debconf"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:718
+#: best-pkging-practices.dbk:711
msgid ""
"Since debconf appeared in Debian, it has been widely abused and several "
"criticisms received by the Debian distribution come from debconf abuse with "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:724
+#: best-pkging-practices.dbk:717
msgid ""
"Keep usage notes to what they belong: the <filename>NEWS.Debian</filename>, "
"or <filename>README.Debian</filename> file. Only use notes for important "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:730
+#: best-pkging-practices.dbk:723
msgid ""
"Carefully choose the questions priorities in maintainer scripts. See "
"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:738
+#: best-pkging-practices.dbk:731
msgid "General recommendations for authors and translators"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:740
+#: best-pkging-practices.dbk:733
msgid "Write correct English"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:742
+#: best-pkging-practices.dbk:735
msgid ""
"Most Debian package maintainers are not native English speakers. So, "
"writing properly phrased templates may not be easy for them."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:746
+#: best-pkging-practices.dbk:739
msgid ""
"Please use (and abuse) &email-debian-l10n-english; mailing list. Have your "
"templates proofread."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:750
+#: best-pkging-practices.dbk:743
msgid ""
"Badly written templates give a poor image of your package, of your "
"work... or even of Debian itself."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:754
+#: best-pkging-practices.dbk:747
msgid ""
"Avoid technical jargon as much as possible. If some terms sound common to "
"you, they may be impossible to understand for others. If you cannot avoid "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:762
+#: best-pkging-practices.dbk:755
msgid "Be kind to translators"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:764
+#: best-pkging-practices.dbk:757
msgid ""
"Debconf templates may be translated. Debconf, along with its sister package "
"<command>po-debconf</command> offers a simple framework for getting "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:769
+#: best-pkging-practices.dbk:762
msgid ""
"Please use gettext-based templates. Install <systemitem "
"role=\"package\">po-debconf</systemitem> on your development system and read "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:774
+#: best-pkging-practices.dbk:767
msgid ""
"Avoid changing templates too often. Changing templates text induces more "
"work to translators which will get their translation fuzzied. A fuzzy "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:782
+#: best-pkging-practices.dbk:775
msgid ""
"If you plan to do changes to your original templates, please use the "
"notification system provided with the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:794
+#: best-pkging-practices.dbk:787
msgid "A recommended use of that utility is:"
msgstr ""
#. type: Content of: <chapter><section><section><section><programlisting>
-#: best-pkging-practices.dbk:796
+#: best-pkging-practices.dbk:789
#, no-wrap
msgid ""
"cd debian/po && podebconf-report-po --call --languageteam "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:798
+#: best-pkging-practices.dbk:791
msgid ""
"This command will first synchronize the PO and POT files in "
"<filename>debian/po</filename> with the templates files listed in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:807
+#: best-pkging-practices.dbk:800
msgid ""
"Giving a deadline to translators is always appreciated, so that they can "
"organize their work. Please remember that some translation teams have a "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:814
+#: best-pkging-practices.dbk:807
msgid ""
"If in doubt, you may also contact the translation team for a given language "
"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:821
+#: best-pkging-practices.dbk:814
msgid "Unfuzzy complete translations when correcting typos and spelling"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:823
+#: best-pkging-practices.dbk:816
msgid ""
"When the text of a debconf template is corrected and you are <emphasis "
"role=\"strong\">sure</emphasis> that the change does <emphasis "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:829
+#: best-pkging-practices.dbk:822
msgid ""
"If you don't do so, the whole template will not be translated as long as a "
"translator will send you an update."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:833
+#: best-pkging-practices.dbk:826
msgid ""
"To <emphasis>unfuzzy</emphasis> translations, you can use "
"<command>msguntypot</command> (part of the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:840
+#: best-pkging-practices.dbk:833
msgid "Regenerate the POT and PO files."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:842 best-pkging-practices.dbk:865
+#: best-pkging-practices.dbk:835 best-pkging-practices.dbk:858
#, no-wrap
msgid "debconf-updatepo"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:846
+#: best-pkging-practices.dbk:839
msgid "Make a copy of the POT file."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:848
+#: best-pkging-practices.dbk:841
#, no-wrap
msgid "cp templates.pot templates.pot.orig"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:852
+#: best-pkging-practices.dbk:845
msgid "Make a copy of all the PO files."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:854
+#: best-pkging-practices.dbk:847
#, no-wrap
msgid "mkdir po_fridge; cp *.po po_fridge"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:858
+#: best-pkging-practices.dbk:851
msgid "Change the debconf template files to fix the typos."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:863
+#: best-pkging-practices.dbk:856
msgid "Regenerate the POT and PO files (again)."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:867
+#: best-pkging-practices.dbk:860
msgid ""
"At this point, the typo fix fuzzied all the translations, and this "
"unfortunate change is the only one between the PO files of your main "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:874
+#: best-pkging-practices.dbk:867
msgid "Discard fuzzy translation, restore the ones from the fridge."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:876
+#: best-pkging-practices.dbk:869
#, no-wrap
msgid "cp po_fridge/*.po ."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:880
+#: best-pkging-practices.dbk:873
msgid ""
"Manually merge the PO files with the new POT file, but taking the useless "
"fuzzy into account."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:882
+#: best-pkging-practices.dbk:875
#, no-wrap
msgid "msguntypot -o templates.pot.orig -n templates.pot *.po"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:886
+#: best-pkging-practices.dbk:879
msgid "Clean up."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:888
+#: best-pkging-practices.dbk:881
#, no-wrap
msgid "rm -rf templates.pot.orig po_fridge"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:894
+#: best-pkging-practices.dbk:887
msgid "Do not make assumptions about interfaces"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:896
+#: best-pkging-practices.dbk:889
msgid ""
"Templates text should not make reference to widgets belonging to some "
"debconf interfaces. Sentences like <emphasis>If you answer "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:901
+#: best-pkging-practices.dbk:894
msgid ""
"String templates should also avoid mentioning the default values in their "
"description. First, because this is redundant with the values seen by the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:907
+#: best-pkging-practices.dbk:900
msgid ""
"More generally speaking, try to avoid referring to user actions. Just give "
"facts."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:913
+#: best-pkging-practices.dbk:906
msgid "Do not use first person"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:915
+#: best-pkging-practices.dbk:908
msgid ""
"You should avoid the use of first person (<emphasis>I will do "
"this...</emphasis> or <emphasis>We recommend...</emphasis>). The computer "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:925
+#: best-pkging-practices.dbk:918
msgid "Be gender neutral"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:927
+#: best-pkging-practices.dbk:920
msgid ""
"The world is made of men and women. Please use gender-neutral constructions "
"in your writing."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:935
+#: best-pkging-practices.dbk:928
msgid "Templates fields definition"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:937
+#: best-pkging-practices.dbk:930
msgid ""
"This part gives some information which is mostly taken from the "
"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:942
+#: best-pkging-practices.dbk:935
msgid "Type"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:944
+#: best-pkging-practices.dbk:937
msgid "string"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:946
+#: best-pkging-practices.dbk:939
msgid "Results in a free-form input field that the user can type any string into."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:951
+#: best-pkging-practices.dbk:944
msgid "password"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:953
+#: best-pkging-practices.dbk:946
msgid ""
"Prompts the user for a password. Use this with caution; be aware that the "
"password the user enters will be written to debconf's database. You should "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:960
+#: best-pkging-practices.dbk:953
msgid "boolean"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:962
+#: best-pkging-practices.dbk:955
msgid ""
"A true/false choice. Remember: true/false, <emphasis role=\"strong\">not "
"yes/no</emphasis>..."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:968
+#: best-pkging-practices.dbk:961
msgid "select"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:970
+#: best-pkging-practices.dbk:963
msgid ""
"A choice between one of a number of values. The choices must be specified "
"in a field named 'Choices'. Separate the possible values with commas and "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:975
+#: best-pkging-practices.dbk:968
msgid ""
"If choices are translatable strings, the 'Choices' field may be marked as "
"translatable by using <literal>__Choices</literal>. The double underscore "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:980
+#: best-pkging-practices.dbk:973
msgid ""
"The <command>po-debconf</command> system also offers interesting "
"possibilities to only mark <emphasis role=\"strong\">some</emphasis> choices "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><programlisting>
-#: best-pkging-practices.dbk:985
+#: best-pkging-practices.dbk:978
#, no-wrap
msgid ""
"Template: foo/bar\n"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:993
+#: best-pkging-practices.dbk:986
msgid ""
"In that example, only the 'Other' string is translatable while others are "
"acronyms that should not be translated. The above allows only 'Other' to be "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:998
+#: best-pkging-practices.dbk:991
msgid ""
"The debconf templates flag system offers many such possibilities. The "
"<citerefentry> <refentrytitle>po-debconf</refentrytitle> "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1006
+#: best-pkging-practices.dbk:999
msgid "multiselect"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:1008
+#: best-pkging-practices.dbk:1001
msgid ""
"Like the select data type, except the user can choose any number of items "
"from the choices list (or chose none of them)."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1014
+#: best-pkging-practices.dbk:1007
msgid "note"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:1016
+#: best-pkging-practices.dbk:1009
msgid ""
"Rather than being a question per se, this datatype indicates a note that can "
"be displayed to the user. It should be used only for important notes that "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1025
+#: best-pkging-practices.dbk:1018
msgid "text"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:1027
+#: best-pkging-practices.dbk:1020
msgid "This type is now considered obsolete: don't use it."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1032
+#: best-pkging-practices.dbk:1025
msgid "error"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:1034
+#: best-pkging-practices.dbk:1027
msgid ""
"This type is designed to handle error messages. It is mostly similar to the "
"note type. Frontends may present it differently (for instance, the dialog "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:1039
+#: best-pkging-practices.dbk:1032
msgid ""
"It is recommended to use this type for any message that needs user attention "
"for a correction of any kind."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1047
+#: best-pkging-practices.dbk:1040
msgid "Description: short and extended description"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1049
+#: best-pkging-practices.dbk:1042
msgid ""
"Template descriptions have two parts: short and extended. The short "
"description is in the Description: line of the template."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1053
+#: best-pkging-practices.dbk:1046
msgid ""
"The short description should be kept short (50 characters or so) so that it "
"may be accommodated by most debconf interfaces. Keeping it short also helps "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1059
+#: best-pkging-practices.dbk:1052
msgid ""
"The short description should be able to stand on its own. Some interfaces "
"do not show the long description by default, or only if the user explicitely "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1065
+#: best-pkging-practices.dbk:1058
msgid ""
"The short description does not necessarily have to be a full sentence. This "
"is part of the keep it short and efficient recommendation."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1069
+#: best-pkging-practices.dbk:1062
msgid ""
"The extended description should not repeat the short description word for "
"word. If you can't think up a long description, then first, think some "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1076
+#: best-pkging-practices.dbk:1069
msgid ""
"The extended description should use complete sentences. Paragraphs should "
"be kept short for improved readability. Do not mix two ideas in the same "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1081
+#: best-pkging-practices.dbk:1074
msgid ""
"Don't be too verbose. User tend to ignore too long screens. 20 lines are "
"by experience a border you shouldn't cross, because that means that in the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1087
+#: best-pkging-practices.dbk:1080
msgid ""
"The extended description should <emphasis role=\"strong\">never</emphasis> "
"include a question."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1091
+#: best-pkging-practices.dbk:1084
msgid ""
"For specific rules depending on templates type (string, boolean, etc.), "
"please read below."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1097
+#: best-pkging-practices.dbk:1090
msgid "Choices"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1099
+#: best-pkging-practices.dbk:1092
msgid ""
"This field should be used for select and multiselect types. It contains the "
"possible choices which will be presented to users. These choices should be "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1106
+#: best-pkging-practices.dbk:1099
msgid "Default"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1108
+#: best-pkging-practices.dbk:1101
msgid ""
"This field is optional. It contains the default answer for string, select "
"and multiselect templates. For multiselect templates, it may contain a "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1117
+#: best-pkging-practices.dbk:1110
msgid "Templates fields specific style guide"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1119
+#: best-pkging-practices.dbk:1112
msgid "Type field"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1121
+#: best-pkging-practices.dbk:1114
msgid ""
"No specific indication except: use the appropriate type by referring to the "
"previous section."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1127
+#: best-pkging-practices.dbk:1120
msgid "Description field"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1129
+#: best-pkging-practices.dbk:1122
msgid ""
"Below are specific instructions for properly writing the Description (short "
"and extended) depending on the template type."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1133
+#: best-pkging-practices.dbk:1126
msgid "String/password templates"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1137
+#: best-pkging-practices.dbk:1130
msgid ""
"The short description is a prompt and <emphasis "
"role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1144
+#: best-pkging-practices.dbk:1137
msgid ""
"The extended description is a complement to the short description. In the "
"extended part, explain what is being asked, rather than ask the same "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1154
+#: best-pkging-practices.dbk:1147
msgid "Boolean templates"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1158
+#: best-pkging-practices.dbk:1151
msgid ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1166
+#: best-pkging-practices.dbk:1159
msgid ""
"Again, please avoid referring to specific interface widgets. A common "
"mistake for such templates is if you answer Yes-type constructions."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1174
+#: best-pkging-practices.dbk:1167
msgid "Select/Multiselect"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1178
+#: best-pkging-practices.dbk:1171
msgid ""
"The short description is a prompt and <emphasis "
"role=\"strong\">not</emphasis> a title. Do <emphasis "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1186
+#: best-pkging-practices.dbk:1179
msgid ""
"The extended description will complete the short description. It may refer "
"to the available choices. It may also mention that the user may choose more "
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1196
+#: best-pkging-practices.dbk:1189
msgid "Notes"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1200
+#: best-pkging-practices.dbk:1193
msgid ""
"The short description should be considered to be a <emphasis "
"role=\"strong\">title</emphasis>."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1205
+#: best-pkging-practices.dbk:1198
msgid ""
"The extended description is what will be displayed as a more detailed "
"explanation of the note. Phrases, no terse writing style."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1211
+#: best-pkging-practices.dbk:1204
msgid ""
"<emphasis role=\"strong\">Do not abuse debconf.</emphasis> Notes are the "
"most common way to abuse debconf. As written in debconf-devel manual page: "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1226
+#: best-pkging-practices.dbk:1219
msgid "Choices field"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1228
+#: best-pkging-practices.dbk:1221
msgid ""
"If the Choices are likely to change often, please consider using the "
"__Choices trick. This will split each individual choice into a single "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1235 best-pkging-practices.dbk:1273
+#: best-pkging-practices.dbk:1228 best-pkging-practices.dbk:1266
msgid "Default field"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1237
+#: best-pkging-practices.dbk:1230
msgid ""
"If the default value, for a select template, is likely to vary depending on "
"the user language (for instance, if the choice is a language choice), please "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1242
+#: best-pkging-practices.dbk:1235
msgid ""
"This special field allow translators to put the most appropriate choice "
"according to their own language. It will become the default choice when "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1248
+#: best-pkging-practices.dbk:1241
msgid "Example, taken from the geneweb package templates:"
msgstr ""
#. type: Content of: <chapter><section><section><section><screen>
-#: best-pkging-practices.dbk:1251
+#: best-pkging-practices.dbk:1244
#, no-wrap
msgid ""
"Template: geneweb/lang\n"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1262
+#: best-pkging-practices.dbk:1255
msgid ""
"Note the use of brackets which allow internal comments in debconf fields. "
"Also note the use of comments which will show up in files the translators "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1267
+#: best-pkging-practices.dbk:1260
msgid ""
"The comments are needed as the _Default trick is a bit confusing: the "
"translators may put their own choice"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1275
+#: best-pkging-practices.dbk:1268
msgid ""
"Do NOT use empty default field. If you don't want to use default values, do "
"not use Default at all."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1279
+#: best-pkging-practices.dbk:1272
msgid ""
"If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, "
"see <xref linkend=\"s6.5.2.2\"/>), consider making this field translatable, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1284
+#: best-pkging-practices.dbk:1277
msgid ""
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1296
+#: best-pkging-practices.dbk:1289
msgid "Internationalization"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:1298
+#: best-pkging-practices.dbk:1291
msgid ""
"This section contains global information for developers to make translators' "
"life easier. More information for translators and developers interested in "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1305
+#: best-pkging-practices.dbk:1298
msgid "Handling debconf translations"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1307
+#: best-pkging-practices.dbk:1300
msgid ""
"Like porters, translators have a difficult task. They work on many packages "
"and must collaborate with many different maintainers. Moreover, most of the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1313
+#: best-pkging-practices.dbk:1306
msgid ""
"The goal of <systemitem role=\"package\">debconf</systemitem> was to make "
"packages configuration easier for maintainers and for users. Originally, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1323
+#: best-pkging-practices.dbk:1316
msgid ""
"Using <systemitem role=\"package\">po-debconf</systemitem>, the translation "
"is stored in <filename>.po</filename> files (drawing from "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1339
+#: best-pkging-practices.dbk:1332
msgid "Internationalized documentation"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1341
+#: best-pkging-practices.dbk:1334
msgid ""
"Internationalizing documentation is crucial for users, but a lot of labor. "
"There's no way to eliminate all that work, but you can make things easier "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1346
+#: best-pkging-practices.dbk:1339
msgid ""
"If you maintain documentation of any size, it is easier for translators if "
"they have access to a source control system. That lets translators see the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1360
+#: best-pkging-practices.dbk:1353
msgid ""
"If you maintain XML or SGML documentation, we suggest that you isolate any "
"language-independent information and define those as entities in a separate "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1366
+#: best-pkging-practices.dbk:1359
msgid ""
"Some tools (e.g. <systemitem role=\"package\">po4a</systemitem>, <systemitem "
"role=\"package\">poxml</systemitem>, or the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1378
+#: best-pkging-practices.dbk:1371
msgid "Common packaging situations"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1389
+#: best-pkging-practices.dbk:1382
msgid "Packages using <command>autoconf</command>/<command>automake</command>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1391
+#: best-pkging-practices.dbk:1384
msgid ""
"Keeping <command>autoconf</command>'s <filename>config.sub</filename> and "
"<filename>config.guess</filename> files up to date is critical for porters, "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1403
+#: best-pkging-practices.dbk:1396
msgid "Libraries"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1405
+#: best-pkging-practices.dbk:1398
msgid ""
"Libraries are always difficult to package for various reasons. The policy "
"imposes many constraints to ease their maintenance and to make sure upgrades "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1411
+#: best-pkging-practices.dbk:1404
msgid ""
"Good practices for library packaging have been grouped in <ulink "
"url=\"&url-libpkg-guide;\">the library packaging guide</ulink>."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1418 resources.dbk:193
+#: best-pkging-practices.dbk:1411 resources.dbk:193
msgid "Documentation"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1420
+#: best-pkging-practices.dbk:1413
msgid ""
"Be sure to follow the <ulink url=\"&url-debian-policy;ch-docs.html\">Policy "
"on documentation</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1425
+#: best-pkging-practices.dbk:1418
msgid ""
"If your package contains documentation built from XML or SGML, we recommend "
"you not ship the XML or SGML source in the binary package(s). If users want "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1430
+#: best-pkging-practices.dbk:1423
msgid ""
"Policy specifies that documentation should be shipped in HTML format. We "
"also recommend shipping documentation in PDF and plain text format if "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1437
+#: best-pkging-practices.dbk:1430
msgid ""
"Major shipped manuals should register themselves with <systemitem "
"role=\"package\">doc-base</systemitem> on installation. See the <systemitem "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1443
+#: best-pkging-practices.dbk:1436
msgid ""
"Debian policy (section 12.1) directs that manual pages should accompany "
"every program, utility, and function, and suggests them for other objects "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1450
+#: best-pkging-practices.dbk:1443
msgid ""
"The manpages do not need to be written directly in the troff format. "
"Popular source formats are Docbook, POD and reST, which can be converted "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1459
+#: best-pkging-practices.dbk:1452
msgid "Specific types of packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1461
+#: best-pkging-practices.dbk:1454
msgid ""
"Several specific types of packages have special sub-policies and "
"corresponding packaging rules and practices:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1467
+#: best-pkging-practices.dbk:1460
msgid ""
"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl "
"policy</ulink>, some examples of packages following that policy are "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1476
+#: best-pkging-practices.dbk:1469
msgid ""
"Python related packages have their python policy; see &file-python-policy; "
"in the <systemitem role=\"package\">python</systemitem> package."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1483
+#: best-pkging-practices.dbk:1476
msgid ""
"Emacs related packages have the <ulink url=\"&url-emacs-policy;\">emacs "
"policy</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1490
+#: best-pkging-practices.dbk:1483
msgid ""
"Java related packages have their <ulink url=\"&url-java-policy;\">java "
"policy</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1497
+#: best-pkging-practices.dbk:1490
msgid ""
"Ocaml related packages have their own policy, found in &file-ocaml-policy; "
"from the <systemitem role=\"package\">ocaml</systemitem> package. A good "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1505
+#: best-pkging-practices.dbk:1498
msgid ""
"Packages providing XML or SGML DTDs should conform to the recommendations "
"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1511
+#: best-pkging-practices.dbk:1504
msgid ""
"Lisp packages should register themselves with <systemitem "
"role=\"package\">common-lisp-controller</systemitem>, about which see "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1541
+#: best-pkging-practices.dbk:1534
msgid "Architecture-independent data"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1543
+#: best-pkging-practices.dbk:1536
msgid ""
"It is not uncommon to have a large amount of architecture-independent data "
"packaged with a program. For example, audio files, a collection of icons, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1550
+#: best-pkging-practices.dbk:1543
msgid ""
"However, if the size of the data is considerable, consider splitting it out "
"into a separate, architecture-independent package "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1562
+#: best-pkging-practices.dbk:1555
msgid "Needing a certain locale during build"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1564
+#: best-pkging-practices.dbk:1557
msgid ""
"If you need a certain locale during build, you can create a temporary file "
"via this trick:"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1568
+#: best-pkging-practices.dbk:1561
msgid ""
"If you set <varname>LOCPATH</varname> to the equivalent of "
"<filename>/usr/lib/locale</filename>, and <varname>LC_ALL</varname> to the "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1573
+#: best-pkging-practices.dbk:1566
#, no-wrap
msgid ""
"LOCALE_PATH=debian/tmpdir/usr/lib/locale\n"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1586
+#: best-pkging-practices.dbk:1579
msgid "Make transition packages deborphan compliant"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1588
+#: best-pkging-practices.dbk:1581
msgid ""
"Deborphan is a program for helping users to detect which packages can safely "
"be removed from the system, i.e. the ones that have no packages depending "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1595
+#: best-pkging-practices.dbk:1588
msgid ""
"For example, with <literal>--guess-dummy</literal>, "
"<command>deborphan</command> tries to search all transitional packages which "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1602
+#: best-pkging-practices.dbk:1595
msgid ""
"So, when you are creating such a package, please make sure to add this text "
"to your short description. If you are looking for examples, just run: "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1608
+#: best-pkging-practices.dbk:1601
msgid ""
"Also, it is recommended to adjust its section to <literal>oldlibs</literal> "
"and its priority to <literal>extra</literal> in order to ease "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1617
+#: best-pkging-practices.dbk:1610
msgid "Best practices for <filename>.orig.tar.{gz,bz2,xz}</filename> files"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1619
+#: best-pkging-practices.dbk:1612
msgid ""
"There are two kinds of original source tarballs: Pristine source and "
"repackaged upstream source."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1623
+#: best-pkging-practices.dbk:1616
msgid "Pristine source"
msgstr ""
#. type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1627
+#: best-pkging-practices.dbk:1620
msgid ""
"We cannot prevent upstream authors from changing the tarball they distribute "
"without also incrementing the version number, so there can be no guarantee "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1625
+#: best-pkging-practices.dbk:1618
msgid ""
"The defining characteristic of a pristine source tarball is that the "
"<filename>.orig.tar.{gz,bz2,xz}</filename> file is byte-for-byte identical "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1645
+#: best-pkging-practices.dbk:1638
msgid ""
"There is no universally accepted guidelines that upstream authors follow "
"regarding to the directory structure inside their tarball, but "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1653
+#: best-pkging-practices.dbk:1646
msgid "It unpacks the tarball in an empty temporary directory by doing"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><screen>
-#: best-pkging-practices.dbk:1656
+#: best-pkging-practices.dbk:1649
#, no-wrap
msgid ""
"zcat "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1661
+#: best-pkging-practices.dbk:1654
msgid ""
"If, after this, the temporary directory contains nothing but one directory "
"and no other files, <command>dpkg-source</command> renames that directory to "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1670
+#: best-pkging-practices.dbk:1663
msgid ""
"Otherwise, the upstream tarball must have been packaged without a common "
"top-level directory (shame on the upstream author!). In this case, "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1681
+#: best-pkging-practices.dbk:1674
msgid "Repackaged upstream source"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1683
+#: best-pkging-practices.dbk:1676
msgid ""
"You <emphasis role=\"strong\">should</emphasis> upload packages with a "
"pristine source tarball if possible, but there are various reasons why it "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1690
+#: best-pkging-practices.dbk:1683
msgid ""
"In these cases the developer must construct a suitable "
"<filename>.orig.tar.{gz,bz2,xz}</filename> file themselves. We refer to "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1699
+#: best-pkging-practices.dbk:1692
msgid ""
"There may be cases where it is desirable to repackage the source even though "
"upstream distributes a <filename>.tar.{gz,bz2,xz}</filename> that could in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1708
+#: best-pkging-practices.dbk:1701
msgid "A repackaged <filename>.orig.tar.{gz,bz2,xz}</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1713
+#: best-pkging-practices.dbk:1706
msgid ""
"<emphasis role=\"strong\">should</emphasis> be documented in the resulting "
"source package. Detailed information on how the repackaged source was "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para>
-#: best-pkging-practices.dbk:1728
+#: best-pkging-practices.dbk:1721
msgid ""
"As a special exception, if the omission of non-free files would lead to the "
"source failing to build without assistance from the Debian diff, it might be "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1726
+#: best-pkging-practices.dbk:1719
msgid ""
"<emphasis role=\"strong\">should not</emphasis> contain any file that does "
"not come from the upstream author(s), or whose contents has been changed by "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1739
+#: best-pkging-practices.dbk:1732
msgid ""
"<emphasis role=\"strong\">should</emphasis>, except where impossible for "
"legal reasons, preserve the entire building and portablility infrastructure "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1748
+#: best-pkging-practices.dbk:1741
msgid ""
"(<emphasis>Rationale:</emphasis> It is common for Debian users who need to "
"build software for non-Debian platforms to fetch the source from a Debian "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1755
+#: best-pkging-practices.dbk:1748
msgid ""
"<emphasis role=\"strong\">should</emphasis> use "
"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-version</replaceable>.orig</filename> "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1763
+#: best-pkging-practices.dbk:1756
msgid ""
"<emphasis role=\"strong\">should</emphasis> be gzipped or bzipped with "
"maximal compression."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1770
+#: best-pkging-practices.dbk:1763
msgid "Changing binary files"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1772
+#: best-pkging-practices.dbk:1765
msgid ""
"Sometimes it is necessary to change binary files contained in the original "
"tarball, or to add binary files that are not in it. This is fully supported "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1787
+#: best-pkging-practices.dbk:1780
msgid "Best practices for debug packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1789
+#: best-pkging-practices.dbk:1782
msgid ""
"A debug package is a package with a name ending in -dbg, that contains "
"additional information that <command>gdb</command> can use. Since Debian "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1797
+#: best-pkging-practices.dbk:1790
msgid ""
"It is up to a package's maintainer whether to create a debug package or "
"not. Maintainers are encouraged to create debug packages for library "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1807
+#: best-pkging-practices.dbk:1800
msgid ""
"Some debug packages may contain an entire special debugging build of a "
"library or other binary, but most of them can save space and build time by "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1819
+#: best-pkging-practices.dbk:1812
msgid ""
"The debugging symbols can be extracted from an object file using "
"<command>objcopy --only-keep-debug</command>. Then the object file can be "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1827
+#: best-pkging-practices.dbk:1820
msgid ""
"The <command>dh_strip</command> command in <systemitem "
"role=\"package\">debhelper</systemitem> supports creating debug packages, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1834
+#: best-pkging-practices.dbk:1827
msgid ""
"Note that the debug package should depend on the package that it provides "
"debugging symbols for, and this dependency should be versioned. For "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1838
+#: best-pkging-practices.dbk:1831
#, no-wrap
msgid "Depends: libfoo (= ${binary:Version})\n"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1842
+#: best-pkging-practices.dbk:1835
msgid "Best practices for meta-packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1844
+#: best-pkging-practices.dbk:1837
msgid ""
"A meta-package is a mostly empty package that makes it easy to install a "
"coherent set of packages that can evolve over time. It achieves this by "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1858
+#: best-pkging-practices.dbk:1851
msgid ""
"The long description of the meta-package must clearly document its purpose "
"so that the user knows what they will lose if they remove the package. Being "
#. type: Content of: <chapter><section><title>
#: pkgs.dbk:1241
-msgid "Moving, removing, renaming, adopting, and orphaning packages"
+msgid "Moving, removing, renaming, orphaning, adopting, and reintroducing packages"
msgstr ""
#. type: Content of: <chapter><section><para>
"fact that they will continue to receive the bugs during that time."
msgstr ""
-#. type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><section><title>
+#: pkgs.dbk:1490
+msgid "Reintroducing packages"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
#: pkgs.dbk:1492
+msgid ""
+"Packages are often removed due to release-critical bugs, absent maintainers, "
+"too few users or poor quality in general. While the process of "
+"reintroduction is similar to the initial packaging process, you can avoid "
+"some pitfalls by doing some historical research first."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1498
+msgid ""
+"You should check why the package was removed in the first place. This "
+"information can be found in the removal item in the news section of the PTS "
+"page for the package or by browsing the log of <ulink "
+"url=\"http://&ftp-master-host;/#removed\">removals</ulink>. The removal bug "
+"will tell you why the package was removed and will give some indication of "
+"what you will need to work on in order to reintroduce the package. It may "
+"indicate that the best way forward is to switch to some other piece of "
+"software instead of reintroducing the package."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1508
+msgid ""
+"It may be appropriate to contact the former maintainers to find out if they "
+"are working on reintroducing the package, interested in co-maintaining the "
+"package or interested in sponsoring the package if needed."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1513
+msgid ""
+"You should do all the things required before introducing new packages (<xref "
+"linkend=\"newpackage\"/>)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1517
+msgid ""
+"You should base your work on the latest packaging available that is "
+"suitable. That might be the latest version from "
+"<literal>unstable</literal>, which will still be present in the <ulink "
+"url=\"&snap-debian-org;\">snapshot archive</ulink>."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1522
+msgid ""
+"The version control system used by the previous maintainer might contain "
+"useful changes, so it might be a good idea to have a look there. Check if "
+"the control file of the previous package contained any headers linking to "
+"the version control system for the package and if it still exists."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: pkgs.dbk:1528
+msgid ""
+"Package removals from unstable (not testing, stable or oldstable) trigger "
+"the closing of all bugs related to the package. You should look through all "
+"the closed bugs (including archived bugs) and unarchive and reopen any that "
+"were closed in a version ending in <literal>+rm</literal> and still "
+"apply. Any that no longer apply should be marked as fixed in the correct "
+"version if that is known."
+msgstr ""
+
+#. type: Content of: <chapter><section><title>
+#: pkgs.dbk:1540
msgid "Porting and being ported"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1494
+#: pkgs.dbk:1542
msgid ""
"Debian supports an ever-increasing number of architectures. Even if you are "
"not a porter, and you don't use any architecture but one, it is part of your "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1500
+#: pkgs.dbk:1548
msgid ""
"Porting is the act of building Debian packages for architectures that are "
"different from the original architecture of the package maintainer's binary "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1509
+#: pkgs.dbk:1557
msgid "Being kind to porters"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1511
+#: pkgs.dbk:1559
msgid ""
"Porters have a difficult and unique task, since they are required to deal "
"with a large volume of packages. Ideally, every source package should build "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1519
+#: pkgs.dbk:1567
msgid ""
"The first and most important thing is to respond quickly to bug or issues "
"raised by porters. Please treat porters with courtesy, as if they were in "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1526
+#: pkgs.dbk:1574
msgid ""
"By far, most of the problems encountered by porters are caused by "
"<emphasis>packaging bugs</emphasis> in the source packages. Here is a "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1533
+#: pkgs.dbk:1581
msgid ""
"Make sure that your <literal>Build-Depends</literal> and "
"<literal>Build-Depends-Indep</literal> settings in "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1548
+#: pkgs.dbk:1596
msgid ""
"If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be "
"of assistance (see <xref linkend=\"dpkg-depcheck\"/>)."
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1552
+#: pkgs.dbk:1600
msgid ""
"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for "
"instructions on setting build dependencies."
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1558
+#: pkgs.dbk:1606
msgid ""
"Don't set architecture to a value other than <literal>all</literal> or "
"<literal>any</literal> unless you really mean it. In too many cases, "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1568
+#: pkgs.dbk:1616
msgid ""
"Make sure your source package is correct. Do <literal>dpkg-source -x "
"<replaceable>package</replaceable>.dsc</literal> to make sure your source "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1576
+#: pkgs.dbk:1624
msgid ""
"Make sure you don't ship your source package with the "
"<filename>debian/files</filename> or <filename>debian/substvars</filename> "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1584
+#: pkgs.dbk:1632
msgid ""
"Make sure you don't rely on locally installed or hacked configurations or "
"programs. For instance, you should never be calling programs in "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1593
+#: pkgs.dbk:1641
msgid ""
"Don't depend on the package you're building being installed already (a "
"sub-case of the above issue). There are, of course, exceptions to this rule, "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1601
+#: pkgs.dbk:1649
msgid ""
"Don't rely on the compiler being a certain version, if possible. If not, "
"then make sure your build dependencies reflect the restrictions, although "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1609
+#: pkgs.dbk:1657
msgid ""
"Make sure your <filename>debian/rules</filename> contains separate "
"<literal>binary-arch</literal> and <literal>binary-indep</literal> targets, "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1620
+#: pkgs.dbk:1668
msgid "Guidelines for porter uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1622
+#: pkgs.dbk:1670
msgid ""
"If the package builds out of the box for the architecture to be ported to, "
"you are in luck and your job is easy. This section applies to that case; it "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1630
+#: pkgs.dbk:1678
msgid ""
"For a porter upload, no changes are being made to the source. You do not "
"need to touch any of the files in the source package. This includes "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1635
+#: pkgs.dbk:1683
msgid ""
"The way to invoke <command>dpkg-buildpackage</command> is as "
"<literal>dpkg-buildpackage -B "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1644
+#: pkgs.dbk:1692
msgid ""
"If you are working on a Debian machine for your porting efforts and you need "
"to sign your upload locally for its acceptance in the archive, you can run "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1651
+#: pkgs.dbk:1699
msgid "Recompilation or binary-only NMU"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1653
+#: pkgs.dbk:1701
msgid ""
"Sometimes the initial porter upload is problematic because the environment "
"in which the package was built was not good enough (outdated or obsolete "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1662
+#: pkgs.dbk:1710
msgid ""
"You have to make sure that your binary-only NMU doesn't render the package "
"uninstallable. This could happen when a source package generates "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1668
+#: pkgs.dbk:1716
msgid ""
"Despite the required modification of the changelog, these are called "
"binary-only NMUs — there is no need in this case to trigger all other "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1673
+#: pkgs.dbk:1721
msgid ""
"Such recompilations require special ``magic'' version numbering, so that the "
"archive maintenance tools recognize that, even though there is a new Debian "
msgstr ""
#. type: Content of: <chapter><section><section><section><para><footnote><para>
-#: pkgs.dbk:1688
+#: pkgs.dbk:1736
msgid ""
"In the past, such NMUs used the third-level number on the Debian part of the "
"revision to denote their recompilation-only status; however, this syntax was "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1680
+#: pkgs.dbk:1728
msgid ""
"The ``magic'' for a recompilation-only NMU is triggered by using a suffix "
"appended to the package version number, following the form "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1696
+#: pkgs.dbk:1744
msgid ""
"Similar to initial porter uploads, the correct way of invoking "
"<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1703
+#: pkgs.dbk:1751
msgid "When to do a source NMU if you are a porter"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1705
+#: pkgs.dbk:1753
msgid ""
"Porters doing a source NMU generally follow the guidelines found in <xref "
"linkend=\"nmu\"/>, just like non-porters. However, it is expected that the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1714
+#: pkgs.dbk:1762
msgid ""
"If you are a porter doing an NMU for <literal>unstable</literal>, the above "
"guidelines for porting should be followed, with two variations. Firstly, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1726
+#: pkgs.dbk:1774
msgid ""
"Secondly, porters doing source NMUs should make sure that the bug they "
"submit to the BTS should be of severity <literal>serious</literal> or "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1734
+#: pkgs.dbk:1782
msgid ""
"Porters should try to avoid patches which simply kludge around bugs in the "
"current version of the compile environment, kernel, or libc. Sometimes such "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1742
+#: pkgs.dbk:1790
msgid ""
"Porters may also have an unofficial location where they can put the results "
"of their work during the waiting period. This helps others running the port "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1752
+#: pkgs.dbk:1800
msgid "Porting infrastructure and automation"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1754
+#: pkgs.dbk:1802
msgid ""
"There is infrastructure and several tools to help automate package porting. "
"This section contains a brief overview of this automation and porting to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1759
+#: pkgs.dbk:1807
msgid "Mailing lists and web pages"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1761
+#: pkgs.dbk:1809
msgid ""
"Web pages containing the status of each port can be found at <ulink "
"url=\"&url-debian-ports;\"></ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1765
+#: pkgs.dbk:1813
msgid ""
"Each port of Debian has a mailing list. The list of porting mailing lists "
"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1773
+#: pkgs.dbk:1821
msgid "Porter tools"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1775
+#: pkgs.dbk:1823
msgid ""
"Descriptions of several porting tools can be found in <xref "
"linkend=\"tools-porting\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:1781
+#: pkgs.dbk:1829
msgid "<systemitem role=\"package\">wanna-build</systemitem>"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1783
+#: pkgs.dbk:1831
msgid ""
"The <systemitem role=\"package\">wanna-build</systemitem> system is used as "
"a distributed, client-server build distribution system. It is usually used "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1791
+#: pkgs.dbk:1839
msgid ""
"<systemitem role=\"package\">wanna-build</systemitem> is not yet available "
"as a package; however, all Debian porting efforts are using it for automated "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1800
+#: pkgs.dbk:1848
msgid ""
"Most of the data produced by <systemitem "
"role=\"package\">wanna-build</systemitem> which is generally useful to "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1806
+#: pkgs.dbk:1854
msgid ""
"We are quite proud of this system, since it has so many possible uses. "
"Independent development groups can use the system for different sub-flavors "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1813
+#: pkgs.dbk:1861
msgid ""
"The wanna-build team, in charge of the buildds, can be reached at "
"<literal>debian-wb-team@lists.debian.org</literal>. To determine who "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:1820
+#: pkgs.dbk:1868
msgid ""
"When requesting binNMUs or give-backs (retries after a failed build), please "
"use the format described at <ulink url=\"&url-release-wb;\"/>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1829
+#: pkgs.dbk:1877
msgid "When your package is <emphasis>not</emphasis> portable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1831
+#: pkgs.dbk:1879
msgid ""
"Some packages still have issues with building and/or working on some of the "
"architectures supported by Debian, and cannot be ported at all, or not "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1838
+#: pkgs.dbk:1886
msgid ""
"In order to prevent broken packages from being uploaded to the archive, and "
"wasting buildd time, you need to do a few things:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1844
+#: pkgs.dbk:1892
msgid ""
"First, make sure your package <emphasis>does</emphasis> fail to build on "
"architectures that it cannot support. There are a few ways to achieve "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1852
+#: pkgs.dbk:1900
msgid ""
"Additionally, if you believe the list of supported architectures is pretty "
"constant, you should change <literal>any</literal> to a list of supported "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1860
+#: pkgs.dbk:1908
msgid ""
"In order to prevent autobuilders from needlessly trying to build your "
"package, it must be included in <filename>Packages-arch-specific</filename>, "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1869
+#: pkgs.dbk:1917
msgid ""
"Please note that it is insufficient to only add your package to "
"<filename>Packages-arch-specific</filename> without making it fail to build "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1880
+#: pkgs.dbk:1928
msgid "Marking non-free packages as auto-buildable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1882
+#: pkgs.dbk:1930
msgid ""
"By default packages from the <literal>non-free</literal> section are not "
"built by the autobuilder network (mostly because the license of the packages "
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1890
+#: pkgs.dbk:1938
msgid ""
"Check whether it is legally allowed and technically possible to auto-build "
"the package;"
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1896
+#: pkgs.dbk:1944
msgid ""
"Add <literal>XS-Autobuild: yes</literal> into the header part of "
"<filename>debian/control</filename>;"
msgstr ""
#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
-#: pkgs.dbk:1902
+#: pkgs.dbk:1950
msgid ""
"Send an email to &email-nonfree-release; and explain why the package can "
"legitimately and technically be auto-built."
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:1911
+#: pkgs.dbk:1959
msgid "Non-Maintainer Uploads (NMUs)"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:1913
+#: pkgs.dbk:1961
msgid ""
"Every package has one or more maintainers. Normally, these are the people "
"who work on and upload new versions of the package. In some situations, it "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:1922
+#: pkgs.dbk:1970
msgid "When and how to do an NMU"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1925
+#: pkgs.dbk:1973
msgid "Before doing an NMU, consider the following questions:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1930
+#: pkgs.dbk:1978
msgid ""
"Does your NMU really fix bugs? Fixing cosmetic issues or changing the "
"packaging style in NMUs is discouraged."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1936
+#: pkgs.dbk:1984
msgid ""
"Did you give enough time to the maintainer? When was the bug reported to the "
"BTS? Being busy for a week or two isn't unusual. Is the bug so severe that "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1943
+#: pkgs.dbk:1991
msgid ""
"How confident are you about your changes? Please remember the Hippocratic "
"Oath: \"Above all, do no harm.\" It is better to leave a package with an "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1953
+#: pkgs.dbk:2001
msgid ""
"Have you clearly expressed your intention to NMU, at least in the BTS? It is "
"also a good idea to try to contact the maintainer by other means (private "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1960
+#: pkgs.dbk:2008
msgid ""
"If the maintainer is usually active and responsive, have you tried to "
"contact them? In general it should be considered preferable that maintainers "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1970
+#: pkgs.dbk:2018
msgid ""
"When doing an NMU, you must first make sure that your intention to NMU is "
"clear. Then, you must send a patch with the differences between the current "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1977
+#: pkgs.dbk:2025
msgid ""
"While preparing the patch, you should better be aware of any "
"package-specific practices that the maintainer might be using. Taking them "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:1985
+#: pkgs.dbk:2033
msgid ""
"Unless you have an excellent reason not to do so, you must then give some "
"time to the maintainer to react (for example, by uploading to the "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1992
+#: pkgs.dbk:2040
msgid ""
"Upload fixing only release-critical bugs older than 7 days, with no "
"maintainer activity on the bug for 7 days and no indication that a fix is in "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:1997
+#: pkgs.dbk:2045
msgid "Upload fixing only release-critical bugs older than 7 days: 2 days"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2002
+#: pkgs.dbk:2050
msgid "Upload fixing only release-critical and important bugs: 5 days"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2007
+#: pkgs.dbk:2055
msgid "Other NMUs: 10 days"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2013
+#: pkgs.dbk:2061
msgid ""
"Those delays are only examples. In some cases, such as uploads fixing "
"security issues, or fixes for trivial bugs that blocking a transition, it is "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2019
+#: pkgs.dbk:2067
msgid ""
"Sometimes, release managers decide to allow NMUs with shorter delays for a "
"subset of bugs (e.g release-critical bugs older than 7 days). Also, some "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2029
+#: pkgs.dbk:2077
msgid ""
"After you upload an NMU, you are responsible for the possible problems that "
"you might have introduced. You must keep an eye on the package (subscribing "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2035
+#: pkgs.dbk:2083
msgid ""
"This is not a license to perform NMUs thoughtlessly. If you NMU when it is "
"clear that the maintainers are active and would have acknowledged a patch in "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2045
+#: pkgs.dbk:2093
msgid "NMUs and <filename>debian/changelog</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2047
+#: pkgs.dbk:2095
msgid ""
"Just like any other (source) upload, NMUs must add an entry to "
"<filename>debian/changelog</filename>, telling what has changed with this "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2052
+#: pkgs.dbk:2100
#, no-wrap
msgid " * Non-maintainer upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2056
+#: pkgs.dbk:2104
msgid "The way to version NMUs differs for native and non-native packages."
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2059
+#: pkgs.dbk:2107
msgid ""
"If the package is a native package (without a Debian revision in the version "
"number), the version must be the version of the last maintainer upload, plus "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2069
+#: pkgs.dbk:2117
msgid ""
"If the package is not a native package, you should add a minor version "
"number to the Debian revision part of the version number (the portion after "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2078
+#: pkgs.dbk:2126
msgid ""
"In both cases, if the last upload was also an NMU, the counter should be "
"increased. For example, if the current version is "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2084
+#: pkgs.dbk:2132
msgid ""
"A special versioning scheme is needed to avoid disrupting the maintainer's "
"work, since using an integer for the Debian revision will potentially "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2094
+#: pkgs.dbk:2141
msgid ""
"If you upload a package to testing or stable, you sometimes need to \"fork\" "
"the version number tree. This is the case for security uploads, for "
"example. For this, a version of the form "
-"<literal>+deb<replaceable>XY</replaceable>u<replaceable>Z</replaceable></literal> "
-"should be used, where <replaceable>X</replaceable> and "
-"<replaceable>Y</replaceable> are the major and minor release numbers, and "
-"<replaceable>Z</replaceable> is a counter starting at <literal>1</literal>. "
-"When the release number is not yet known (often the case for "
-"<literal>testing</literal>, at the beginning of release cycles), the lowest "
-"release number higher than the last stable release number must be used. For "
-"example, while Lenny (Debian 5.0) is stable, a security NMU to stable for a "
-"package at version <literal>1.5-3</literal> would have version "
-"<literal>1.5-3+deb50u1</literal>, whereas a security NMU to Squeeze would "
-"get version <literal>1.5-3+deb60u1</literal>. After the release of Squeeze, "
-"security uploads to the <literal>testing</literal> distribution will be "
-"versioned <literal>+deb61uZ</literal>, until it is known whether that "
-"release will be Debian 6.1 or Debian 7.0 (if that becomes the case, uploads "
-"will be versioned as <literal>+deb70uZ</literal>)."
+"<literal>+deb<replaceable>X</replaceable>u<replaceable>Y</replaceable></literal> "
+"should be used, where <replaceable>X</replaceable> is the major release "
+"number, and <replaceable>Y</replaceable> is a counter starting at "
+"<literal>1</literal>. For example, while Wheezy (Debian 7.0) is stable, a "
+"security NMU to stable for a package at version <literal>1.5-3</literal> "
+"would have version <literal>1.5-3+deb7u1</literal>, whereas a security NMU "
+"to Jessie would get version <literal>1.5-3+deb8u1</literal>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2116
+#: pkgs.dbk:2155
msgid "Using the <literal>DELAYED/</literal> queue"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2119
+#: pkgs.dbk:2158
msgid ""
"Having to wait for a response after you request permission to NMU is "
"inefficient, because it costs the NMUer a context switch to come back to the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2133
+#: pkgs.dbk:2172
msgid ""
"The <literal>DELAYED</literal> queue should not be used to put additional "
"pressure on the maintainer. In particular, it's important that you are "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2140
+#: pkgs.dbk:2179
msgid ""
"If you make an NMU to <literal>DELAYED</literal> and the maintainer updates "
"the package before the delay expires, your upload will be rejected because a "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2150
+#: pkgs.dbk:2189
msgid "NMUs from the maintainer's point of view"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2153
+#: pkgs.dbk:2192
msgid ""
"When someone NMUs your package, this means they want to help you to keep it "
"in good shape. This gives users fixed packages faster. You can consider "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2162
+#: pkgs.dbk:2201
msgid ""
"To acknowledge an NMU, include its changes and changelog entry in your next "
"maintainer upload. If you do not acknowledge the NMU by including the NMU "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2171
+#: pkgs.dbk:2210
msgid "Source NMUs vs Binary-only NMUs (binNMUs)"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2174
+#: pkgs.dbk:2213
msgid ""
"The full name of an NMU is <emphasis>source NMU</emphasis>. There is also "
"another type, namely the <emphasis>binary-only NMU</emphasis>, or "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2181
+#: pkgs.dbk:2220
msgid ""
"When a library (or other dependency) is updated, the packages using it may "
"need to be rebuilt. Since no changes to the source are needed, the same "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2187
+#: pkgs.dbk:2226
msgid ""
"BinNMUs are usually triggered on the buildds by wanna-build. An entry is "
"added to <filename>debian/changelog</filename>, explaining why the upload "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2195
+#: pkgs.dbk:2234
msgid ""
"Buildds upload packages for their architecture to the archive as binary-only "
"uploads. Strictly speaking, these are binNMUs. However, they are not "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2203
+#: pkgs.dbk:2242
msgid "NMUs vs QA uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2206
+#: pkgs.dbk:2245
msgid ""
"NMUs are uploads of packages by somebody else than their assigned "
"maintainer. There is another type of upload where the uploaded package is "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2213
+#: pkgs.dbk:2252
msgid ""
"QA uploads are very much like normal maintainer uploads: they may fix "
"anything, even minor issues; the version numbering is normal, and there is "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2221
+#: pkgs.dbk:2260
#, no-wrap
msgid " * QA upload.\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2225
+#: pkgs.dbk:2264
msgid ""
"If you want to do an NMU, and it seems that the maintainer is not active, it "
"is wise to check if the package is orphaned (this information is displayed "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2236
+#: pkgs.dbk:2275
msgid ""
"Instead of doing a QA upload, you can also consider adopting the package by "
"making yourself the maintainer. You don't need permission from anybody to "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2245
+#: pkgs.dbk:2284
msgid "NMUs vs team uploads"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2248
+#: pkgs.dbk:2287
msgid ""
"Sometimes you are fixing and/or updating a package because you are member of "
"a packaging team (which uses a mailing list as <literal>Maintainer</literal> "
msgstr ""
#. type: Content of: <chapter><section><section><screen>
-#: pkgs.dbk:2258
+#: pkgs.dbk:2297
#, no-wrap
msgid " * Team upload.\n"
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2266
+#: pkgs.dbk:2305
msgid "Collaborative maintenance"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2268
+#: pkgs.dbk:2307
msgid ""
"Collaborative maintenance is a term describing the sharing of Debian package "
"maintenance duties by several people. This collaboration is almost always a "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2276
+#: pkgs.dbk:2315
msgid ""
"Generally there is a primary maintainer and one or more co-maintainers. The "
"primary maintainer is the person whose name is listed in the "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2284
+#: pkgs.dbk:2323
msgid ""
"In its most basic form, the process of adding a new co-maintainer is quite "
"easy:"
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2290
+#: pkgs.dbk:2329
msgid ""
"Setup the co-maintainer with access to the sources you build the package "
"from. Generally this implies you are using a network-capable version "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2298
+#: pkgs.dbk:2337
msgid ""
"Add the co-maintainer's correct maintainer name and address to the "
"<literal>Uploaders</literal> field in the first paragraph of the "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><screen>
-#: pkgs.dbk:2303
+#: pkgs.dbk:2342
#, no-wrap
msgid ""
"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex "
msgstr ""
#. type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2308
+#: pkgs.dbk:2347
msgid ""
"Using the PTS (<xref linkend=\"pkg-tracking-system\"/>), the co-maintainers "
"should subscribe themselves to the appropriate source package."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2314
+#: pkgs.dbk:2353
msgid ""
"Another form of collaborative maintenance is team maintenance, which is "
"recommended if you maintain several packages with the same group of "
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2323
+#: pkgs.dbk:2362
msgid ""
"Put the team member mainly responsible for the package in the "
"<literal>Maintainer</literal> field. In the <literal>Uploaders</literal>, "
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: pkgs.dbk:2330
+#: pkgs.dbk:2369
msgid ""
"Put the mailing list address in the <literal>Maintainer</literal> field. In "
"the <literal>Uploaders</literal> field, put the team members who care for "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: pkgs.dbk:2339
+#: pkgs.dbk:2378
msgid ""
"In any case, it is a bad idea to automatically put all team members in the "
"<literal>Uploaders</literal> field. It clutters the Developer's Package "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: pkgs.dbk:2352
+#: pkgs.dbk:2391
msgid "The testing distribution"
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2354
+#: pkgs.dbk:2393
msgid "Basics"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2356
+#: pkgs.dbk:2395
msgid ""
"Packages are usually installed into the <literal>testing</literal> "
"distribution after they have undergone some degree of "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2361
+#: pkgs.dbk:2400
msgid ""
"They must be in sync on all architectures and mustn't have dependencies that "
"make them uninstallable; they also have to have generally no known "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2370
+#: pkgs.dbk:2409
msgid "Updates from unstable"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2372
+#: pkgs.dbk:2411
msgid ""
"The scripts that update the <literal>testing</literal> distribution are run "
"twice each day, right after the installation of the updated packages; these "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2380
+#: pkgs.dbk:2419
msgid ""
"The inclusion of a package from <literal>unstable</literal> is conditional "
"on the following:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2386
+#: pkgs.dbk:2425
msgid ""
"The package must have been available in <literal>unstable</literal> for 2, 5 "
"or 10 days, depending on the urgency (high, medium or low). Please note "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2394
+#: pkgs.dbk:2433
msgid ""
"It must not have new release-critical bugs (RC bugs affecting the version "
"available in <literal>unstable</literal>, but not affecting the version in "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2401
+#: pkgs.dbk:2440
msgid ""
"It must be available on all architectures on which it has previously been "
"built in <literal>unstable</literal>. <link linkend=\"dak-ls\">dak ls</link> "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2408
+#: pkgs.dbk:2447
msgid ""
"It must not break any dependency of a package which is already available in "
"<literal>testing</literal>;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2414
+#: pkgs.dbk:2453
msgid ""
"The packages on which it depends must either be available in "
"<literal>testing</literal> or they must be accepted into "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2422
+#: pkgs.dbk:2461
msgid ""
"The phase of the project. I.e. automatic transitions are turned off during "
"the <emphasis>freeze</emphasis> of the <literal>testing</literal> "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2428
+#: pkgs.dbk:2467
msgid ""
"To find out whether a package is progressing into <literal>testing</literal> "
"or not, see the <literal>testing</literal> script output on the <ulink "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2439
+#: pkgs.dbk:2478
msgid ""
"The <filename>update_excuses</filename> file does not always give the "
"precise reason why the package is refused; you may have to find it on your "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2446
+#: pkgs.dbk:2485
msgid ""
"Sometimes, some packages never enter <literal>testing</literal> because the "
"set of interrelationship is too complicated and cannot be sorted out by the "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2451
+#: pkgs.dbk:2490
msgid ""
"Some further dependency analysis is shown on <ulink "
"url=\"http://release.debian.org/migration/\"></ulink> — but be warned, this "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2456
+#: pkgs.dbk:2495
msgid "Out-of-date"
msgstr ""
#. FIXME: better rename this file than document rampant professionalism?
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2459
+#: pkgs.dbk:2498
msgid ""
"For the <literal>testing</literal> migration script, outdated means: There "
"are different versions in <literal>unstable</literal> for the release "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2467
+#: pkgs.dbk:2506
msgid "Consider this example:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2474 pkgs.dbk:2507
+#: pkgs.dbk:2513 pkgs.dbk:2546
msgid "alpha"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2475 pkgs.dbk:2508
+#: pkgs.dbk:2514 pkgs.dbk:2547
msgid "arm"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2480 pkgs.dbk:2514 pkgs.dbk:2576
+#: pkgs.dbk:2519 pkgs.dbk:2553 pkgs.dbk:2615
msgid "testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2481 pkgs.dbk:2486 pkgs.dbk:2515 pkgs.dbk:2516 pkgs.dbk:2523
+#: pkgs.dbk:2520 pkgs.dbk:2525 pkgs.dbk:2554 pkgs.dbk:2555 pkgs.dbk:2562
msgid "1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2482 pkgs.dbk:2517 pkgs.dbk:2522
+#: pkgs.dbk:2521 pkgs.dbk:2556 pkgs.dbk:2561
msgid "-"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2485 pkgs.dbk:2520 pkgs.dbk:2577
+#: pkgs.dbk:2524 pkgs.dbk:2559 pkgs.dbk:2616
msgid "unstable"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2487 pkgs.dbk:2521
+#: pkgs.dbk:2526 pkgs.dbk:2560
msgid "2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2493
+#: pkgs.dbk:2532
msgid ""
"The package is out of date on <literal>alpha</literal> in "
"<literal>unstable</literal>, and will not go to "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2499
+#: pkgs.dbk:2538
msgid ""
"However, if ftp-master removes a package in <literal>unstable</literal> "
"(here on <literal>arm</literal>):"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry>
-#: pkgs.dbk:2509
+#: pkgs.dbk:2548
msgid "hurd-i386"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2529
+#: pkgs.dbk:2568
msgid ""
"In this case, the package is up to date on all release architectures in "
"<literal>unstable</literal> (and the extra <literal>hurd-i386</literal> "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2534
+#: pkgs.dbk:2573
msgid ""
"Sometimes, the question is raised if it is possible to allow packages in "
"that are not yet built on all architectures: No. Just plainly no. (Except "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2541
+#: pkgs.dbk:2580
msgid "Removals from testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2543
+#: pkgs.dbk:2582
msgid ""
"Sometimes, a package is removed to allow another package in: This happens "
"only to allow <emphasis>another</emphasis> package to go in if it's ready in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2550
+#: pkgs.dbk:2589
msgid ""
"Of course, there is another reason to remove a package from "
"<literal>testing</literal>: It's just too buggy (and having a single RC-bug "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2555
+#: pkgs.dbk:2594
msgid ""
"Furthermore, if a package has been removed from <literal>unstable</literal>, "
"and no package in <literal>testing</literal> depends on it any more, then it "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2562
+#: pkgs.dbk:2601
msgid "Circular dependencies"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2564
+#: pkgs.dbk:2603
msgid ""
"A situation which is not handled very well by britney is if package "
"<literal>a</literal> depends on the new version of package "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2569
+#: pkgs.dbk:2608
msgid "An example of this is:"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2582
+#: pkgs.dbk:2621
msgid "a"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2583
+#: pkgs.dbk:2622
msgid "1; depends: b=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2584
+#: pkgs.dbk:2623
msgid "2; depends: b=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2587
+#: pkgs.dbk:2626
msgid "b"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2588
+#: pkgs.dbk:2627
msgid "1; depends: a=1"
msgstr ""
#. type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry>
-#: pkgs.dbk:2589
+#: pkgs.dbk:2628
msgid "2; depends: a=2"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2595
+#: pkgs.dbk:2634
msgid ""
"Neither package <literal>a</literal> nor package <literal>b</literal> is "
"considered for update."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2599
+#: pkgs.dbk:2638
msgid ""
"Currently, this requires some manual hinting from the release team. Please "
"contact them by sending mail to &email-debian-release; if this happens to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2606
+#: pkgs.dbk:2645
msgid "Influence of package in testing"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2608
+#: pkgs.dbk:2647
msgid ""
"Generally, there is nothing that the status of a package in "
"<literal>testing</literal> means for transition of the next version from "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2620
+#: pkgs.dbk:2659
msgid ""
"In summary this means: The only influence that a package being in "
"<literal>testing</literal> has on a new version of the same package is that "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2627
+#: pkgs.dbk:2666
msgid "Details"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2629
+#: pkgs.dbk:2668
msgid "If you are interested in details, this is how britney works:"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2632
+#: pkgs.dbk:2671
msgid ""
"The packages are looked at to determine whether they are valid candidates. "
"This gives the update excuses. The most common reasons why a package is not "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2639
+#: pkgs.dbk:2678
msgid ""
"Now, the more complex part happens: Britney tries to update "
"<literal>testing</literal> with the valid candidates. For that, britney "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2649
+#: pkgs.dbk:2688
msgid ""
"If you want to see more details, you can look it up on <ulink "
"url=\"http://&ftp-master-host;/testing/update_output/\"></ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2653
+#: pkgs.dbk:2692
msgid ""
"The hints are available via <ulink "
"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>, where you can find "
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2667
+#: pkgs.dbk:2706
msgid "Direct updates to testing"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2669
+#: pkgs.dbk:2708
msgid ""
"The <literal>testing</literal> distribution is fed with packages from "
"<literal>unstable</literal> according to the rules explained above. "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2676
+#: pkgs.dbk:2715
msgid ""
"Keep in mind that packages uploaded there are not automatically processed, "
"they have to go through the hands of the release manager. So you'd better "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2683
+#: pkgs.dbk:2722
msgid ""
"You should not upload to <literal>testing-proposed-updates</literal> when "
"you can update your packages through <literal>unstable</literal>. If you "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2692
+#: pkgs.dbk:2731
msgid ""
"Version numbers are usually selected by adding the codename of the "
"<literal>testing</literal> distribution and a running number, like "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: pkgs.dbk:2699
+#: pkgs.dbk:2738
msgid "Please make sure you didn't miss any of these items in your upload:"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2704
+#: pkgs.dbk:2743
msgid ""
"Make sure that your package really needs to go through "
"<literal>testing-proposed-updates</literal>, and can't go through "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2711
+#: pkgs.dbk:2750
msgid "Make sure that you included only the minimal amount of changes;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2716
+#: pkgs.dbk:2755
msgid "Make sure that you included an appropriate explanation in the changelog;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2721
+#: pkgs.dbk:2760
msgid ""
"Make sure that you've written <literal>testing</literal> or "
"<literal>testing-proposed-updates</literal> into your target distribution;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2727
+#: pkgs.dbk:2766
msgid ""
"Make sure that you've built and tested your package in "
"<literal>testing</literal>, not in <literal>unstable</literal>;"
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2733
+#: pkgs.dbk:2772
msgid ""
"Make sure that your version number is higher than the version in "
"<literal>testing</literal> and <literal>testing-proposed-updates</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: pkgs.dbk:2740
+#: pkgs.dbk:2779
msgid ""
"After uploading and successful build on all platforms, contact the release "
"team at &email-debian-release; and ask them to approve your upload."
msgstr ""
#. type: Content of: <chapter><section><section><title>
-#: pkgs.dbk:2748
+#: pkgs.dbk:2787
msgid "Frequently asked questions"
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2750
+#: pkgs.dbk:2789
msgid "What are release-critical bugs, and how do they get counted?"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2752
+#: pkgs.dbk:2791
msgid ""
"All bugs of some higher severities are by default considered "
"release-critical; currently, these are <literal>critical</literal>, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2757
+#: pkgs.dbk:2796
msgid ""
"Such bugs are presumed to have an impact on the chances that the package "
"will be released with the <literal>stable</literal> release of Debian: in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2764
+#: pkgs.dbk:2803
msgid ""
"The <literal>unstable</literal> bug count are all release-critical bugs "
"which are marked to apply to "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: pkgs.dbk:2772
+#: pkgs.dbk:2811
msgid ""
"How could installing a package into <literal>testing</literal> possibly "
"break other packages?"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2775
+#: pkgs.dbk:2814
msgid ""
"The structure of the distribution archives is such that they can only "
"contain one version of a package; a package is defined by its name. So when "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2783
+#: pkgs.dbk:2822
msgid ""
"However, the old version may have provided a binary package with an old "
"soname of a library, such as <literal>libacme-foo0</literal>. Removing the "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2789
+#: pkgs.dbk:2828
msgid ""
"Evidently, this mainly affects packages which provide changing sets of "
"binary packages in different versions (in turn, mainly libraries). However, "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2795
+#: pkgs.dbk:2834
msgid ""
"When the set of binary packages provided by a source package change in this "
"way, all the packages that depended on the old binaries will have to be "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: pkgs.dbk:2806
+#: pkgs.dbk:2845
msgid ""
"If you are having problems with complicated groups of packages like this, "
"contact &email-debian-devel; or &email-debian-release; for help."
~ianmdlvl / developers-reference.git / blobdiff