From: debacle Date: Sun, 1 Jul 2007 23:43:58 +0000 (+0000) Subject: Now everything builds. Translators needed! X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=commitdiff_plain;h=77cab965d9dbb3b3ec96b588c612b3dba78efb3a;ds=sidebyside Now everything builds. Translators needed! git-svn-id: svn://anonscm.debian.org/ddp/developers-reference/trunk@4912 313b444b-1b9f-4f58-a734-7bb04f332e8d --- diff --git a/Makefile b/Makefile index 2dfbe39..17f2168 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,8 @@ # Makefile, used for the developers-reference in DocBook XML -SOURCES := $(wildcard *.dbk *.ent) +# Note: This Makefile should work perfectly without the debian/ directory. + +SOURCES := $(wildcard *.dbk) common.ent version.ent FORMATS := html txt pdf LANGS := fr ja @@ -8,6 +10,11 @@ TARGETS := $(foreach fmt,$(FORMATS),developers-reference.$(fmt)) \ $(foreach lng,$(LANGS), \ $(foreach fmt,$(FORMATS), \ $(lng)/developers-reference.$(fmt))) + +# hopefully overwritten by caller, e.g. debian/rules +VERSION=unknown +PUBDATE=unknown + # programs for creating output XP=xsltproc --nonet --novalid --xinclude XL=xmllint --nonet --noout --postvalid --xinclude @@ -18,8 +25,8 @@ XL=xmllint --nonet --noout --postvalid --xinclude # - docbook2pdf (seems to die on UTF-8, #431085); and # - xmllint (not mature enough, waits in NEW, #182445) FOP=fop -# The "-k 0" should be removed as soon as the translations are ready -TRANSLATE=po4a-translate -f docbook -k 0 +# The "--keep 0" should be removed as soon as the translations are ready +TRANSLATE=po4a-translate --format docbook --keep 0 # XSL files and parameters # note: the URL is used as identifier, no HTTP is used! @@ -59,7 +66,8 @@ index.html: $(PWD)/developers-reference.html .PRECIOUS: %.dbk %.ent ifndef LINGUA %.dbk %.ent: FORCE - [ "$$LINGUA" = . ] || $(MAKE) $@ LINGUA=$(@D) + $(MAKE) $@ LINGUA=$(@D) + FORCE: else $(LINGUA)/%.dbk: %.dbk $(patsubst %.dbk,po4a/$(LINGUA)/%.po,%.dbk) @@ -84,8 +92,21 @@ developers-reference.pdf: $(PWD)/developers-reference.pdf %/developers-reference.pdf: %/developers-reference.fo $(FOP) -fo $< -pdf $@ -version.ent: debian/changelog - ./debian/rules $@ +.PHONY: pot +pot: $(patsubst %.dbk,po4a/po/%.pot,$(SOURCES)) +po4a/po/%.pot: %.dbk + po4a-gettextize --format docbook --master $< --po $@ + +ifdef LINGUA +.PHONY: updatepo +updatepo: $(patsubst %.dbk,po4a/$(LINGUA)/%.po,$(SOURCES)) +po4a/$(LINGUA)/%.po: %.dbk + po4a-updatepo --format docbook --master $< --po $@ +endif + +version.ent: + echo '' > $@ + echo '' >> $@ .PHONY: clean clean: diff --git a/README-contrib b/README-contrib index 226b5a9..2afeddf 100644 --- a/README-contrib +++ b/README-contrib @@ -3,16 +3,25 @@ The following 'make' targets exist for your convenience: make validate - validate the well-formedness of all SGML materials + validate the well-formedness of all XML materials - make all + make or make all (optional: VERSION=x.y.z PUBDATE=2007-07-01) build all languages in all formats - make developers-reference.sgml.validate - validate the well-formedness of the English manual + make index.html + build the English manual in HTML format - make developers-reference.html - build the English manual + make fr/developers-reference.pdf + build the French manual in PDF format + + make ja/developers-reference.txt + build the Japanese manual in text format + + make pot + generate .pot files from .dbk sources + + make updatepo LINGUA=xx (with xx=language code) + update .po files for language xx * Contacting @@ -26,25 +35,25 @@ To contain the maintainers of this package, email If you want to contribute to the Developer's Reference, it's best to first submit a few patches as bug reports. Writing patches for existing bugs are also always appreciated. You may wish to make -patches against the CVS sources, about which see below. +patches against the SVN sources, about which see below. Do not commit patches to the developers reference yourself unless authorized to do so. Patches need to be finalized and common opinion before they are applied. This is even true if you happen to have -cvs access for other reasons. +SVN access for other reasons. -* CVS +* SVN If you're interested in ongoing maintenance, once you've shown that you've mastered the style of the manual with a couple accepted -patches, you can be given CVS pserver access. If you have already -access to the CVS server for other reasons, do not use it unless +patches, you can be given SVN access. If you have already +access to the SVN server for other reasons, do not use it unless authorized to do so. -Instructions on how to get the CVS version of this software, including -how to get CVS access, can be found at -. +Instructions on how to get the SVN version of this software, including +how to get SVN access, can be found at +. * Translators @@ -53,19 +62,5 @@ We have tried to keep language-independant bits of text in common.ent. Feel free to truck stuff out of the English manual into common.ent if it's useful, or else report the problem. -You should exploit CVS to see the diffs between when the document was -last translated and the latest version. Be sure to set the cvs-en-rev -entity as appropriate when you do update a translation. - -We have provided commands to help with this. To see the difference in -numbers between the latest translated version and the latest version, -do, for instance: - - ./translation-status fr - -To get the diff between the latest translated version and the latest -version: - - ./translation-status -d fr - - +The translation .po files are in po4a/fr/ and po4a/ja/ for French and +Japanese. We hope very much for more translations. diff --git a/debian/rules b/debian/rules index 4311407..906ff70 100755 --- a/debian/rules +++ b/debian/rules @@ -10,8 +10,8 @@ docbaserel := /usr/share/doc-base docbasedir := $(prefix)$(docbaserel) # list of language packages, in the form pkg-LANG; must jibe -# with debian/control, see also DATE_uc(LANG) below -langs := fr +# with debian/control +langs := fr ja # tool abstraction install_file := install -o root -g root -m 644 -p @@ -22,23 +22,15 @@ make_directory := install -d -o root -g root -m 755 DEB_VERSION := $(shell awk -F '[()]' '/^$(package)/{ print $$2; exit }' debian/changelog) DEB_DATE := $(shell dpkg-parsechangelog 2>/dev/null | sed -n 's/^Date: *//p') # pretty-print the date; I wish this was dynamic like the top-level makefile but oh well -DATE_EN := $(shell LC_ALL=C date --date="$(DEB_DATE)" '+%d %B, %Y') -DATE_FR := $(shell LC_ALL=fr_FR date --date="$(DEB_DATE)" '+%d %B %Y') -DATE_JA := $(shell LC_ALL=ja_JP date --date="$(DEB_DATE)" '+%x') +PUBDATE := $(shell LC_ALL=C date --date="$(DEB_DATE)" -I) # debhelper verbose mode #export DH_VERBOSE=1 -version.ent: debian/changelog - :> version.ent - echo "" >> version.ent - echo "" >> version.ent - echo "" >> version.ent - echo "" >> version.ent - build: $(checkdir) - $(MAKE) + rm -f version.ent + $(MAKE) VERSION=$(DEB_VERSION) PUBDATE=$(PUBDATE) touch build .PHONY: clean @@ -58,12 +50,16 @@ install: build $(checkroot) dh_clean -k - dh_installdocs -p$(package) README-contrib developers-reference.txt \ - developers-reference.pdf developers-reference.html/* + dh_installdocs -p$(package) README-contrib \ + *.html \ + developers-reference.txt \ + developers-reference.pdf set -e; for lang in $(langs); do \ - dh_installdocs -p$(package)-$$lang README-contrib developers-reference.$$lang.txt \ - developers-reference.$$lang.pdf developers-reference.$$lang.html/* ;\ + dh_installdocs -p$(package)-$$lang README-contrib \ + $$lang/*.html \ + $$lang/developers-reference.txt \ + $$lang/developers-reference.pdf; \ done @@ -89,7 +85,7 @@ binary-arch: build install define checkdir test -f debian/rules - test -f developers-reference.sgml + test -f index.dbk endef # Below here is fairly generic really @@ -100,7 +96,3 @@ endef .PHONY: binary binary: binary-indep binary-arch - -#Local variables: -#mode: makefile -#End: diff --git a/index.dbk b/index.dbk index af81e02..a92739c 100644 --- a/index.dbk +++ b/index.dbk @@ -2,6 +2,7 @@ %commondata; + %versiondata; ]> @@ -26,8 +27,8 @@ Ian Jackson -ver. 3.3.9, 16 June, 2007 - +ver. &version; +&pubdate; 2004 2005 @@ -77,6 +78,8 @@ it by writing to the &fsf-addr;. If you want to print this reference, you should use the pdf version. This page is also available in French. + diff --git a/po4a/fr/best-pkging-practices.po b/po4a/fr/best-pkging-practices.po index afae0ad..94dd2af 100644 --- a/po4a/fr/best-pkging-practices.po +++ b/po4a/fr/best-pkging-practices.po @@ -1,38 +1,40 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR , YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:09+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: -#: best-pkging-practices.dbk:5 +#: best-pkging-practices.dbk:7 msgid "Best Packaging Practices" -msgstr "" +msgstr "Les meilleurs pratiques pour la construction des paquets" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:7 +#: best-pkging-practices.dbk:9 msgid "" -"Debian's quality is largely due to the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>, " -"which defines explicit baseline requirements which all Debian packages must " -"fulfill. Yet there is also a shared history of experience which goes beyond " -"the Debian Policy, an accumulation of years of experience in packaging. " -"Many very talented people have created great tools, tools which help you, " -"the Debian maintainer, create and maintain excellent packages." +"Debian's quality is largely due to the <ulink url=\"&url-debian-policy;" +"\">Debian Policy</ulink>, which defines explicit baseline requirements which " +"all Debian packages must fulfill. Yet there is also a shared history of " +"experience which goes beyond the Debian Policy, an accumulation of years of " +"experience in packaging. Many very talented people have created great " +"tools, tools which help you, the Debian maintainer, create and maintain " +"excellent packages." msgstr "" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:16 +#: best-pkging-practices.dbk:18 msgid "" "This chapter provides some best practices for Debian developers. All " "recommendations are merely that, and are not requirements or policy. These " @@ -41,12 +43,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:22 +#: best-pkging-practices.dbk:24 msgid "Best practices for <filename>debian/rules</filename>" -msgstr "" +msgstr "Les meilleures pratiques pour le fichier <filename>debian/rules</filename>" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:24 +#: best-pkging-practices.dbk:26 msgid "" "The following recommendations apply to the <filename>debian/rules</filename> " "file. Since <filename>debian/rules</filename> controls the build process " @@ -55,27 +57,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:30 +#: best-pkging-practices.dbk:32 msgid "Helper scripts" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:32 +#: best-pkging-practices.dbk:34 msgid "" "The rationale for using helper scripts in <filename>debian/rules</filename> " "is that they let maintainers use and share common logic among many " "packages. Take for instance the question of installing menu entries: you " -"need to put the file into <filename>/usr/lib/menu</filename> (or " -"<filename>/usr/lib/menu</filename> for executable binary menufiles, if this " -"is needed), and add commands to the maintainer scripts to register and " -"unregister the menu entries. Since this is a very common thing for packages " -"to do, why should each maintainer rewrite all this on their own, sometimes " -"with bugs? Also, supposing the menu directory changed, every package would " -"have to be changed." +"need to put the file into <filename>/usr/lib/menu</filename> (or <filename>/" +"usr/lib/menu</filename> for executable binary menufiles, if this is needed), " +"and add commands to the maintainer scripts to register and unregister the " +"menu entries. Since this is a very common thing for packages to do, why " +"should each maintainer rewrite all this on their own, sometimes with bugs? " +"Also, supposing the menu directory changed, every package would have to be " +"changed." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:43 +#: best-pkging-practices.dbk:45 msgid "" "Helper scripts take care of these issues. Assuming you comply with the " "conventions expected by the helper script, the helper takes care of all the " @@ -85,56 +87,55 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:50 +#: best-pkging-practices.dbk:52 msgid "" "<xref linkend=\"tools\"/> contains a couple of different helpers. The most " -"common and best (in our opinion) helper system is <systemitem " -"role=\"package\">debhelper</systemitem>. Previous helper systems, such as " -"<systemitem role=\"package\">debmake</systemitem>, were monolithic: you " -"couldn't pick and choose which part of the helper you found useful, but had " -"to use the helper to do everything. <systemitem " -"role=\"package\">debhelper</systemitem>, however, is a number of separate " -"little <command>dh_*</command> programs. For instance, " -"<command>dh_installman</command> installs and compresses man pages, " -"<command>dh_installmenu</command> installs menu files, and so on. Thus, it " -"offers enough flexibility to be able to use the little helper scripts, where " -"useful, in conjunction with hand-crafted commands in " +"common and best (in our opinion) helper system is <systemitem role=\"package" +"\">debhelper</systemitem>. Previous helper systems, such as <systemitem " +"role=\"package\">debmake</systemitem>, were monolithic: you couldn't pick " +"and choose which part of the helper you found useful, but had to use the " +"helper to do everything. <systemitem role=\"package\">debhelper</" +"systemitem>, however, is a number of separate little <command>dh_*</command> " +"programs. For instance, <command>dh_installman</command> installs and " +"compresses man pages, <command>dh_installmenu</command> installs menu files, " +"and so on. Thus, it offers enough flexibility to be able to use the little " +"helper scripts, where useful, in conjunction with hand-crafted commands in " "<filename>debian/rules</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:64 +#: best-pkging-practices.dbk:66 msgid "" "You can get started with <systemitem role=\"package\">debhelper</systemitem> " "by reading <citerefentry> <refentrytitle>debhelper</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry>, and looking at the examples that " "come with the package. <command>dh_make</command>, from the <systemitem " -"role=\"package\">dh-make</systemitem> package (see <xref " -"linkend=\"dh-make\"/> ), can be used to convert a vanilla source package to " -"a <systemitem role=\"package\">debhelper</systemitem>ized package. This " -"shortcut, though, should not convince you that you do not need to bother " -"understanding the individual <command>dh_*</command> helpers. If you are " -"going to use a helper, you do need to take the time to learn to use that " -"helper, to learn its expectations and behavior." +"role=\"package\">dh-make</systemitem> package (see <xref linkend=\"dh-make\"/" +"> ), can be used to convert a vanilla source package to a <systemitem role=" +"\"package\">debhelper</systemitem>ized package. This shortcut, though, " +"should not convince you that you do not need to bother understanding the " +"individual <command>dh_*</command> helpers. If you are going to use a " +"helper, you do need to take the time to learn to use that helper, to learn " +"its expectations and behavior." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:77 +#: 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=\"http://arch.debian.org/arch/private/srivasta/\"></ulink>." +"<ulink url=\"&url-rules-files;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:86 +#: best-pkging-practices.dbk:88 msgid "Separating your patches into multiple files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:88 +#: best-pkging-practices.dbk:90 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 " @@ -146,20 +147,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:97 +#: best-pkging-practices.dbk:99 msgid "" "Unfortunately, the packaging system as such currently doesn't provide for " "separating the patches into several files. Nevertheless, there are ways to " "separate patches: the patch files are shipped within the Debian patch file " -"(<filename>.diff.gz</filename>), usually within the " -"<filename>debian/</filename> directory. The only difference is that they " -"aren't applied immediately by dpkg-source, but by the " -"<literal>build</literal> rule of <filename>debian/rules</filename>. " -"Conversely, they are reverted in the <literal>clean</literal> rule." +"(<filename>.diff.gz</filename>), usually within the <filename>debian/</" +"filename> directory. The only difference is that they aren't applied " +"immediately by dpkg-source, but by the <literal>build</literal> rule of " +"<filename>debian/rules</filename>. Conversely, they are reverted in the " +"<literal>clean</literal> rule." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:107 +#: best-pkging-practices.dbk:109 msgid "" "<command>dbs</command> is one of the more popular approaches to this. It " "does all of the above, and provides a facility for creating new and updating " @@ -169,67 +170,66 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:114 +#: best-pkging-practices.dbk:116 msgid "" "<command>dpatch</command> also provides these facilities, but it's intended " -"to be even easier to use. See the package <systemitem " -"role=\"package\">dpatch</systemitem> for documentation and examples (in " -"<filename>/usr/share/doc/dpatch</filename>)." +"to be even easier to use. See the package <systemitem role=\"package" +"\">dpatch</systemitem> for documentation and examples (in <filename>/usr/" +"share/doc/dpatch</filename>)." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:122 +#: best-pkging-practices.dbk:124 msgid "Multiple binary packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:124 +#: best-pkging-practices.dbk:126 msgid "" "A single source package will often build several binary packages, either to " -"provide several flavors of the same software (e.g., the <systemitem " -"role=\"package\">vim</systemitem> source package) or to make several small " +"provide several flavors of the same software (e.g., the <systemitem role=" +"\"package\">vim</systemitem> source package) or to make several small " "packages instead of a big one (e.g., so the user can install only the subset " "needed, and thus save some disk space)." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:131 +#: best-pkging-practices.dbk:133 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 " -"the package's temporary trees. You can do this using " -"<command>install</command> or <command>dh_install</command> from <systemitem " -"role=\"package\">debhelper</systemitem>. Be sure to check the different " -"permutations of the various packages, ensuring that you have the " -"inter-package dependencies set right in <filename>debian/control</filename>." +"the package's temporary trees. You can do this using <command>install</" +"command> or <command>dh_install</command> from <systemitem role=\"package" +"\">debhelper</systemitem>. Be sure to check the different permutations of " +"the various packages, ensuring that you have the inter-package dependencies " +"set right in <filename>debian/control</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:140 +#: best-pkging-practices.dbk:142 msgid "" "The first case is a bit more difficult since it involves multiple recompiles " "of the same software but with different configuration options. The " "<systemitem role=\"package\">vim</systemitem> source package is an example " -"of how to manage this using an hand-crafted " -"<filename>debian/rules</filename> file." +"of how to manage this using an hand-crafted <filename>debian/rules</" +"filename> file." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:150 +#: best-pkging-practices.dbk:154 msgid "Best practices for <filename>debian/control</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:152 +#: best-pkging-practices.dbk:156 msgid "" -"The following practices are relevant to the " -"<filename>debian/control</filename> file. They supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-binary.html#s-descriptions\">Policy " -"on package descriptions</ulink>." +"The following practices are relevant to the <filename>debian/control</" +"filename> file. They supplement the <ulink url=\"&url-debian-policy;ch-" +"binary.html#s-descriptions\">Policy on package descriptions</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:158 +#: best-pkging-practices.dbk:162 msgid "" "The description of the package, as defined by the corresponding field in the " "<filename>control</filename> file, contains both the package synopsis and " @@ -241,12 +241,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:167 +#: best-pkging-practices.dbk:171 msgid "General guidelines for package descriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:169 +#: best-pkging-practices.dbk:173 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, " @@ -256,16 +256,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:176 +#: best-pkging-practices.dbk:180 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 " -"non-technical users. Unless your package really is only for technical " -"users, this is a problem." +"descriptions are technical, that is, are not written to make sense for non-" +"technical users. Unless your package really is only for technical users, " +"this is a problem." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:182 +#: best-pkging-practices.dbk:186 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 — " @@ -275,7 +275,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:189 +#: best-pkging-practices.dbk:193 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 " @@ -283,37 +283,36 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:194 +#: best-pkging-practices.dbk:198 msgid "" "References to the names of any other software packages, protocol names, " "standards, or specifications should use their canonical forms, if one " -"exists. For example, use X Window System, X11, or X; not X Windows, " -"X-Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. " -"Use PostScript, not Postscript or postscript." +"exists. For example, use X Window System, X11, or X; not X Windows, X-" +"Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. Use " +"PostScript, not Postscript or postscript." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:201 +#: best-pkging-practices.dbk:205 msgid "" "If you are having problems writing your description, you may wish to send it " -"along to <email>debian-l10n-english@lists.debian.org</email> and request " -"feedback." +"along to &email-debian-l10n-english; and request feedback." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:208 +#: best-pkging-practices.dbk:211 msgid "The package synopsis, or short description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:210 +#: best-pkging-practices.dbk:213 msgid "" "The synopsis line (the short description) should be concise. It must not " "repeat the package's name (this is policy)." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:214 +#: best-pkging-practices.dbk:217 msgid "" "It's a good idea to think of the synopsis as an appositive clause, not a " "full sentence. An appositive clause is defined in WordNet as a grammatical " @@ -326,48 +325,42 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:223 +#: best-pkging-practices.dbk:226 msgid "" "It might help to imagine that the synopsis is combined with the package name " "in the following way:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:227 +#: best-pkging-practices.dbk:230 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> is a " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> is a <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:230 +#: best-pkging-practices.dbk:233 msgid "Alternatively, it might make sense to think of it as" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:233 +#: best-pkging-practices.dbk:236 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> is " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> is <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:236 +#: best-pkging-practices.dbk:239 msgid "or, if the package name itself is a plural (such as developers-tools)" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:239 +#: best-pkging-practices.dbk:242 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> are " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> are <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:242 +#: best-pkging-practices.dbk:245 msgid "" "This way of forming a sentence from the package name and synopsis should be " "considered as a heuristic and not a strict rule. There are some cases where " @@ -375,12 +368,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:249 +#: best-pkging-practices.dbk:252 msgid "The long description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:251 +#: best-pkging-practices.dbk:254 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 " @@ -389,12 +382,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:257 +#: best-pkging-practices.dbk:260 msgid "The long description should consist of full and complete sentences." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:260 +#: best-pkging-practices.dbk:263 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 " @@ -403,7 +396,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:266 +#: best-pkging-practices.dbk:269 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 " @@ -414,42 +407,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:274 +#: best-pkging-practices.dbk:277 msgid "" -"Be careful to avoid spelling and grammar mistakes. Ensure that you " -"spell-check it. Both <command>ispell</command> and " -"<command>aspell</command> have special modes for checking " -"<filename>debian/control</filename> files:" +"Be careful to avoid spelling and grammar mistakes. Ensure that you spell-" +"check it. Both <command>ispell</command> and <command>aspell</command> have " +"special modes for checking <filename>debian/control</filename> files:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:279 +#: best-pkging-practices.dbk:282 #, no-wrap -msgid "-d american -g debian/control" +msgid "ispell -d american -g debian/control" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:282 +#: best-pkging-practices.dbk:285 #, no-wrap -msgid "-d en -D -c debian/control" +msgid "aspell -d en -D -c debian/control" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:285 +#: best-pkging-practices.dbk:288 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:290 +#: best-pkging-practices.dbk:293 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:296 +#: best-pkging-practices.dbk:299 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 " @@ -457,14 +449,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:303 +#: best-pkging-practices.dbk:306 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:309 +#: best-pkging-practices.dbk:312 msgid "" "If the package is experimental, or there are other reasons it should not be " "used, if there are other packages that should be used instead, it should be " @@ -472,7 +464,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:316 +#: best-pkging-practices.dbk:319 msgid "" "How is this package different from the competition? Is it a better " "implementation? more features? different features? Why should I choose this " @@ -480,12 +472,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:325 +#: best-pkging-practices.dbk:332 msgid "Upstream home page" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:327 +#: best-pkging-practices.dbk:334 msgid "" "We recommend that you add the URL for the package's home page to the package " "description in <filename>debian/control</filename>. This information should " @@ -493,7 +485,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:332 +#: best-pkging-practices.dbk:339 #, no-wrap msgid "" ".\n" @@ -501,52 +493,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:336 +#: best-pkging-practices.dbk:343 msgid "" "Note the spaces prepending the line, which serves to break the lines " -"correctly. To see an example of how this displays, see <ulink " -"url=\"http://packages.debian.org/unstable/web/wml\"></ulink>." +"correctly. To see an example of how this displays, see <ulink url=\"&url-eg-" +"desc-upstream-info;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:341 +#: best-pkging-practices.dbk:348 msgid "" -"If there is no home page for the software, this should naturally be left " -"out." +"If there is no home page for the software, this should naturally be left out." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:344 +#: best-pkging-practices.dbk:351 msgid "" "Note that we expect this field will eventually be replaced by a proper " -"<filename>debian/control</filename> field understood by " -"<command>dpkg</command> and <literal>packages.debian.org</literal>. If you " -"don't want to bother migrating the home page from the description to this " -"field, you should probably wait until that is available. Please make sure " -"that this line matches the regular expression <literal>/^ Homepage: [^ " -"]*$/</literal>, as this allows <filename>packages.debian.org</filename> to " -"parse it correctly." +"<filename>debian/control</filename> field understood by <command>dpkg</" +"command> and <literal>&packages-host;</literal>. If you don't want to " +"bother migrating the home page from the description to this field, you " +"should probably wait until that is available. Please make sure that this " +"line matches the regular expression <literal>/^ Homepage: [^ ]*$/</literal>, " +"as this allows <filename>&packages-host;</filename> to parse it correctly." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:355 +#: best-pkging-practices.dbk:362 msgid "Version Control System location" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:357 +#: best-pkging-practices.dbk:364 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:361 +#: best-pkging-practices.dbk:368 msgid "XS-Vcs-Browser" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:363 +#: best-pkging-practices.dbk:370 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 " @@ -554,7 +544,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:368 +#: best-pkging-practices.dbk:375 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 " @@ -562,12 +552,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:375 +#: best-pkging-practices.dbk:382 msgid "XS-Vcs-*" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:377 +#: best-pkging-practices.dbk:384 msgid "" "Value of this field should be a string identifying unequivocally the " "location of the Version Control System repository used to maintain the given " @@ -577,12 +567,11 @@ msgid "" "<literal>cvs</literal>, <literal>darcs</literal>, <literal>git</literal>, " "<literal>hg</literal> (Mercurial), <literal>mtn</literal> (Monotone), " "<literal>svn</literal> (Subversion). It is allowed to specify different VCS " -"fields for the same package: they will all be shown in the PTS web " -"interface." +"fields for the same package: they will all be shown in the PTS web interface." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:388 +#: best-pkging-practices.dbk:395 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 " @@ -596,18 +585,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:399 +#: best-pkging-practices.dbk:406 msgid "" "In the following example, an instance of the field for a Subversion " "repository of the <systemitem role=\"package\">vim</systemitem> package is " "shown. Note how the URL is in the <literal>svn://</literal> scheme (instead " -"of <literal>svn+ssh://</literal>) and how it points to the " -"<filename>trunk/</filename> branch. The use of the " -"<literal>XS-Vcs-Browser</literal> field described above is also shown." +"of <literal>svn+ssh://</literal>) and how it points to the <filename>trunk/</" +"filename> branch. The use of the <literal>XS-Vcs-Browser</literal> field " +"described above is also shown." msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:407 +#: best-pkging-practices.dbk:414 #, no-wrap msgid "" "Source: vim\n" @@ -619,33 +608,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:421 +#: best-pkging-practices.dbk:428 msgid "Best practices for <filename>debian/changelog</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:423 +#: best-pkging-practices.dbk:430 msgid "" -"The following practices supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html#s-changelogs\">Policy " -"on changelog files</ulink>." +"The following practices supplement the <ulink url=\"&url-debian-policy;ch-" +"docs.html#s-changelogs\">Policy on changelog files</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:428 +#: best-pkging-practices.dbk:435 msgid "Writing useful changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:430 +#: best-pkging-practices.dbk:437 msgid "" "The changelog entry for a package revision documents changes in that " -"revision, and only them. Concentrate on describing significant and " -"user-visible changes that were made since the last version." +"revision, and only them. Concentrate on describing significant and user-" +"visible changes that were made since the last version." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:435 +#: best-pkging-practices.dbk:442 msgid "" "Focus on <emphasis>what</emphasis> was changed — who, how and when are " "usually less important. Having said that, remember to politely attribute " @@ -654,7 +642,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:441 +#: best-pkging-practices.dbk:448 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 " @@ -664,7 +652,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:448 +#: best-pkging-practices.dbk:455 msgid "" "Use common English so that the majority of readers can comprehend it. Avoid " "abbreviations, tech-speak and jargon when explaining changes that close " @@ -673,7 +661,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:454 +#: best-pkging-practices.dbk:461 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 " @@ -682,20 +670,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:460 +#: best-pkging-practices.dbk:467 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 " -"linkend=\"upload-bugfix\"/> for more information." +"how it was fixed, and append the closes: #nnnnn string. See <xref linkend=" +"\"upload-bugfix\"/> for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:467 +#: best-pkging-practices.dbk:474 msgid "Common misconceptions about changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:469 +#: best-pkging-practices.dbk:476 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> " "document generic packaging issues (Hey, if you're looking for foo.conf, it's " @@ -706,7 +694,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:477 +#: best-pkging-practices.dbk:484 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 " @@ -714,7 +702,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:482 +#: best-pkging-practices.dbk:489 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> be " "used for random discussion with bug reporters (I don't see segfaults when " @@ -728,7 +716,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:493 +#: best-pkging-practices.dbk:500 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 " @@ -737,73 +725,73 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:501 +#: best-pkging-practices.dbk:508 msgid "Common errors in changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:503 +#: best-pkging-practices.dbk:510 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:507 +#: best-pkging-practices.dbk:514 #, no-wrap msgid "* Fixed all outstanding bugs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:510 +#: best-pkging-practices.dbk:517 msgid "This doesn't tell readers anything too useful, obviously." msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:513 +#: best-pkging-practices.dbk:520 #, no-wrap msgid "* Applied patch from Jane Random." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:516 +#: best-pkging-practices.dbk:523 msgid "What was the patch about?" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:519 +#: best-pkging-practices.dbk:526 #, no-wrap msgid "* Late night install target overhaul." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:522 +#: best-pkging-practices.dbk:529 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:526 +#: best-pkging-practices.dbk:533 #, no-wrap msgid "* Fix vsync FU w/ ancient CRTs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:529 +#: best-pkging-practices.dbk:536 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:533 +#: best-pkging-practices.dbk:540 #, no-wrap msgid "* This is not a bug, closes: #nnnnnn." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:536 +#: best-pkging-practices.dbk:543 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 " @@ -811,13 +799,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:541 +#: best-pkging-practices.dbk:548 #, no-wrap msgid "* Has been fixed for ages, but I forgot to close; closes: #54321." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:544 +#: best-pkging-practices.dbk:551 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 " @@ -828,25 +816,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:551 +#: best-pkging-practices.dbk:558 #, no-wrap msgid "* Closes: #12345, #12346, #15432" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:554 +#: best-pkging-practices.dbk:561 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:560 +#: best-pkging-practices.dbk:567 msgid "Supplementing changelogs with NEWS.Debian files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:562 +#: best-pkging-practices.dbk:569 msgid "" "Important news about changes in a package can also be put in NEWS.Debian " "files. The news will be displayed by tools like apt-listchanges, before all " @@ -858,7 +846,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:571 +#: best-pkging-practices.dbk:578 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 " @@ -869,31 +857,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:579 +#: best-pkging-practices.dbk:586 #, no-wrap msgid "" -"(3.0pl1-74) unstable; urgency=low\n" +"cron (3.0pl1-74) unstable; urgency=low\n" "\n" " The checksecurity script is no longer included with the cron package:\n" " it now has its own package, checksecurity. If you liked the\n" " functionality provided with that script, please install the new\n" " package.\n" "\n" -" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 " -"-0500" +" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 -0500" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:589 +#: best-pkging-practices.dbk:596 msgid "" -"The NEWS.Debian file is installed as " -"/usr/share/doc/<package>/NEWS.Debian.gz. It is compressed, and always " -"has that name even in Debian native packages. If you use debhelper, " -"dh_installchangelogs will install debian/NEWS files for you." +"The NEWS.Debian file is installed as /usr/share/doc/<package>/NEWS." +"Debian.gz. It is compressed, and always has that name even in Debian native " +"packages. If you use debhelper, dh_installchangelogs will install debian/" +"NEWS files for you." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:595 +#: best-pkging-practices.dbk:602 msgid "" "Unlike changelog files, you need not update NEWS.Debian files with every " "release. Only update them if you have something particularly newsworthy " @@ -902,24 +889,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:605 +#: best-pkging-practices.dbk:623 msgid "Best practices for maintainer scripts" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:607 +#: best-pkging-practices.dbk:625 msgid "" "Maintainer scripts include the files <filename>debian/postinst</filename>, " "<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and " "<filename>debian/postrm</filename>. These scripts take care of any package " "installation or deinstallation setup which isn't handled merely by the " "creation or removal of files and directories. The following instructions " -"supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>." +"supplement the <ulink url=\"&url-debian-policy;\">Debian Policy</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:615 +#: best-pkging-practices.dbk:633 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 " @@ -927,34 +913,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:620 +#: best-pkging-practices.dbk:638 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:624 +#: best-pkging-practices.dbk:642 msgid "" "All prompting or interactive configuration should be kept to a minimum. " -"When it is necessary, you should use the <systemitem " -"role=\"package\">debconf</systemitem> package for the interface. Remember " -"that prompting in any case can only be in the <literal>configure</literal> " -"stage of the <filename>postinst</filename> script." +"When it is necessary, you should use the <systemitem role=\"package" +"\">debconf</systemitem> package for the interface. Remember that prompting " +"in any case can only be in the <literal>configure</literal> stage of the " +"<filename>postinst</filename> script." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:631 +#: best-pkging-practices.dbk:649 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 " "maintainer script must have a bash shebang line. POSIX shell or Bash are " -"preferred to Perl, since they enable <systemitem " -"role=\"package\">debhelper</systemitem> to easily add bits to the scripts." +"preferred to Perl, since they enable <systemitem role=\"package\">debhelper</" +"systemitem> to easily add bits to the scripts." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:638 +#: best-pkging-practices.dbk:656 msgid "" "If you change your maintainer scripts, be sure to test package removal, " "double installation, and purging. Be sure that a purged package is " @@ -963,73 +949,55 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:644 +#: best-pkging-practices.dbk:662 msgid "" "If you need to check for the existence of a command, you should use " "something like" msgstr "" -# type: Content of: <chapter><section><screen> -#: best-pkging-practices.dbk:648 +# type: Content of: <chapter><section><programlisting> +#: best-pkging-practices.dbk:665 #, no-wrap -msgid "[ -x /usr/sbin/install-docs ]; then ..." +msgid "if [ -x /usr/sbin/install-docs ]; then ..." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:651 +#: best-pkging-practices.dbk:667 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><screen> -#: best-pkging-practices.dbk:655 -#, no-wrap -msgid "" -"() {\n" -" OLDIFS=$IFS\n" -" IFS=:\n" -" for p in $PATH; do\n" -" if [ -x $p/$* ]; then\n" -" IFS=$OLDIFS\n" -" return 0\n" -" fi\n" -" done\n" -" IFS=$OLDIFS\n" -" return 1\n" -"}" -msgstr "" - # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:669 +#: best-pkging-practices.dbk:672 msgid "" "You can use this function to search <literal>$PATH</literal> for a command " "name, passed as an argument. It returns true (zero) if the command was " "found, and false if not. This is really the most portable way, since " -"<literal>command -v</literal>, <command>type</command>, and " -"<command>which</command> are not POSIX." +"<literal>command -v</literal>, <command>type</command>, and <command>which</" +"command> are not POSIX." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:676 +#: best-pkging-practices.dbk:679 msgid "" "While <command>which</command> is an acceptable alternative, since it is " "from the required <systemitem role=\"package\">debianutils</systemitem> " -"package, it's not on the root partition. That is, it's in " -"<filename>/usr/bin</filename> rather than <filename>/bin</filename>, so one " -"can't use it in scripts which are run before the <filename>/usr</filename> " -"partition is mounted. Most scripts won't have this problem, though." +"package, it's not on the root partition. That is, it's in <filename>/usr/" +"bin</filename> rather than <filename>/bin</filename>, so one can't use it in " +"scripts which are run before the <filename>/usr</filename> partition is " +"mounted. Most scripts won't have this problem, though." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:686 +#: best-pkging-practices.dbk:689 msgid "" -"Configuration management with <systemitem " -"role=\"package\">debconf</systemitem>" +"Configuration management with <systemitem role=\"package\">debconf</" +"systemitem>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:688 +#: best-pkging-practices.dbk:691 msgid "" "<systemitem role=\"package\">Debconf</systemitem> is a configuration " "management system which can be used by all the various packaging scripts " @@ -1040,17 +1008,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:696 +#: best-pkging-practices.dbk:699 msgid "" "Debconf is a great tool but it is often poorly used. Many common mistakes " -"are listed in the <citerefentry> " -"<refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry> man page. It is something that you must read if you decide " -"to use debconf. Also, we document some best practices here." +"are listed in the <citerefentry> <refentrytitle>debconf-devel</" +"refentrytitle> <manvolnum>7</manvolnum> </citerefentry> man page. It is " +"something that you must read if you decide to use debconf. Also, we " +"document some best practices here." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:703 +#: best-pkging-practices.dbk:706 msgid "" "These guidelines include some writing style and typography recommendations, " "general considerations about debconf usage as well as more specific " @@ -1059,12 +1027,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:709 +#: best-pkging-practices.dbk:712 msgid "Do not abuse debconf" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:711 +#: best-pkging-practices.dbk:714 msgid "" "Since debconf appeared in Debian, it has been widely abused and several " "criticisms received by the Debian distribution come from debconf abuse with " @@ -1073,7 +1041,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:717 +#: best-pkging-practices.dbk:720 msgid "" "Keep usage notes to what they belong: the NEWS.Debian, or README.Debian " "file. Only use notes for important notes which may directly affect the " @@ -1082,47 +1050,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:723 +#: best-pkging-practices.dbk:726 msgid "" "Carefully choose the questions priorities in maintainer scripts. See " -"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " -"<manvolnum>7</manvolnum> </citerefentry> for details about priorities. Most " -"questions should use medium and low priorities." +"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> for details about priorities. Most questions " +"should use medium and low priorities." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:731 +#: best-pkging-practices.dbk:734 msgid "General recommendations for authors and translators" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:733 +#: best-pkging-practices.dbk:736 msgid "Write correct English" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:735 +#: best-pkging-practices.dbk:738 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:739 +#: best-pkging-practices.dbk:742 msgid "" -"Please use (and abuse) <email>debian-l10n-english@lists.debian.org</email> " -"mailing list. Have your templates proofread." +"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:743 +#: best-pkging-practices.dbk:746 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:747 +#: best-pkging-practices.dbk:750 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 " @@ -1131,12 +1099,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:755 +#: best-pkging-practices.dbk:758 msgid "Be kind to translators" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:757 +#: best-pkging-practices.dbk:760 msgid "" "Debconf templates may be translated. Debconf, along with its sister package " "<command>po-debconf</command> offers a simple framework for getting " @@ -1144,15 +1112,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:762 +#: best-pkging-practices.dbk:765 msgid "" -"Please use gettext-based templates. Install <systemitem " -"role=\"package\">po-debconf</systemitem> on your development system and read " -"its documentation (man po-debconf is a good start)." +"Please use gettext-based templates. Install <systemitem role=\"package\">po-" +"debconf</systemitem> on your development system and read its documentation " +"(man po-debconf is a good start)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:767 +#: best-pkging-practices.dbk:770 msgid "" "Avoid changing templates too often. Changing templates text induces more " "work to translators which will get their translation fuzzied. If you plan " @@ -1164,7 +1132,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:776 +#: best-pkging-practices.dbk:779 msgid "" "The use of the <command>podebconf-report-po</command> from the po-debconf " "package is highly recommended to warn translators which have incomplete " @@ -1172,69 +1140,68 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:781 +#: best-pkging-practices.dbk:784 msgid "" "If in doubt, you may also contact the translation team for a given language " -"(debian-l10n-xxxxx@lists.debian.org), or the " -"<email>debian-i18n@lists.debian.org</email> mailing list." +"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:786 +#: best-pkging-practices.dbk:789 msgid "" -"Calls for translations posted to <email>debian-i18n@lists.debian.org</email> " -"with the <filename>debian/po/templates.pot</filename> file attached or " -"referenced in a URL are encouraged. Be sure to mentions in these calls for " -"new translations which languages you have existing translations for, in " -"order to avoid duplicate work." +"Calls for translations posted to &email-debian-i18n; with the " +"<filename>debian/po/templates.pot</filename> file attached or referenced in " +"a URL are encouraged. Be sure to mentions in these calls for new " +"translations which languages you have existing translations for, in order to " +"avoid duplicate work." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:795 +#: best-pkging-practices.dbk:798 msgid "Unfuzzy complete translations when correcting typos and spelling" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:797 +#: best-pkging-practices.dbk:800 msgid "" -"When the text of a debconf template is corrected and you are <emphasis " -"role=\"strong\">sure</emphasis> that the change does <emphasis " -"role=\"strong\">not</emphasis> affect translations, please be kind to " -"translators and unfuzzy their translations." +"When the text of a debconf template is corrected and you are <emphasis role=" +"\"strong\">sure</emphasis> that the change does <emphasis role=\"strong" +"\">not</emphasis> affect translations, please be kind to translators and " +"unfuzzy their translations." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:803 +#: best-pkging-practices.dbk:806 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:807 +#: best-pkging-practices.dbk:810 msgid "" "To <emphasis role=\"strong\">unfuzzy</emphasis> translations, you can " "proceed the following way:" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:813 +#: best-pkging-practices.dbk:816 msgid "" "Put all incomplete PO files out of the way. You can check the completeness " "by using (needs the <systemitem role=\"package\">gettext</systemitem> " "package installed):" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> -#: best-pkging-practices.dbk:818 +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> +#: best-pkging-practices.dbk:820 #, no-wrap msgid "" -"i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" +"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" "--statistics $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:824 +#: best-pkging-practices.dbk:825 msgid "" "move all files which report either fuzzy strings to a temporary place. " "Files which report no fuzzy strings (only translated and untranslated) will " @@ -1242,7 +1209,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:831 +#: best-pkging-practices.dbk:832 msgid "" "now <emphasis role=\"strong\">and now only</emphasis>, modify the template " "for the typos and check again that translation are not impacted (typos, " @@ -1250,51 +1217,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:838 +#: best-pkging-practices.dbk:839 msgid "" "run <command>debconf-updatepo</command>. This will fuzzy all strings you " "modified in translations. You can see this by running the above again" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:844 +#: best-pkging-practices.dbk:845 msgid "use the following command:" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> #: best-pkging-practices.dbk:847 #, no-wrap -msgid "i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" +msgid "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:852 +#: best-pkging-practices.dbk:851 msgid "" -"move back to debian/po the files which showed fuzzy strings in the first " -"step" +"move back to debian/po the files which showed fuzzy strings in the first step" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:857 +#: best-pkging-practices.dbk:856 msgid "run <command>debconf-updatepo</command> again" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:864 +#: best-pkging-practices.dbk:863 msgid "Do not make assumptions about interfaces" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:866 +#: best-pkging-practices.dbk:865 msgid "" "Templates text should not make reference to widgets belonging to some " "debconf interfaces. Sentences like If you answer Yes... have no meaning " -"for users of graphical interfaces which use checkboxes for boolean " -"questions." +"for users of graphical interfaces which use checkboxes for boolean questions." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:871 +#: best-pkging-practices.dbk:870 msgid "" "String templates should also avoid mentioning the default values in their " "description. First, because this is redundant with the values seen by the " @@ -1303,19 +1268,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:877 +#: best-pkging-practices.dbk:876 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:883 +#: best-pkging-practices.dbk:882 msgid "Do not use first person" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:885 +#: best-pkging-practices.dbk:884 msgid "" "You should avoid the use of first person (I will do this... or We " "recommend...). The computer is not a person and the Debconf templates do " @@ -1327,52 +1292,53 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:895 +#: best-pkging-practices.dbk:894 msgid "Be gender neutral" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:897 +#: best-pkging-practices.dbk:896 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:905 +#: best-pkging-practices.dbk:904 msgid "Templates fields definition" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:907 +#: best-pkging-practices.dbk:906 msgid "" "This part gives some information which is mostly taken from the " -"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " -"<manvolnum>7</manvolnum> </citerefentry> manual page." +"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> manual page." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:912 +#: best-pkging-practices.dbk:911 msgid "Type" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:914 +#: best-pkging-practices.dbk:913 msgid "string:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:916 -msgid "Results in a free-form input field that the user can type any string into." +#: best-pkging-practices.dbk:915 +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:921 +#: best-pkging-practices.dbk:920 msgid "password:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:923 +#: best-pkging-practices.dbk:922 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 " @@ -1380,24 +1346,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:930 +#: best-pkging-practices.dbk:929 msgid "boolean:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:932 +#: best-pkging-practices.dbk:931 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:938 +#: best-pkging-practices.dbk:937 msgid "select:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:940 +#: best-pkging-practices.dbk:939 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 " @@ -1405,24 +1371,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:947 +#: best-pkging-practices.dbk:946 msgid "multiselect:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:949 +#: best-pkging-practices.dbk:948 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:955 +#: best-pkging-practices.dbk:954 msgid "note:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:957 +#: best-pkging-practices.dbk:956 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 " @@ -1432,22 +1398,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:966 +#: best-pkging-practices.dbk:965 msgid "text:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:968 +#: best-pkging-practices.dbk:967 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:973 +#: best-pkging-practices.dbk:972 msgid "error:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:975 +#: best-pkging-practices.dbk:974 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 " @@ -1455,26 +1421,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:980 +#: best-pkging-practices.dbk:979 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:988 +#: best-pkging-practices.dbk:987 msgid "Description: short and extended description" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:990 +#: best-pkging-practices.dbk:989 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:994 +#: best-pkging-practices.dbk:993 msgid "" "The short description should be kept short (50 characters or so) so that it " "may be accomodated by most debconf interfaces. Keeping it short also helps " @@ -1483,7 +1449,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1000 +#: best-pkging-practices.dbk:999 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 " @@ -1492,14 +1458,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1006 +#: best-pkging-practices.dbk:1005 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:1010 +#: best-pkging-practices.dbk:1009 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 " @@ -1509,7 +1475,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1017 +#: best-pkging-practices.dbk:1016 msgid "" "The extended description should use complete sentences. Paragraphs should " "be kept short for improved readability. Do not mix two ideas in the same " @@ -1517,7 +1483,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1022 +#: best-pkging-practices.dbk:1021 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 " @@ -1526,26 +1492,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1028 +#: best-pkging-practices.dbk:1027 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:1032 +#: best-pkging-practices.dbk:1031 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:1038 +#: best-pkging-practices.dbk:1037 msgid "Choices" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1040 +#: best-pkging-practices.dbk:1039 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 " @@ -1553,12 +1519,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1047 +#: best-pkging-practices.dbk:1046 msgid "Default" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1049 +#: best-pkging-practices.dbk:1048 msgid "" "This field is optional. It contains the default answer for string, select " "and multiselect templates. For multiselect templates, it may contain a " @@ -1566,50 +1532,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1058 +#: best-pkging-practices.dbk:1057 msgid "Templates fields specific style guide" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1060 +#: best-pkging-practices.dbk:1059 msgid "Type field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1062 +#: best-pkging-practices.dbk:1061 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:1068 +#: best-pkging-practices.dbk:1067 msgid "Description field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1070 +#: best-pkging-practices.dbk:1069 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:1074 +#: best-pkging-practices.dbk:1073 msgid "String/password templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1078 +#: best-pkging-practices.dbk:1077 msgid "" -"The short description is a prompt and <emphasis " -"role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP " -"Address?) in favour of opened prompts (IP address:). The use of colons is " -"recommended." +"The short description is a prompt and <emphasis role=\"strong\">not</" +"emphasis> a title. Avoid question style prompts (IP Address?) in favour of " +"opened prompts (IP address:). The use of colons is recommended." msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1085 +#: best-pkging-practices.dbk:1084 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 " @@ -1618,12 +1583,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1095 +#: best-pkging-practices.dbk:1094 msgid "Boolean templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1099 +#: best-pkging-practices.dbk:1098 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 " @@ -1632,28 +1597,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1107 +#: best-pkging-practices.dbk:1106 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:1115 +#: best-pkging-practices.dbk:1114 msgid "Select/Multiselect" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1119 +#: best-pkging-practices.dbk:1118 msgid "" -"The short description is a prompt and <emphasis " -"role=\"strong\">not</emphasis> a title. Do <emphasis " -"role=\"strong\">not</emphasis> use useless Please choose... constructions. " -"Users are clever enough to figure out they have to choose something...:)" +"The short description is a prompt and <emphasis role=\"strong\">not</" +"emphasis> a title. Do <emphasis role=\"strong\">not</emphasis> use useless " +"Please choose... constructions. Users are clever enough to figure out they " +"have to choose something...:)" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1127 +#: best-pkging-practices.dbk:1126 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 " @@ -1662,24 +1627,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1137 +#: best-pkging-practices.dbk:1136 msgid "Notes" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1141 +#: best-pkging-practices.dbk:1140 msgid "The short description should be considered to be a *title*." msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1146 +#: best-pkging-practices.dbk:1145 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:1152 +#: best-pkging-practices.dbk:1151 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: " @@ -1691,12 +1656,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1167 +#: best-pkging-practices.dbk:1166 msgid "Choices field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1169 +#: best-pkging-practices.dbk:1168 msgid "" "If the Choices are likely to change often, please consider using the " "__Choices trick. This will split each individual choice into a single " @@ -1704,12 +1669,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1176 best-pkging-practices.dbk:1214 +#: best-pkging-practices.dbk:1175 best-pkging-practices.dbk:1213 msgid "Default field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1178 +#: best-pkging-practices.dbk:1177 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 " @@ -1717,7 +1682,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1183 +#: best-pkging-practices.dbk:1182 msgid "" "This special field allow translators to put the most appropriate choice " "according to their own language. It will become the default choice when " @@ -1726,21 +1691,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1189 +#: best-pkging-practices.dbk:1188 msgid "Example, taken from the geneweb package templates:" msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:1192 +#: best-pkging-practices.dbk:1191 #, no-wrap msgid "" -": geneweb/lang\n" +"Template: geneweb/lang\n" "Type: select\n" -"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech " -"(cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), " -"Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian " -"(it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian " -"(ro), Russian (ru), Spanish (es), Swedish (sv)\n" +"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech (cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian (it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Spanish (es), Swedish (sv)\n" "# This is the default choice. Translators may put their own language here\n" "# instead of the default.\n" "# WARNING : you MUST use the ENGLISH FORM of your language\n" @@ -1750,7 +1711,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1203 +#: best-pkging-practices.dbk:1202 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 " @@ -1758,21 +1719,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1208 +#: best-pkging-practices.dbk:1207 msgid "" "The comments are needed as the DefaultChoice 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:1216 +#: best-pkging-practices.dbk:1215 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:1220 +#: best-pkging-practices.dbk:1219 msgid "" "If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, " "see 2.2), consider making this field translatable, if you think it may be " @@ -1780,27 +1741,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1225 +#: best-pkging-practices.dbk:1224 msgid "" "If the default value may vary depending on language/country (for instance " "the default value for a language choice), consider using the special " -"_DefaultChoice type documented in <citerefentry> " -"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry>)." +"_DefaultChoice type documented in <citerefentry> <refentrytitle>po-debconf</" +"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1237 +#: best-pkging-practices.dbk:1236 msgid "Internationalization" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1239 +#: best-pkging-practices.dbk:1238 msgid "Handling debconf translations" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1241 +#: best-pkging-practices.dbk:1240 msgid "" "Like porters, translators have a difficult task. They work on many packages " "and must collaborate with many different maintainers. Moreover, most of the " @@ -1809,43 +1769,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1247 +#: best-pkging-practices.dbk:1246 msgid "" "The goal of <systemitem role=\"package\">debconf</systemitem> was to make " "packages configuration easier for maintainers and for users. Originally, " -"translation of debconf templates was handled with " -"<command>debconf-mergetemplate</command>. However, that technique is now " -"deprecated; the best way to accomplish <systemitem " -"role=\"package\">debconf</systemitem> internationalization is by using the " -"<systemitem role=\"package\">po-debconf</systemitem> package. This method " -"is easier both for maintainer and translators; transition scripts are " -"provided." +"translation of debconf templates was handled with <command>debconf-" +"mergetemplate</command>. However, that technique is now deprecated; the " +"best way to accomplish <systemitem role=\"package\">debconf</systemitem> " +"internationalization is by using the <systemitem role=\"package\">po-" +"debconf</systemitem> package. This method is easier both for maintainer and " +"translators; transition scripts are provided." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1257 +#: best-pkging-practices.dbk:1256 msgid "" "Using <systemitem role=\"package\">po-debconf</systemitem>, the translation " -"is stored in <filename>po</filename> files (drawing from " -"<command>gettext</command> translation techniques). Special template files " -"contain the original messages and mark which fields are translatable. When " -"you change the value of a translatable field, by calling " -"<command>debconf-updatepo</command>, the translation is marked as needing " -"attention from the translators. Then, at build time, the " -"<command>dh_installdebconf</command> program takes care of all the needed " -"magic to add the template along with the up-to-date translations into the " -"binary packages. Refer to the <citerefentry> " -"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry> manual page for details." +"is stored in <filename>po</filename> files (drawing from <command>gettext</" +"command> translation techniques). Special template files contain the " +"original messages and mark which fields are translatable. When you change " +"the value of a translatable field, by calling <command>debconf-updatepo</" +"command>, the translation is marked as needing attention from the " +"translators. Then, at build time, the <command>dh_installdebconf</command> " +"program takes care of all the needed magic to add the template along with " +"the up-to-date translations into the binary packages. Refer to the " +"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> manual page for details." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1273 +#: best-pkging-practices.dbk:1272 msgid "Internationalized documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1275 +#: best-pkging-practices.dbk:1274 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 " @@ -1853,7 +1811,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1280 +#: best-pkging-practices.dbk:1279 msgid "" "If you maintain documentation of any size, its easier for translators if " "they have access to a source control system. That lets translators see the " @@ -1861,18 +1819,16 @@ msgid "" "they can see what needs to be retranslated. It is recommended that the " "translated documentation maintain a note about what source control revision " "the translation is based on. An interesting system is provided by <ulink " -"url=\"http://cvs.debian.org/boot-floppies/documentation/doc-check?rev=HEAD\\|[amp " -"]\\|content-type=text/vnd.viewcvs-markup\">doc-check</ulink> in the " -"<systemitem role=\"package\">boot-floppies</systemitem> package, which shows " -"an overview of the translation status for any given language, using " -"structured comments for the current revision of the file to be translated " -"and, for a translated file, the revision of the original file the " -"translation is based on. You might wish to adapt and provide that in your " -"CVS area." +"url=\"&url-i18n-doc-check;\">doc-check</ulink> in the <systemitem role=" +"\"package\">boot-floppies</systemitem> package, which shows an overview of " +"the translation status for any given language, using structured comments for " +"the current revision of the file to be translated and, for a translated " +"file, the revision of the original file the translation is based on. You " +"might wish to adapt and provide that in your CVS area." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1295 +#: best-pkging-practices.dbk:1293 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 " @@ -1881,36 +1837,35 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1305 +#: best-pkging-practices.dbk:1303 msgid "Common packaging situations" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1307 +#: best-pkging-practices.dbk:1314 msgid "Packages using <command>autoconf</command>/<command>automake</command>" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1309 +#: best-pkging-practices.dbk:1316 msgid "" "Keeping <command>autoconf</command>'s <filename>config.sub</filename> and " "<filename>config.guess</filename> files up to date is critical for porters, " "especially on more volatile architectures. Some very good packaging " "practices for any package using <command>autoconf</command> and/or " -"<command>automake</command> have been synthesized in " -"<filename>/usr/share/doc/autotools-dev/README.Debian.gz</filename> from the " -"<systemitem role=\"package\">autotools-dev</systemitem> package. You're " -"strongly encouraged to read this file and to follow the given " +"<command>automake</command> have been synthesized in &file-bpp-autotools; " +"from the <systemitem role=\"package\">autotools-dev</systemitem> package. " +"You're strongly encouraged to read this file and to follow the given " "recommendations." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1321 +#: best-pkging-practices.dbk:1328 msgid "Libraries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1323 +#: best-pkging-practices.dbk:1330 msgid "" "Libraries are always difficult to package for various reasons. The policy " "imposes many constraints to ease their maintenance and to make sure upgrades " @@ -1919,28 +1874,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1329 +#: best-pkging-practices.dbk:1336 msgid "" -"Good practices for library packaging have been grouped in <ulink " -"url=\"http://www.netfort.gr.jp/~dancer/column/libpkg-guide/\">the library " -"packaging guide</ulink>." +"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><section><title> -#: best-pkging-practices.dbk:1336 +#: best-pkging-practices.dbk:1343 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1338 +#: best-pkging-practices.dbk:1345 msgid "" -"Be sure to follow the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html\">Policy on " -"documentation</ulink>." +"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:1343 +#: best-pkging-practices.dbk:1350 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 " @@ -1948,7 +1901,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1348 +#: best-pkging-practices.dbk:1355 msgid "" "Policy specifies that documentation should be shipped in HTML format. We " "also recommend shipping documentation in PDF and plain text format if " @@ -1958,93 +1911,86 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1355 +#: best-pkging-practices.dbk:1362 msgid "" -"Major shipped manuals should register themselves with <systemitem " -"role=\"package\">doc-base</systemitem> on installation. See the <systemitem " -"role=\"package\">doc-base</systemitem> package documentation for more " -"information." +"Major shipped manuals should register themselves with <systemitem role=" +"\"package\">doc-base</systemitem> on installation. See the <systemitem role=" +"\"package\">doc-base</systemitem> package documentation for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1363 +#: best-pkging-practices.dbk:1370 msgid "Specific types of packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1365 +#: best-pkging-practices.dbk:1372 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:1371 +#: best-pkging-practices.dbk:1378 msgid "" -"Perl related packages have a <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/perl-policy/\">Perl " -"policy</ulink>, some examples of packages following that policy are " -"<systemitem role=\"package\">libdbd-pg-perl</systemitem> (binary perl " -"module) or <systemitem role=\"package\">libmldbm-perl</systemitem> (arch " -"independent perl module)." +"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl policy</" +"ulink>, some examples of packages following that policy are <systemitem role=" +"\"package\">libdbd-pg-perl</systemitem> (binary perl module) or <systemitem " +"role=\"package\">libmldbm-perl</systemitem> (arch independent perl module)." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1380 +#: best-pkging-practices.dbk:1387 msgid "" -"Python related packages have their python policy; see " -"<filename>/usr/share/doc/python/python-policy.txt.gz</filename> in the " -"<systemitem role=\"package\">python</systemitem> package." +"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:1387 +#: best-pkging-practices.dbk:1394 msgid "" -"Emacs related packages have the <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/debian-emacs-policy\">emacs " +"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:1394 +#: best-pkging-practices.dbk:1401 msgid "" -"Java related packages have their <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/java-policy/\">java " +"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:1401 +#: best-pkging-practices.dbk:1408 msgid "" -"Ocaml related packages have their own policy, found in " -"<filename>/usr/share/doc/ocaml/ocaml_packaging_policy.gz</filename> from the " -"<systemitem role=\"package\">ocaml</systemitem> package. A good example is " -"the <systemitem role=\"package\">camlzip</systemitem> source package." +"Ocaml related packages have their own policy, found in &file-ocaml-policy; " +"from the <systemitem role=\"package\">ocaml</systemitem> package. A good " +"example is the <systemitem role=\"package\">camlzip</systemitem> source " +"package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1409 +#: best-pkging-practices.dbk:1416 msgid "" "Packages providing XML or SGML DTDs should conform to the recommendations " -"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> " -"package." +"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1415 +#: best-pkging-practices.dbk:1422 msgid "" -"Lisp packages should register themselves with <systemitem " -"role=\"package\">common-lisp-controller</systemitem>, about which see " -"<filename>/usr/share/doc/common-lisp-controller/README.packaging</filename>." +"Lisp packages should register themselves with <systemitem role=\"package" +"\">common-lisp-controller</systemitem>, about which see &file-lisp-" +"controller;." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1424 +#: best-pkging-practices.dbk:1452 msgid "Architecture-independent data" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1426 +#: best-pkging-practices.dbk:1454 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, " @@ -2054,12 +2000,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1433 +#: best-pkging-practices.dbk:1461 msgid "" "However, if the size of the data is considerable, consider splitting it out " "into a separate, architecture-independent package (_all.deb). By doing " -"this, you avoid needless duplication of the same data into eleven or more " -".debs, one per each architecture. While this adds some extra overhead into " +"this, you avoid needless duplication of the same data into eleven or more ." +"debs, one per each architecture. While this adds some extra overhead into " "the <filename>Packages</filename> files, it saves a lot of disk space on " "Debian mirrors. Separating out architecture-independent data also reduces " "processing time of <command>lintian</command> or <command>linda</command> " @@ -2068,48 +2014,48 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1445 +#: best-pkging-practices.dbk:1473 msgid "Needing a certain locale during build" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1447 +#: best-pkging-practices.dbk:1475 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:1451 +#: best-pkging-practices.dbk:1479 msgid "" -"If you set LOCPATH to the equivalent of /usr/lib/locale, and LC_ALL to the " -"name of the locale you generate, you should get what you want without being " -"root. Something like this:" +"If you set <varname>LOCPATH</varname> to the equivalent of <filename>/usr/" +"lib/locale</filename>, and <varname>LC_ALL</varname> to the name of the " +"locale you generate, you should get what you want without being root. " +"Something like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1456 +#: best-pkging-practices.dbk:1484 #, no-wrap msgid "" -"=debian/tmpdir/usr/lib/locale\n" +"LOCALE_PATH=debian/tmpdir/usr/lib/locale\n" "LOCALE_NAME=en_IN\n" "LOCALE_CHARSET=UTF-8\n" "\n" "mkdir -p $LOCALE_PATH\n" -"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET " -"$LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n" +"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET $LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n" "\n" "# Using the locale\n" "LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1469 +#: best-pkging-practices.dbk:1497 msgid "Make transition packages deborphan compliant" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1471 +#: best-pkging-practices.dbk:1499 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 " @@ -2119,7 +2065,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1478 +#: best-pkging-practices.dbk:1506 msgid "" "For example, with --guess-dummy, deborphan tries to search all transitional " "packages which were needed for upgrade but which can now safely be removed. " @@ -2128,76 +2074,56 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1484 +#: best-pkging-practices.dbk:1512 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><screen> -#: best-pkging-practices.dbk:1488 -#, no-wrap -msgid "-cache search .|grep dummy" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1491 -msgid "or" -msgstr "" - -# type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1494 -#, no-wrap -msgid "-cache search .|grep transitional" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1497 -msgid "." +"to your short description. If you are looking for examples, just run: " +"<command>apt-cache search .|grep dummy</command> or <command>apt-cache " +"search .|grep transitional</command>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1502 +#: best-pkging-practices.dbk:1520 msgid "Best practices for <filename>orig.tar.gz</filename> files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1504 +#: best-pkging-practices.dbk:1522 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:1508 +#: best-pkging-practices.dbk:1526 msgid "Pristine source" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1510 +#: best-pkging-practices.dbk:1528 msgid "" -"The defining characteristic of a pristine source tarball is that the " -".orig.tar.gz file is byte-for-byte identical to a tarball officially " -"distributed by the upstream author. <footnote>" +"The defining characteristic of a pristine source tarball is that the .orig." +"tar.gz file is byte-for-byte identical to a tarball officially distributed " +"by the upstream author. <footnote>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1512 +#: best-pkging-practices.dbk:1530 msgid "" "We cannot prevent upstream authors from changing the tarball they distribute " "without also incrementing the version number, so there can be no guarantee " -"that a pristine tarball is identical to what upstream " -"<emphasis>currently</emphasis> distributing at any point in time. All that " -"can be expected is that it is identical to something that upstream once " -"<emphasis>did</emphasis> distribute. If a difference arises later (say, if " -"upstream notices that he wasn't using maximal comression in his original " -"distribution and then re-<literal>gzip</literal>s it), that's just too bad. " -"Since there is no good way to upload a new .orig.tar.gz for the same " -"version, there is not even any point in treating this situation as a bug." +"that a pristine tarball is identical to what upstream <emphasis>currently</" +"emphasis> distributing at any point in time. All that can be expected is " +"that it is identical to something that upstream once <emphasis>did</" +"emphasis> distribute. If a difference arises later (say, if upstream " +"notices that he wasn't using maximal comression in his original distribution " +"and then re-<literal>gzip</literal>s it), that's just too bad. Since there " +"is no good way to upload a new .orig.tar.gz for the same version, there is " +"not even any point in treating this situation as a bug." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1522 +#: best-pkging-practices.dbk:1540 msgid "" "</footnote> This makes it possible to use checksums to easily verify that " "all changes between Debian's version and upstream's are contained in the " @@ -2207,28 +2133,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1530 +#: best-pkging-practices.dbk:1548 msgid "" "There is no universally accepted guidelines that upstream authors follow " -"regarding to the directory structure inside their tarball, but " -"<command>dpkg-source</command> is nevertheless able to deal with most " -"upstream tarballs as pristine source. Its strategy is equivalent to the " -"following:" +"regarding to the directory structure inside their tarball, but <command>dpkg-" +"source</command> is nevertheless able to deal with most upstream tarballs as " +"pristine source. Its strategy is equivalent to the following:" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1538 +#: best-pkging-practices.dbk:1556 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:1541 +#: best-pkging-practices.dbk:1559 #, no-wrap -msgid "path/to/<packagename>_<upstream-version>.orig.tar.gz | tar xf -" +msgid "zcat path/to/<packagename>_<upstream-version>.orig.tar.gz | tar xf -" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1546 +#: best-pkging-practices.dbk:1564 msgid "" "If, after this, the temporary directory contains nothing but one directory " "and no other files, <command>dpkg-source</command> renames that directory to " @@ -2238,74 +2163,73 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1555 +#: best-pkging-practices.dbk:1573 msgid "" -"Otherwise, the upstream tarball must have been packaged without a common " -"top-level directory (shame on the upstream author!). In this case, " +"Otherwise, the upstream tarball must have been packaged without a common top-" +"level directory (shame on the upstream author!). In this case, " "<command>dpkg-source</command> renames the temporary directory " -"<emphasis>itself</emphasis> to " -"<literal><packagename>-<upstream-version>(.orig)</literal>." +"<emphasis>itself</emphasis> to <literal><packagename>-<upstream-" +"version>(.orig)</literal>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1566 +#: best-pkging-practices.dbk:1584 msgid "Repackaged upstream source" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1568 +#: best-pkging-practices.dbk:1586 msgid "" "You <emphasis role=\"strong\">should</emphasis> upload packages with a " "pristine source tarball if possible, but there are various reasons why it " "might not be possible. This is the case if upstream does not distribute the " -"source as gzipped tar at all, or if upstream's tarball contains " -"non-DFSG-free material that you must remove before uploading." +"source as gzipped tar at all, or if upstream's tarball contains non-DFSG-" +"free material that you must remove before uploading." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1575 +#: best-pkging-practices.dbk:1593 msgid "" "In these cases the developer must construct a suitable .orig.tar.gz file " "himself. We refer to such a tarball as a repackaged upstream source. Note " "that a repackaged upstream source is different from a Debian-native " "package. A repackaged source still comes with Debian-specific changes in a " "separate <literal>.diff.gz</literal> and still has a version number composed " -"of <literal><upstream-version></literal> and " -"<literal><debian-revision></literal>." +"of <literal><upstream-version></literal> and <literal><debian-" +"revision></literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1584 +#: best-pkging-practices.dbk:1602 msgid "" "There may be cases where it is desirable to repackage the source even though " "upstream distributes a <literal>.tar.gz</literal> that could in principle be " -"used in its pristine form. The most obvious is if " -"<emphasis>significant</emphasis> space savings can be achieved by " -"recompressing the tar archive or by removing genuinely useless cruft from " -"the upstream archive. Use your own discretion here, but be prepared to " -"defend your decision if you repackage source that could have been pristine." +"used in its pristine form. The most obvious is if <emphasis>significant</" +"emphasis> space savings can be achieved by recompressing the tar archive or " +"by removing genuinely useless cruft from the upstream archive. Use your own " +"discretion here, but be prepared to defend your decision if you repackage " +"source that could have been pristine." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1593 +#: best-pkging-practices.dbk:1611 msgid "A repackaged .orig.tar.gz" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1598 +#: best-pkging-practices.dbk:1616 msgid "" "<emphasis role=\"strong\">must</emphasis> contain detailed information how " "the repackaged source was obtained, and how this can be reproduced in the " "<filename>debian/copyright</filename>. It is also a good idea to provide a " -"<literal>get-orig-source</literal> target in your " -"<filename>debian/rules</filename> file that repeats the process, as " -"described in the Policy Manual, <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules\">Main " -"building script: debian/rules</ulink>." +"<literal>get-orig-source</literal> target in your <filename>debian/rules</" +"filename> file that repeats the process, as described in the Policy Manual, " +"<ulink url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building " +"script: debian/rules</ulink>." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote> -#: best-pkging-practices.dbk:1610 +#: best-pkging-practices.dbk:1628 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 " @@ -2313,7 +2237,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para> -#: best-pkging-practices.dbk:1612 +#. or similarly named +#: best-pkging-practices.dbk:1630 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 " @@ -2325,7 +2250,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1623 +#: best-pkging-practices.dbk:1642 msgid "" "<emphasis role=\"strong\">should</emphasis>, except where impossible for " "legal reasons, preserve the entire building and portablility infrastructure " @@ -2337,86 +2262,75 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1632 +#: best-pkging-practices.dbk:1651 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 " -"mirror rather than trying to locate a canonical upstream distribution " -"point)." +"mirror rather than trying to locate a canonical upstream distribution point)." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1639 +#: best-pkging-practices.dbk:1658 msgid "" -"<emphasis role=\"strong\">should</emphasis> use " -"<literal><packagename>-<upstream-version>.orig</literal> as the " -"name of the top-level directory in its tarball. This makes it possible to " -"distinguish pristine tarballs from repackaged ones." +"<emphasis role=\"strong\">should</emphasis> use <literal><packagename>-" +"<upstream-version>.orig</literal> as the name of the top-level " +"directory in its tarball. This makes it possible to distinguish pristine " +"tarballs from repackaged ones." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1647 +#: best-pkging-practices.dbk:1666 msgid "" "<emphasis role=\"strong\">should</emphasis> be gzipped with maximal " "compression." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1652 +#: best-pkging-practices.dbk:1671 msgid "" -"The canonical way to meet the latter two points is to let " -"<literal>dpkg-source -b</literal> construct the repackaged tarball from an " -"unpacked directory." +"The canonical way to meet the latter two points is to let <literal>dpkg-" +"source -b</literal> construct the repackaged tarball from an unpacked " +"directory." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1658 +#: best-pkging-practices.dbk:1677 msgid "Changing binary files in <literal>diff.gz</literal>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1660 +#: best-pkging-practices.dbk:1679 msgid "" "Sometimes it is necessary to change binary files contained in the original " "tarball, or to add binary files that are not in it. If this is done by " -"simply copying the files into the debianized source tree, " -"<command>dpkg-source</command> will not be able to handle this. On the " -"other hand, according to the guidelines given above, you cannot include such " -"a changed binary file in a repackaged <filename>orig.tar.gz</filename>. " -"Instead, include the file in the <filename>debian</filename> directory in " +"simply copying the files into the debianized source tree, <command>dpkg-" +"source</command> will not be able to handle this. On the other hand, " +"according to the guidelines given above, you cannot include such a changed " +"binary file in a repackaged <filename>orig.tar.gz</filename>. Instead, " +"include the file in the <filename>debian</filename> directory in " "<command>uuencode</command>d (or similar) form <footnote>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1667 +#: best-pkging-practices.dbk:1686 msgid "" "The file should have a name that makes it clear which binary file it " "encodes. Usually, some postfix indicating the encoding should be appended " "to the original filename. Note that you don't need to depend on <systemitem " -"role=\"package\">sharutils</systemitem> to get the " -"<command>uudecode</command> program if you use <command>perl</command>'s " -"<literal>pack</literal> function. The code could look like" -msgstr "" - -# type: Content of: <chapter><section><section><section><para><footnote><screen> -#: best-pkging-practices.dbk:1673 -#, no-wrap -msgid "" -"-file: perl -ne 'print(pack u, $$_);'\n" -"$(file) > $(file).uuencoded uudecode-file: perl -ne 'print(unpack u, " -"$$_);'\n" -"$(file).uuencoded > $(file)" +"role=\"package\">sharutils</systemitem> to get the <command>uudecode</" +"command> program if you use <command>perl</command>'s <literal>pack</" +"literal> function. The code could look like" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1675 +#: best-pkging-practices.dbk:1694 msgid "" -"</footnote>. The file would then be decoded and copied to its place during " -"the build process. Thus the change will be visible quite easy." +"&example-uu; </footnote>. The file would then be decoded and copied to its " +"place during the build process. Thus the change will be visible quite easy." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1680 +#: best-pkging-practices.dbk:1700 msgid "" "Some packages use <command>dbs</command> to manage patches to their upstream " "source, and always create a new <literal>orig.tar.gz</literal> file that " @@ -2428,12 +2342,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1693 +#: best-pkging-practices.dbk:1713 msgid "Best practices for debug packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1695 +#: best-pkging-practices.dbk:1715 msgid "" "A debug package is a package with a name ending in -dbg, that contains " "additional information that gdb can use. Since Debian binaries are stripped " @@ -2444,7 +2358,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1703 +#: best-pkging-practices.dbk:1723 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 " @@ -2457,7 +2371,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1713 +#: best-pkging-practices.dbk:1733 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 " @@ -2467,40 +2381,39 @@ msgid "" "<emphasis>path</emphasis> is the path to the executable or library. For " "example, debugging symbols for <filename>/usr/bin/foo</filename> go in " "<filename>/usr/lib/debug/usr/bin/foo</filename>, and debugging symbols for " -"<filename>/usr/lib/libfoo.so.1</filename> go in " -"<filename>/usr/lib/debug/usr/lib/libfoo.so.1</filename>." +"<filename>/usr/lib/libfoo.so.1</filename> go in <filename>/usr/lib/debug/usr/" +"lib/libfoo.so.1</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1725 +#: best-pkging-practices.dbk:1745 msgid "" -"The debugging symbols can be extracted from an object file using objcopy " -"--only-keep-debug. Then the object file can be stripped, and objcopy " -"--add-gnu-debuglink used to specify the path to the debugging symbol file. " -"<citerefentry> <refentrytitle>objcopy</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> explains in detail how this works." +"The debugging symbols can be extracted from an object file using objcopy --" +"only-keep-debug. Then the object file can be stripped, and objcopy --add-" +"gnu-debuglink used to specify the path to the debugging symbol file. " +"<citerefentry> <refentrytitle>objcopy</refentrytitle> <manvolnum>1</" +"manvolnum> </citerefentry> explains in detail how this works." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1732 +#: best-pkging-practices.dbk:1752 msgid "" "The dh_strip command in debhelper supports creating debug packages, and can " "take care of using objcopy to separate out the debugging symbols for you. " -"If your package uses debhelper, all you need to do is call dh_strip " -"--dbg-package=libfoo-dbg, and add an entry to debian/control for the debug " -"package." +"If your package uses debhelper, all you need to do is call dh_strip --dbg-" +"package=libfoo-dbg, and add an entry to debian/control for the debug package." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1739 +#: best-pkging-practices.dbk:1759 msgid "" "Note that the Debian package should depend on the package that it provides " -"debugging symbols for, and this dependency should be versioned. For " -"example:" +"debugging symbols for, and this dependency should be versioned. For example:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1743 +#: best-pkging-practices.dbk:1763 #, no-wrap -msgid ": libfoo-dbg (= ${binary:Version})" +msgid "Depends: libfoo-dbg (= ${binary:Version})" msgstr "" + diff --git a/po4a/fr/beyond-pkging.po b/po4a/fr/beyond-pkging.po index 586c3ca..2d00dd6 100644 --- a/po4a/fr/beyond-pkging.po +++ b/po4a/fr/beyond-pkging.po @@ -1,26 +1,28 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:09+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: beyond-pkging.dbk:5 +#: beyond-pkging.dbk:7 msgid "Beyond Packaging" -msgstr "" +msgstr "Au-delà de l'empaquetage" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:7 +#: beyond-pkging.dbk:9 msgid "" "Debian is about a lot more than just packaging software and maintaining " "those packages. This chapter contains information about ways, often really " @@ -29,7 +31,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:12 +#: beyond-pkging.dbk:14 msgid "" "As a volunteer organization, Debian relies on the discretion of its members " "in choosing what they want to work on and in choosing the most critical " @@ -37,12 +39,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:17 +#: beyond-pkging.dbk:19 msgid "Bug reporting" -msgstr "" +msgstr "Rapporter des bogues" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:19 +#: beyond-pkging.dbk:21 msgid "" "We encourage you to file bugs as you find them in Debian packages. In fact, " "Debian developers are often the first line testers. Finding and reporting " @@ -50,15 +52,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:24 +#: beyond-pkging.dbk:26 msgid "" -"Read the <ulink url=\"http://www.debian.org/Bugs/Reporting\">instructions " -"for reporting bugs</ulink> in the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>." +"Read the <ulink url=\"&url-bts-report;\">instructions for reporting bugs</" +"ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking system</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:29 +#: beyond-pkging.dbk:31 msgid "" "Try to submit the bug from a normal user account at which you are likely to " "receive mail, so that people can reach you if they need further information " @@ -66,28 +67,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:34 +#: beyond-pkging.dbk:36 msgid "" -"You can use a tool like <citerefentry> " -"<refentrytitle>reportbug</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry> to submit bugs. It can automate and generally ease the " -"process." +"You can use a tool like <citerefentry> <refentrytitle>reportbug</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry> to submit bugs. It " +"can automate and generally ease the process." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:39 +#: beyond-pkging.dbk:41 msgid "" "Make sure the bug is not already filed against a package. Each package has " -"a bug list easily reachable at " -"<literal>http://bugs.debian.org/<replaceable>packagename</replaceable></literal> " -"Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> can also provide you with this " -"information (and <command>reportbug</command> will usually invoke " -"<command>querybts</command> before sending, too)." +"a bug list easily reachable at <literal>http://&bugs-host;/" +"<replaceable>packagename</replaceable></literal> Utilities like " +"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</" +"manvolnum> </citerefentry> can also provide you with this information (and " +"<command>reportbug</command> will usually invoke <command>querybts</command> " +"before sending, too)." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:48 +#: beyond-pkging.dbk:50 msgid "" "Try to direct your bugs to the proper location. When for example your bug " "is about a package which overwrites files from another package, check the " @@ -96,7 +96,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:54 +#: beyond-pkging.dbk:56 msgid "" "For extra credit, you can go through other packages, merging bugs which are " "reported more than once, or tagging bugs `fixed' when they have already been " @@ -106,72 +106,70 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:61 +#: beyond-pkging.dbk:63 msgid "" "From time to time you may want to check what has been going on with the bug " "reports that you submitted. Take this opportunity to close those that you " "can't reproduce anymore. To find out all the bugs you submitted, you just " -"have to visit " -"<literal>http://bugs.debian.org/from:<replaceable><your-email-addr></replaceable></literal>." +"have to visit <literal>http://&bugs-host;/from:<replaceable><your-email-" +"addr></replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:68 +#: beyond-pkging.dbk:70 msgid "Reporting lots of bugs at once (mass bug filing)" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:70 +#: beyond-pkging.dbk:72 msgid "" "Reporting a great number of bugs for the same problem on a great number of " "different packages — i.e., more than 10 — is a deprecated practice. Take " "all possible steps to avoid submitting bulk bugs at all. For instance, if " "checking for the problem can be automated, add a new check to <systemitem " -"role=\"package\">lintian</systemitem> so that an error or warning is " -"emitted." +"role=\"package\">lintian</systemitem> so that an error or warning is emitted." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:77 +#: beyond-pkging.dbk:79 msgid "" "If you report more than 10 bugs on the same topic at once, it is recommended " -"that you send a message to <email>debian-devel@lists.debian.org</email> " -"describing your intention before submitting the report, and mentioning the " -"fact in the subject of your mail. This will allow other developers to " -"verify that the bug is a real problem. In addition, it will help prevent a " -"situation in which several maintainers start filing the same bug report " -"simultaneously." +"that you send a message to &email-debian-devel; describing your intention " +"before submitting the report, and mentioning the fact in the subject of your " +"mail. This will allow other developers to verify that the bug is a real " +"problem. In addition, it will help prevent a situation in which several " +"maintainers start filing the same bug report simultaneously." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:85 +#: beyond-pkging.dbk:87 msgid "" "Please use the programms <command>dd-list</command> and if appropriate " "<command>whodepends</command> (from the package devscripts) to generate a " -"list of all affected packages, and include the output in your mail to " -"<email>debian-devel@lists.debian.org</email>." +"list of all affected packages, and include the output in your mail to &email-" +"debian-devel;." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:91 +#: beyond-pkging.dbk:93 msgid "" "Note that when sending lots of bugs on the same subject, you should send the " -"bug report to <email>maintonly@bugs.debian.org</email> so that the bug " -"report is not forwarded to the bug distribution mailing list." +"bug report to <email>maintonly@&bugs-host;</email> so that the bug report is " +"not forwarded to the bug distribution mailing list." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:100 +#: beyond-pkging.dbk:102 msgid "Quality Assurance effort" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:102 +#: beyond-pkging.dbk:104 msgid "Daily work" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:104 +#: beyond-pkging.dbk:106 msgid "" "Even though there is a dedicated group of people for Quality Assurance, QA " "duties are not reserved solely for them. You can participate in this effort " @@ -180,30 +178,29 @@ msgid "" "possible, then you should consider orphaning some of your packages (see " "<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of " "other people in order to catch up with the backlog of bugs that you have " -"(you can ask for help on <email>debian-qa@lists.debian.org</email> or " -"<email>debian-devel@lists.debian.org</email>). At the same time, you can " -"look for co-maintainers (see <xref linkend=\"collaborative-maint\"/> )." +"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the " +"same time, you can look for co-maintainers (see <xref linkend=" +"\"collaborative-maint\"/> )." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:118 +#: beyond-pkging.dbk:120 msgid "Bug squashing parties" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:120 +#: beyond-pkging.dbk:122 msgid "" "From time to time the QA group organizes bug squashing parties to get rid of " -"as many problems as possible. They are announced on " -"<email>debian-devel-announce@lists.debian.org</email> and the announcement " -"explains which area will be the focus of the party: usually they focus on " -"release critical bugs but it may happen that they decide to help finish a " -"major upgrade (like a new perl version which requires recompilation of all " -"the binary modules)." +"as many problems as possible. They are announced on &email-debian-devel-" +"announce; and the announcement explains which area will be the focus of the " +"party: usually they focus on release critical bugs but it may happen that " +"they decide to help finish a major upgrade (like a new perl version which " +"requires recompilation of all the binary modules)." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:129 +#: beyond-pkging.dbk:131 msgid "" "The rules for non-maintainer uploads differ during the parties because the " "announcement of the party is considered prior notice for NMU. If you have " @@ -216,7 +213,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:138 +#: beyond-pkging.dbk:140 msgid "" "People participating in the party have special rules for NMU, they can NMU " "without prior notice if they upload their NMU to DELAYED/3-day at least. " @@ -227,19 +224,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:145 +#: beyond-pkging.dbk:147 msgid "" "If you don't feel confident about doing an NMU, just send a patch to the " "BTS. It's far better than a broken NMU." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:153 +#: beyond-pkging.dbk:155 msgid "Contacting other maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:155 +#: beyond-pkging.dbk:157 msgid "" "During your lifetime within Debian, you will have to contact other " "maintainers for various reasons. You may want to discuss a new way of " @@ -248,32 +245,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:161 +#: beyond-pkging.dbk:163 msgid "" "Looking up the email address of the maintainer for the package can be " -"distracting. Fortunately, there is a simple email alias, " -"<literal><package>@packages.debian.org</literal>, which provides a way " -"to email the maintainer, whatever their individual email address (or " -"addresses) may be. Replace <literal><package></literal> with the " -"name of a source or a binary package." +"distracting. Fortunately, there is a simple email alias, <literal><" +"package>@&packages-host;</literal>, which provides a way to email the " +"maintainer, whatever their individual email address (or addresses) may be. " +"Replace <literal><package></literal> with the name of a source or a " +"binary package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:169 +#: beyond-pkging.dbk:171 msgid "" "You may also be interested in contacting the persons who are subscribed to a " "given source package via <xref linkend=\"pkg-tracking-system\"/> . You can " -"do so by using the <literal><package>@packages.qa.debian.org</literal> " -"email address." +"do so by using the <literal><package>@&pts-host;</literal> email " +"address." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:177 +#: beyond-pkging.dbk:180 msgid "Dealing with inactive and/or unreachable maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:179 +#: beyond-pkging.dbk:182 msgid "" "If you notice that a package is lacking maintenance, you should make sure " "that the maintainer is active and will continue to work on their packages. " @@ -283,32 +280,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:186 +#: beyond-pkging.dbk:189 msgid "" "There is a simple system (the MIA database) in which information about " "maintainers who are deemed Missing In Action is recorded. When a member of " "the QA group contacts an inactive maintainer or finds more information about " -"one, this is recorded in the MIA database. This system is available in " -"/org/qa.debian.org/mia on the host qa.debian.org, and can be queried with a " -"tool known as <command>mia-query</command>. Use" -msgstr "" - -# type: Content of: <chapter><section><screen> -#: beyond-pkging.dbk:194 -#, no-wrap -msgid "-query --help" -msgstr "" - -# type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:197 -msgid "" -"to see how to query the database. If you find that no information has been " -"recorded about an inactive maintainer yet, or that you can add more " +"one, this is recorded in the MIA database. This system is available in /org/" +"qa.debian.org/mia on the host qa.debian.org, and can be queried with a tool " +"known as <command>mia-query</command>. Use <command>mia-query --help</" +"command> to see how to query the database. If you find that no information " +"has been recorded about an inactive maintainer yet, or that you can add more " "information, you should generally proceed as follows." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:202 +#: beyond-pkging.dbk:200 msgid "" "The first step is to politely contact the maintainer, and wait a reasonable " "time for a response. It is quite hard to define reasonable time, but it is " @@ -317,7 +303,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:208 +#: beyond-pkging.dbk:206 msgid "" "If the maintainer doesn't reply within four weeks (a month), one can assume " "that a response will probably not happen. If that happens, you should " @@ -326,17 +312,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:216 +#: beyond-pkging.dbk:214 msgid "" -"The echelon information available through the <ulink " -"url=\"https://db.debian.org/\">developers' LDAP database</ulink>, which " -"indicates when the developer last posted to a Debian mailing list. (This " -"includes uploads via debian-*-changes lists.) Also, remember to check " -"whether the maintainer is marked as on vacation in the database." +"The echelon information available through the <ulink url=\"&url-debian-db;" +"\">developers' LDAP database</ulink>, which indicates when the developer " +"last posted to a Debian mailing list. (This includes uploads via debian-*-" +"changes lists.) Also, remember to check whether the maintainer is marked as " +"on vacation in the database." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:225 +#: beyond-pkging.dbk:223 msgid "" "The number of packages this maintainer is responsible for, and the condition " "of those packages. In particular, are there any RC bugs that have been open " @@ -346,7 +332,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:234 +#: beyond-pkging.dbk:232 msgid "" "Is there any activity of the maintainer outside of Debian? For example, they " "might have posted something recently to non-Debian mailing lists or news " @@ -354,7 +340,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:241 +#: beyond-pkging.dbk:239 msgid "" "A bit of a problem are packages which were sponsored — the maintainer is not " "an official Debian developer. The echelon information is not available for " @@ -365,28 +351,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:249 +#: beyond-pkging.dbk:247 msgid "" -"It is also allowed to post a query to " -"<email>debian-devel@lists.debian.org</email>, asking if anyone is aware of " -"the whereabouts of the missing maintainer. Please Cc: the person in " -"question." +"It is also allowed to post a query to &email-debian-devel;, asking if anyone " +"is aware of the whereabouts of the missing maintainer. Please Cc: the " +"person in question." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:254 +#: beyond-pkging.dbk:252 msgid "" -"Once you have gathered all of this, you can contact " -"<email>mia@qa.debian.org</email>. People on this alias will use the " -"information you provide in order to decide how to proceed. For example, " -"they might orphan one or all of the packages of the maintainer. If a " -"package has been NMUed, they might prefer to contact the NMUer before " -"orphaning the package — perhaps the person who has done the NMU is " -"interested in the package." +"Once you have gathered all of this, you can contact &email-mia;. People on " +"this alias will use the information you provide in order to decide how to " +"proceed. For example, they might orphan one or all of the packages of the " +"maintainer. If a package has been NMUed, they might prefer to contact the " +"NMUer before orphaning the package — perhaps the person who has done the NMU " +"is interested in the package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:262 +#: beyond-pkging.dbk:260 msgid "" "One last word: please remember to be polite. We are all volunteers and " "cannot dedicate all of our time to Debian. Also, you are not aware of the " @@ -397,7 +381,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:270 +#: beyond-pkging.dbk:268 msgid "" "On the other hand, although we are volunteers, we do have a responsibility. " "So you can stress the importance of the greater good — if a maintainer does " @@ -406,21 +390,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:276 +#: beyond-pkging.dbk:274 msgid "" "If you are interested in working in the MIA team, please have a look at the " "README file in /org/qa.debian.org/mia on qa.debian.org where the technical " -"details and the MIA procedures are documented and contact " -"<email>mia@qa.debian.org</email>." +"details and the MIA procedures are documented and contact &email-mia;." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:284 +#: beyond-pkging.dbk:282 msgid "Interacting with prospective Debian developers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:286 +#: beyond-pkging.dbk:284 msgid "" "Debian's success depends on its ability to attract and retain new and " "talented volunteers. If you are an experienced developer, we recommend that " @@ -429,12 +412,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:292 +#: beyond-pkging.dbk:290 msgid "Sponsoring packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:294 +#: beyond-pkging.dbk:292 msgid "" "Sponsoring a package means uploading a package for a maintainer who is not " "able to do it on their own, a new maintainer applicant. Sponsoring a " @@ -442,7 +425,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:299 +#: beyond-pkging.dbk:303 msgid "" "New maintainers usually have certain difficulties creating Debian packages — " "this is quite understandable. That is why the sponsor is there, to check " @@ -452,7 +435,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:306 +#: beyond-pkging.dbk:310 msgid "" "Sponsoring merely by signing the upload or just recompiling is <emphasis " "role=\"strong\">definitely not recommended</emphasis>. You need to build " @@ -463,7 +446,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:313 +#: beyond-pkging.dbk:317 msgid "" "If you are an application manager for a prospective developer, you can also " "be their sponsor. That way you can also verify how the applicant is " @@ -471,12 +454,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:320 +#: beyond-pkging.dbk:324 msgid "Managing sponsored packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:322 +#: beyond-pkging.dbk:326 msgid "" "By uploading a sponsored package to Debian, you are certifying that the " "package meets minimum Debian standards. That implies that you must build " @@ -484,19 +467,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:327 +#: beyond-pkging.dbk:331 msgid "" "You cannot simply upload a binary <filename>.deb</filename> from the " "sponsoree. In theory, you should only ask for the diff file and the " "location of the original source tarball, and then you should download the " "source and apply the diff yourself. In practice, you may want to use the " "source package built by your sponsoree. In that case, you have to check " -"that they haven't altered the upstream files in the " -"<filename>.orig.tar.gz</filename> file that they're providing." +"that they haven't altered the upstream files in the <filename>.orig.tar.gz</" +"filename> file that they're providing." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:336 +#: beyond-pkging.dbk:340 msgid "" "Do not be afraid to write the sponsoree back and point out changes that need " "to be made. It often takes several rounds of back-and-forth email before " @@ -504,18 +487,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:341 +#: beyond-pkging.dbk:345 msgid "Once the package meets Debian standards, build and sign it with" msgstr "" # type: Content of: <chapter><section><section><screen> -#: beyond-pkging.dbk:344 +#: beyond-pkging.dbk:348 #, no-wrap -msgid "-buildpackage -k<replaceable>KEY-ID</replaceable>" +msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:347 +#: beyond-pkging.dbk:351 msgid "" "before uploading it to the incoming directory. Of course, you can also use " "any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique " @@ -523,7 +506,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:352 +#: beyond-pkging.dbk:356 msgid "" "The Maintainer field of the <filename>control</filename> file and the " "<filename>changelog</filename> should list the person who did the packaging, " @@ -532,41 +515,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:358 +#: beyond-pkging.dbk:362 msgid "" "If you prefer to leave a more evident trace of your sponsorship job, you can " "add a line stating it in the most recent changelog entry." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:362 +#: beyond-pkging.dbk:366 msgid "" "You are encouraged to keep tabs on the package you sponsor using <xref " "linkend=\"pkg-tracking-system\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:368 +#: beyond-pkging.dbk:372 msgid "Advocating new developers" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:370 +#: beyond-pkging.dbk:374 msgid "" -"See the page about <ulink " -"url=\"http://www.debian.org/devel/join/nm-advocate\">advocating a " +"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a " "prospective developer</ulink> at the Debian web site." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:377 +#: beyond-pkging.dbk:381 msgid "Handling new maintainer applications" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:379 +#: beyond-pkging.dbk:383 msgid "" -"Please see <ulink " -"url=\"http://www.debian.org/devel/join/nm-amchecklist\">Checklist for " +"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for " "Application Managers</ulink> at the Debian web site." msgstr "" + diff --git a/po4a/fr/developer-duties.po b/po4a/fr/developer-duties.po index 487ca81..6def51f 100644 --- a/po4a/fr/developer-duties.po +++ b/po4a/fr/developer-duties.po @@ -1,64 +1,66 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:10+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: developer-duties.dbk:5 +#: developer-duties.dbk:7 msgid "Debian Developer's Duties" -msgstr "" +msgstr "Les charges du responsable Debian" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:7 +#: developer-duties.dbk:9 msgid "Maintaining your Debian information" -msgstr "" +msgstr "Mise à jour de vos références Debian" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:9 +#: developer-duties.dbk:11 msgid "" "There's a LDAP database containing information about Debian developers at " -"<ulink url=\"https://db.debian.org/\"></ulink>. You should enter your " -"information there and update it as it changes. Most notably, make sure that " -"the address where your debian.org email gets forwarded to is always up to " -"date, as well as the address where you get your debian-private subscription " -"if you choose to subscribe there." +"<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information " +"there and update it as it changes. Most notably, make sure that the address " +"where your debian.org email gets forwarded to is always up to date, as well " +"as the address where you get your debian-private subscription if you choose " +"to subscribe there." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:17 +#: developer-duties.dbk:19 msgid "" -"For more information about the database, please see <xref " -"linkend=\"devel-db\"/> ." +"For more information about the database, please see <xref linkend=\"devel-db" +"\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:23 +#: developer-duties.dbk:25 msgid "Maintaining your public key" -msgstr "" +msgstr "Gérer votre clé publique" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:25 +#: developer-duties.dbk:27 msgid "" "Be very careful with your private keys. Do not place them on any public " -"servers or multiuser machines, such as the Debian servers (see <xref " -"linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. " -"Read the documentation that comes with your software; read the <ulink " -"url=\"http://www.cam.ac.uk.pgp.net/pgpnet/pgp-faq/\">PGP FAQ</ulink>." +"servers or multiuser machines, such as the Debian servers (see <xref linkend=" +"\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the " +"documentation that comes with your software; read the <ulink url=\"&url-pgp-" +"faq;\">PGP FAQ</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:32 +#: developer-duties.dbk:34 msgid "" "You need to ensure not only that your key is secure against being stolen, " "but also that it is secure against being lost. Generate and make a copy " @@ -67,90 +69,87 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:38 +#: developer-duties.dbk:40 msgid "" "If you add signatures to your public key, or add user identities, you can " "update the Debian key ring by sending your key to the key server at " -"<literal>keyring.debian.org</literal>." +"<literal>&keyserver-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:43 +#: developer-duties.dbk:45 msgid "" "If you need to add a completely new key or remove an old key, you need to " "get the new key signed by another developer. If the old key is compromised " "or invalid, you also have to add the revocation certificate. If there is no " "real reason for a new key, the Keyring Maintainers might reject the new " -"key. Details can be found at <ulink " -"url=\"http://keyring.debian.org/replacing_keys.html\"></ulink>." +"key. Details can be found at <ulink url=\"http://&keyserver-host;/" +"replacing_keys.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:51 +#: developer-duties.dbk:53 msgid "" -"The same key extraction routines discussed in <xref " -"linkend=\"registering\"/> apply." +"The same key extraction routines discussed in <xref linkend=\"registering\"/" +"> apply." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:55 +#: developer-duties.dbk:57 msgid "" "You can find a more in-depth discussion of Debian key maintenance in the " -"documentation of the <systemitem " -"role=\"package\">debian-keyring</systemitem> package." +"documentation of the <systemitem role=\"package\">debian-keyring</" +"systemitem> package." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:62 +#: developer-duties.dbk:64 msgid "Voting" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:64 +#: developer-duties.dbk:66 msgid "" "Even though Debian isn't really a democracy, we use a democratic process to " "elect our leaders and to approve general resolutions. These procedures are " -"defined by the <ulink " -"url=\"http://www.debian.org/devel/constitution\">Debian " -"Constitution</ulink>." +"defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:70 +#: developer-duties.dbk:72 msgid "" "Other than the yearly leader election, votes are not routinely held, and " "they are not undertaken lightly. Each proposal is first discussed on the " -"<email>debian-vote@lists.debian.org</email> mailing list and it requires " -"several endorsements before the project secretary starts the voting " -"procedure." +"&email-debian-vote; mailing list and it requires several endorsements before " +"the project secretary starts the voting procedure." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:76 +#: developer-duties.dbk:78 msgid "" "You don't have to track the pre-vote discussions, as the secretary will " -"issue several calls for votes on " -"<email>debian-devel-announce@lists.debian.org</email> (and all developers " -"are expected to be subscribed to that list). Democracy doesn't work well if " -"people don't take part in the vote, which is why we encourage all developers " -"to vote. Voting is conducted via GPG-signed/encrypted email messages." +"issue several calls for votes on &email-debian-devel-announce; (and all " +"developers are expected to be subscribed to that list). Democracy doesn't " +"work well if people don't take part in the vote, which is why we encourage " +"all developers to vote. Voting is conducted via GPG-signed/encrypted email " +"messages." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:84 +#: developer-duties.dbk:86 msgid "" -"The list of all proposals (past and current) is available on the <ulink " -"url=\"http://www.debian.org/vote/\">Debian Voting Information</ulink> page, " -"along with information on how to make, second and vote on proposals." +"The list of all proposals (past and current) is available on the <ulink url=" +"\"&url-vote;\">Debian Voting Information</ulink> page, along with " +"information on how to make, second and vote on proposals." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:91 +#: developer-duties.dbk:93 msgid "Going on vacation gracefully" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:93 +#: developer-duties.dbk:95 msgid "" "It is common for developers to have periods of absence, whether those are " "planned vacations or simply being buried in other work. The important thing " @@ -160,7 +159,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:100 +#: developer-duties.dbk:102 msgid "" "Usually this means that other developers are allowed to NMU (see <xref " "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, " @@ -170,30 +169,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote> -#: developer-duties.dbk:107 +#: developer-duties.dbk:109 msgid "" "In order to inform the other developers, there are two things that you " -"should do. First send a mail to " -"<email>debian-private@lists.debian.org</email> with [VAC] prepended to the " -"subject of your message<footnote>" +"should do. First send a mail to <email>debian-private@&lists-host;</email> " +"with [VAC] prepended to the subject of your message<footnote>" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: developer-duties.dbk:109 +#: developer-duties.dbk:111 msgid "" "This is so that the message can be easily filtered by people who don't want " "to read vacation notices." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:111 +#: developer-duties.dbk:113 msgid "" "</footnote> and state the period of time when you will be on vacation. You " "can also give some special instructions on what to do if a problem occurs." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:116 +#: developer-duties.dbk:118 msgid "" "The other thing to do is to mark yourself as on vacation in the <link " "linkend=\"devel-db\">Debian developers' LDAP database</link> (this " @@ -202,22 +200,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:122 +#: developer-duties.dbk:124 msgid "" -"Ideally, you should sign up at the <ulink " -"url=\"http://nm.debian.org/gpg.php\">GPG coordination site</ulink> when " -"booking a holiday and check if anyone there is looking for signing. This is " -"especially important when people go to exotic places where we don't have any " -"developers yet but where there are people who are interested in applying." +"Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php" +"\">GPG coordination site</ulink> when booking a holiday and check if anyone " +"there is looking for signing. This is especially important when people go " +"to exotic places where we don't have any developers yet but where there are " +"people who are interested in applying." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:131 +#: developer-duties.dbk:133 msgid "Coordination with upstream developers" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:133 +#: developer-duties.dbk:135 msgid "" "A big part of your job as Debian maintainer will be to stay in contact with " "the upstream developers. Debian users will sometimes report bugs that are " @@ -227,7 +225,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:140 +#: developer-duties.dbk:142 msgid "" "While it's not your job to fix non-Debian specific bugs, you may freely do " "so if you're able. When you make such fixes, be sure to pass them on to the " @@ -237,7 +235,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:147 +#: developer-duties.dbk:149 msgid "" "If you need to modify the upstream sources in order to build a policy " "compliant package, then you should propose a nice fix to the upstream " @@ -247,12 +245,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:156 +#: developer-duties.dbk:158 msgid "Managing release-critical bugs" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:158 +#: developer-duties.dbk:160 msgid "" "Generally you should deal with bug reports on your packages as described in " "<xref linkend=\"bug-handling\"/> . However, there's a special category of " @@ -266,49 +264,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:169 +#: developer-duties.dbk:171 msgid "" -"Developers who are part of the <ulink url=\"http://qa.debian.org/\">Quality " +"Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality " "Assurance</ulink> group are following all such bugs, and trying to help " "whenever possible. If, for any reason, you aren't able fix an RC bug in a " "package of yours within 2 weeks, you should either ask for help by sending a " -"mail to the Quality Assurance (QA) group " -"<email>debian-qa@lists.debian.org</email>, or explain your difficulties and " -"present a plan to fix them by sending a mail to the bug report. Otherwise, " -"people from the QA group may want to do a Non-Maintainer Upload (see <xref " -"linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long " -"as usual before they do their NMU if they have seen no recent activity from " -"you in the BTS)." +"mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</" +"email>, or explain your difficulties and present a plan to fix them by " +"sending a mail to the bug report. Otherwise, people from the QA group may " +"want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after " +"trying to contact you (they might not wait as long as usual before they do " +"their NMU if they have seen no recent activity from you in the BTS)." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:184 +#: developer-duties.dbk:186 msgid "Retiring" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:186 +#: developer-duties.dbk:188 msgid "" "If you choose to leave the Debian project, you should make sure you do the " "following steps:" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:192 -msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ." +#: developer-duties.dbk:194 +msgid "" +"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:197 +#: developer-duties.dbk:199 msgid "" "Send an gpg-signed email about why you are leaving the project to " -"<email>debian-private@lists.debian.org</email>." +"<email>debian-private@&lists-host;</email>." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:203 +#: developer-duties.dbk:205 msgid "" "Notify the Debian key ring maintainers that you are leaving by opening a " "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the " "words 'Debian RT' somewhere in the subject line (case doesn't matter)." msgstr "" + diff --git a/po4a/fr/index.po b/po4a/fr/index.po index c633212..dcacdb7 100644 --- a/po4a/fr/index.po +++ b/po4a/fr/index.po @@ -1,6 +1,6 @@ # SOME DESCRIPTIVE TITLE # Copyright (C) 2007 Free Software Foundation, Inc. -# debacle <EMAIL@ADDRESS>, 2007. +# debacle <>, 2007. # , fuzzy # # @@ -8,64 +8,68 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" -"PO-Revision-Date: 2007-06-27 10:39+0000\n" -"Last-Translator: debacle <EMAIL@ADDRESS>\n" +"POT-Creation-Date: 2007-07-01 22:28+0000\n" +"PO-Revision-Date: 2007-07-01 23:36+0000\n" +"Last-Translator: debacle <>\n" "Language-Team: English <en@li.org>\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit" # type: Attribute 'lang' of: <book> -#: index.dbk:4 +#: index.dbk:7 msgid "en" msgstr "fr" # type: Content of: <book><title> -#: index.dbk:6 +#: index.dbk:9 msgid "Debian Developer's Reference" msgstr "Référence du développeur Debian" # type: Content of: <book><bookinfo><releaseinfo> -#: index.dbk:27 -msgid "ver. 3.3.9, 16 June, 2007" -msgstr "ver. 3.3.9, 16 June, 2007" +#: index.dbk:30 +msgid "ver. &version;" +msgstr "ver.·&version;" + +# type: Content of: <book><bookinfo><pubdate> +#: index.dbk:31 +msgid "&pubdate;" +msgstr "&pubdate;" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:34 +#: index.dbk:37 msgid "Andreas Barth" msgstr "Andreas Barth" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:43 +#: index.dbk:46 msgid "Adam Di Carlo" msgstr "Adam Di Carlo" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:48 +#: index.dbk:51 msgid "Raphaël Hertzog" msgstr "Raphaël Hertzog" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:53 +#: index.dbk:56 msgid "Christian Schwarz" msgstr "Christian Schwarz" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:57 +#: index.dbk:60 msgid "" "This manual is free software; you may redistribute it and/or modify it under " "the terms of the GNU General Public License as published by the Free " -"Software Foundation; either version 2, or (at your option) any later " -"version." +"Software Foundation; either version 2, or (at your option) any later version." msgstr "" -"Ce manuel est un logiciel libre; il peut être redistribué et/ou " -"modifié selon les termes de la licence publique générale du projet GNU " -"(GNU GPL), telle que publiée par la «Free Software " -"Foundation» (version 2 ou toute version postérieure)." +"Ce manuel est un logiciel libre; il peut être redistribué et/ou modifié " +"selon les termes de la licence publique générale du projet GNU (GNU GPL), " +"telle que publiée par la «Free Software Foundation» (version 2 ou toute " +"version postérieure)." # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:62 +#: index.dbk:65 msgid "" "This is distributed in the hope that it will be useful, but " "<emphasis>without any warranty</emphasis>; without even the implied warranty " @@ -74,35 +78,35 @@ msgid "" msgstr "" "Il est distribué dans l'espoir qu'il sera utile, mais <emphasis>sans aucune " "garantie</emphasis>, sans même la garantie implicite d'une possible valeur " -"marchande ou d'une adéquation à un besoin particulier. Consultez la " -"licence publique générale du projet GNU pour plus de détails." +"marchande ou d'une adéquation à un besoin particulier. Consultez la licence " +"publique générale du projet GNU pour plus de détails." # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:68 +#: index.dbk:71 msgid "" -"A copy of the GNU General Public License is available as " -"<filename>/usr/share/common-licenses/GPL</filename> in the Debian GNU/Linux " -"distribution or on the World Wide Web at <ulink " -"url=\"http://www.gnu.org/copyleft/gpl.html\">the GNU web site</ulink>. You " -"can also obtain it by writing to the Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA." +"A copy of the GNU General Public License is available as &file-GPL; in the " +"&debian-formal; distribution or on the World Wide Web at <ulink url=\"&url-" +"gpl;\">the GNU web site</ulink>. You can also obtain it by writing to the " +"&fsf-addr;." msgstr "" -"Une copie de la licence publique générale du projet GNU est disponible " -"dans le fichier <filename>/usr/share/common-licenses/GPL</filename> de la distribution Debian GNU/Linux ou sur " -"la toile: <ulink " -"url=\"http://www.gnu.org/copyleft/gpl.html\">" -"la licence publique générale du projet GNU</ulink>. Vous pouvez " -"également l'obtenir en écrivant à la Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA." +"Une copie de la licence publique générale du projet GNU est disponible dans " +"le fichier &file-GPL; de la distribution &debian-formal; ou sur la toile: " +"<ulink url=\"&url-gpl;\">la licence publique générale du projet GNU</ulink>. " +"Vous pouvez également l'obtenir en écrivant à la &fsf-addr;." # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:76 +#. TODO: Maybe better: "This document has originally been written +#. in English. Translations into different languages are available." +#: index.dbk:78 msgid "" -"If you want to print this reference, you should use the <ulink " -"url=\"developers-reference.pdf\">pdf version</ulink>. This page is also " +"If you want to print this reference, you should use the <ulink url=" +"\"developers-reference.pdf\">pdf version</ulink>. This page is also " "available in <ulink url=\"index.fr.html\">French</ulink>." msgstr "" -"Si vous désirez imprimer cette référence, vous devriez utiliser la " -"<ulink url=\"developers-reference.pdf\">version PDF</ulink>. Cette page est " +"Si vous désirez imprimer cette référence, vous devriez utiliser la <ulink " +"url=\"developers-reference.pdf\">version PDF</ulink>. Cette page est " "également disponible en <ulink url=\"index.html\">anglais</ulink>." +# type: Content of: <book><bookinfo><releaseinfo> +#~ msgid "ver. 3.3.9, 16 June, 2007" +#~ msgstr "ver. 3.3.9, 16 June, 2007" diff --git a/po4a/fr/l10n.po b/po4a/fr/l10n.po index d09b196..3eb1bb0 100644 --- a/po4a/fr/l10n.po +++ b/po4a/fr/l10n.po @@ -1,28 +1,29 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:14+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: l10n.dbk:5 +#: l10n.dbk:7 msgid "" -"Internationalizing, translating, being internationalized and being " -"translated" -msgstr "" +"Internationalizing, translating, being internationalized and being translated" +msgstr "Internationalisation, traduction, être internationalisé et être traduit" # type: Content of: <chapter><para> -#: l10n.dbk:7 +#: l10n.dbk:9 msgid "" "Debian supports an ever-increasing number of natural languages. Even if you " "are a native English speaker and do not speak any other language, it is part " @@ -33,19 +34,25 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:15 +#: l10n.dbk:17 msgid "" -"According to <ulink " -"url=\"http://www.debian.org/doc/manuals/intro-i18n/\">Introduction to " -"i18n</ulink> from Tomohiro KUBOTA, I18N (internationalization) means " -"modification of a software or related technologies so that a software can " -"potentially handle multiple languages, customs, and so on in the world. " -"while L10N (localization) means implementation of a specific language for an " -"already internationalized software." -msgstr "" +"According to <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/" +"\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N " +"(internationalization) means modification of a software or related " +"technologies so that a software can potentially handle multiple languages, " +"customs, and so on in the world. while L10N (localization) means " +"implementation of a specific language for an already internationalized " +"software." +msgstr "Selon l'<ulink url=\"http://www.debian.org/doc/manuals/intro-i18n/\">introduction à l'i18n</ulink> de Tomohiro KUBOTA, «I18N" +"(internationalisation) veut dire la modification d'un logiciel ou de" +"technologies liées pour qu'un logiciel puisse potentiellement gérer des" +"langues multiples, des conventions multiples et ainsi de suite dans le" +"monde entier» alors que «L10N (localisation) veut dire" +"l'implémentation dans une langue spécifique pour un logiciel déjà" +"internationalisé»." # type: Content of: <chapter><para> -#: l10n.dbk:24 +#: l10n.dbk:26 msgid "" "l10n and i18n are interconnected, but the difficulties related to each of " "them are very different. It's not really difficult to allow a program to " @@ -56,7 +63,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:32 +#: l10n.dbk:34 msgid "" "Setting aside the i18n problems, where no general guideline can be given, " "there is actually no central infrastructure for l10n within Debian which " @@ -65,36 +72,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:38 +#: l10n.dbk:40 msgid "How translations are handled within Debian" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:40 +#: l10n.dbk:42 msgid "" "Handling translation of the texts contained in a package is still a manual " -"task, and the process depends on the kind of text you want to see " -"translated." +"task, and the process depends on the kind of text you want to see translated." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:44 +#: l10n.dbk:46 msgid "" "For program messages, the gettext infrastructure is used most of the time. " "Most of the time, the translation is handled upstream within projects like " "the <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">Free " -"Translation Project</ulink>, the <ulink " -"url=\"http://developer.gnome.org/projects/gtp/\">Gnome translation " -"Project</ulink> or the <ulink url=\"http://i18n.kde.org/\">KDE one</ulink>. " -"The only centralized resource within Debian is the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " -"statistics</ulink>, where you can find some statistics about the translation " -"files found in the actual packages, but no real infrastructure to ease the " -"translation process." +"Translation Project</ulink>, the <ulink url=\"http://developer.gnome.org/" +"projects/gtp/\">Gnome translation Project</ulink> or the <ulink url=\"http://" +"i18n.kde.org/\">KDE one</ulink>. The only centralized resource within " +"Debian is the <ulink url=\"http://&www-debian-org;/intl/l10n/\">Central " +"Debian translation statistics</ulink>, where you can find some statistics " +"about the translation files found in the actual packages, but no real " +"infrastructure to ease the translation process." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:57 +#: l10n.dbk:59 msgid "" "An effort to translate the package descriptions started long ago, even if " "very little support is offered by the tools to actually use them (i.e., only " @@ -104,26 +109,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:64 +#: l10n.dbk:66 msgid "" "For debconf templates, maintainers should use the po-debconf package to ease " "the work of translators, who could use the DDTP to do their work (but the " "French and Brazilian teams don't). Some statistics can be found both on the " -"DDTP site (about what is actually translated), and on the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " +"DDTP site (about what is actually translated), and on the <ulink url=" +"\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink> site (about what is integrated in the packages)." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:72 +#: l10n.dbk:74 msgid "" "For web pages, each l10n team has access to the relevant CVS, and the " -"statistics are available from the Central Debian translation statistics " -"site." +"statistics are available from the Central Debian translation statistics site." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:76 +#: l10n.dbk:78 msgid "" "For general documentation about Debian, the process is more or less the same " "as for the web pages (the translators have access to the CVS), but there are " @@ -131,34 +135,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:81 +#: l10n.dbk:83 msgid "" "For package-specific documentation (man pages, info documents, other " "formats), almost everything remains to be done." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:85 +#: l10n.dbk:87 msgid "" "Most notably, the KDE project handles translation of its documentation in " "the same way as its program messages." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:89 +#: l10n.dbk:91 msgid "" -"There is an effort to handle Debian-specific man pages within a <ulink " -"url=\"http://cvs.debian.org/manpages/?cvsroot=debian-doc\">specific CVS " -"repository</ulink>." +"There is an effort to handle Debian-specific man pages within a <ulink url=" +"\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS repository</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:96 +#: l10n.dbk:98 msgid "I18N & L10N FAQ for maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:98 +#: l10n.dbk:100 msgid "" "This is a list of problems that maintainers may face concerning i18n and " "l10n. While reading this, keep in mind that there is no real consensus on " @@ -168,12 +171,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:105 +#: l10n.dbk:107 msgid "How to get a given text translated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:107 +#: l10n.dbk:109 msgid "" "To translate package descriptions or debconf templates, you have nothing to " "do; the DDTP infrastructure will dispatch the material to translate to " @@ -181,7 +184,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:112 +#: l10n.dbk:114 msgid "" "For all other material (gettext files, man pages, or other documentation), " "the best solution is to put your text somewhere on the Internet, and ask on " @@ -192,12 +195,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:122 +#: l10n.dbk:124 msgid "How to get a given translation reviewed" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:124 +#: l10n.dbk:126 msgid "" "From time to time, individuals translate some texts in your package and will " "ask you for inclusion of the translation in the package. This can become " @@ -208,12 +211,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:134 +#: l10n.dbk:136 msgid "How to get a given translation updated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:136 +#: l10n.dbk:138 msgid "" "If you have some translations of a given text lying around, each time you " "update the original, you should ask the previous translator to update the " @@ -222,7 +225,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:142 +#: l10n.dbk:144 msgid "" "If the translator is unresponsive, you may ask for help on the corresponding " "l10n mailing list. If everything fails, don't forget to put a warning in " @@ -231,7 +234,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:148 +#: l10n.dbk:150 msgid "" "Avoid removing a translation completely because it is outdated. Old " "documentation is often better than no documentation at all for non-English " @@ -239,12 +242,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:155 +#: l10n.dbk:157 msgid "How to handle a bug report concerning a translation" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:157 +#. TODO: add the i18n tag to the bug? +#: l10n.dbk:159 msgid "" "The best solution may be to mark the bug as forwarded to upstream, and " "forward it to both the previous translator and his/her team (using the " @@ -252,12 +256,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:166 +#: l10n.dbk:169 msgid "I18N & L10N FAQ for translators" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:168 +#: l10n.dbk:171 msgid "" "While reading this, please keep in mind that there is no general procedure " "within Debian concerning these points, and that in any case, you should " @@ -265,12 +269,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:173 +#: l10n.dbk:176 msgid "How to help the translation effort" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:175 +#: l10n.dbk:178 msgid "" "Choose what you want to translate, make sure that nobody is already working " "on it (using your debian-l10n-XXX mailing list), translate it, get it " @@ -279,12 +283,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:183 +#: l10n.dbk:186 msgid "How to provide a translation for inclusion in a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:185 +#: l10n.dbk:188 msgid "" "Make sure your translation is correct (asking for review on your l10n " "mailing list) before providing it for inclusion. It will save time for " @@ -293,7 +297,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:191 +#: l10n.dbk:194 msgid "" "The best solution is to file a regular bug containing the translation " "against the package. Make sure to use the 'PATCH' tag, and to not use a " @@ -302,12 +306,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:201 +#: l10n.dbk:204 msgid "Best current practice concerning l10n" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:205 +#: l10n.dbk:208 msgid "" "As a maintainer, never edit the translations in any way (even to reformat " "the layout) without asking on the corresponding l10n mailing list. You risk " @@ -316,7 +320,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:213 +#: l10n.dbk:216 msgid "" "As a translator, if you find an error in the original text, make sure to " "report it. Translators are often the most attentive readers of a given " @@ -324,7 +328,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:220 +#: l10n.dbk:223 msgid "" "In any case, remember that the major issue with l10n is that it requires " "several people to cooperate, and that it is very easy to start a flamewar " @@ -335,8 +339,9 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:230 +#: l10n.dbk:233 msgid "" -"In any case, cooperation can only be achieved with <emphasis " -"role=\"strong\">mutual respect</emphasis>." +"In any case, cooperation can only be achieved with <emphasis role=\"strong" +"\">mutual respect</emphasis>." msgstr "" + diff --git a/po4a/fr/new-maintainer.po b/po4a/fr/new-maintainer.po index a48fcef..536a038 100644 --- a/po4a/fr/new-maintainer.po +++ b/po4a/fr/new-maintainer.po @@ -1,333 +1,196 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:07+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit" # type: Content of: <chapter><title> -#: new-maintainer.dbk:5 +#: new-maintainer.dbk:7 msgid "Applying to Become a Maintainer" -msgstr "" +msgstr "Devenir responsable Debian" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:7 +#: new-maintainer.dbk:9 msgid "Getting started" -msgstr "" +msgstr "Pour commencer" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:9 -msgid "" -"So, you've read all the documentation, you've gone through the <ulink " -"url=\"http://www.debian.org/doc/maint-guide/\">Debian New Maintainers' " -"Guide</ulink>, understand what everything in the <systemitem " -"role=\"package\">hello</systemitem> example package is for, and you're about " -"to Debianize your favorite piece of software. How do you actually become a " -"Debian developer so that your work can be incorporated into the Project?" -msgstr "" +#: new-maintainer.dbk:11 +msgid "So, you've read all the documentation, you've gone through the <ulink url=\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, understand what everything in the <systemitem role=\"package\">hello</systemitem> example package is for, and you're about to Debianize your favorite piece of software. How do you actually become a Debian developer so that your work can be incorporated into the Project?" +msgstr "Vous avez lu toute la documentation, vous avez examiné le <ulink url=\"&url-newmaint-guide;\">guide du nouveau responsable</ulink>, vous" +"comprenez l'intérêt de tout ce qui se trouve dans le paquet d'exemple" +"<systemitem role=\"package\">hello</systemitem> et vous vous apprêtez à mettre en paquet votre" +"logiciel préféré. Comment devenir responsable Debian et intégrer votre" +"travail au projet?" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:17 -msgid "" -"Firstly, subscribe to <email>debian-devel@lists.debian.org</email> if you " -"haven't already. Send the word <literal>subscribe</literal> in the " -"<emphasis>Subject</emphasis> of an email to " -"<email>debian-devel-REQUEST@lists.debian.org</email>. In case of problems, " -"contact the list administrator at " -"<email>listmaster@lists.debian.org</email>. More information on available " -"mailing lists can be found in <xref linkend=\"mailing-lists\"/> . " -"<email>debian-devel-announce@lists.debian.org</email> is another list which " -"is mandatory for anyone who wishes to follow Debian's development." -msgstr "" +#: new-maintainer.dbk:19 +msgid "Firstly, subscribe to &email-debian-devel; if you haven't already. Send the word <literal>subscribe</literal> in the <emphasis>Subject</emphasis> of an email to &email-debian-devel-req;. In case of problems, contact the list administrator at &email-listmaster;. More information on available mailing lists can be found in <xref linkend=\"mailing-lists\"/> . &email-debian-devel-announce; is another list which is mandatory for anyone who wishes to follow Debian's development." +msgstr "Si vous ne l'avez pas encore fait, commencez par vous inscrire à la" +"liste &email-debian-devel;. Pour cela, envoyez un courrier à l'adresse" +"&email-debian-devel-req; avec le mot <literal>subscribe</literal> dans la ligne" +"<emphasis>Objet</emphasis><footnote><para><emphasis>Subject</emphasis> en anglais</para></footnote>" +"de votre message. En cas de problème, contactez l'administrateur de la" +"liste &email-listmaster;. Vous trouverez plus d'informations dans la" +"section <xref linkend=\"mailing-lists\"/>. &email-debian-devel-announce; est une" +"autre liste incontournable pour qui veut suivre les développements de" +"Debian." # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:28 -msgid "" -"You should subscribe and lurk (that is, read without posting) for a bit " -"before doing any coding, and you should post about your intentions to work " -"on something to avoid duplicated effort." -msgstr "" +#: new-maintainer.dbk:29 +msgid "You should subscribe and lurk (that is, read without posting) for a bit before doing any coding, and you should post about your intentions to work on something to avoid duplicated effort." +msgstr "Vous suivrez les discussions de cette liste (sans poster) pendant" +"quelque temps avant de coder quoi que ce soit et vous informerez la" +"liste de votre intention de travailler sur quelque chose pour éviter de" +"dupliquer le travail d'un autre." # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:33 -msgid "" -"Another good list to subscribe to is " -"<email>debian-mentors@lists.debian.org</email>. See <xref " -"linkend=\"mentors\"/> for details. The IRC channel " -"<literal>#debian</literal> can also be helpful; see <xref " -"linkend=\"irc-channels\"/> ." -msgstr "" +#: new-maintainer.dbk:34 +msgid "Another good list to subscribe to is &email-debian-mentors;. See <xref linkend=\"mentors\"/> for details. The IRC channel <literal>#debian</literal> can also be helpful; see <xref linkend=\"irc-channels\"/> ." +msgstr "Une autre liste intéressante est &email-debian-mentors;. Voir la" +"section <xref linkend=\"mentors\"/> pour les détails. Le canal IRC" +"<literal>#debian</literal> pourra aussi être utile ; voir <xref linkend=\"irc-channels\"/>." # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:39 -msgid "" -"When you know how you want to contribute to Debian GNU/Linux, you should get " -"in contact with existing Debian maintainers who are working on similar " -"tasks. That way, you can learn from experienced developers. For example, " -"if you are interested in packaging existing software for Debian, you should " -"try to get a sponsor. A sponsor will work together with you on your package " -"and upload it to the Debian archive once they are happy with the packaging " -"work you have done. You can find a sponsor by mailing the " -"<email>debian-mentors@lists.debian.org</email> mailing list, describing your " -"package and yourself and asking for a sponsor (see <xref " -"linkend=\"sponsoring\"/> and <ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"for more information on sponsoring). On the other hand, if you are " -"interested in porting Debian to alternative architectures or kernels you can " -"subscribe to port specific mailing lists and ask there how to get started. " -"Finally, if you are interested in documentation or Quality Assurance (QA) " -"work you can join maintainers already working on these tasks and submit " -"patches and improvements." +#: new-maintainer.dbk:40 +msgid "When you know how you want to contribute to &debian-formal;, you should get in contact with existing Debian maintainers who are working on similar tasks. That way, you can learn from experienced developers. For example, if you are interested in packaging existing software for Debian, you should try to get a sponsor. A sponsor will work together with you on your package and upload it to the Debian archive once they are happy with the packaging work you have done. You can find a sponsor by mailing the &email-debian-mentors; mailing list, describing your package and yourself and asking for a sponsor (see <xref linkend=\"sponsoring\"/> and <ulink url=\"&url-mentors;\"></ulink> for more information on sponsoring). On the other hand, if you are interested in porting Debian to alternative architectures or kernels you can subscribe to port specific mailing lists and ask there how to get started. Finally, if you are interested in documentation or Quality Assurance (QA) work you can join maintainers already working on these tasks and submit patches and improvements." msgstr "" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:57 -msgid "" -"One pitfall could be a too-generic local part in your mailadress: Terms like " -"mail, admin, root, master should be avoided, please see <ulink " -"url=\"http://www.debian.org/MailingLists/\"></ulink> for details." +msgid "One pitfall could be a too-generic local part in your mailadress: Terms like mail, admin, root, master should be avoided, please see <ulink url=\"&url-debian-lists;\"></ulink> for details." msgstr "" # type: Content of: <chapter><section><title> #: new-maintainer.dbk:64 msgid "Debian mentors and sponsors" -msgstr "" +msgstr "Mentors et parrains Debian" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:66 -msgid "" -"The mailing list <email>debian-mentors@lists.debian.org</email> has been set " -"up for novice maintainers who seek help with initial packaging and other " -"developer-related issues. Every new developer is invited to subscribe to " -"that list (see <xref linkend=\"mailing-lists\"/> for details)." +msgid "The mailing list &email-debian-mentors; has been set up for novice maintainers who seek help with initial packaging and other developer-related issues. Every new developer is invited to subscribe to that list (see <xref linkend=\"mailing-lists\"/> for details)." msgstr "" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:72 -msgid "" -"Those who prefer one-on-one help (e.g., via private email) should also post " -"to that list and an experienced developer will volunteer to help." +msgid "Those who prefer one-on-one help (e.g., via private email) should also post to that list and an experienced developer will volunteer to help." msgstr "" +# +# +# +# # type: Content of: <chapter><section><para> +#. FIXME - out of order +#. Those who are seeking a +#. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/"></ulink>. #: new-maintainer.dbk:76 -msgid "" -"In addition, if you have some packages ready for inclusion in Debian, but " -"are waiting for your new maintainer application to go through, you might be " -"able find a sponsor to upload your package for you. Sponsors are people who " -"are official Debian Developers, and who are willing to criticize and upload " -"your packages for you. Please read the unofficial debian-mentors FAQ at " -"<ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"first." +msgid "In addition, if you have some packages ready for inclusion in Debian, but are waiting for your new maintainer application to go through, you might be able find a sponsor to upload your package for you. Sponsors are people who are official Debian Developers, and who are willing to criticize and upload your packages for you. Please read the unofficial debian-mentors FAQ at <ulink url=\"&url-mentors;\"></ulink> first." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:84 -msgid "" -"If you wish to be a mentor and/or sponsor, more information is available in " -"<xref linkend=\"newmaint\"/> ." +#: new-maintainer.dbk:89 +msgid "If you wish to be a mentor and/or sponsor, more information is available in <xref linkend=\"newmaint\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:90 +#: new-maintainer.dbk:95 msgid "Registering as a Debian developer" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:92 -msgid "" -"Before you decide to register with Debian GNU/Linux, you will need to read " -"all the information available at the <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink>. It describes in detail the preparations you have to do " -"before you can register to become a Debian developer. For example, before " -"you apply, you have to read the <ulink " -"url=\"http://www.debian.org/social_contract\">Debian Social " -"Contract</ulink>. Registering as a developer means that you agree with and " -"pledge to uphold the Debian Social Contract; it is very important that " -"maintainers are in accord with the essential ideas behind Debian GNU/Linux. " -"Reading the <ulink url=\"http://www.gnu.org/gnu/manifesto.html\">GNU " -"Manifesto</ulink> would also be a good idea." +#: new-maintainer.dbk:97 +msgid "Before you decide to register with &debian-formal;, you will need to read all the information available at the <ulink url=\"&url-newmaint;\">New Maintainer's Corner</ulink>. It describes in detail the preparations you have to do before you can register to become a Debian developer. For example, before you apply, you have to read the <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink>. Registering as a developer means that you agree with and pledge to uphold the Debian Social Contract; it is very important that maintainers are in accord with the essential ideas behind &debian-formal;. Reading the <ulink url=\"&url-gnu-manifesto;\">GNU Manifesto</ulink> would also be a good idea." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:105 -msgid "" -"The process of registering as a developer is a process of verifying your " -"identity and intentions, and checking your technical skills. As the number " -"of people working on Debian GNU/Linux has grown to over 900 and our systems " -"are used in several very important places, we have to be careful about being " -"compromised. Therefore, we need to verify new maintainers before we can " -"give them accounts on our servers and let them upload packages." +#: new-maintainer.dbk:111 +msgid "The process of registering as a developer is a process of verifying your identity and intentions, and checking your technical skills. As the number of people working on &debian-formal; has grown to over &number-of-maintainers; and our systems are used in several very important places, we have to be careful about being compromised. Therefore, we need to verify new maintainers before we can give them accounts on our servers and let them upload packages." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:113 -msgid "" -"Before you actually register you should have shown that you can do competent " -"work and will be a good contributor. You show this by submitting patches " -"through the Bug Tracking System and having a package sponsored by an " -"existing Debian Developer for a while. Also, we expect that contributors " -"are interested in the whole project and not just in maintaining their own " -"packages. If you can help other maintainers by providing further " -"information on a bug or even a patch, then do so!" +#: new-maintainer.dbk:120 +msgid "Before you actually register you should have shown that you can do competent work and will be a good contributor. You show this by submitting patches through the Bug Tracking System and having a package sponsored by an existing Debian Developer for a while. Also, we expect that contributors are interested in the whole project and not just in maintaining their own packages. If you can help other maintainers by providing further information on a bug or even a patch, then do so!" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:122 -msgid "" -"Registration requires that you are familiar with Debian's philosophy and " -"technical documentation. Furthermore, you need a GnuPG key which has been " -"signed by an existing Debian maintainer. If your GnuPG key is not signed " -"yet, you should try to meet a Debian Developer in person to get your key " -"signed. There's a <ulink url=\"http://nm.debian.org/gpg.php\">GnuPG Key " -"Signing Coordination page</ulink> which should help you find a Debian " -"Developer close to you. (If there is no Debian Developer close to you, " -"alternative ways to pass the ID check may be permitted as an absolute " -"exception on a case-by-case-basis. See the <ulink " -"url=\"http://www.debian.org/devel/join/nm-step2\">identification " -"page</ulink> for more information.)" +#: new-maintainer.dbk:129 +msgid "Registration requires that you are familiar with Debian's philosophy and technical documentation. Furthermore, you need a GnuPG key which has been signed by an existing Debian maintainer. If your GnuPG key is not signed yet, you should try to meet a Debian Developer in person to get your key signed. There's a <ulink url=\"&url-gpg-coord;\">GnuPG Key Signing Coordination page</ulink> which should help you find a Debian Developer close to you. (If there is no Debian Developer close to you, alternative ways to pass the ID check may be permitted as an absolute exception on a case-by-case-basis. See the <ulink url=\"&url-newmaint-id;\">identification page</ulink> for more information.)" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:135 -msgid "" -"If you do not have an OpenPGP key yet, generate one. Every developer needs " -"an OpenPGP key in order to sign and verify package uploads. You should read " -"the manual for the software you are using, since it has much important " -"information which is critical to its security. Many more security failures " -"are due to human error than to software failure or high-powered spy " -"techniques. See <xref linkend=\"key-maint\"/> for more information on " -"maintaining your public key." +#: new-maintainer.dbk:142 +msgid "If you do not have an OpenPGP key yet, generate one. Every developer needs an OpenPGP key in order to sign and verify package uploads. You should read the manual for the software you are using, since it has much important information which is critical to its security. Many more security failures are due to human error than to software failure or high-powered spy techniques. See <xref linkend=\"key-maint\"/> for more information on maintaining your public key." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:143 -msgid "" -"Debian uses the <command>GNU Privacy Guard</command> (package <systemitem " -"role=\"package\">gnupg</systemitem> version 1 or better) as its baseline " -"standard. You can use some other implementation of OpenPGP as well. Note " -"that OpenPGP is an open standard based on <ulink " -"url=\"http://www.rfc-editor.org/rfc/rfc2440.txt\">RFC 2440</ulink>." +#: new-maintainer.dbk:150 +msgid "Debian uses the <command>GNU Privacy Guard</command> (package <systemitem role=\"package\">gnupg</systemitem> version 1 or better) as its baseline standard. You can use some other implementation of OpenPGP as well. Note that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC 2440</ulink>." msgstr "" # type: Content of: <chapter><section><para><footnote> -#: new-maintainer.dbk:150 -msgid "" -"You need a version 4 key for use in Debian Development. Your key length " -"must be at least 1024 bits; there is no reason to use a smaller key, and " -"doing so would be much less secure. <footnote>" +#: new-maintainer.dbk:157 +msgid "You need a version 4 key for use in Debian Development. Your key length must be at least 1024 bits; there is no reason to use a smaller key, and doing so would be much less secure. <footnote>" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:152 -msgid "" -"Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC " -"2440. Version 4 is the key type that has always been created when using " -"GnuPG. PGP versions since 5.x also could create v4 keys, the other choice " -"having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)." +#: new-maintainer.dbk:159 +msgid "Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC 2440. Version 4 is the key type that has always been created when using GnuPG. PGP versions since 5.x also could create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys (also called legacy RSA by PGP)." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:156 -msgid "" -"Version 4 (primary) keys can either use the RSA or the DSA algorithms, so " -"this has nothing to do with GnuPG's question about which kind of key do you " -"want: (1) DSA and Elgamal, (2) DSA (sign only), (5) RSA (sign only). If " -"you don't have any special requirements just pick the default." +#: new-maintainer.dbk:163 +msgid "Version 4 (primary) keys can either use the RSA or the DSA algorithms, so this has nothing to do with GnuPG's question about which kind of key do you want: (1) DSA and Elgamal, (2) DSA (sign only), (5) RSA (sign only). If you don't have any special requirements just pick the default." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:160 -msgid "" -"The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) " -"key is to look at the fingerprint: Fingerprints of version 4 keys are the " -"SHA-1 hash of some key matieral, so they are 40 hex digits, usually grouped " -"in blocks of 4. Fingerprints of older key format versions used MD5 and are " -"generally shown in blocks of 2 hex digits. For example if your fingerprint " -"looks like " -"<literal>5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F</literal> then " -"it's a v4 key." +#: new-maintainer.dbk:167 +msgid "The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) key is to look at the fingerprint: Fingerprints of version 4 keys are the SHA-1 hash of some key matieral, so they are 40 hex digits, usually grouped in blocks of 4. Fingerprints of older key format versions used MD5 and are generally shown in blocks of 2 hex digits. For example if your fingerprint looks like <literal>5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F</literal> then it's a v4 key." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:167 -msgid "" -"Another possibility is to pipe the key into <command>pgpdump</command>, " -"which will say something like Public Key Packet - Ver 4." +#: new-maintainer.dbk:174 +msgid "Another possibility is to pipe the key into <command>pgpdump</command>, which will say something like Public Key Packet - Ver 4." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:169 -msgid "" -"Also note that your key must be self-signed (i.e. it has to sign all its " -"own user IDs; this prevents user ID tampering). All modern OpenPGP software " -"does that automatically, but if you have an older key you may have to " -"manually add those signatures." +#: new-maintainer.dbk:176 +msgid "Also note that your key must be self-signed (i.e. it has to sign all its own user IDs; this prevents user ID tampering). All modern OpenPGP software does that automatically, but if you have an older key you may have to manually add those signatures." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:175 -msgid "" -"If your public key isn't on a public key server such as " -"<literal>subkeys.pgp.net</literal>, please read the documentation available " -"at <ulink url=\"http://www.debian.org/devel/join/nm-step2\">NM Step 2: " -"Identification</ulink>. That document contains instructions on how to put " -"your key on the public key servers. The New Maintainer Group will put your " -"public key on the servers if it isn't already there." +#: new-maintainer.dbk:182 +msgid "If your public key isn't on a public key server such as &pgp-keyserv;, please read the documentation available at <ulink url=\"&url-newmaint-id;\">NM Step 2: Identification</ulink>. That document contains instructions on how to put your key on the public key servers. The New Maintainer Group will put your public key on the servers if it isn't already there." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:183 -msgid "" -"Some countries restrict the use of cryptographic software by their " -"citizens. This need not impede one's activities as a Debian package " -"maintainer however, as it may be perfectly legal to use cryptographic " -"products for authentication, rather than encryption purposes. If you live " -"in a country where use of cryptography even for authentication is forbidden " -"then please contact us so we can make special arrangements." +#: new-maintainer.dbk:190 +msgid "Some countries restrict the use of cryptographic software by their citizens. This need not impede one's activities as a Debian package maintainer however, as it may be perfectly legal to use cryptographic products for authentication, rather than encryption purposes. If you live in a country where use of cryptography even for authentication is forbidden then please contact us so we can make special arrangements." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:191 -msgid "" -"To apply as a new maintainer, you need an existing Debian Developer to " -"support your application (an <emphasis>advocate</emphasis>). After you have " -"contributed to Debian for a while, and you want to apply to become a " -"registered developer, an existing developer with whom you have worked over " -"the past months has to express their belief that you can contribute to " -"Debian successfully." +#: new-maintainer.dbk:198 +msgid "To apply as a new maintainer, you need an existing Debian Developer to support your application (an <emphasis>advocate</emphasis>). After you have contributed to Debian for a while, and you want to apply to become a registered developer, an existing developer with whom you have worked over the past months has to express their belief that you can contribute to Debian successfully." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:198 -msgid "" -"When you have found an advocate, have your GnuPG key signed and have already " -"contributed to Debian for a while, you're ready to apply. You can simply " -"register on our <ulink url=\"http://nm.debian.org/newnm.php\">application " -"page</ulink>. After you have signed up, your advocate has to confirm your " -"application. When your advocate has completed this step you will be " -"assigned an Application Manager who will go with you through the necessary " -"steps of the New Maintainer process. You can always check your status on " -"the <ulink url=\"http://nm.debian.org/\">applications status board</ulink>." +#: new-maintainer.dbk:205 +msgid "When you have found an advocate, have your GnuPG key signed and have already contributed to Debian for a while, you're ready to apply. You can simply register on our <ulink url=\"&url-newmaint-apply;\">application page</ulink>. After you have signed up, your advocate has to confirm your application. When your advocate has completed this step you will be assigned an Application Manager who will go with you through the necessary steps of the New Maintainer process. You can always check your status on the <ulink url=\"&url-newmaint-db;\">applications status board</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:208 -msgid "" -"For more details, please consult <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink> at the Debian web site. Make sure that you are familiar with " -"the necessary steps of the New Maintainer process before actually applying. " -"If you are well prepared, you can save a lot of time later on." +#: new-maintainer.dbk:215 +msgid "For more details, please consult <ulink url=\"&url-newmaint;\">New Maintainer's Corner</ulink> at the Debian web site. Make sure that you are familiar with the necessary steps of the New Maintainer process before actually applying. If you are well prepared, you can save a lot of time later on." msgstr "" + diff --git a/po4a/fr/pkgs.po b/po4a/fr/pkgs.po index 994e65d..155efa5 100644 --- a/po4a/fr/pkgs.po +++ b/po4a/fr/pkgs.po @@ -1,50 +1,52 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:15+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: pkgs.dbk:5 +#: pkgs.dbk:7 msgid "Managing Packages" -msgstr "" +msgstr "Gestion des paquets" # type: Content of: <chapter><para> -#: pkgs.dbk:7 +#: pkgs.dbk:9 msgid "" "This chapter contains information related to creating, uploading, " "maintaining, and porting packages." -msgstr "" +msgstr "Ce chapitre contient des informations relatives à la création, l'envoi," +"la maintenance et le portage des paquets." # type: Content of: <chapter><section><title> -#: pkgs.dbk:11 +#: pkgs.dbk:13 msgid "New packages" -msgstr "" +msgstr "Nouveaux paquets" # type: Content of: <chapter><section><para> -#: pkgs.dbk:13 +#: pkgs.dbk:15 msgid "" "If you want to create a new package for the Debian distribution, you should " -"first check the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " +"first check the <ulink url=\"&url-wnpp;\">Work-Needing and Prospective " "Packages (WNPP)</ulink> list. Checking the WNPP list ensures that no one is " "already working on packaging that software, and that effort is not " -"duplicated. Read the <ulink url=\"http://www.debian.org/devel/wnpp/\">WNPP " -"web pages</ulink> for more information." +"duplicated. Read the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink> for " +"more information." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:21 +#: pkgs.dbk:23 msgid "" "Assuming no one else is already working on your prospective package, you " "must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the " @@ -55,31 +57,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:29 +#: pkgs.dbk:31 msgid "" -"You should set the subject of the bug to ``ITP: " -"<replaceable>foo</replaceable> -- <replaceable>short " -"description</replaceable>'', substituting the name of the new package for " -"<replaceable>foo</replaceable>. The severity of the bug report must be set " -"to <emphasis>wishlist</emphasis>. If you feel it's necessary, send a copy " -"to <email>debian-devel@lists.debian.org</email> by putting the address in " -"the <literal>X-Debbugs-CC:</literal> header of the message (no, don't use " -"<literal>CC:</literal>, because that way the message's subject won't " -"indicate the bug number)." +"You should set the subject of the bug to ``ITP: <replaceable>foo</" +"replaceable> -- <replaceable>short description</replaceable>'', substituting " +"the name of the new package for <replaceable>foo</replaceable>. The " +"severity of the bug report must be set to <emphasis>wishlist</emphasis>. If " +"you feel it's necessary, send a copy to &email-debian-devel; by putting the " +"address in the <literal>X-Debbugs-CC:</literal> header of the message (no, " +"don't use <literal>CC:</literal>, because that way the message's subject " +"won't indicate the bug number)." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:39 +#: pkgs.dbk:41 msgid "" -"Please include a <literal>Closes: " -"bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the " -"new package in order for the bug report to be automatically closed once the " -"new package is installed in the archive (see <xref " -"linkend=\"upload-bugfix\"/> )." +"Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></" +"literal> entry in the changelog of the new package in order for the bug " +"report to be automatically closed once the new package is installed in the " +"archive (see <xref linkend=\"upload-bugfix\"/> )." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:45 +#: pkgs.dbk:47 msgid "" "When closing security bugs include CVE numbers as well as the Closes: " "#nnnnn. This is useful for the security team to track vulnerabilities. If " @@ -90,14 +90,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:53 +#: pkgs.dbk:55 msgid "" "There are a number of reasons why we ask maintainers to announce their " "intentions:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:59 +#: pkgs.dbk:61 msgid "" "It helps the (potentially new) maintainer to tap into the experience of " "people on the list, and lets them know if anyone else is working on it " @@ -105,14 +105,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:65 +#: pkgs.dbk:67 msgid "" "It lets other people thinking about working on the package know that there " "already is a volunteer, so efforts may be shared." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:71 +#: pkgs.dbk:73 msgid "" "It lets the rest of the maintainers know more about the package than the one " "line description and the usual changelog entry ``Initial release'' that gets " @@ -120,98 +120,96 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:78 +#: pkgs.dbk:80 msgid "" "It is helpful to the people who live off unstable (and form our first line " "of testers). We should encourage these people." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:84 +#: pkgs.dbk:86 msgid "" "The announcements give maintainers and other interested parties a better " "feel of what is going on, and what is new, in the project." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:90 +#: pkgs.dbk:92 msgid "" -"Please see <ulink " -"url=\"http://ftp-master.debian.org/REJECT-FAQ.html\"></ulink> for common " -"rejection reasons for a new package." +"Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> " +"for common rejection reasons for a new package." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:96 +#: pkgs.dbk:98 msgid "Recording changes in the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:98 +#: pkgs.dbk:100 msgid "" "Changes that you make to the package need to be recorded in the " "<filename>debian/changelog</filename>. These changes should provide a " "concise description of what was changed, why (if it's in doubt), and note if " "any bugs were closed. They also record when the package was completed. " -"This file will be installed in " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.Debian.gz</filename>, " -"or " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</filename> " -"for native packages." +"This file will be installed in <filename>/usr/share/doc/" +"<replaceable>package</replaceable>/changelog.Debian.gz</filename>, or " +"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</" +"filename> for native packages." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:109 +#: pkgs.dbk:111 msgid "" "The <filename>debian/changelog</filename> file conforms to a certain " "structure, with a number of different fields. One field of note, the " -"<emphasis>distribution</emphasis>, is described in <xref " -"linkend=\"distribution\"/> . More information about the structure of this " -"file can be found in the Debian Policy section titled " -"<filename>debian/changelog</filename>." +"<emphasis>distribution</emphasis>, is described in <xref linkend=" +"\"distribution\"/> . More information about the structure of this file can " +"be found in the Debian Policy section titled <filename>debian/changelog</" +"filename>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:117 +#: pkgs.dbk:119 msgid "" "Changelog entries can be used to automatically close Debian bugs when the " -"package is installed into the archive. See <xref " -"linkend=\"upload-bugfix\"/> ." +"package is installed into the archive. See <xref linkend=\"upload-bugfix\"/" +"> ." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:121 +#: pkgs.dbk:123 msgid "" "It is conventional that the changelog entry of a package that contains a new " "upstream version of the software looks like this:" msgstr "" # type: Content of: <chapter><section><screen> -#: pkgs.dbk:125 +#: pkgs.dbk:127 #, no-wrap msgid "* new upstream version" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:128 +#: pkgs.dbk:130 msgid "" "There are tools to help you create entries and finalize the " -"<filename>changelog</filename> for release — see <xref " -"linkend=\"devscripts\"/> and <xref linkend=\"dpkg-dev-el\"/> ." +"<filename>changelog</filename> for release — see <xref linkend=\"devscripts" +"\"/> and <xref linkend=\"dpkg-dev-el\"/> ." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:133 +#: pkgs.dbk:135 msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:138 +#: pkgs.dbk:140 msgid "Testing the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:140 +#: pkgs.dbk:142 msgid "" "Before you upload your package, you should do basic testing on it. At a " "minimum, you should try the following activities (you'll need to have an " @@ -219,7 +217,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:147 +#: pkgs.dbk:149 msgid "" "Install the package and make sure the software works, or upgrade the package " "from an older version to your new version if a Debian package for it already " @@ -227,53 +225,52 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:154 +#: pkgs.dbk:156 msgid "" "Run <command>lintian</command> over the package. You can run " "<command>lintian</command> as follows: <literal>lintian -v " "<replaceable>package-version</replaceable>.changes</literal>. This will " "check the source package as well as the binary package. If you don't " "understand the output that <command>lintian</command> generates, try adding " -"the <literal>-i</literal> switch, which will cause " -"<command>lintian</command> to output a very verbose description of the " -"problem." +"the <literal>-i</literal> switch, which will cause <command>lintian</" +"command> to output a very verbose description of the problem." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:163 +#: pkgs.dbk:165 msgid "" "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes " "lintian to emit errors (they will start with <literal>E</literal>)." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:167 +#: pkgs.dbk:169 msgid "" -"For more information on <command>lintian</command>, see <xref " -"linkend=\"lintian\"/> ." +"For more information on <command>lintian</command>, see <xref linkend=" +"\"lintian\"/> ." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:173 +#: pkgs.dbk:175 msgid "" "Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older " "version, if one exists." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:179 +#: pkgs.dbk:181 msgid "" "Downgrade the package to the previous version (if one exists) — this tests " "the <filename>postrm</filename> and <filename>prerm</filename> scripts." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:185 +#: pkgs.dbk:187 msgid "Remove the package, then reinstall it." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:190 +#: pkgs.dbk:192 msgid "" "Copy the source package in a different directory and try unpacking it and " "rebuilding it. This tests if the package relies on existing files outside " @@ -282,42 +279,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:200 +#: pkgs.dbk:202 msgid "Layout of the source package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:202 +#: pkgs.dbk:204 msgid "There are two types of Debian source packages:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:207 +#: pkgs.dbk:209 msgid "" "the so-called <emphasis>native</emphasis> packages, where there is no " "distinction between the original sources and the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:213 +#: pkgs.dbk:215 msgid "" "the (more common) packages where there's an original source tarball file " "accompanied by another file that contains the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:219 +#: pkgs.dbk:221 msgid "" "For the native packages, the source package includes a Debian source control " -"file (<literal>.dsc</literal>) and the source tarball " -"(<literal>.tar.gz</literal>). A source package of a non-native package " -"includes a Debian source control file, the original source tarball " -"(<literal>.orig.tar.gz</literal>) and the Debian patches " -"(<literal>.diff.gz</literal>)." +"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.gz</" +"literal>). A source package of a non-native package includes a Debian " +"source control file, the original source tarball (<literal>.orig.tar.gz</" +"literal>) and the Debian patches (<literal>.diff.gz</literal>)." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:227 +#: pkgs.dbk:229 msgid "" "Whether a package is native or not is determined when it is built by " "<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle> " @@ -326,38 +322,37 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:233 +#: pkgs.dbk:235 msgid "" "The first time a version is uploaded which corresponds to a particular " "upstream version, the original source tar file should be uploaded and " "included in the <filename>.changes</filename> file. Subsequently, this very " -"same tar file should be used to build the new diffs and " -"<filename>.dsc</filename> files, and will not need to be re-uploaded." +"same tar file should be used to build the new diffs and <filename>.dsc</" +"filename> files, and will not need to be re-uploaded." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:240 +#: pkgs.dbk:242 msgid "" -"By default, <command>dpkg-genchanges</command> and " -"<command>dpkg-buildpackage</command> will include the original source tar " -"file if and only if the Debian revision part of the source version number is " -"0 or 1, indicating a new upstream version. This behavior may be modified by " -"using <literal>-sa</literal> to always include it or <literal>-sd</literal> " -"to always leave it out." +"By default, <command>dpkg-genchanges</command> and <command>dpkg-" +"buildpackage</command> will include the original source tar file if and only " +"if the Debian revision part of the source version number is 0 or 1, " +"indicating a new upstream version. This behavior may be modified by using " +"<literal>-sa</literal> to always include it or <literal>-sd</literal> to " +"always leave it out." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:248 +#: pkgs.dbk:250 msgid "" -"If no original source is included in the upload, the original source " -"tar-file used by <command>dpkg-source</command> when constructing the " -"<filename>.dsc</filename> file and diff to be uploaded " -"<emphasis>must</emphasis> be byte-for-byte identical with the one already in " -"the archive." +"If no original source is included in the upload, the original source tar-" +"file used by <command>dpkg-source</command> when constructing the <filename>." +"dsc</filename> file and diff to be uploaded <emphasis>must</emphasis> be " +"byte-for-byte identical with the one already in the archive." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:255 +#: pkgs.dbk:257 msgid "" "Please notice that, in non-native packages, permissions on files that are " "not present in the .orig.tar.gz will not be preserved, as diff does not " @@ -365,12 +360,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:262 +#: pkgs.dbk:264 msgid "Picking a distribution" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:264 +#: pkgs.dbk:266 msgid "" "Each upload needs to specify which distribution the package is intended " "for. The package build process extracts this information from the first " @@ -380,7 +375,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:270 +#: pkgs.dbk:272 msgid "" "There are several possible values for this field: `stable', `unstable', " "`testing-proposed-updates' and `experimental'. Normally, packages are " @@ -388,7 +383,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:275 +#: pkgs.dbk:277 msgid "" "Actually, there are two other possible distributions: `stable-security' and " "`testing-security', but read <xref linkend=\"bug-security\"/> for more " @@ -396,19 +391,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:280 +#: pkgs.dbk:282 msgid "" "It is not possible to upload a package into several distributions at the " "same time." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:284 +#: pkgs.dbk:286 msgid "Special case: uploads to the <emphasis>stable</emphasis> distribution" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:286 +#: pkgs.dbk:288 msgid "" "Uploading to <emphasis>stable</emphasis> means that the package will " "transfered to the <emphasis>p-u-new</emphasis>-queue for review by the " @@ -419,7 +414,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:294 +#: pkgs.dbk:296 msgid "" "Extra care should be taken when uploading to <emphasis>stable</emphasis>. " "Basically, a package should only be uploaded to stable if one of the " @@ -427,22 +422,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:301 +#: pkgs.dbk:303 msgid "a truly critical functionality problem" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:306 +#: pkgs.dbk:308 msgid "the package becomes uninstallable" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:311 +#: pkgs.dbk:313 msgid "a released architecture lacks the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:316 +#: pkgs.dbk:318 msgid "" "In the past, uploads to <emphasis>stable</emphasis> were used to address " "security problems as well. However, this practice is deprecated, as uploads " @@ -453,84 +448,81 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:324 +#: pkgs.dbk:326 msgid "" "Changing anything else in the package that isn't important is discouraged, " "because even trivial fixes can cause bugs later on." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:328 +#: pkgs.dbk:330 msgid "" "Packages uploaded to <emphasis>stable</emphasis> need to be compiled on " "systems running <emphasis>stable</emphasis>, so that their dependencies are " -"limited to the libraries (and other packages) available in " -"<emphasis>stable</emphasis>; for example, a package uploaded to " -"<emphasis>stable</emphasis> that depends on a library package that only " -"exists in unstable will be rejected. Making changes to dependencies of " -"other packages (by messing with <literal>Provides</literal> or shlibs " -"files), possibly making those other packages uninstallable, is strongly " -"discouraged." +"limited to the libraries (and other packages) available in <emphasis>stable</" +"emphasis>; for example, a package uploaded to <emphasis>stable</emphasis> " +"that depends on a library package that only exists in unstable will be " +"rejected. Making changes to dependencies of other packages (by messing with " +"<literal>Provides</literal> or shlibs files), possibly making those other " +"packages uninstallable, is strongly discouraged." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:338 +#: pkgs.dbk:340 msgid "" -"The Release Team (which can be reached at " -"<email>debian-release@lists.debian.org</email>) will regularly evaluate the " -"uploads To <emphasis>stable-proposed-updates</emphasis> and decide if your " -"package can be included in <emphasis>stable</emphasis>. Please be clear " -"(and verbose, if necessary) in your changelog entries for uploads to " -"<emphasis>stable</emphasis>, because otherwise the package won't be " -"considered for inclusion." +"The Release Team (which can be reached at &email-debian-release;) will " +"regularly evaluate the uploads To <emphasis>stable-proposed-updates</" +"emphasis> and decide if your package can be included in <emphasis>stable</" +"emphasis>. Please be clear (and verbose, if necessary) in your changelog " +"entries for uploads to <emphasis>stable</emphasis>, because otherwise the " +"package won't be considered for inclusion." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:347 +#: pkgs.dbk:349 msgid "" "It's best practice to speak with the stable release manager " -"<emphasis>before</emphasis> uploading to " -"<emphasis>stable</emphasis>/<emphasis>stable-proposed-updates</emphasis>, so " -"that the uploaded package fits the needs of the next point release." +"<emphasis>before</emphasis> uploading to <emphasis>stable</emphasis>/" +"<emphasis>stable-proposed-updates</emphasis>, so that the uploaded package " +"fits the needs of the next point release." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:355 +#: pkgs.dbk:357 msgid "" -"Special case: uploads to " -"<emphasis>testing/testing-proposed-updates</emphasis>" +"Special case: uploads to <emphasis>testing/testing-proposed-updates</" +"emphasis>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:357 +#: pkgs.dbk:359 msgid "" -"Please see the information in the <link linkend=\"t-p-u\">testing " -"section</link> for details." +"Please see the information in the <link linkend=\"t-p-u\">testing section</" +"link> for details." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:365 +#: pkgs.dbk:367 msgid "Uploading a package" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:367 +#: pkgs.dbk:369 msgid "Uploading to <literal>ftp-master</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:369 +#: pkgs.dbk:371 msgid "" "To upload a package, you should upload the files (including the signed " -"changes and dsc-file) with anonymous ftp to " -"<literal>ftp-master.debian.org</literal> in the directory <ulink " -"url=\"ftp://ftp-master.debian.org/pub/UploadQueue/\">/pub/UploadQueue/</ulink>. " -"To get the files processed there, they need to be signed with a key in the " -"debian keyring." +"changes and dsc-file) with anonymous ftp to <literal>&ftp-master-host;</" +"literal> in the directory <ulink url=\"ftp://&ftp-master-host;&upload-queue;" +"\">&upload-queue;</ulink>. To get the files processed there, they need to " +"be signed with a key in the debian keyring." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:377 +#: pkgs.dbk:379 msgid "" "Please note that you should transfer the changes file last. Otherwise, your " "upload may be rejected because the archive maintenance software will parse " @@ -538,7 +530,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:382 +#: pkgs.dbk:384 msgid "" "You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref " "linkend=\"dput\"/> useful when uploading packages. These handy programs " @@ -546,45 +538,43 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:387 +#: pkgs.dbk:389 msgid "" "For removing packages, please see the README file in that ftp directory, and " "the Debian package <xref linkend=\"dcut\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:393 +#: pkgs.dbk:395 msgid "Uploading to <literal>non-US</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:395 +#: pkgs.dbk:397 msgid "" -"<emphasis>Note:</emphasis> non-us was discontinued with the release of " -"sarge." +"<emphasis>Note:</emphasis> non-us was discontinued with the release of sarge." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:400 +#: pkgs.dbk:402 msgid "Delayed uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:402 +#: pkgs.dbk:404 msgid "" "Delayed uploads are done for the moment via the delayed queue at gluck. The " -"upload-directory is " -"<literal>gluck:~tfheen/DELAYED/[012345678]-day</literal>. 0-day is uploaded " -"multiple times per day to ftp-master." +"upload-directory is <literal>gluck:~tfheen/DELAYED/[012345678]-day</" +"literal>. 0-day is uploaded multiple times per day to ftp-master." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:407 +#: pkgs.dbk:409 msgid "With a fairly recent dput, this section" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:410 +#: pkgs.dbk:412 #, no-wrap msgid "" "[tfheen_delayed]\n" @@ -594,64 +584,64 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:416 +#: pkgs.dbk:418 msgid "in ~/.dput.cf should work fine for uploading to the DELAYED queue." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:419 +#: pkgs.dbk:421 msgid "" -"<emphasis>Note:</emphasis> Since this upload queue goes to " -"<literal>ftp-master</literal>, the prescription found in <xref " -"linkend=\"upload-ftp-master\"/> applies here as well." +"<emphasis>Note:</emphasis> Since this upload queue goes to <literal>ftp-" +"master</literal>, the prescription found in <xref linkend=\"upload-ftp-master" +"\"/> applies here as well." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:426 +#: pkgs.dbk:428 msgid "Security uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:428 +#: pkgs.dbk:430 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " "authorization from the security team. If the package does not exactly meet " "the team's requirements, it will cause many problems and delays in dealing " -"with the unwanted upload. For details, please see section <xref " -"linkend=\"bug-security\"/> ." +"with the unwanted upload. For details, please see section <xref linkend=" +"\"bug-security\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:438 +#: pkgs.dbk:440 msgid "Other upload queues" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:440 +#: pkgs.dbk:442 msgid "" "The scp queues on ftp-master, and security are mostly unusable due to the " "login restrictions on those hosts." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:444 +#: pkgs.dbk:446 msgid "" "The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are " "currently down. Work is underway to resurrect them." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:448 +#: pkgs.dbk:450 msgid "" "The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and " "ftp.chiark.greenend.org.uk are down permanently, and will not be " -"resurrected. The queue in Japan will be replaced with a new queue on " -"hp.debian.or.jp some day." +"resurrected. The queue in Japan will be replaced with a new queue on hp." +"debian.or.jp some day." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:454 +#: pkgs.dbk:456 msgid "" "For the time being, the anonymous ftp queue on auric.debian.org (the former " "ftp-master) works, but it is deprecated and will be removed at some point in " @@ -659,12 +649,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:461 +#: pkgs.dbk:463 msgid "Notification that a new package has been installed" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:463 +#: pkgs.dbk:465 msgid "" "The Debian archive maintainers are responsible for handling package " "uploads. For the most part, uploads are automatically handled on a daily " @@ -677,7 +667,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:472 +#: pkgs.dbk:474 msgid "" "In any case, you will receive an email notification indicating that the " "package has been added to the archive, which also indicates which bugs will " @@ -686,7 +676,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:478 +#: pkgs.dbk:480 msgid "" "The installation notification also includes information on what section the " "package was inserted into. If there is a disparity, you will receive a " @@ -694,135 +684,131 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:483 +#: pkgs.dbk:485 msgid "" "Note that if you upload via queues, the queue daemon software will also send " "you a notification by email." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:491 +#: pkgs.dbk:493 msgid "Specifying the package section, subsection and priority" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:493 +#: pkgs.dbk:495 msgid "" "The <filename>debian/control</filename> file's <literal>Section</literal> " "and <literal>Priority</literal> fields do not actually specify where the " "file will be placed in the archive, nor its priority. In order to retain " "the overall integrity of the archive, it is the archive maintainers who have " -"control over these fields. The values in the " -"<filename>debian/control</filename> file are actually just hints." +"control over these fields. The values in the <filename>debian/control</" +"filename> file are actually just hints." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:501 +#: pkgs.dbk:503 msgid "" "The archive maintainers keep track of the canonical sections and priorities " "for packages in the <emphasis>override file</emphasis>. If there is a " "disparity between the <emphasis>override file</emphasis> and the package's " "fields as indicated in <filename>debian/control</filename>, then you will " "receive an email noting the divergence when the package is installed into " -"the archive. You can either correct your " -"<filename>debian/control</filename> file for your next upload, or else you " -"may wish to make a change in the <emphasis>override file</emphasis>." +"the archive. You can either correct your <filename>debian/control</" +"filename> file for your next upload, or else you may wish to make a change " +"in the <emphasis>override file</emphasis>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:511 +#: pkgs.dbk:513 msgid "" "To alter the actual section that a package is put in, you need to first make " "sure that the <filename>debian/control</filename> file in your package is " -"accurate. Next, send an email <email>override-change@debian.org</email> or " -"submit a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem> requesting that the section or " -"priority for your package be changed from the old section or priority to the " -"new one. Be sure to explain your reasoning." +"accurate. Next, send an email &email-override; or submit a bug against " +"<systemitem role=\"package\">ftp.debian.org</systemitem> requesting that the " +"section or priority for your package be changed from the old section or " +"priority to the new one. Be sure to explain your reasoning." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:519 +#: pkgs.dbk:521 msgid "" "For more information about <emphasis>override files</emphasis>, see " "<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> and <ulink " -"url=\"http://www.debian.org/Bugs/Developer#maintincorrect\"></ulink>." +"<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;" +"#maintincorrect\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:525 +#: pkgs.dbk:527 msgid "" "Note that the <literal>Section</literal> field describes both the section as " -"well as the subsection, which are described in <xref " -"linkend=\"archive-sections\"/> . If the section is main, it should be " -"omitted. The list of allowable subsections can be found in <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections\"></ulink>." +"well as the subsection, which are described in <xref linkend=\"archive-" +"sections\"/> . If the section is main, it should be omitted. The list of " +"allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-" +"archive.html#s-subsections\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:534 +#: pkgs.dbk:536 msgid "Handling bugs" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:536 +#: pkgs.dbk:538 msgid "" -"Every developer has to be able to work with the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>. This " -"includes knowing how to file bug reports properly (see <xref " -"linkend=\"submit-bug\"/> ), how to update them and reorder them, and how to " -"process and close them." +"Every developer has to be able to work with the Debian <ulink url=\"&url-bts;" +"\">bug tracking system</ulink>. This includes knowing how to file bug " +"reports properly (see <xref linkend=\"submit-bug\"/> ), how to update them " +"and reorder them, and how to process and close them." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:542 +#: pkgs.dbk:544 msgid "" -"The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for " -"developers</ulink>. This includes closing bugs, sending followup messages, " -"assigning severities and tags, marking bugs as forwarded, and other issues." +"The bug tracking system's features are described in the <ulink url=\"&url-" +"bts-devel;\">BTS documentation for developers</ulink>. This includes " +"closing bugs, sending followup messages, assigning severities and tags, " +"marking bugs as forwarded, and other issues." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:548 +#: pkgs.dbk:550 msgid "" "Operations such as reassigning bugs to other packages, merging separate bug " "reports about the same issue, or reopening bugs when they are prematurely " "closed, are handled using the so-called control mail server. All of the " -"commands available on this server are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " -"documentation</ulink>." +"commands available on this server are described in the <ulink url=\"&url-bts-" +"control;\">BTS control server documentation</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:556 +#: pkgs.dbk:558 msgid "Monitoring bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:558 +#: pkgs.dbk:560 msgid "" "If you want to be a good maintainer, you should periodically check the " -"<ulink url=\"http://www.debian.org/Bugs/\">Debian bug tracking system " -"(BTS)</ulink> for your packages. The BTS contains all the open bugs against " -"your packages. You can check them by browsing this page: " -"<literal>http://bugs.debian.org/<replaceable>yourlogin</replaceable>@debian.org</literal>." +"<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your " +"packages. The BTS contains all the open bugs against your packages. You " +"can check them by browsing this page: <literal>http://&bugs-host;/" +"<replaceable>yourlogin</replaceable>@debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:565 +#: pkgs.dbk:567 msgid "" -"Maintainers interact with the BTS via email addresses at " -"<literal>bugs.debian.org</literal>. Documentation on available commands can " -"be found at <ulink url=\"http://www.debian.org/Bugs/\"></ulink>, or, if you " -"have installed the <systemitem role=\"package\">doc-debian</systemitem> " -"package, you can look at the local files " -"<filename>/usr/share/doc/debian/bug-*</filename>." +"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;" +"</literal>. Documentation on available commands can be found at <ulink url=" +"\"&url-bts;\"></ulink>, or, if you have installed the <systemitem role=" +"\"package\">doc-debian</systemitem> package, you can look at the local files " +"&file-bts-docs;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:572 +#: pkgs.dbk:574 msgid "" "Some find it useful to get periodic reports on open bugs. You can add a " "cron job such as the following if you want to get a weekly email outlining " @@ -830,86 +816,83 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:577 +#: pkgs.dbk:579 #, no-wrap msgid "" "# ask for weekly reports of bugs in my packages\n" -"0 17 * * fri echo index maint <replaceable>address</replaceable> | mail " -"request@bugs.debian.org" +"&cron-bug-report;" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:581 +#: pkgs.dbk:583 msgid "" "Replace <replaceable>address</replaceable> with your official Debian " "maintainer address." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:587 +#: pkgs.dbk:589 msgid "Responding to bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:589 +#: pkgs.dbk:591 msgid "" "When responding to bugs, make sure that any discussion you have about bugs " -"is sent both to the original submitter of the bug, and to the bug itself " -"(e.g., <email>123@bugs.debian.org</email>). If you're writing a new mail " -"and you don't remember the submitter email address, you can use the " -"<email>123-submitter@bugs.debian.org</email> email to contact the submitter " -"<emphasis>and</emphasis> to record your mail within the bug log (that means " -"you don't need to send a copy of the mail to " -"<email>123@bugs.debian.org</email>)." +"is sent both to the original submitter of the bug, and to the bug itself (e." +"g., <email>123@&bugs-host;</email>). If you're writing a new mail and you " +"don't remember the submitter email address, you can use the <email>123-" +"submitter@&bugs-host;</email> email to contact the submitter <emphasis>and</" +"emphasis> to record your mail within the bug log (that means you don't need " +"to send a copy of the mail to <email>123@&bugs-host;</email>)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:598 +#: pkgs.dbk:600 msgid "" "If you get a bug which mentions FTBFS, this means Fails to build from " "source. Porters frequently use this acronym." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:602 +#: pkgs.dbk:604 msgid "" "Once you've dealt with a bug report (e.g. fixed it), mark it as " "<emphasis>done</emphasis> (close it) by sending an explanation message to " -"<email>123-done@bugs.debian.org</email>. If you're fixing a bug by changing " -"and uploading the package, you can automate bug closing as described in " -"<xref linkend=\"upload-bugfix\"/> ." +"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and " +"uploading the package, you can automate bug closing as described in <xref " +"linkend=\"upload-bugfix\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:609 +#: pkgs.dbk:611 msgid "" "You should <emphasis>never</emphasis> close bugs via the bug server " -"<literal>close</literal> command sent to " -"<email>control@bugs.debian.org</email>. If you do so, the original " -"submitter will not receive any information about why the bug was closed." +"<literal>close</literal> command sent to &email-bts-control;. If you do so, " +"the original submitter will not receive any information about why the bug " +"was closed." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:617 +#: pkgs.dbk:619 msgid "Bug housekeeping" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:619 +#: pkgs.dbk:621 msgid "" "As a package maintainer, you will often find bugs in other packages or have " "bugs reported against your packages which are actually bugs in other " "packages. The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for Debian " -"developers</ulink>. Operations such as reassigning, merging, and tagging " -"bug reports are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " +"url=\"&url-bts-devel;\">BTS documentation for Debian developers</ulink>. " +"Operations such as reassigning, merging, and tagging bug reports are " +"described in the <ulink url=\"&url-bts-control;\">BTS control server " "documentation</ulink>. This section contains some guidelines for managing " "your own bugs, based on the collective Debian developer experience." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:630 +#: pkgs.dbk:632 msgid "" "Filing bugs for problems that you find in other packages is one of the civic " "obligations of maintainership, see <xref linkend=\"submit-bug\"/> for " @@ -918,12 +901,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:635 +#: pkgs.dbk:637 msgid "Here's a list of steps that you may follow to handle a bug report:" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:640 +#: pkgs.dbk:642 msgid "" "Decide whether the report corresponds to a real bug or not. Sometimes users " "are just calling a program in the wrong way because they haven't read the " @@ -936,7 +919,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:650 +#: pkgs.dbk:652 msgid "" "If the bug submitter disagrees with your decision to close the bug, they may " "reopen it until you find an agreement on how to handle it. If you don't " @@ -946,24 +929,23 @@ msgid "" "decision of the technical committee by reassigning the bug to <systemitem " "role=\"package\">tech-ctte</systemitem> (you may use the clone command of " "the BTS if you wish to keep it reported against your package). Before doing " -"so, please read the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">recommended procedure</ulink>." +"so, please read the <ulink url=\"&url-tech-ctte;\">recommended procedure</" +"ulink>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:664 +#: pkgs.dbk:666 msgid "" "If the bug is real but it's caused by another package, just reassign the bug " "to the right package. If you don't know which package it should be " -"reassigned to, you should ask for help on <link " -"linkend=\"irc-channels\">IRC</link> or on " -"<email>debian-devel@lists.debian.org</email>. Please make sure that the " +"reassigned to, you should ask for help on <link linkend=\"irc-channels" +"\">IRC</link> or on &email-debian-devel;. Please make sure that the " "maintainer(s) of the package the bug is reassigned to know why you " "reassigned it." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:672 +#: pkgs.dbk:674 msgid "" "Sometimes you also have to adjust the severity of the bug so that it matches " "our definition of the severity. That's because people tend to inflate the " @@ -973,7 +955,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:680 +#: pkgs.dbk:682 msgid "" "If the bug is real but the same problem has already been reported by someone " "else, then the two relevant bug reports should be merged into one using the " @@ -985,7 +967,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:691 +#: pkgs.dbk:693 msgid "" "The bug submitter may have forgotten to provide some information, in which " "case you have to ask them for the required information. You may use the " @@ -997,22 +979,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:702 +#: pkgs.dbk:704 msgid "" "If the bug is related to the packaging, you just fix it. If you are not " "able to fix it yourself, then tag the bug as <literal>help</literal>. You " -"can also ask for help on <email>debian-devel@lists.debian.org</email> or " -"<email>debian-qa@lists.debian.org</email>. If it's an upstream problem, you " -"have to forward it to the upstream author. Forwarding a bug is not enough, " -"you have to check at each release if the bug has been fixed or not. If it " -"has, you just close it, otherwise you have to remind the author about it. " -"If you have the required skills you can prepare a patch that fixes the bug " -"and send it to the author at the same time. Make sure to send the patch to " -"the BTS and to tag the bug as <literal>patch</literal>." +"can also ask for help on &email-debian-devel; or &email-debian-qa;. If it's " +"an upstream problem, you have to forward it to the upstream author. " +"Forwarding a bug is not enough, you have to check at each release if the bug " +"has been fixed or not. If it has, you just close it, otherwise you have to " +"remind the author about it. If you have the required skills you can prepare " +"a patch that fixes the bug and send it to the author at the same time. Make " +"sure to send the patch to the BTS and to tag the bug as <literal>patch</" +"literal>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:716 +#: pkgs.dbk:718 msgid "" "If you have fixed a bug in your local copy, or if a fix has been committed " "to the CVS repository, you may tag the bug as <literal>pending</literal> to " @@ -1023,7 +1005,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:726 +#: pkgs.dbk:728 msgid "" "Once a corrected package is available in the <emphasis>unstable</emphasis> " "distribution, you can close the bug. This can be done automatically, read " @@ -1031,12 +1013,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:735 +#: pkgs.dbk:737 msgid "When bugs are closed by new uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:737 +#: pkgs.dbk:739 msgid "" "As bugs and problems are fixed in your packages, it is your responsibility " "as the package maintainer to close these bugs. However, you should not " @@ -1047,19 +1029,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:745 +#: pkgs.dbk:747 msgid "" "However, it's possible to avoid having to manually close bugs after the " -"upload — just list the fixed bugs in your " -"<filename>debian/changelog</filename> file, following a certain syntax, and " -"the archive maintenance software will close the bugs for you. For example:" +"upload — just list the fixed bugs in your <filename>debian/changelog</" +"filename> file, following a certain syntax, and the archive maintenance " +"software will close the bugs for you. For example:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:751 +#: pkgs.dbk:753 #, no-wrap msgid "" -"-cannon (3.1415) unstable; urgency=low\n" +"acme-cannon (3.1415) unstable; urgency=low\n" "\n" " * Frobbed with options (closes: Bug#98339)\n" " * Added safety to prevent operator dismemberment, closes: bug#98765,\n" @@ -1068,32 +1050,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:759 +#: pkgs.dbk:761 msgid "" "Technically speaking, the following Perl regular expression describes how " "bug closing changelogs are identified:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:763 +#: pkgs.dbk:765 #, no-wrap msgid "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:766 +#: pkgs.dbk:768 msgid "" "We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> " "syntax, as it is the most concise entry and the easiest to integrate with " "the text of the <filename>changelog</filename>. Unless specified different " -"by the <replaceable>-v</replaceable>-switch to " -"<command>dpkg-buildpackage</command>, only the bugs closed in the most " -"recent changelog entry are closed (basically, exactly the bugs mentioned in " -"the changelog-part in the <filename>.changes</filename> file are closed)." +"by the <replaceable>-v</replaceable>-switch to <command>dpkg-buildpackage</" +"command>, only the bugs closed in the most recent changelog entry are closed " +"(basically, exactly the bugs mentioned in the changelog-part in the " +"<filename>.changes</filename> file are closed)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:775 +#: pkgs.dbk:777 msgid "" "Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer " "upload (NMU)</link> were tagged <literal>fixed</literal> instead of being " @@ -1102,48 +1084,45 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:781 +#: pkgs.dbk:783 msgid "" "If you happen to mistype a bug number or forget a bug in the changelog " "entries, don't hesitate to undo any damage the error caused. To reopen " -"wrongly closed bugs, send a <literal>reopen " -"<replaceable>XXX</replaceable></literal> command to the bug tracking " -"system's control address, <email>control@bugs.debian.org</email>. To close " -"any remaining bugs that were fixed by your upload, email the " -"<filename>.changes</filename> file to " -"<email>XXX-done@bugs.debian.org</email>, where " -"<replaceable>XXX</replaceable> is the bug number, and put Version: YYY and " -"an empty line as the first two lines of the body of the email, where " -"<replaceable>YYY</replaceable> is the first version where the bug has been " -"fixed." +"wrongly closed bugs, send a <literal>reopen <replaceable>XXX</replaceable></" +"literal> command to the bug tracking system's control address, &email-bts-" +"control;. To close any remaining bugs that were fixed by your upload, email " +"the <filename>.changes</filename> file to <email>XXX-done@&bugs-host;</" +"email>, where <replaceable>XXX</replaceable> is the bug number, and put " +"Version: YYY and an empty line as the first two lines of the body of the " +"email, where <replaceable>YYY</replaceable> is the first version where the " +"bug has been fixed." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:793 +#: pkgs.dbk:795 msgid "" "Bear in mind that it is not obligatory to close bugs using the changelog as " "described above. If you simply want to close bugs that don't have anything " "to do with an upload you made, do it by emailing an explanation to " -"<email>XXX-done@bugs.debian.org</email>. Do <emphasis " -"role=\"strong\">not</emphasis> close bugs in the changelog entry of a " -"version if the changes in that version of the package don't have any bearing " -"on the bug." +"<email>XXX-done@&bugs-host;</email>. Do <emphasis role=\"strong\">not</" +"emphasis> close bugs in the changelog entry of a version if the changes in " +"that version of the package don't have any bearing on the bug." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:801 +#: pkgs.dbk:803 msgid "" "For general information on how to write your changelog entries, see <xref " "linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:807 +#: pkgs.dbk:809 msgid "Handling security-related bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:809 +#: pkgs.dbk:811 msgid "" "Due to their sensitive nature, security-related bugs must be handled " "carefully. The Debian Security Team exists to coordinate this activity, " @@ -1153,18 +1132,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:816 +#: pkgs.dbk:820 msgid "" "When you become aware of a security-related bug in a Debian package, whether " "or not you are the maintainer, collect pertinent information about the " -"problem, and promptly contact the security team at " -"<email>team@security.debian.org</email> as soon as possible. <emphasis " -"role=\"strong\">DO NOT UPLOAD</emphasis> any packages for stable; the " -"security team will do that. Useful information includes, for example:" +"problem, and promptly contact the security team at &email-security-team; as " +"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any " +"packages for stable; the security team will do that. Useful information " +"includes, for example:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:826 +#: pkgs.dbk:830 msgid "" "Which versions of the package are known to be affected by the bug. Check " "each version that is present in a supported Debian release, as well as " @@ -1172,39 +1151,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:833 -msgid "The nature of the fix, if any is available (patches are especially helpful)" +#: pkgs.dbk:837 +msgid "" +"The nature of the fix, if any is available (patches are especially helpful)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:838 +#: pkgs.dbk:842 msgid "" -"Any fixed packages that you have prepared yourself (send only the " -"<literal>.diff.gz</literal> and <literal>.dsc</literal> files and read <xref " -"linkend=\"bug-security-building\"/> first)" +"Any fixed packages that you have prepared yourself (send only the <literal>." +"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend=" +"\"bug-security-building\"/> first)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:845 +#: pkgs.dbk:849 msgid "" "Any assistance you can provide to help with testing (exploits, regression " "testing, etc.)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:851 +#: pkgs.dbk:855 msgid "" -"Any information needed for the advisory (see <xref " -"linkend=\"bug-security-advisories\"/> )" +"Any information needed for the advisory (see <xref linkend=\"bug-security-" +"advisories\"/> )" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:857 +#: pkgs.dbk:861 msgid "Confidentiality" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:859 +#: pkgs.dbk:863 msgid "" "Unlike most other activities within Debian, information about security " "issues must sometimes be kept private for a time. This allows software " @@ -1215,27 +1195,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:866 +#: pkgs.dbk:870 msgid "There are several ways developers can learn of a security problem:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:871 +#: pkgs.dbk:875 msgid "they notice it on a public forum (mailing list, web site, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:876 +#: pkgs.dbk:880 msgid "someone files a bug report" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:881 +#: pkgs.dbk:885 msgid "someone informs them via private email" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:886 +#: pkgs.dbk:890 msgid "" "In the first two cases, the information is public and it is important to " "have a fix as soon as possible. In the last case, however, it might not be " @@ -1244,14 +1224,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:894 +#: pkgs.dbk:898 msgid "" "If the security exposure is minor, there is sometimes no need to keep the " "problem a secret and a fix should be made and released." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:900 +#: pkgs.dbk:904 msgid "" "If the problem is severe, it is preferable to share the information with " "other vendors and coordinate a release. The security team keeps in contact " @@ -1259,7 +1239,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:907 +#: pkgs.dbk:911 msgid "" "In all cases if the person who reports the problem asks that it not be " "disclosed, such requests should be honored, with the obvious exception of " @@ -1269,7 +1249,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:914 +#: pkgs.dbk:918 msgid "" "Please note that if secrecy is needed you may not upload a fix to unstable " "(or anywhere else, such as a public CVS repository). It is not sufficient " @@ -1278,7 +1258,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:920 +#: pkgs.dbk:924 msgid "" "There are two reasons for releasing information even though secrecy is " "requested: the problem has been known for a while, or the problem or exploit " @@ -1286,91 +1266,90 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:927 +#: pkgs.dbk:931 msgid "Security Advisories" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:929 +#: pkgs.dbk:933 msgid "" "Security advisories are only issued for the current, released stable " "distribution, and <emphasis>not</emphasis> for testing or unstable. When " -"released, advisories are sent to the " -"<email>debian-security-announce@lists.debian.org</email> mailing list and " -"posted on <ulink url=\"http://www.debian.org/security/\">the security web " -"page</ulink>. Security advisories are written and posted by the security " -"team. However they certainly do not mind if a maintainer can supply some of " -"the information for them, or write part of the text. Information that " -"should be in an advisory includes:" +"released, advisories are sent to the &email-debian-security-announce; " +"mailing list and posted on <ulink url=\"&url-debian-security-advisories;" +"\">the security web page</ulink>. Security advisories are written and " +"posted by the security team. However they certainly do not mind if a " +"maintainer can supply some of the information for them, or write part of the " +"text. Information that should be in an advisory includes:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:942 +#: pkgs.dbk:946 msgid "A description of the problem and its scope, including:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:947 +#: pkgs.dbk:951 msgid "The type of problem (privilege escalation, denial of service, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:952 +#: pkgs.dbk:956 msgid "What privileges may be gained, and by whom (if any)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:957 +#: pkgs.dbk:961 msgid "How it can be exploited" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:962 +#: pkgs.dbk:966 msgid "Whether it is remotely or locally exploitable" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:967 +#: pkgs.dbk:971 msgid "How the problem was fixed" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:972 +#: pkgs.dbk:976 msgid "This information allows users to assess the threat to their systems." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:977 +#: pkgs.dbk:981 msgid "Version numbers of affected packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:982 +#: pkgs.dbk:986 msgid "Version numbers of fixed packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:987 +#: pkgs.dbk:991 msgid "" "Information on where to obtain the updated packages (usually from the Debian " "security archive)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:993 +#: pkgs.dbk:997 msgid "" -"References to upstream advisories, <ulink " -"url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other " -"information useful in cross-referencing the vulnerability" +"References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</" +"ulink> identifiers, and any other information useful in cross-referencing " +"the vulnerability" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1002 +#: pkgs.dbk:1006 msgid "Preparing packages to address security issues" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1004 +#: pkgs.dbk:1008 msgid "" "One way that you can assist the security team in their duties is to provide " "them with fixed packages suitable for a security advisory for the stable " @@ -1378,7 +1357,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1009 +#: pkgs.dbk:1013 msgid "" "When an update is made to the stable release, care must be taken to avoid " "changing system behavior or introducing new bugs. In order to do this, make " @@ -1389,7 +1368,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1017 +#: pkgs.dbk:1021 msgid "" "This means that moving to a new upstream version is not a good solution. " "Instead, the relevant changes should be back-ported to the version present " @@ -1399,7 +1378,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1023 +#: pkgs.dbk:1027 msgid "" "In some cases, it is not possible to back-port a security fix, for example " "when large amounts of source code need to be modified or rewritten. If this " @@ -1409,7 +1388,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1030 +#: pkgs.dbk:1034 msgid "" "Related to this is another important guideline: always test your changes. " "If you have an exploit available, try it and see if it indeed succeeds on " @@ -1419,53 +1398,51 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1037 +#: pkgs.dbk:1041 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your " "package which are not directly related to fixing the vulnerability. These " "will only need to be reverted, and this wastes time. If there are other " -"bugs in your package that you would like to fix, make an upload to " -"proposed-updates in the usual way, after the security advisory is issued. " -"The security update mechanism is not a means for introducing changes to your " +"bugs in your package that you would like to fix, make an upload to proposed-" +"updates in the usual way, after the security advisory is issued. The " +"security update mechanism is not a means for introducing changes to your " "package which would otherwise be rejected from the stable release, so please " "do not attempt to do this." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1047 +#: pkgs.dbk:1051 msgid "" "Review and test your changes as much as possible. Check the differences " "from the previous version repeatedly (<command>interdiff</command> from the " "<systemitem role=\"package\">patchutils</systemitem> package and " -"<command>debdiff</command> from <systemitem " -"role=\"package\">devscripts</systemitem> are useful tools for this, see " -"<xref linkend=\"debdiff\"/> )." +"<command>debdiff</command> from <systemitem role=\"package\">devscripts</" +"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/> )." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1055 +#: pkgs.dbk:1059 msgid "Be sure to verify the following items:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1060 -msgid "" -"Target the right distribution in your " -"<filename>debian/changelog</filename>. For stable this is " -"<literal>stable-security</literal> and for testing this is " -"<literal>testing-security</literal>, and for the previous stable release, " -"this is <literal>oldstable-security</literal>. Do not target " -"<replaceable>distribution</replaceable>-proposed-updates or " +#: pkgs.dbk:1064 +msgid "" +"Target the right distribution in your <filename>debian/changelog</" +"filename>. For stable this is <literal>stable-security</literal> and for " +"testing this is <literal>testing-security</literal>, and for the previous " +"stable release, this is <literal>oldstable-security</literal>. Do not " +"target <replaceable>distribution</replaceable>-proposed-updates or " "<literal>stable</literal>!" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1070 +#: pkgs.dbk:1074 msgid "The upload should have urgency=high." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1075 +#: pkgs.dbk:1079 msgid "" "Make descriptive, meaningful changelog entries. Others will rely on them to " "determine whether a particular bug was fixed. Always include an external " @@ -1478,7 +1455,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1087 +#: pkgs.dbk:1091 msgid "" "Make sure the version number is proper. It must be greater than the current " "package, but less than package versions in later distributions. If in " @@ -1491,17 +1468,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1099 +#: pkgs.dbk:1103 msgid "" "Do not make source-only uploads if your package has any binary-all packages " -"(do not use the <literal>-S</literal> option to " -"<command>dpkg-buildpackage</command>). The <command>buildd</command> " -"infrastructure will not build those. This point applies to normal package " -"uploads as well." +"(do not use the <literal>-S</literal> option to <command>dpkg-buildpackage</" +"command>). The <command>buildd</command> infrastructure will not build " +"those. This point applies to normal package uploads as well." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1108 +#: pkgs.dbk:1112 msgid "" "Unless the upstream source has been uploaded to security.debian.org before " "(by a previous security update), build the upload with full upstream source " @@ -1511,7 +1487,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1117 +#: pkgs.dbk:1121 msgid "" "Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in " "the normal archive, otherwise it is not possible to move the security fix " @@ -1519,22 +1495,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1124 +#: pkgs.dbk:1128 msgid "" "Build the package on a clean system which only has packages installed from " "the distribution you are building for. If you do not have such a system " -"yourself, you can use a debian.org machine (see <xref " -"linkend=\"server-machines\"/> ) or setup a chroot (see <xref " -"linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )." +"yourself, you can use a debian.org machine (see <xref linkend=\"server-" +"machines\"/> ) or setup a chroot (see <xref linkend=\"pbuilder\"/> and <xref " +"linkend=\"debootstrap\"/> )." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1135 +#: pkgs.dbk:1139 msgid "Uploading the fixed package" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1137 +#: pkgs.dbk:1141 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " @@ -1544,11 +1520,11 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1144 +#: pkgs.dbk:1148 msgid "" -"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to " -"proposed-updates without coordinating with the security team. Packages from " -"security.debian.org will be copied into the proposed-updates directory " +"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to proposed-" +"updates without coordinating with the security team. Packages from security." +"debian.org will be copied into the proposed-updates directory " "automatically. If a package with the same or a higher version number is " "already installed into the archive, the security update will be rejected by " "the archive system. That way, the stable distribution will end up without a " @@ -1556,17 +1532,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1153 +#: pkgs.dbk:1157 msgid "" "Once you have created and tested the new package and it has been approved by " "the security team, it needs to be uploaded so that it can be installed in " "the archives. For security uploads, the place to upload to is " -"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal> " -"." +"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</" +"literal> ." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1159 +#: pkgs.dbk:1163 msgid "" "Once an upload to the security queue has been accepted, the package will " "automatically be rebuilt for all architectures and stored for verification " @@ -1574,7 +1550,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1164 +#: pkgs.dbk:1168 msgid "" "Uploads which are waiting for acceptance or verification are only accessible " "by the security team. This is necessary since there might be fixes for " @@ -1582,7 +1558,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1169 +#: pkgs.dbk:1173 msgid "" "If a member of the security team accepts a package, it will be installed on " "security.debian.org as well as proposed for the proper " @@ -1590,12 +1566,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1180 +#: pkgs.dbk:1184 msgid "Moving, removing, renaming, adopting, and orphaning packages" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1182 +#: pkgs.dbk:1186 msgid "" "Some archive manipulation operations are not automated in the Debian upload " "process. These procedures should be manually followed by maintainers. This " @@ -1603,12 +1579,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1187 +#: pkgs.dbk:1191 msgid "Moving packages" msgstr "" # type: Content of: <chapter><section><section><para><footnote> -#: pkgs.dbk:1189 +#: pkgs.dbk:1193 msgid "" "Sometimes a package will change its section. For instance, a package from " "the `non-free' section might be GPL'd in a later version, in which case the " @@ -1616,20 +1592,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para><footnote><para> -#: pkgs.dbk:1191 +#: pkgs.dbk:1195 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for guidelines on what section a package belongs in." +"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"guidelines on what section a package belongs in." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1196 +#: pkgs.dbk:1200 msgid "" "If you need to change the section for one of your packages, change the " "package control information to place the package in the desired section, and " -"re-upload the package (see the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). You must ensure that you include the " +"re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian " +"Policy Manual</ulink> for details). You must ensure that you include the " "<filename>.orig.tar.gz</filename> in your upload (even if you are not " "uploading a new upstream version), or it will not appear in the new section " "together with the rest of the package. If your new section is valid, it " @@ -1638,51 +1613,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1208 +#: pkgs.dbk:1212 msgid "" -"If, on the other hand, you need to change the " -"<emphasis>subsection</emphasis> of one of your packages (e.g., ``devel'', " -"``admin''), the procedure is slightly different. Correct the subsection as " -"found in the control file of the package, and re-upload that. Also, you'll " -"need to get the override file updated, as described in <xref " -"linkend=\"override-file\"/> ." +"If, on the other hand, you need to change the <emphasis>subsection</" +"emphasis> of one of your packages (e.g., ``devel'', ``admin''), the " +"procedure is slightly different. Correct the subsection as found in the " +"control file of the package, and re-upload that. Also, you'll need to get " +"the override file updated, as described in <xref linkend=\"override-file\"/" +"> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1217 +#: pkgs.dbk:1221 msgid "Removing packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1219 +#: pkgs.dbk:1223 msgid "" "If for some reason you want to completely remove a package (say, if it is an " "old compatibility library which is no longer required), you need to file a " "bug against <literal>ftp.debian.org</literal> asking that the package be " "removed; as all bugs, this bug should normally have normal severity. Make " "sure you indicate which distribution the package should be removed from. " -"Normally, you can only have packages removed from " -"<emphasis>unstable</emphasis> and <emphasis>experimental</emphasis>. " -"Packages are not removed from <emphasis>testing</emphasis> directly. " -"Rather, they will be removed automatically after the package has been " -"removed from <emphasis>unstable</emphasis> and no package in " -"<emphasis>testing</emphasis> depends on it." +"Normally, you can only have packages removed from <emphasis>unstable</" +"emphasis> and <emphasis>experimental</emphasis>. Packages are not removed " +"from <emphasis>testing</emphasis> directly. Rather, they will be removed " +"automatically after the package has been removed from <emphasis>unstable</" +"emphasis> and no package in <emphasis>testing</emphasis> depends on it." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1232 +#: pkgs.dbk:1236 msgid "" "There is one exception when an explicit removal request is not necessary: If " -"a (source or binary) package is an orphan, it will be removed " -"semi-automatically. For a binary-package, this means if there is no longer " -"any source package producing this binary package; if the binary package is " -"just no longer produced on some architectures, a removal request is still " +"a (source or binary) package is an orphan, it will be removed semi-" +"automatically. For a binary-package, this means if there is no longer any " +"source package producing this binary package; if the binary package is just " +"no longer produced on some architectures, a removal request is still " "necessary. For a source-package, this means that all binary packages it " "refers to have been taken over by another source package." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1241 +#: pkgs.dbk:1245 msgid "" "In your removal request, you have to detail the reasons justifying the " "request. This is to avoid unwanted removals and to keep a trace of why a " @@ -1691,7 +1665,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1247 +#: pkgs.dbk:1251 msgid "" "Usually you only ask for the removal of a package maintained by yourself. " "If you want to remove another package, you have to get the approval of its " @@ -1699,79 +1673,76 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1252 +#: pkgs.dbk:1256 msgid "" "Further information relating to these and other package removal related " -"topics may be found at <ulink " -"url=\"http://wiki.debian.org/ftpmaster_Removals\"></ulink> and <ulink " -"url=\"http://qa.debian.org/howto-remove.html\"></ulink>." +"topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals" +"\"></ulink> and <ulink url=\"&url-debian-qa;howto-remove.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1257 +#: pkgs.dbk:1261 msgid "" -"If in doubt concerning whether a package is disposable, email " -"<email>debian-devel@lists.debian.org</email> asking for opinions. Also of " -"interest is the <command>apt-cache</command> program from the <systemitem " -"role=\"package\">apt</systemitem> package. When invoked as " -"<literal>apt-cache showpkg <replaceable>package</replaceable></literal>, the " -"program will show details for <replaceable>package</replaceable>, including " -"reverse depends. Other useful programs include <literal>apt-cache " -"rdepends</literal>, <command>apt-rdepends</command> and " -"<command>grep-dctrl</command>. Removal of orphaned packages is discussed on " -"<email>debian-qa@lists.debian.org</email>." +"If in doubt concerning whether a package is disposable, email &email-debian-" +"devel; asking for opinions. Also of interest is the <command>apt-cache</" +"command> program from the <systemitem role=\"package\">apt</systemitem> " +"package. When invoked as <literal>apt-cache showpkg <replaceable>package</" +"replaceable></literal>, the program will show details for " +"<replaceable>package</replaceable>, including reverse depends. Other useful " +"programs include <literal>apt-cache rdepends</literal>, <command>apt-" +"rdepends</command> and <command>grep-dctrl</command>. Removal of orphaned " +"packages is discussed on &email-debian-qa;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1268 +#: pkgs.dbk:1272 msgid "" "Once the package has been removed, the package's bugs should be handled. " "They should either be reassigned to another package in the case where the " -"actual code has evolved into another package (e.g. " -"<literal>libfoo12</literal> was removed because <literal>libfoo13</literal> " -"supersedes it) or closed if the software is simply no longer part of Debian." +"actual code has evolved into another package (e.g. <literal>libfoo12</" +"literal> was removed because <literal>libfoo13</literal> supersedes it) or " +"closed if the software is simply no longer part of Debian." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1275 +#: pkgs.dbk:1279 msgid "Removing packages from <filename>Incoming</filename>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1277 +#: pkgs.dbk:1281 msgid "" -"In the past, it was possible to remove packages from " -"<filename>incoming</filename>. However, with the introduction of the new " -"incoming system, this is no longer possible. Instead, you have to upload a " -"new revision of your package with a higher version than the package you want " -"to replace. Both versions will be installed in the archive but only the " -"higher version will actually be available in <emphasis>unstable</emphasis> " -"since the previous version will immediately be replaced by the higher. " -"However, if you do proper testing of your packages, the need to replace a " -"package should not occur too often anyway." +"In the past, it was possible to remove packages from <filename>incoming</" +"filename>. However, with the introduction of the new incoming system, this " +"is no longer possible. Instead, you have to upload a new revision of your " +"package with a higher version than the package you want to replace. Both " +"versions will be installed in the archive but only the higher version will " +"actually be available in <emphasis>unstable</emphasis> since the previous " +"version will immediately be replaced by the higher. However, if you do " +"proper testing of your packages, the need to replace a package should not " +"occur too often anyway." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1292 +#: pkgs.dbk:1296 msgid "Replacing or renaming packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1294 +#: pkgs.dbk:1298 msgid "" "When you make a mistake naming your package, you should follow a two-step " "process to rename it. First, set your <filename>debian/control</filename> " "file to replace and conflict with the obsolete name of the package (see the " -"<ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). Once you've uploaded the package and the " -"package has moved into the archive, file a bug against " -"<literal>ftp.debian.org</literal> asking to remove the package with the " -"obsolete name. Do not forget to properly reassign the package's bugs at the " -"same time." +"<ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"details). Once you've uploaded the package and the package has moved into " +"the archive, file a bug against <literal>ftp.debian.org</literal> asking to " +"remove the package with the obsolete name. Do not forget to properly " +"reassign the package's bugs at the same time." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1304 +#: pkgs.dbk:1308 msgid "" "At other times, you may make a mistake in constructing your package and wish " "to replace it. The only way to do this is to increase the version number " @@ -1779,70 +1750,68 @@ msgid "" "manner. Note that this applies to each part of your package, including the " "sources: if you wish to replace the upstream source tarball of your package, " "you will need to upload it with a different version. An easy possibility is " -"to replace <filename>foo_1.00.orig.tar.gz</filename> with " -"<filename>foo_1.00+0.orig.tar.gz</filename>. This restriction gives each " -"file on the ftp site a unique name, which helps to ensure consistency across " -"the mirror network." +"to replace <filename>foo_1.00.orig.tar.gz</filename> with <filename>foo_1.00" +"+0.orig.tar.gz</filename>. This restriction gives each file on the ftp site " +"a unique name, which helps to ensure consistency across the mirror network." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1318 +#: pkgs.dbk:1322 msgid "Orphaning a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1320 +#: pkgs.dbk:1324 msgid "" "If you can no longer maintain a package, you need to inform others, and see " "that the package is marked as orphaned. You should set the package " -"maintainer to <literal>Debian QA Group " -"<packages@qa.debian.org></literal> and submit a bug report against the " -"pseudo package <systemitem role=\"package\">wnpp</systemitem>. The bug " -"report should be titled <literal>O: <replaceable>package</replaceable> -- " -"<replaceable>short description</replaceable></literal> indicating that the " -"package is now orphaned. The severity of the bug should be set to " -"<emphasis>normal</emphasis>; if the package has a priority of standard or " -"higher, it should be set to important. If you feel it's necessary, send a " -"copy to <email>debian-devel@lists.debian.org</email> by putting the address " -"in the X-Debbugs-CC: header of the message (no, don't use CC:, because that " -"way the message's subject won't indicate the bug number)." +"maintainer to <literal>Debian QA Group &orphan-address;</literal> and submit " +"a bug report against the pseudo package <systemitem role=\"package\">wnpp</" +"systemitem>. The bug report should be titled <literal>O: " +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal> indicating that the package is now orphaned. The " +"severity of the bug should be set to <emphasis>normal</emphasis>; if the " +"package has a priority of standard or higher, it should be set to " +"important. If you feel it's necessary, send a copy to &email-debian-devel; " +"by putting the address in the X-Debbugs-CC: header of the message (no, don't " +"use CC:, because that way the message's subject won't indicate the bug " +"number)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1335 +#: pkgs.dbk:1339 msgid "" "If you just intend to give the package away, but you can keep maintainership " "for the moment, then you should instead submit a bug against <systemitem " "role=\"package\">wnpp</systemitem> and title it <literal>RFA: " -"<replaceable>package</replaceable> -- <replaceable>short " -"description</replaceable></literal>. <literal>RFA</literal> stands for " -"<emphasis>Request For Adoption</emphasis>." +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal>. <literal>RFA</literal> stands for <emphasis>Request " +"For Adoption</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1343 +#: pkgs.dbk:1347 msgid "" -"More information is on the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">WNPP web pages</ulink>." +"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1349 +#: pkgs.dbk:1353 msgid "Adopting a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1351 +#: pkgs.dbk:1355 msgid "" "A list of packages in need of a new maintainer is available in the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " -"Packages list (WNPP)</ulink>. If you wish to take over maintenance of any " -"of the packages listed in the WNPP, please take a look at the aforementioned " -"page for information and procedures." +"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</" +"ulink>. If you wish to take over maintenance of any of the packages listed " +"in the WNPP, please take a look at the aforementioned page for information " +"and procedures." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1358 +#: pkgs.dbk:1362 msgid "" "It is not OK to simply take over a package that you feel is neglected — that " "would be package hijacking. You can, of course, contact the current " @@ -1852,20 +1821,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1364 +#: pkgs.dbk:1368 msgid "" "Generally, you may not take over the package without the assent of the " "current maintainer. Even if they ignore you, that is still not grounds to " "take over a package. Complaints about maintainers should be brought up on " "the developers' mailing list. If the discussion doesn't end with a positive " "conclusion, and the issue is of a technical nature, consider bringing it to " -"the attention of the technical committee (see the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">technical committee web " -"page</ulink> for more information)." +"the attention of the technical committee (see the <ulink url=\"&url-tech-" +"ctte;\">technical committee web page</ulink> for more information)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1374 +#: pkgs.dbk:1378 msgid "" "If you take over an old package, you probably want to be listed as the " "package's official maintainer in the bug system. This will happen " @@ -1878,12 +1846,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1388 +#: pkgs.dbk:1392 msgid "Porting and being ported" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1390 +#: pkgs.dbk:1394 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 " @@ -1892,23 +1860,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1396 +#: pkgs.dbk:1400 msgid "" "Porting is the act of building Debian packages for architectures that are " "different from the original architecture of the package maintainer's binary " "package. It is a unique and essential activity. In fact, porters do most " "of the actual compiling of Debian packages. For instance, for a single " "<emphasis>i386</emphasis> binary package, there must be a recompile for each " -"architecture, which amounts to 12 more builds." +"architecture, which amounts to &number-of-arches; more builds." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1404 +#: pkgs.dbk:1408 msgid "Being kind to porters" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1406 +#: pkgs.dbk:1410 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 " @@ -1919,7 +1887,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1414 +#: pkgs.dbk:1418 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 " @@ -1929,7 +1897,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1421 +#: pkgs.dbk:1425 msgid "" "By far, most of the problems encountered by porters are caused by " "<emphasis>packaging bugs</emphasis> in the source packages. Here is a " @@ -1937,49 +1905,46 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1428 -msgid "" -"Make sure that your <literal>Build-Depends</literal> and " -"<literal>Build-Depends-Indep</literal> settings in " -"<filename>debian/control</filename> are set properly. The best way to " -"validate this is to use the <systemitem " -"role=\"package\">debootstrap</systemitem> package to create an unstable " -"chroot environment (see <xref linkend=\"debootstrap\"/> ). Within that " -"chrooted environment, install the <systemitem " -"role=\"package\">build-essential</systemitem> package and any package " -"dependencies mentioned in <literal>Build-Depends</literal> and/or " -"<literal>Build-Depends-Indep</literal>. Finally, try building your package " -"within that chrooted environment. These steps can be automated by the use " -"of the <command>pbuilder</command> program which is provided by the package " -"of the same name (see <xref linkend=\"pbuilder\"/> )." +#: pkgs.dbk:1432 +msgid "" +"Make sure that your <literal>Build-Depends</literal> and <literal>Build-" +"Depends-Indep</literal> settings in <filename>debian/control</filename> are " +"set properly. The best way to validate this is to use the <systemitem role=" +"\"package\">debootstrap</systemitem> package to create an unstable chroot " +"environment (see <xref linkend=\"debootstrap\"/> ). Within that chrooted " +"environment, install the <systemitem role=\"package\">build-essential</" +"systemitem> package and any package dependencies mentioned in <literal>Build-" +"Depends</literal> and/or <literal>Build-Depends-Indep</literal>. Finally, " +"try building your package within that chrooted environment. These steps can " +"be automated by the use of the <command>pbuilder</command> program which is " +"provided by the package of the same name (see <xref linkend=\"pbuilder\"/> )." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1442 +#: pkgs.dbk:1446 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:1446 +#: pkgs.dbk:1450 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for instructions on setting build dependencies." +"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:1452 +#: pkgs.dbk:1456 msgid "" "Don't set architecture to a value other than ``all'' or ``any'' unless you " "really mean it. In too many cases, maintainers don't follow the " -"instructions in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>. Setting your architecture to ``i386'' is usually incorrect." +"instructions in the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</" +"ulink>. Setting your architecture to ``i386'' is usually incorrect." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1460 +#: pkgs.dbk:1464 msgid "" "Make sure your source package is correct. Do <literal>dpkg-source -x " "<replaceable>package</replaceable>.dsc</literal> to make sure your source " @@ -1988,33 +1953,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1468 +#: pkgs.dbk:1472 msgid "" -"Make sure you don't ship your source package with the " -"<filename>debian/files</filename> or <filename>debian/substvars</filename> " -"files. They should be removed by the `clean' target of " -"<filename>debian/rules</filename>." +"Make sure you don't ship your source package with the <filename>debian/" +"files</filename> or <filename>debian/substvars</filename> files. They " +"should be removed by the `clean' target of <filename>debian/rules</filename>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1476 +#: pkgs.dbk:1480 msgid "" "Make sure you don't rely on locally installed or hacked configurations or " -"programs. For instance, you should never be calling programs in " -"<filename>/usr/local/bin</filename> or the like. Try not to rely on " -"programs being setup in a special way. Try building your package on another " -"machine, even if it's the same architecture." +"programs. For instance, you should never be calling programs in <filename>/" +"usr/local/bin</filename> or the like. Try not to rely on programs being " +"setup in a special way. Try building your package on another machine, even " +"if it's the same architecture." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1485 +#: pkgs.dbk:1489 msgid "" -"Don't depend on the package you're building being installed already (a " -"sub-case of the above issue)." +"Don't depend on the package you're building being installed already (a sub-" +"case of the above issue)." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1491 +#: pkgs.dbk:1495 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 " @@ -2023,22 +1987,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1499 +#: pkgs.dbk:1503 msgid "" -"Make sure your debian/rules contains separate ``binary-arch'' and " -"``binary-indep'' targets, as the Debian Policy Manual requires. Make sure " -"that both targets work independently, that is, that you can call the target " -"without having called the other before. To test this, try to run " -"<literal>dpkg-buildpackage -B</literal>." +"Make sure your debian/rules contains separate ``binary-arch'' and ``binary-" +"indep'' targets, as the Debian Policy Manual requires. Make sure that both " +"targets work independently, that is, that you can call the target without " +"having called the other before. To test this, try to run <literal>dpkg-" +"buildpackage -B</literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1510 +#: pkgs.dbk:1514 msgid "Guidelines for porter uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1512 +#: pkgs.dbk:1516 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 " @@ -2049,7 +2013,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1520 +#: pkgs.dbk:1524 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 " @@ -2057,34 +2021,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1525 +#: pkgs.dbk:1529 msgid "" -"The way to invoke <command>dpkg-buildpackage</command> is as " -"<literal>dpkg-buildpackage -B " -"-m<replaceable>porter-email</replaceable></literal>. Of course, set " -"<replaceable>porter-email</replaceable> to your email address. This will do " -"a binary-only build of only the architecture-dependent portions of the " -"package, using the `binary-arch' target in " -"<filename>debian/rules</filename>." +"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-" +"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of " +"course, set <replaceable>porter-email</replaceable> to your email address. " +"This will do a binary-only build of only the architecture-dependent portions " +"of the package, using the `binary-arch' target in <filename>debian/rules</" +"filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1533 +#: pkgs.dbk:1537 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 " "<command>debsign</command> on your <filename>.changes</filename> file to " -"have it signed conveniently, or use the remote signing mode of " -"<command>dpkg-sig</command>." +"have it signed conveniently, or use the remote signing mode of <command>dpkg-" +"sig</command>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1540 +#: pkgs.dbk:1544 msgid "Recompilation or binary-only NMU" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1542 +#: pkgs.dbk:1546 msgid "" "Sometimes the initial porter upload is problematic because the environment " "in which the package was built was not good enough (outdated or obsolete " @@ -2096,24 +2059,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1551 +#: pkgs.dbk:1555 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 " -"arch-dependent and arch-independent packages that depend on each other via " +"uninstallable. This could happen when a source package generates arch-" +"dependent and arch-independent packages that depend on each other via " "$(Source-Version)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1557 +#: pkgs.dbk:1561 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 " -"architectures to consider themselves out of date or requiring recompilation." +"Despite the required modification of the changelog, these are called binary-" +"only NMUs — there is no need in this case to trigger all other architectures " +"to consider themselves out of date or requiring recompilation." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1562 +#: pkgs.dbk:1566 msgid "" "Such recompilations require special ``magic'' version numbering, so that the " "archive maintenance tools recognize that, even though there is a new Debian " @@ -2123,7 +2086,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: pkgs.dbk:1569 +#: pkgs.dbk:1573 msgid "" "The ``magic'' for a recompilation-only NMU is triggered by using a suffix " "appended to the package version number, following the form b<number>. " @@ -2134,7 +2097,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: pkgs.dbk:1574 +#: pkgs.dbk:1578 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 " @@ -2144,20 +2107,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1582 +#: pkgs.dbk:1586 msgid "" -"Similar to initial porter uploads, the correct way of invoking " -"<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage " -"-B</literal> to only build the architecture-dependent parts of the package." +"Similar to initial porter uploads, the correct way of invoking <command>dpkg-" +"buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only " +"build the architecture-dependent parts of the package." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1589 +#: pkgs.dbk:1593 msgid "When to do a source NMU if you are a porter" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1591 +#: pkgs.dbk:1595 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 " @@ -2170,7 +2133,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1600 +#: pkgs.dbk:1604 msgid "" "If you are a porter doing an NMU for `unstable', the above guidelines for " "porting should be followed, with two variations. Firstly, the acceptable " @@ -2184,7 +2147,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1611 +#: pkgs.dbk:1615 msgid "" "Secondly, porters doing source NMUs should make sure that the bug they " "submit to the BTS should be of severity `serious' or greater. This ensures " @@ -2195,7 +2158,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1619 +#: pkgs.dbk:1623 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 " @@ -2206,7 +2169,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1627 +#: pkgs.dbk:1631 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 " @@ -2215,12 +2178,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1637 +#: pkgs.dbk:1641 msgid "Porting infrastructure and automation" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1639 +#: pkgs.dbk:1643 msgid "" "There is infrastructure and several tools to help automate package porting. " "This section contains a brief overview of this automation and porting to " @@ -2229,40 +2192,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1644 +#: pkgs.dbk:1648 msgid "Mailing lists and web pages" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1646 +#: pkgs.dbk:1650 msgid "" -"Web pages containing the status of each port can be found at <ulink " -"url=\"http://www.debian.org/ports/\"></ulink>." +"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:1650 +#: pkgs.dbk:1654 msgid "" "Each port of Debian has a mailing list. The list of porting mailing lists " -"can be found at <ulink url=\"http://lists.debian.org/ports.html\"></ulink>. " -"These lists are used to coordinate porters, and to connect the users of a " -"given port with the porters." +"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These " +"lists are used to coordinate porters, and to connect the users of a given " +"port with the porters." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1658 +#: pkgs.dbk:1662 msgid "Porter tools" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1660 +#: pkgs.dbk:1664 msgid "" -"Descriptions of several porting tools can be found in <xref " -"linkend=\"tools-porting\"/> ." +"Descriptions of several porting tools can be found in <xref linkend=\"tools-" +"porting\"/> ." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1668 +#: pkgs.dbk:1672 msgid "" "The <systemitem role=\"package\">buildd</systemitem> system is used as a " "distributed, client-server build distribution system. It is usually used in " @@ -2274,32 +2237,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1677 +#: pkgs.dbk:1681 msgid "" "<systemitem role=\"package\">buildd</systemitem> is not yet available as a " "package; however, most porting efforts are either using it currently or " "planning to use it in the near future. The actual automated builder is " "packaged as <systemitem role=\"package\">sbuild</systemitem>, see its " -"description in <xref linkend=\"sbuild\"/> . The complete <systemitem " -"role=\"package\">buildd</systemitem> system also collects a number of as yet " +"description in <xref linkend=\"sbuild\"/> . The complete <systemitem role=" +"\"package\">buildd</systemitem> system also collects a number of as yet " "unpackaged components which are currently very useful and in use " -"continually, such as <command>andrea</command> and " -"<command>wanna-build</command>." +"continually, such as <command>andrea</command> and <command>wanna-build</" +"command>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1687 +#: pkgs.dbk:1691 msgid "" -"Some of the data produced by <systemitem " -"role=\"package\">buildd</systemitem> which is generally useful to porters is " -"available on the web at <ulink url=\"http://buildd.debian.org/\"></ulink>. " -"This data includes nightly updated information from " -"<command>andrea</command> (source dependencies) and <systemitem " -"role=\"package\">quinn-diff</systemitem> (packages needing recompilation)." +"Some of the data produced by <systemitem role=\"package\">buildd</" +"systemitem> which is generally useful to porters is available on the web at " +"<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated " +"information from <command>andrea</command> (source dependencies) and " +"<systemitem role=\"package\">quinn-diff</systemitem> (packages needing " +"recompilation)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1695 +#: pkgs.dbk:1699 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 " @@ -2309,36 +2272,36 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1702 +#: pkgs.dbk:1706 msgid "" "The buildds admins of each arch can be contacted at the mail address " "$arch@buildd.debian.org." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1710 +#: pkgs.dbk:1714 msgid "When your package is <emphasis>not</emphasis> portable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1712 +#: pkgs.dbk:1716 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 " -"within a reasonable amount of time. An example is a package that is " -"SVGA-specific (only i386), or uses other hardware-specific features not " -"supported on all architectures." +"within a reasonable amount of time. An example is a package that is SVGA-" +"specific (only i386), or uses other hardware-specific features not supported " +"on all architectures." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1719 +#: pkgs.dbk:1723 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:1725 +#: pkgs.dbk:1729 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 " @@ -2350,7 +2313,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1733 +#: pkgs.dbk:1737 msgid "" "Additionally, if you believe the list of supported architectures is pretty " "constant, you should change 'any' to a list of supported architectures in " @@ -2359,35 +2322,35 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1741 +#: pkgs.dbk:1745 msgid "" "In order to prevent autobuilders from needlessly trying to build your " "package, it must be included in <filename>packages-arch-specific</filename>, " "a list used by the <command>wanna-build</command> script. The current " -"version is available as <ulink " -"url=\"http://cvs.debian.org/srcdep/Packages-arch-specific?cvsroot=dak\"></ulink>; " -"please see the top of the file for whom to contact for changes." +"version is available as <ulink url=\"&url-cvsweb;srcdep/Packages-arch-" +"specific?cvsroot=dak\"></ulink>; please see the top of the file for whom to " +"contact for changes." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1751 +#: pkgs.dbk:1755 msgid "" -"Please note that it is insufficient to only add your package to " -"Packages-arch-specific without making it fail to build on unsupported " -"architectures: A porter or any other person trying to build your package " -"might accidently upload it without noticing it doesn't work. If in the past " -"some binary packages were uploaded on unsupported architectures, request " -"their removal by filing a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem>" +"Please note that it is insufficient to only add your package to Packages-" +"arch-specific without making it fail to build on unsupported architectures: " +"A porter or any other person trying to build your package might accidently " +"upload it without noticing it doesn't work. If in the past some binary " +"packages were uploaded on unsupported architectures, request their removal " +"by filing a bug against <systemitem role=\"package\">ftp.debian.org</" +"systemitem>" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1764 +#: pkgs.dbk:1768 msgid "Non-Maintainer Uploads (NMUs)" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1766 +#: pkgs.dbk:1770 msgid "" "Under certain circumstances it is necessary for someone other than the " "official package maintainer to make a release of a package. This is called " @@ -2395,17 +2358,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1771 +#: pkgs.dbk:1775 msgid "" "This section handles only source NMUs, i.e. NMUs which upload a new version " "of the package. For binary-only NMUs by porters or QA members, please see " "<xref linkend=\"binary-only-nmu\"/> . If a buildd builds and uploads a " -"package, that too is strictly speaking a binary NMU. See <xref " -"linkend=\"buildd\"/> for some more information." +"package, that too is strictly speaking a binary NMU. See <xref linkend=" +"\"buildd\"/> for some more information." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1778 +#: pkgs.dbk:1782 msgid "" "The main reason why NMUs are done is when a developer needs to fix another " "developer's package in order to address serious problems or crippling bugs " @@ -2414,7 +2377,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1783 +#: pkgs.dbk:1787 msgid "" "First and foremost, it is critical that NMU patches to source should be as " "non-disruptive as possible. Do not do housekeeping tasks, do not change the " @@ -2426,20 +2389,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1792 +#: pkgs.dbk:1796 msgid "" "And please remember the Hippocratic Oath: Above all, do no harm. It is " -"better to leave a package with an open grave bug than applying a " -"non-functional patch, or one that hides the bug instead of resolving it." +"better to leave a package with an open grave bug than applying a non-" +"functional patch, or one that hides the bug instead of resolving it." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1797 +#: pkgs.dbk:1801 msgid "How to do a NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1799 +#: pkgs.dbk:1803 msgid "" "NMUs which fix important, serious or higher severity bugs are encouraged and " "accepted. You should endeavor to reach the current maintainer of the " @@ -2448,7 +2411,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1805 +#: pkgs.dbk:1809 msgid "" "NMUs should be made to assist a package's maintainer in resolving bugs. " "Maintainers should be thankful for that help, and NMUers should respect the " @@ -2457,14 +2420,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1811 +#: pkgs.dbk:1815 msgid "" "A NMU should follow all conventions, written down in this section. For an " "upload to testing or unstable, this order of steps is recommended:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1817 +#: pkgs.dbk:1821 msgid "" "Make sure that the package's bugs that the NMU is meant to address are all " "filed in the Debian Bug Tracking System (BTS). If they are not, submit them " @@ -2472,7 +2435,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1824 +#: pkgs.dbk:1828 msgid "" "Wait a few days for the response from the maintainer. If you don't get any " "response, you may want to help them by sending the patch that fixes the " @@ -2480,7 +2443,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1831 +#: pkgs.dbk:1835 msgid "" "Wait a few more days. If you still haven't got an answer from the " "maintainer, send them a mail announcing your intent to NMU the package. " @@ -2491,7 +2454,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1841 +#: pkgs.dbk:1845 msgid "" "Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. " "<xref linkend=\"delayed-incoming\"/> ), send the final patch to the " @@ -2500,7 +2463,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1849 +#: pkgs.dbk:1853 msgid "" "Follow what happens, you're responsible for any bug that you introduced with " "your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> " @@ -2508,7 +2471,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1856 +#: pkgs.dbk:1860 msgid "" "At times, the release manager or an organized group of developers can " "announce a certain period of time in which the NMU rules are relaxed. This " @@ -2520,7 +2483,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1865 +#: pkgs.dbk:1869 msgid "" "For the testing distribution, the rules may be changed by the release " "managers. Please take additional care, and acknowledge that the usual way " @@ -2528,7 +2491,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1870 +#: pkgs.dbk:1874 msgid "" "For the stable distribution, please take extra care. Of course, the release " "managers may also change the rules here. Please verify before you upload " @@ -2537,7 +2500,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1876 +#: pkgs.dbk:1880 msgid "" "When a security bug is detected, the security team may do an NMU, using " "their own rules. Please refer to <xref linkend=\"bug-security\"/> for more " @@ -2545,14 +2508,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1881 +#: pkgs.dbk:1885 msgid "" -"For the differences for Porters NMUs, please see <xref " -"linkend=\"source-nmu-when-porter\"/> ." +"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-" +"when-porter\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1885 +#: pkgs.dbk:1889 msgid "" "Of course, it is always possible to agree on special rules with a maintainer " "(like the maintainer asking please upload this fix directly for me, and no " @@ -2560,20 +2523,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1892 +#: pkgs.dbk:1896 msgid "NMU version numbering" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1894 +#: pkgs.dbk:1898 msgid "" "Whenever you have made a change to a package, no matter how trivial, the " -"version number needs to change. This enables our packing system to " -"function." +"version number needs to change. This enables our packing system to function." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1898 +#: pkgs.dbk:1902 msgid "" "If you are doing a non-maintainer upload (NMU), you should add a new minor " "version number to the <replaceable>debian-revision</replaceable> part of the " @@ -2582,12 +2544,12 @@ msgid "" "version 1.1-3. In the archive, the source package control file would be " "<filename>foo_1.1-3.dsc</filename>. The upstream version is `1.1' and the " "Debian revision is `3'. The next NMU would add a new minor number `.1' to " -"the Debian revision; the new source control file would be " -"<filename>foo_1.1-3.1.dsc</filename>." +"the Debian revision; the new source control file would be <filename>foo_1.1-" +"3.1.dsc</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1909 +#: pkgs.dbk:1913 msgid "" "The Debian revision minor number is needed to avoid stealing one of the " "package maintainer's version numbers, which might disrupt their work. It " @@ -2596,7 +2558,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1915 +#: pkgs.dbk:1919 msgid "" "If there is no <replaceable>debian-revision</replaceable> component in the " "version number then one should be created, starting at `0.1' (but in case of " @@ -2609,7 +2571,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1925 +#: pkgs.dbk:1929 msgid "" "If you upload a package to testing or stable, sometimes, you need to fork " "the version number tree. For this, version numbers like 1.1-3sarge0.1 could " @@ -2617,12 +2579,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1932 +#: pkgs.dbk:1936 msgid "Source NMUs must have a new changelog entry" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1934 +#: pkgs.dbk:1938 msgid "" "Anyone who is doing a source NMU must create a changelog entry, describing " "which bugs are fixed by the NMU, and generally why the NMU was required and " @@ -2631,23 +2593,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1940 +#: pkgs.dbk:1944 msgid "By convention, source NMU changelog entries start with the line" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:1943 +#: pkgs.dbk:1947 #, no-wrap msgid "* Non-maintainer upload" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1948 +#: pkgs.dbk:1952 msgid "Source NMUs and the Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1950 +#: pkgs.dbk:1954 msgid "" "Maintainers other than the official package maintainer should make as few " "changes to the package as possible, and they should always send a patch as a " @@ -2656,7 +2618,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1956 +#: pkgs.dbk:1960 msgid "" "What if you are simply recompiling the package? If you just need to " "recompile it for a single architecture, then you may do a binary-only NMU as " @@ -2667,7 +2629,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1963 +#: pkgs.dbk:1967 msgid "" "Bugs fixed by source NMUs used to be tagged fixed instead of closed, but " "since version tracking is in place, such bugs are now also closed with the " @@ -2675,7 +2637,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1968 +#: pkgs.dbk:1972 msgid "" "Also, after doing an NMU, you have to send the information to the existing " "bugs that are fixed by your NMU, including the unified diff. Historically, " @@ -2690,7 +2652,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1979 +#: pkgs.dbk:1983 msgid "" "In addition, the normal maintainer should <emphasis>always</emphasis> retain " "the entry in the changelog file documenting the non-maintainer upload -- and " @@ -2699,12 +2661,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1987 +#: pkgs.dbk:1991 msgid "Building source NMUs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1989 +#: pkgs.dbk:1993 msgid "" "Source NMU packages are built normally. Pick a distribution using the same " "rules as found in <xref linkend=\"distribution\"/> , follow the other " @@ -2712,7 +2674,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1994 +#: pkgs.dbk:1998 msgid "" "Make sure you do <emphasis>not</emphasis> change the value of the maintainer " "in the <filename>debian/control</filename> file. Your name as given in the " @@ -2721,12 +2683,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2002 +#: pkgs.dbk:2006 msgid "Acknowledging an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2004 +#: pkgs.dbk:2008 msgid "" "If one of your packages has been NMU'ed, you have to incorporate the changes " "in your copy of the sources. This is easy, you just have to apply the patch " @@ -2740,7 +2702,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2015 +#: pkgs.dbk:2019 msgid "" "In any case, you should not be upset by the NMU. An NMU is not a personal " "attack against the maintainer. It is a proof that someone cares enough " @@ -2751,80 +2713,80 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2025 +#: pkgs.dbk:2029 msgid "NMU vs QA uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2027 +#: pkgs.dbk:2031 msgid "" "Unless you know the maintainer is still active, it is wise to check the " "package to see if it has been orphaned. The current list of orphaned " "packages which haven't had their maintainer set correctly is available at " -"<ulink url=\"http://qa.debian.org/orphaned.html\"></ulink>. If you perform " -"an NMU on an improperly orphaned package, please set the maintainer to " -"``Debian QA Group <packages@qa.debian.org>''." +"<ulink url=\"&url-debian-qa-orphaned;\"></ulink>. If you perform an NMU on " +"an improperly orphaned package, please set the maintainer to <literal>Debian " +"QA Group <packages@qa.debian.org></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2037 +#: pkgs.dbk:2041 msgid "Who can do an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2039 +#: pkgs.dbk:2043 msgid "" "Only official, registered Debian Developers can do binary or source NMUs. A " -"Debian Developer is someone who has their key in the Debian key ring. " -"Non-developers, however, are encouraged to download the source package and " -"start hacking on it to fix problems; however, rather than doing an NMU, they " +"Debian Developer is someone who has their key in the Debian key ring. Non-" +"developers, however, are encouraged to download the source package and start " +"hacking on it to fix problems; however, rather than doing an NMU, they " "should just submit worthwhile patches to the Bug Tracking System. " "Maintainers almost always appreciate quality patches and bug reports." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2049 +#: pkgs.dbk:2053 msgid "Terminology" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2051 +#: pkgs.dbk:2055 msgid "" "There are two new terms used throughout this section: ``binary-only NMU'' " "and ``source NMU''. These terms are used with specific technical meaning " "throughout this document. Both binary-only and source NMUs are similar, " "since they involve an upload of a package by a developer who is not the " -"official maintainer of that package. That is why it's a " -"<emphasis>non-maintainer</emphasis> upload." +"official maintainer of that package. That is why it's a <emphasis>non-" +"maintainer</emphasis> upload." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2059 +#: pkgs.dbk:2063 msgid "" "A source NMU is an upload of a package by a developer who is not the " "official maintainer, for the purposes of fixing a bug in the package. " "Source NMUs always involves changes to the source (even if it is just a " "change to <filename>debian/changelog</filename>). This can be either a " "change to the upstream source, or a change to the Debian bits of the " -"source. Note, however, that source NMUs may also include " -"architecture-dependent packages, as well as an updated Debian diff." +"source. Note, however, that source NMUs may also include architecture-" +"dependent packages, as well as an updated Debian diff." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2068 +#: pkgs.dbk:2072 msgid "" "A binary-only NMU is a recompilation and upload of a binary package for a " "given architecture. As such, it is usually part of a porting effort. A " "binary-only NMU is a non-maintainer uploaded binary version of a package, " "with no source changes required. There are many cases where porters must " "fix problems in the source in order to get them to compile for their target " -"architecture; that would be considered a source NMU rather than a " -"binary-only NMU. As you can see, we don't distinguish in terminology " -"between porter NMUs and non-porter NMUs." +"architecture; that would be considered a source NMU rather than a binary-" +"only NMU. As you can see, we don't distinguish in terminology between " +"porter NMUs and non-porter NMUs." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2078 +#: pkgs.dbk:2082 msgid "" "Both classes of NMUs, source and binary-only, can be lumped under the term " "``NMU''. However, this often leads to confusion, since most people think " @@ -2833,50 +2795,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2088 +#: pkgs.dbk:2092 msgid "Collaborative maintenance" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2090 +#: pkgs.dbk:2094 msgid "" "Collaborative maintenance is a term describing the sharing of Debian package " "maintenance duties by several people. This collaboration is almost always a " "good idea, since it generally results in higher quality and faster bug fix " "turnaround times. It is strongly recommended that packages with a priority " -"of <literal>Standard</literal> or which are part of the base set have " -"co-maintainers." +"of <literal>Standard</literal> or which are part of the base set have co-" +"maintainers." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2098 +#: pkgs.dbk:2102 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 " -"<literal>Maintainer</literal> field of the " -"<filename>debian/control</filename> file. Co-maintainers are all the other " -"maintainers." +"<literal>Maintainer</literal> field of the <filename>debian/control</" +"filename> file. Co-maintainers are all the other maintainers." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2104 +#: pkgs.dbk:2108 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:2110 +#: pkgs.dbk:2114 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 " -"control system, such as <command>CVS</command> or " -"<command>Subversion</command>. Alioth (see <xref linkend=\"alioth\"/> ) " -"provides such tools, amongst others." +"control system, such as <command>CVS</command> or <command>Subversion</" +"command>. Alioth (see <xref linkend=\"alioth\"/> ) provides such tools, " +"amongst others." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2118 +#: pkgs.dbk:2122 msgid "" "Add the co-maintainer's correct maintainer name and address to the " "<literal>Uploaders</literal> field in the global part of the " @@ -2884,20 +2845,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><screen> -#: pkgs.dbk:2123 +#: pkgs.dbk:2127 #, no-wrap -msgid ": John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>" +msgid "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2128 +#: pkgs.dbk:2132 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:2134 +#: pkgs.dbk:2138 msgid "" "Another form of collaborative maintenance is team maintenance, which is " "recommended if you maintain several packages with the same group of " @@ -2907,7 +2868,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2143 +#: pkgs.dbk:2147 msgid "" "Put the team member mainly responsible for the package in the Maintainer " "field. In the Uploaders, put the mailing list address, and the team members " @@ -2915,7 +2876,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2150 +#: pkgs.dbk:2154 msgid "" "Put the mailing list address in the Maintainer field. In the Uploaders " "field, put the team members who care for the package. In this case, you " @@ -2924,7 +2885,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2158 +#: pkgs.dbk:2162 msgid "" "In any case, it is a bad idea to automatically put all team members in the " "Uploaders field. It clutters the Developer's Package Overview listing (see " @@ -2933,39 +2894,39 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2166 +#: pkgs.dbk:2170 msgid "The testing distribution" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2168 +#: pkgs.dbk:2172 msgid "Basics" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2170 +#: pkgs.dbk:2174 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2174 +#: pkgs.dbk:2178 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 " -"release-critical bugs at the time they're installed into testing. This way, " +"make them uninstallable; they also have to have generally no known release-" +"critical bugs at the time they're installed into testing. This way, " "`testing' should always be close to being a release candidate. Please see " "below for details." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2183 +#: pkgs.dbk:2187 msgid "Updates from unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2185 +#: pkgs.dbk:2189 msgid "" "The scripts that update the <emphasis>testing</emphasis> distribution are " "run each day after the installation of the updated packages; these scripts " @@ -2976,14 +2937,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2193 +#: pkgs.dbk:2197 msgid "" "The inclusion of a package from <emphasis>unstable</emphasis> is conditional " "on the following:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2199 +#: pkgs.dbk:2203 msgid "" "The package must have been available in <emphasis>unstable</emphasis> for 2, " "5 or 10 days, depending on the urgency (high, medium or low). Please note " @@ -2994,14 +2955,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2208 +#: pkgs.dbk:2212 msgid "" "It must have the same number or fewer release-critical bugs than the version " "currently available in <emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2214 +#: pkgs.dbk:2218 msgid "" "It must be available on all architectures on which it has previously been " "built in unstable. <xref linkend=\"madison\"/> may be of interest to check " @@ -3009,14 +2970,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2221 +#: pkgs.dbk:2225 msgid "" "It must not break any dependency of a package which is already available in " "<emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2227 +#: pkgs.dbk:2231 msgid "" "The packages on which it depends must either be available in " "<emphasis>testing</emphasis> or they must be accepted into " @@ -3025,32 +2986,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2235 +#: pkgs.dbk:2239 msgid "" "To find out whether a package is progressing into testing or not, see the " -"testing script output on the <ulink " -"url=\"http://www.debian.org/devel/testing\">web page of the testing " -"distribution</ulink>, or use the program <command>grep-excuses</command> " -"which is in the <systemitem role=\"package\">devscripts</systemitem> " -"package. This utility can easily be used in a <citerefentry> " -"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> " -"</citerefentry> to keep yourself informed of the progression of your " -"packages into <emphasis>testing</emphasis>." +"testing script output on the <ulink url=\"&url-testing-maint;\">web page of " +"the testing distribution</ulink>, or use the program <command>grep-excuses</" +"command> which is in the <systemitem role=\"package\">devscripts</" +"systemitem> package. This utility can easily be used in a <citerefentry> " +"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> </" +"citerefentry> to keep yourself informed of the progression of your packages " +"into <emphasis>testing</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2246 +#: pkgs.dbk:2250 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 " "own by looking for what would break with the inclusion of the package. The " -"<ulink url=\"http://www.debian.org/devel/testing\">testing web page</ulink> " -"gives some more information about the usual problems which may be causing " -"such troubles." +"<ulink url=\"&url-testing-maint;\">testing web page</ulink> gives some more " +"information about the usual problems which may be causing such troubles." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2253 +#: pkgs.dbk:2257 msgid "" "Sometimes, some packages never enter <emphasis>testing</emphasis> because " "the set of inter-relationship is too complicated and cannot be sorted out by " @@ -3058,20 +3017,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2258 +#: pkgs.dbk:2262 msgid "" -"Some further dependency analysis is shown on <ulink " -"url=\"http://bjorn.haxx.se/debian/\"></ulink> — but be warned, this page " -"also shows build dependencies which are not considered by britney." +"Some further dependency analysis is shown on <ulink url=\"http://bjorn.haxx." +"se/debian/\"></ulink> — but be warned, this page also shows build " +"dependencies which are not considered by britney." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2263 +#: pkgs.dbk:2267 msgid "out-of-date" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2265 +#. FIXME: better rename this file than document rampant professionalism? +#: pkgs.dbk:2270 msgid "" "For the testing migration script, outdated means: There are different " "versions in unstable for the release architectures (except for the " @@ -3081,47 +3041,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2272 +#: pkgs.dbk:2277 msgid "Consider this example:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2279 pkgs.dbk:2310 +#: pkgs.dbk:2284 pkgs.dbk:2315 msgid "alpha" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2280 pkgs.dbk:2311 +#: pkgs.dbk:2285 pkgs.dbk:2316 msgid "arm" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2285 pkgs.dbk:2317 pkgs.dbk:2377 +#: pkgs.dbk:2290 pkgs.dbk:2322 pkgs.dbk:2382 msgid "testing" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2286 pkgs.dbk:2291 pkgs.dbk:2318 pkgs.dbk:2319 pkgs.dbk:2326 +#: pkgs.dbk:2291 pkgs.dbk:2296 pkgs.dbk:2323 pkgs.dbk:2324 pkgs.dbk:2331 msgid "1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2287 pkgs.dbk:2320 pkgs.dbk:2325 +#: pkgs.dbk:2292 pkgs.dbk:2325 pkgs.dbk:2330 msgid "-" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2290 pkgs.dbk:2323 pkgs.dbk:2378 +#: pkgs.dbk:2295 pkgs.dbk:2328 pkgs.dbk:2383 msgid "unstable" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2292 pkgs.dbk:2324 +#: pkgs.dbk:2297 pkgs.dbk:2329 msgid "2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2298 +#: pkgs.dbk:2303 msgid "" "The package is out of date on alpha in unstable, and will not go to " "testing. And removing foo from testing would not help at all, the package " @@ -3129,17 +3089,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2303 +#: pkgs.dbk:2308 msgid "However, if ftp-master removes a package in unstable (here on arm):" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2312 +#: pkgs.dbk:2317 msgid "hurd-i386" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2332 +#: pkgs.dbk:2337 msgid "" "In this case, the package is up to date on all release architectures in " "unstable (and the extra hurd-i386 doesn't matter, as it's not a release " @@ -3147,7 +3107,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2337 +#: pkgs.dbk:2342 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 " @@ -3155,105 +3115,104 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2344 +#: pkgs.dbk:2349 msgid "Removals from testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2346 +#: pkgs.dbk:2351 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 " "every other sense. Suppose e.g. that <emphasis>a</emphasis> cannot be " -"installed with the new version of <emphasis>b</emphasis>; then " -"<emphasis>a</emphasis> may be removed to allow <emphasis>b</emphasis> in." +"installed with the new version of <emphasis>b</emphasis>; then <emphasis>a</" +"emphasis> may be removed to allow <emphasis>b</emphasis> in." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2353 +#: pkgs.dbk:2358 msgid "" "Of course, there is another reason to remove a package from testing: It's " "just too buggy (and having a single RC-bug is enough to be in this state)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2357 +#: pkgs.dbk:2362 msgid "" "Furthermore, if a package has been removed from unstable, and no package in " "testing depends on it any more, then it will automatically be removed." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2363 +#: pkgs.dbk:2368 msgid "circular dependencies" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2365 +#: pkgs.dbk:2370 msgid "" "A situation which is not handled very well by britney is if package " -"<emphasis>a</emphasis> depends on the new version of package " -"<emphasis>b</emphasis>, and vice versa." +"<emphasis>a</emphasis> depends on the new version of package <emphasis>b</" +"emphasis>, and vice versa." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2370 +#: pkgs.dbk:2375 msgid "An example of this is:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2383 +#: pkgs.dbk:2388 msgid "a" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2384 +#: pkgs.dbk:2389 msgid "1; depends: b=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2385 +#: pkgs.dbk:2390 msgid "2; depends: b=2" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2388 +#: pkgs.dbk:2393 msgid "b" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2389 +#: pkgs.dbk:2394 msgid "1; depends: a=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2390 +#: pkgs.dbk:2395 msgid "2; depends: a=2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2396 +#: pkgs.dbk:2401 msgid "" "Neither package <emphasis>a</emphasis> nor package <emphasis>b</emphasis> is " "considered for update." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2400 +#: pkgs.dbk:2405 msgid "" "Currently, this requires some manual hinting from the release team. Please " -"contact them by sending mail to " -"<email>debian-release@lists.debian.org</email> if this happens to one of " -"your packages." +"contact them by sending mail to &email-debian-release; if this happens to " +"one of your packages." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2407 +#: pkgs.dbk:2412 msgid "influence of package in testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2409 +#: pkgs.dbk:2414 msgid "" "Generally, there is nothing that the status of a package in testing means " "for transition of the next version from unstable to testing, with two " @@ -3267,7 +3226,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2419 +#: pkgs.dbk:2424 msgid "" "In summary this means: The only influence that a package being in testing " "has on a new version of the same package is that the new version might go in " @@ -3275,17 +3234,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2426 +#: pkgs.dbk:2431 msgid "details" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2428 +#: pkgs.dbk:2433 msgid "If you are interested in details, this is how britney works:" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2431 +#: pkgs.dbk:2436 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 " @@ -3298,7 +3257,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2440 +#: pkgs.dbk:2445 msgid "" "Now, the more complex part happens: Britney tries to update testing with the " "valid candidates; first, each package alone, and then larger and even larger " @@ -3309,29 +3268,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2448 +#: pkgs.dbk:2453 msgid "" -"If you want to see more details, you can look it up on " -"merkel:/org/ftp.debian.org/testing/update_out/ (or there in " -"~aba/testing/update_out to see a setup with a smaller packages file). Via " -"web, it's at <ulink " -"url=\"http://ftp-master.debian.org/testing/update_out_code/\"></ulink>" +"If you want to see more details, you can look it up on merkel:/org/&ftp-" +"debian-org;/testing/update_out/ (or there in ~aba/testing/update_out to see " +"a setup with a smaller packages file). Via web, it's at <ulink url=\"http://" +"&ftp-master-host;/testing/update_out_code/\"></ulink>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2455 +#: pkgs.dbk:2460 msgid "" -"The hints are available via <ulink " -"url=\"http://ftp-master.debian.org/testing/hints/\"></ulink>." +"The hints are available via <ulink url=\"http://&ftp-master-host;/testing/" +"hints/\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2463 +#: pkgs.dbk:2468 msgid "Direct updates to testing" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2465 +#: pkgs.dbk:2470 msgid "" "The testing distribution is fed with packages from unstable according to the " "rules explained above. However, in some cases, it is necessary to upload " @@ -3340,17 +3298,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2471 +#: pkgs.dbk:2476 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 " "have a good reason to upload there. In order to know what a good reason is " "in the release managers' eyes, you should read the instructions that they " -"regularly give on <email>debian-devel-announce@lists.debian.org</email>." +"regularly give on &email-debian-devel-announce;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2478 +#: pkgs.dbk:2483 msgid "" "You should not upload to <emphasis>testing-proposed-updates</emphasis> when " "you can update your packages through <emphasis>unstable</emphasis>. If you " @@ -3362,7 +3320,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2487 +#: pkgs.dbk:2492 msgid "" "Version numbers are usually selected by adding the codename of the testing " "distribution and a running number, like 1.2sarge1 for the first upload " @@ -3370,78 +3328,76 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2492 +#: pkgs.dbk:2497 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:2497 +#: pkgs.dbk:2502 msgid "" -"Make sure that your package really needs to go through " -"<emphasis>testing-proposed-updates</emphasis>, and can't go through " -"unstable;" +"Make sure that your package really needs to go through <emphasis>testing-" +"proposed-updates</emphasis>, and can't go through unstable;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2503 +#: pkgs.dbk:2508 msgid "Make sure that you included only the minimal amount of changes;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2508 -msgid "Make sure that you included an appropriate explanation in the changelog;" +#: pkgs.dbk:2513 +msgid "" +"Make sure that you included an appropriate explanation in the changelog;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2513 +#: pkgs.dbk:2518 msgid "" "Make sure that you've written <emphasis>testing</emphasis> or " "<emphasis>testing-proposed-updates</emphasis> into your target distribution;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2519 +#: pkgs.dbk:2524 msgid "" -"Make sure that you've built and tested your package in " -"<emphasis>testing</emphasis>, not in <emphasis>unstable</emphasis>;" +"Make sure that you've built and tested your package in <emphasis>testing</" +"emphasis>, not in <emphasis>unstable</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2525 +#: pkgs.dbk:2530 msgid "" "Make sure that your version number is higher than the version in " -"<emphasis>testing</emphasis> and " -"<emphasis>testing-proposed-updates</emphasis>, and lower than in " -"<emphasis>unstable</emphasis>;" +"<emphasis>testing</emphasis> and <emphasis>testing-proposed-updates</" +"emphasis>, and lower than in <emphasis>unstable</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2532 +#: pkgs.dbk:2537 msgid "" "After uploading and successful build on all platforms, contact the release " -"team at <email>debian-release@lists.debian.org</email> and ask them to " -"approve your upload." +"team at &email-debian-release; and ask them to approve your upload." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2541 +#: pkgs.dbk:2545 msgid "Frequently asked questions" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2543 +#: pkgs.dbk:2547 msgid "What are release-critical bugs, and how do they get counted?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2545 +#: pkgs.dbk:2549 msgid "" -"All bugs of some higher severities are by default considered " -"release-critical; currently, these are critical, grave, and serious bugs." +"All bugs of some higher severities are by default considered release-" +"critical; currently, these are critical, grave, and serious bugs." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2549 +#: pkgs.dbk:2553 msgid "" "Such bugs are presumed to have an impact on the chances that the package " "will be released with the stable release of Debian: in general, if a package " @@ -3450,7 +3406,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2555 +#: pkgs.dbk:2559 msgid "" "The unstable bug count are all release-critical bugs without either any " "release-tag (such as potato, woody) or with release-tag sid; also, only if " @@ -3460,19 +3416,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2562 +#: pkgs.dbk:2566 msgid "" "This will change post-sarge, as soon as we have versions in the bug tracking " "system." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2568 -msgid "How could installing a package into testing possibly break other packages?" +#: pkgs.dbk:2572 +msgid "" +"How could installing a package into testing possibly break other packages?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2570 +#: pkgs.dbk:2574 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 " @@ -3482,7 +3439,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2577 +#: pkgs.dbk:2581 msgid "" "However, the old version may have provided a binary package with an old " "soname of a library, such as libacme-foo0. Removing the old acmefoo will " @@ -3490,7 +3447,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2582 +#: pkgs.dbk:2586 msgid "" "Evidently, this mainly affects packages which provide changing sets of " "binary packages in different versions (in turn, mainly libraries). However, " @@ -3499,7 +3456,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2588 +#: pkgs.dbk:2592 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 " @@ -3512,8 +3469,9 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2598 +#: pkgs.dbk:2602 msgid "" "If you are having problems with complicated groups of packages like this, " "contact debian-devel or debian-release for help." msgstr "" + diff --git a/po4a/fr/resources.po b/po4a/fr/resources.po index 856c359..dcbbeb6 100644 --- a/po4a/fr/resources.po +++ b/po4a/fr/resources.po @@ -1,59 +1,64 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:16+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: resources.dbk:5 +#: resources.dbk:7 msgid "Resources for Debian Developers" -msgstr "" +msgstr "Ressources pour le responsable Debian" # type: Content of: <chapter><para> -#: resources.dbk:7 +#: resources.dbk:9 msgid "" "In this chapter you will find a very brief road map of the Debian mailing " "lists, the Debian machines which may be available to you as a developer, and " "all the other resources that are available to help you in your maintainer " "work." -msgstr "" +msgstr "Dans ce chapitre, vous trouverez une brève description des listes de" +"diffusion, des machines Debian qui seront à votre disposition en tant" +"que responsable Debian ainsi que toutes les autres ressources à votre" +"disposition pour vous aider dans votre travail de responsable." # type: Content of: <chapter><section><title> -#: resources.dbk:12 +#: resources.dbk:14 msgid "Mailing lists" -msgstr "" +msgstr "Les listes de diffusion" # type: Content of: <chapter><section><para> -#: resources.dbk:14 +#: resources.dbk:16 msgid "" "Much of the conversation between Debian developers (and users) is managed " -"through a wide array of mailing lists we host at <literal><ulink " -"url=\"http://lists.debian.org/\">lists.debian.org</ulink></literal>. To " -"find out more on how to subscribe or unsubscribe, how to post and how not to " -"post, where to find old posts and how to search them, how to contact the " -"list maintainers and see various other information about the mailing lists, " -"please read <ulink url=\"http://www.debian.org/MailingLists/\"></ulink>. " -"This section will only cover aspects of mailing lists that are of particular " -"interest to developers." +"through a wide array of mailing lists we host at <literal><ulink url=" +"\"http://&lists-host;/\">&lists-host;</ulink></literal>. To find out more " +"on how to subscribe or unsubscribe, how to post and how not to post, where " +"to find old posts and how to search them, how to contact the list " +"maintainers and see various other information about the mailing lists, " +"please read <ulink url=\"&url-debian-lists;\"></ulink>. This section will " +"only cover aspects of mailing lists that are of particular interest to " +"developers." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:24 +#: resources.dbk:27 msgid "Basic rules for use" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:26 +#: resources.dbk:29 msgid "" "When replying to messages on the mailing list, please do not send a carbon " "copy (<literal>CC</literal>) to the original poster unless they explicitly " @@ -62,175 +67,166 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:32 +#: resources.dbk:35 msgid "" "Cross-posting (sending the same message to multiple lists) is discouraged. " "As ever on the net, please trim down the quoting of articles you're replying " -"to. In general, please adhere to the usual conventions for posting " -"messages." +"to. In general, please adhere to the usual conventions for posting messages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:37 +#: resources.dbk:40 msgid "" -"Please read the <ulink " -"url=\"http://www.debian.org/MailingLists/#codeofconduct\">code of " +"Please read the <ulink url=\"&url-debian-lists;#codeofconduct\">code of " "conduct</ulink> for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:44 +#: resources.dbk:47 msgid "Core development mailing lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:46 +#: resources.dbk:49 msgid "The core Debian mailing lists that developers should use are:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:51 +#: resources.dbk:54 msgid "" -"<email>debian-devel-announce@lists.debian.org</email>, used to announce " -"important things to developers. All developers are expected to be " -"subscribed to this list." +"&email-debian-devel-announce;, used to announce important things to " +"developers. All developers are expected to be subscribed to this list." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:58 +#: resources.dbk:61 msgid "" -"<email>debian-devel@lists.debian.org</email>, used to discuss various " -"development related technical issues." +"&email-debian-devel;, used to discuss various development related technical " +"issues." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:64 +#: resources.dbk:67 msgid "" -"<email>debian-policy@lists.debian.org</email>, where the Debian Policy is " -"discussed and voted on." +"&email-debian-policy;, where the Debian Policy is discussed and voted on." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:70 +#: resources.dbk:73 msgid "" -"<email>debian-project@lists.debian.org</email>, used to discuss various " -"non-technical issues related to the project." +"&email-debian-project;, used to discuss various non-technical issues related " +"to the project." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:76 +#: resources.dbk:79 msgid "" "There are other mailing lists available for a variety of special topics; see " -"<ulink url=\"http://lists.debian.org/\"></ulink> for a list." +"<ulink url=\"http://&lists-host;/\"></ulink> for a list." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:82 +#: resources.dbk:85 msgid "Special lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:84 +#: resources.dbk:87 msgid "" -"<email>debian-private@lists.debian.org</email> is a special mailing list for " -"private discussions amongst Debian developers. It is meant to be used for " -"posts which for whatever reason should not be published publicly. As such, " -"it is a low volume list, and users are urged not to use " -"<email>debian-private@lists.debian.org</email> unless it is really " -"necessary. Moreover, do <emphasis>not</emphasis> forward email from that " -"list to anyone. Archives of this list are not available on the web for " -"obvious reasons, but you can see them using your shell account on " -"<literal>lists.debian.org</literal> and looking in the " -"<filename>~debian/archive/debian-private</filename> directory." +"&email-debian-private; is a special mailing list for private discussions " +"amongst Debian developers. It is meant to be used for posts which for " +"whatever reason should not be published publicly. As such, it is a low " +"volume list, and users are urged not to use &email-debian-private; unless it " +"is really necessary. Moreover, do <emphasis>not</emphasis> forward email " +"from that list to anyone. Archives of this list are not available on the " +"web for obvious reasons, but you can see them using your shell account on " +"<literal>&lists-host;</literal> and looking in the <filename>&file-debian-" +"private-archive;</filename> directory." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:96 +#: resources.dbk:99 msgid "" -"<email>debian-email@lists.debian.org</email> is a special mailing list used " -"as a grab-bag for Debian related correspondence such as contacting upstream " -"authors about licenses, bugs, etc. or discussing the project with others " -"where it might be useful to have the discussion archived somewhere." +"&email-debian-email; is a special mailing list used as a grab-bag for Debian " +"related correspondence such as contacting upstream authors about licenses, " +"bugs, etc. or discussing the project with others where it might be useful " +"to have the discussion archived somewhere." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:104 +#: resources.dbk:107 msgid "Requesting new development-related lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:106 +#: resources.dbk:109 msgid "" "Before requesting a mailing list that relates to the development of a " "package (or a small group of related packages), please consider if using an " "alias (via a .forward-aliasname file on master.debian.org, which translates " "into a reasonably nice <replaceable>you-aliasname@debian.org</replaceable> " -"address) or a self-managed mailing list on <link " -"linkend=\"alioth\">Alioth</link> is more appropriate." +"address) or a self-managed mailing list on <link linkend=\"alioth\">Alioth</" +"link> is more appropriate." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:114 +#: resources.dbk:117 msgid "" -"If you decide that a regular mailing list on lists.debian.org is really what " -"you want, go ahead and fill in a request, following <ulink " -"url=\"http://www.debian.org/MailingLists/HOWTO_start_list\">the " -"HOWTO</ulink>." +"If you decide that a regular mailing list on &lists-host; is really what you " +"want, go ahead and fill in a request, following <ulink url=\"&url-debian-" +"lists-new;\">the HOWTO</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:123 +#: resources.dbk:126 msgid "IRC channels" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:125 +#: resources.dbk:128 msgid "" "Several IRC channels are dedicated to Debian's development. They are mainly " -"hosted on the <ulink url=\"http://www.oftc.net/oftc/\">Open and free " -"technology community (OFTC)</ulink> network. The " -"<literal>irc.debian.org</literal> DNS entry is an alias to " -"<literal>irc.oftc.net</literal>." +"hosted on the <ulink url=\"&url-oftc;\">Open and free technology community " +"(OFTC)</ulink> network. The <literal>irc.debian.org</literal> DNS entry is " +"an alias to <literal>irc.oftc.net</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:131 +#: resources.dbk:134 msgid "" "The main channel for Debian in general is <emphasis>#debian</emphasis>. " "This is a large, general-purpose channel where users can find recent news in " "the topic and served by bots. <emphasis>#debian</emphasis> is for English " -"speakers; there are also <emphasis>#debian.de</emphasis>, " -"<emphasis>#debian-fr</emphasis>, <emphasis>#debian-br</emphasis> and other " -"similarly named channels for speakers of other languages." +"speakers; there are also <emphasis>#debian.de</emphasis>, <emphasis>#debian-" +"fr</emphasis>, <emphasis>#debian-br</emphasis> and other similarly named " +"channels for speakers of other languages." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:139 +#: resources.dbk:142 msgid "" -"The main channel for Debian development is " -"<emphasis>#debian-devel</emphasis>. It is a very active channel since " -"usually over 150 people are always logged in. It's a channel for people who " -"work on Debian, it's not a support channel (there's " -"<emphasis>#debian</emphasis> for that). It is however open to anyone who " -"wants to lurk (and learn). Its topic is commonly full of interesting " -"information for developers." +"The main channel for Debian development is <emphasis>#debian-devel</" +"emphasis>. It is a very active channel since usually over 150 people are " +"always logged in. It's a channel for people who work on Debian, it's not a " +"support channel (there's <emphasis>#debian</emphasis> for that). It is " +"however open to anyone who wants to lurk (and learn). Its topic is commonly " +"full of interesting information for developers." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:147 +#: resources.dbk:150 msgid "" "Since <emphasis>#debian-devel</emphasis> is an open channel, you should not " -"speak there of issues that are discussed in " -"<email>debian-private@lists.debian.org</email>. There's another channel for " -"this purpose, it's called <emphasis>#debian-private</emphasis> and it's " -"protected by a key. This key is available in the archives of debian-private " -"in <filename>master.debian.org:~debian/archive/debian-private/</filename>, " -"just <command>zgrep</command> for <emphasis>#debian-private</emphasis> in " -"all the files." +"speak there of issues that are discussed in &email-debian-private;. There's " +"another channel for this purpose, it's called <emphasis>#debian-private</" +"emphasis> and it's protected by a key. This key is available in the " +"archives of debian-private in <filename>master.debian.org:&file-debian-" +"private-archive;</filename>, just <command>zgrep</command> for " +"<emphasis>#debian-private</emphasis> in all the files." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:157 +#: resources.dbk:160 msgid "" "There are other additional channels dedicated to specific subjects. " "<emphasis>#debian-bugs</emphasis> is used for coordinating bug squashing " @@ -240,12 +236,12 @@ msgid "" "channels are dedicated to an architecture or a set of packages: " "<emphasis>#debian-bsd</emphasis>, <emphasis>#debian-kde</emphasis>, " "<emphasis>#debian-jr</emphasis>, <emphasis>#debian-edu</emphasis>, " -"<emphasis>#debian-sf</emphasis> (SourceForge package), " -"<emphasis>#debian-oo</emphasis> (OpenOffice package) ..." +"<emphasis>#debian-sf</emphasis> (SourceForge package), <emphasis>#debian-oo</" +"emphasis> (OpenOffice package) ..." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:169 +#: resources.dbk:172 msgid "" "Some non-English developers' channels exist as well, for example " "<emphasis>#debian-devel-fr</emphasis> for French speaking people interested " @@ -253,66 +249,64 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:174 +#: resources.dbk:177 msgid "" "Channels dedicated to Debian also exist on other IRC networks, notably on " -"the <ulink url=\"http://www.freenode.net/\">freenode</ulink> IRC network, " -"which was pointed at by the <literal>irc.debian.org</literal> alias until " -"4th June 2006." +"the <ulink url=\"&url-openprojects;\">freenode</ulink> IRC network, which " +"was pointed at by the <literal>irc.debian.org</literal> alias until 4th June " +"2006." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:179 +#: resources.dbk:183 msgid "" "To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a " "signed mail where you tell what your nick is. Put cloak somewhere in the " -"Subject: header. The nick should be registered: <ulink " -"url=\"http://freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. " -"The mail needs to be signed by a key in the Debian keyring. Please see " -"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenodes " -"documentation</ulink> for more information about cloaks." +"Subject: header. The nick should be registered: <ulink url=\"http://" +"freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. The mail needs " +"to be signed by a key in the Debian keyring. Please see <ulink url=\"http://" +"freenode.net/faq.shtml#projectcloak\">Freenodes documentation</ulink> for " +"more information about cloaks." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:190 +#: resources.dbk:194 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:192 +#: resources.dbk:196 msgid "" "This document contains a lot of information which is useful to Debian " "developers, but it cannot contain everything. Most of the other interesting " -"documents are linked from <ulink url=\"http://www.debian.org/devel/\">The " -"Developers' Corner</ulink>. Take the time to browse all the links, you will " -"learn many more things." +"documents are linked from <ulink url=\"&url-devel-docs;\">The Developers' " +"Corner</ulink>. Take the time to browse all the links, you will learn many " +"more things." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:201 +#: resources.dbk:205 msgid "Debian machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:203 +#: resources.dbk:207 msgid "" "Debian has several computers working as servers, most of which serve " "critical functions in the Debian project. Most of the machines are used for " -"porting activities, and they all have a permanent connection to the " -"Internet." +"porting activities, and they all have a permanent connection to the Internet." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:208 +#: resources.dbk:212 msgid "" "Most of the machines are available for individual developers to use, as long " -"as the developers follow the rules set forth in the <ulink " -"url=\"http://www.debian.org/devel/dmup\">Debian Machine Usage " -"Policies</ulink>." +"as the developers follow the rules set forth in the <ulink url=\"&url-dmup;" +"\">Debian Machine Usage Policies</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:213 +#: resources.dbk:217 msgid "" "Generally speaking, you can use these machines for Debian-related purposes " "as you see fit. Please be kind to system administrators, and do not use up " @@ -322,7 +316,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:220 +#: resources.dbk:224 msgid "" "Please take care to protect your Debian passwords and SSH keys installed on " "Debian machines. Avoid login or upload methods which send passwords over " @@ -330,162 +324,160 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:225 +#: resources.dbk:229 msgid "" "Please do not put any material that doesn't relate to Debian on the Debian " "servers, unless you have prior permission." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:229 +#: resources.dbk:233 msgid "" -"The current list of Debian machines is available at <ulink " -"url=\"http://db.debian.org/machines.cgi\"></ulink>. That web page contains " -"machine names, contact information, information about who can log in, SSH " -"keys etc." +"The current list of Debian machines is available at <ulink url=\"&url-devel-" +"machines;\"></ulink>. That web page contains machine names, contact " +"information, information about who can log in, SSH keys etc." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:235 +#: resources.dbk:239 msgid "" "If you have a problem with the operation of a Debian server, and you think " "that the system operators need to be notified of this problem, the Debian " -"system administrator team is reachable at " -"<email>debian-admin@lists.debian.org</email>." +"system administrator team is reachable at <email>debian-admin@&lists-host;</" +"email>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:241 +#: resources.dbk:245 msgid "" "If you have a problem with a certain service, not related to the system " "administration (such as packages to be removed from the archive, suggestions " -"for the web site, etc.), generally you'll report a bug against a " -"``pseudo-package''. See <xref linkend=\"submit-bug\"/> for information on " -"how to submit bugs." +"for the web site, etc.), generally you'll report a bug against a ``pseudo-" +"package''. See <xref linkend=\"submit-bug\"/> for information on how to " +"submit bugs." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:248 +#: resources.dbk:252 msgid "" "Some of the core servers are restricted, but the information from there is " "mirrored to another server." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:252 +#: resources.dbk:256 msgid "The bugs server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:254 +#: resources.dbk:258 msgid "" -"<literal>bugs.debian.org</literal> is the canonical location for the Bug " +"<literal>&bugs-host;</literal> is the canonical location for the Bug " "Tracking System (BTS)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:258 resources.dbk:276 +#: resources.dbk:262 resources.dbk:280 msgid "It is restricted; a mirror is available on <literal>merkel</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:261 +#: resources.dbk:265 msgid "" "If you plan on doing some statistical analysis or processing of Debian bugs, " -"this would be the place to do it. Please describe your plans on " -"<email>debian-devel@lists.debian.org</email> before implementing anything, " -"however, to reduce unnecessary duplication of effort or wasted processing " -"time." +"this would be the place to do it. Please describe your plans on &email-" +"debian-devel; before implementing anything, however, to reduce unnecessary " +"duplication of effort or wasted processing time." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:269 +#: resources.dbk:273 msgid "The ftp-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:271 +#: resources.dbk:275 msgid "" -"The <literal>ftp-master.debian.org</literal> server holds the canonical copy " -"of the Debian archive (excluding the non-US packages). Generally, package " +"The <literal>&ftp-master-host;</literal> server holds the canonical copy of " +"the Debian archive (excluding the non-US packages). Generally, package " "uploads go to this server; see <xref linkend=\"upload\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:279 +#: resources.dbk:283 msgid "" "Problems with the Debian FTP archive generally need to be reported as bugs " -"against the <systemitem role=\"package\">ftp.debian.org</systemitem> " -"pseudo-package or an email to <email>ftpmaster@debian.org</email>, but also " -"see the procedures in <xref linkend=\"archive-manip\"/> ." +"against the <systemitem role=\"package\">&ftp-debian-org;</systemitem> " +"pseudo-package or an email to &email-ftpmaster;, but also see the procedures " +"in <xref linkend=\"archive-manip\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:287 +#: resources.dbk:291 msgid "The non-US server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:289 +#: resources.dbk:293 msgid "" -"The non-US server <literal>non-us.debian.org</literal> was discontinued with " -"the release of sarge. The pseudo-package <systemitem " -"role=\"package\">nonus.debian.org</systemitem> still exists for now." +"The non-US server <literal>&non-us-host;</literal> was discontinued with the " +"release of sarge. The pseudo-package <systemitem role=\"package\">nonus." +"debian.org</systemitem> still exists for now." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:296 +#: resources.dbk:300 msgid "The www-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:298 +#: resources.dbk:302 msgid "" "The main web server is <literal>www-master.debian.org</literal>. It holds " "the official web pages, the face of Debian for most newbies." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:302 +#: resources.dbk:306 msgid "" "If you find a problem with the Debian web server, you should generally " -"submit a bug against the pseudo-package, <systemitem " -"role=\"package\">www.debian.org</systemitem>. Remember to check whether or " -"not someone else has already reported the problem to the <ulink " -"url=\"http://bugs.debian.org/www.debian.org\">Bug Tracking System</ulink>." +"submit a bug against the pseudo-package, <systemitem role=\"package\">www." +"debian.org</systemitem>. Remember to check whether or not someone else has " +"already reported the problem to the <ulink url=\"http://&bugs-host;/&www-" +"debian-org;\">Bug Tracking System</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:311 +#: resources.dbk:315 msgid "The people web server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:313 +#: resources.dbk:317 msgid "" "<literal>people.debian.org</literal> is the server used for developers' own " "web pages about anything related to Debian." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:317 +#: resources.dbk:321 msgid "" "If you have some Debian-specific information which you want to serve on the " -"web, you can do this by putting material in the " -"<filename>public_html</filename> directory under your home directory on " -"<literal>people.debian.org</literal>. This will be accessible at the URL " -"<literal>http://people.debian.org/~<replaceable>your-user-id</replaceable>/</literal>." +"web, you can do this by putting material in the <filename>public_html</" +"filename> directory under your home directory on <literal>people.debian.org</" +"literal>. This will be accessible at the URL <literal>http://people.debian." +"org/~<replaceable>your-user-id</replaceable>/</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:324 +#: resources.dbk:328 msgid "" "You should only use this particular location because it will be backed up, " "whereas on other hosts it won't." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:328 +#: resources.dbk:332 msgid "" "Usually the only reason to use a different host is when you need to publish " "materials subject to the U.S. export restrictions, in which case you can " @@ -493,24 +485,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:333 -msgid "" -"Send mail to <email>debian-devel@lists.debian.org</email> if you have any " -"questions." +#: resources.dbk:337 +msgid "Send mail to &email-debian-devel; if you have any questions." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:339 +#: resources.dbk:342 msgid "The CVS server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:341 +#: resources.dbk:345 msgid "Our CVS server is located on <literal>cvs.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:344 +#: resources.dbk:348 msgid "" "If you need to use a publicly accessible CVS server, for instance, to help " "coordinate work on a package between many different developers, you can " @@ -518,239 +508,172 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:349 +#: resources.dbk:353 msgid "" "Generally, <literal>cvs.debian.org</literal> offers a combination of local " "CVS access, anonymous client-server read-only access, and full client-server " "access through <command>ssh</command>. Also, the CVS area can be accessed " -"read-only via the Web at <ulink url=\"http://cvs.debian.org/\"></ulink>." +"read-only via the Web at <ulink url=\"&url-cvsweb;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:355 +#: resources.dbk:359 msgid "" -"To request a CVS area, send a request via email to " -"<email>debian-admin@debian.org</email>. Include the name of the requested " -"CVS area, the Debian account that should own the CVS root area, and why you " -"need it." +"To request a CVS area, send a request via email to &email-debian-admin;. " +"Include the name of the requested CVS area, the Debian account that should " +"own the CVS root area, and why you need it." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:363 +#: resources.dbk:367 msgid "chroots to different distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:365 +#: resources.dbk:369 msgid "" "On some machines, there are chroots to different distributions available. " "You can use them like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:369 +#: resources.dbk:373 #, no-wrap msgid "" -"% dchroot unstable\n" +"vore$ dchroot unstable\n" "Executing shell in chroot: /org/vore.debian.org/chroots/user/unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:373 +#: resources.dbk:377 msgid "" "In all chroots, the normal user home directories are available. You can " -"find out which chroots are available via " -"<literal>http://db.debian.org/machines.cgi</literal>." +"find out which chroots are available via <literal>&url-devel-machines;</" +"literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:382 +#: resources.dbk:386 msgid "The Developers Database" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:384 +#: resources.dbk:388 msgid "" -"The Developers Database, at <ulink url=\"https://db.debian.org/\"></ulink>, " -"is an LDAP directory for managing Debian developer attributes. You can use " -"this resource to search the list of Debian developers. Part of this " -"information is also available through the finger service on Debian servers, " -"try <command>finger yourlogin@db.debian.org</command> to see what it " -"reports." +"The Developers Database, at <ulink url=\"&url-debian-db;\"></ulink>, is an " +"LDAP directory for managing Debian developer attributes. You can use this " +"resource to search the list of Debian developers. Part of this information " +"is also available through the finger service on Debian servers, try " +"<command>finger yourlogin@db.debian.org</command> to see what it reports." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:391 +#: resources.dbk:396 msgid "" -"Developers can <ulink url=\"https://db.debian.org/login.html\">log into the " -"database</ulink> to change various information about themselves, such as:" +"Developers can <ulink url=\"&url-debian-db-login;\">log into the database</" +"ulink> to change various information about themselves, such as:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:397 +#: resources.dbk:402 msgid "forwarding address for your debian.org email" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:402 +#: resources.dbk:407 msgid "subscription to debian-private" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:407 +#: resources.dbk:412 msgid "whether you are on vacation" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:412 +#: resources.dbk:417 msgid "" "personal information such as your address, country, the latitude and " -"longitude of the place where you live for use in <ulink " -"url=\"http://www.debian.org/devel/developers.loc\">the world map of Debian " -"developers</ulink>, phone and fax numbers, IRC nickname and web page" +"longitude of the place where you live for use in <ulink url=\"&url-worldmap;" +"\">the world map of Debian developers</ulink>, phone and fax numbers, IRC " +"nickname and web page" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:420 +#: resources.dbk:425 msgid "password and preferred shell on Debian Project machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:425 +#: resources.dbk:430 msgid "" "Most of the information is not accessible to the public, naturally. For " "more information please read the online documentation that you can find at " -"<ulink url=\"http://db.debian.org/doc-general.html\"></ulink>." +"<ulink url=\"&url-debian-db-doc;\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:430 +#: resources.dbk:435 msgid "" "Developers can also submit their SSH keys to be used for authorization on " "the official Debian machines, and even add new *.debian.net DNS entries. " -"Those features are documented at <ulink " -"url=\"http://db.debian.org/doc-mail.html\"></ulink>." +"Those features are documented at <ulink url=\"&url-debian-db-mail-gw;\"></" +"ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:438 +#: resources.dbk:443 msgid "The Debian archive" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:440 +#: resources.dbk:445 msgid "" -"The Debian GNU/Linux distribution consists of a lot of packages " -"(<filename>.deb</filename>'s, currently around 9000) and a few additional " +"The &debian-formal; distribution consists of a lot of packages (<filename>." +"deb</filename>'s, currently around &number-of-pkgs;) and a few additional " "files (such as documentation and installation disk images)." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:445 +#: resources.dbk:451 msgid "Here is an example directory tree of a complete Debian archive:" msgstr "" -# type: Content of: <chapter><section><screen> -#: resources.dbk:448 -#, no-wrap -msgid "" -"/stable/main/\n" -"dists/stable/main/binary-i386/\n" -"dists/stable/main/binary-m68k/\n" -"dists/stable/main/binary-alpha/\n" -" ...\n" -"dists/stable/main/source/\n" -" ...\n" -"dists/stable/main/disks-i386/\n" -"dists/stable/main/disks-m68k/\n" -"dists/stable/main/disks-alpha/\n" -" ...\n" -"\n" -"dists/stable/contrib/\n" -"dists/stable/contrib/binary-i386/\n" -"dists/stable/contrib/binary-m68k/\n" -"dists/stable/contrib/binary-alpha/\n" -" ...\n" -"dists/stable/contrib/source/\n" -"\n" -"dists/stable/non-free/\n" -"dists/stable/non-free/binary-i386/\n" -"dists/stable/non-free/binary-m68k/\n" -"dists/stable/non-free/binary-alpha/\n" -" ...\n" -"dists/stable/non-free/source/\n" -"\n" -"dists/testing/\n" -"dists/testing/main/\n" -" ...\n" -"dists/testing/contrib/\n" -" ...\n" -"dists/testing/non-free/\n" -" ...\n" -"\n" -"dists/unstable\n" -"dists/unstable/main/\n" -" ...\n" -"dists/unstable/contrib/\n" -" ...\n" -"dists/unstable/non-free/\n" -" ...\n" -"\n" -"pool/\n" -"pool/main/a/\n" -"pool/main/a/apt/\n" -" ...\n" -"pool/main/b/\n" -"pool/main/b/bash/\n" -" ...\n" -"pool/main/liba/\n" -"pool/main/liba/libalias-perl/\n" -" ...\n" -"pool/main/m/\n" -"pool/main/m/mailx/\n" -" ...\n" -"pool/non-free/n/\n" -"pool/non-free/n/netscape/\n" -" ..." -msgstr "" - # type: Content of: <chapter><section><para> -#: resources.dbk:508 +#: resources.dbk:455 msgid "" "As you can see, the top-level directory contains two directories, " "<filename>dists/</filename> and <filename>pool/</filename>. The latter is a " "“pool” in which the packages actually are, and which is handled by the " "archive maintenance database and the accompanying programs. The former " -"contains the distributions, <emphasis>stable</emphasis>, " -"<emphasis>testing</emphasis> and <emphasis>unstable</emphasis>. The " -"<filename>Packages</filename> and <filename>Sources</filename> files in the " -"distribution subdirectories can reference files in the " -"<filename>pool/</filename> directory. The directory tree below each of the " -"distributions is arranged in an identical manner. What we describe below " -"for <emphasis>stable</emphasis> is equally applicable to the " -"<emphasis>unstable</emphasis> and <emphasis>testing</emphasis> " -"distributions." +"contains the distributions, <emphasis>stable</emphasis>, <emphasis>testing</" +"emphasis> and <emphasis>unstable</emphasis>. The <filename>Packages</" +"filename> and <filename>Sources</filename> files in the distribution " +"subdirectories can reference files in the <filename>pool/</filename> " +"directory. The directory tree below each of the distributions is arranged " +"in an identical manner. What we describe below for <emphasis>stable</" +"emphasis> is equally applicable to the <emphasis>unstable</emphasis> and " +"<emphasis>testing</emphasis> distributions." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:522 +#: resources.dbk:469 msgid "" "<filename>dists/stable</filename> contains three directories, namely " -"<filename>main</filename>, <filename>contrib</filename>, and " -"<filename>non-free</filename>." +"<filename>main</filename>, <filename>contrib</filename>, and <filename>non-" +"free</filename>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:527 +#: resources.dbk:474 msgid "" "In each of the areas, there is a directory for the source packages " "(<filename>source</filename>) and a directory for each supported " -"architecture (<filename>binary-i386</filename>, " -"<filename>binary-m68k</filename>, etc.)." +"architecture (<filename>binary-i386</filename>, <filename>binary-m68k</" +"filename>, etc.)." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:532 +#: resources.dbk:479 msgid "" "The <filename>main</filename> area contains additional directories which " "hold the disk images and some essential pieces of documentation required for " @@ -759,61 +682,59 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:538 +#: resources.dbk:485 msgid "Sections" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:540 +#: resources.dbk:487 msgid "" "The <emphasis>main</emphasis> section of the Debian archive is what makes up " -"the <emphasis role=\"strong\">official Debian GNU/Linux " -"distribution</emphasis>. The <emphasis>main</emphasis> section is official " -"because it fully complies with all our guidelines. The other two sections " -"do not, to different degrees; as such, they are <emphasis " -"role=\"strong\">not</emphasis> officially part of Debian GNU/Linux." +"the <emphasis role=\"strong\">official &debian-formal; distribution</" +"emphasis>. The <emphasis>main</emphasis> section is official because it " +"fully complies with all our guidelines. The other two sections do not, to " +"different degrees; as such, they are <emphasis role=\"strong\">not</" +"emphasis> officially part of &debian-formal;." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:548 +#: resources.dbk:495 msgid "" -"Every package in the main section must fully comply with the <ulink " -"url=\"http://www.debian.org/social_contract#guidelines\">Debian Free " -"Software Guidelines</ulink> (DFSG) and with all other policy requirements as " -"described in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>. The DFSG is our definition of “free software.” Check out " -"the Debian Policy Manual for details." +"Every package in the main section must fully comply with the <ulink url=" +"\"&url-dfsg;\">Debian Free Software Guidelines</ulink> (DFSG) and with all " +"other policy requirements as described in the <ulink url=\"&url-debian-" +"policy;\">Debian Policy Manual</ulink>. The DFSG is our definition of “free " +"software.” Check out the Debian Policy Manual for details." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:556 +#: resources.dbk:503 msgid "" "Packages in the <emphasis>contrib</emphasis> section have to comply with the " -"DFSG, but may fail other requirements. For instance, they may depend on " -"non-free packages." +"DFSG, but may fail other requirements. For instance, they may depend on non-" +"free packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:561 +#: resources.dbk:508 msgid "" -"Packages which do not conform to the DFSG are placed in the " -"<emphasis>non-free</emphasis> section. These packages are not considered as " -"part of the Debian distribution, though we support their use, and we provide " -"infrastructure (such as our bug-tracking system and mailing lists) for " -"non-free software packages." +"Packages which do not conform to the DFSG are placed in the <emphasis>non-" +"free</emphasis> section. These packages are not considered as part of the " +"Debian distribution, though we support their use, and we provide " +"infrastructure (such as our bug-tracking system and mailing lists) for non-" +"free software packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:568 +#: resources.dbk:515 msgid "" -"The <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> contains a more exact definition of the three sections. The " -"above discussion is just an introduction." +"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> contains " +"a more exact definition of the three sections. The above discussion is just " +"an introduction." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:573 +#: resources.dbk:520 msgid "" "The separation of the three sections at the top-level of the archive is " "important for all people who want to distribute Debian, either via FTP " @@ -824,7 +745,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:581 +#: resources.dbk:528 msgid "" "On the other hand, a CD-ROM vendor could easily check the individual package " "licenses of the packages in <emphasis>non-free</emphasis> and include as " @@ -833,24 +754,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:587 +#: resources.dbk:534 msgid "" "Note that the term section is also used to refer to categories which " "simplify the organization and browsing of available packages, e.g. " -"<emphasis>admin</emphasis>, <emphasis>net</emphasis>, " -"<emphasis>utils</emphasis> etc. Once upon a time, these sections " -"(subsections, rather) existed in the form of subdirectories within the " -"Debian archive. Nowadays, these exist only in the Section header fields of " -"packages." +"<emphasis>admin</emphasis>, <emphasis>net</emphasis>, <emphasis>utils</" +"emphasis> etc. Once upon a time, these sections (subsections, rather) " +"existed in the form of subdirectories within the Debian archive. Nowadays, " +"these exist only in the Section header fields of packages." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:597 +#: resources.dbk:544 msgid "Architectures" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:599 +#: resources.dbk:546 msgid "" "In the first days, the Linux kernel was only available for Intel i386 (or " "greater) platforms, and so was Debian. But as Linux became more and more " @@ -858,7 +778,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:604 +#: resources.dbk:551 msgid "" "The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola 680x0 " "(like Atari, Amiga and Macintoshes), MIPS, and PowerPC. The Linux 2.2 " @@ -867,59 +787,56 @@ msgid "" "Therefore, Debian has ports underway; in fact, we also have ports underway " "to non-Linux kernels. Aside from <emphasis>i386</emphasis> (our name for " "Intel x86), there is <emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, " -"<emphasis>powerpc</emphasis>, <emphasis>sparc</emphasis>, " -"<emphasis>hurd-i386</emphasis>, <emphasis>arm</emphasis>, " -"<emphasis>ia64</emphasis>, <emphasis>hppa</emphasis>, " -"<emphasis>s390</emphasis>, <emphasis>mips</emphasis>, " -"<emphasis>mipsel</emphasis> and <emphasis>sh</emphasis> as of this writing." +"<emphasis>powerpc</emphasis>, <emphasis>sparc</emphasis>, <emphasis>hurd-" +"i386</emphasis>, <emphasis>arm</emphasis>, <emphasis>ia64</emphasis>, " +"<emphasis>hppa</emphasis>, <emphasis>s390</emphasis>, <emphasis>mips</" +"emphasis>, <emphasis>mipsel</emphasis> and <emphasis>sh</emphasis> as of " +"this writing." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:618 +#: resources.dbk:565 msgid "" -"Debian GNU/Linux 1.3 is only available as <emphasis>i386</emphasis>. Debian " +"&debian-formal; 1.3 is only available as <emphasis>i386</emphasis>. Debian " "2.0 shipped for <emphasis>i386</emphasis> and <emphasis>m68k</emphasis> " "architectures. Debian 2.1 ships for the <emphasis>i386</emphasis>, " -"<emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, and " -"<emphasis>sparc</emphasis> architectures. Debian 2.2 added support for the " +"<emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, and <emphasis>sparc</" +"emphasis> architectures. Debian 2.2 added support for the " "<emphasis>powerpc</emphasis> and <emphasis>arm</emphasis> architectures. " -"Debian 3.0 added support of five new architectures: " -"<emphasis>ia64</emphasis>, <emphasis>hppa</emphasis>, " -"<emphasis>s390</emphasis>, <emphasis>mips</emphasis> and " -"<emphasis>mipsel</emphasis>." +"Debian 3.0 added support of five new architectures: <emphasis>ia64</" +"emphasis>, <emphasis>hppa</emphasis>, <emphasis>s390</emphasis>, " +"<emphasis>mips</emphasis> and <emphasis>mipsel</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:629 +#: resources.dbk:576 msgid "" "Information for developers and users about the specific ports are available " -"at the <ulink url=\"http://www.debian.org/ports/\">Debian Ports web " -"pages</ulink>." +"at the <ulink url=\"&url-debian-ports;\">Debian Ports web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:635 +#: resources.dbk:582 msgid "Packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:637 +#: resources.dbk:584 msgid "" "There are two types of Debian packages, namely <emphasis>source</emphasis> " "and <emphasis>binary</emphasis> packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:641 +#: resources.dbk:588 msgid "" -"Source packages consist of either two or three files: a " -"<filename>.dsc</filename> file, and either a <filename>.tar.gz</filename> " -"file or both an <filename>.orig.tar.gz</filename> and a " -"<filename>.diff.gz</filename> file." +"Source packages consist of either two or three files: a <filename>.dsc</" +"filename> file, and either a <filename>.tar.gz</filename> file or both an " +"<filename>.orig.tar.gz</filename> and a <filename>.diff.gz</filename> file." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:647 +#: resources.dbk:594 msgid "" "If a package is developed specially for Debian and is not distributed " "outside of Debian, there is just one <filename>.tar.gz</filename> file which " @@ -932,7 +849,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:657 +#: resources.dbk:604 msgid "" "The <filename>.dsc</filename> file lists all the files in the source package " "together with checksums (<command>md5sums</command>) and some additional " @@ -940,31 +857,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:664 +#: resources.dbk:611 msgid "Distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:666 +#: resources.dbk:613 msgid "" "The directory system described in the previous chapter is itself contained " "within <emphasis>distribution directories</emphasis>. Each distribution is " -"actually contained in the <filename>pool</filename> directory in the " -"top-level of the Debian archive itself." +"actually contained in the <filename>pool</filename> directory in the top-" +"level of the Debian archive itself." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:672 +#: resources.dbk:619 msgid "" "To summarize, the Debian archive has a root directory within an FTP server. " "For instance, at the mirror site, <literal>ftp.us.debian.org</literal>, the " -"Debian archive itself is contained in <ulink " -"url=\"ftp://ftp.us.debian.org/debian\">/debian</ulink>, which is a common " -"location (another is <filename>/pub/debian</filename>)." +"Debian archive itself is contained in <ulink url=\"ftp://ftp.us.debian.org/" +"debian\">/debian</ulink>, which is a common location (another is <filename>/" +"pub/debian</filename>)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:679 +#: resources.dbk:626 msgid "" "A distribution comprises Debian source and binary packages, and the " "respective <filename>Sources</filename> and <filename>Packages</filename> " @@ -975,23 +892,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:687 +#: resources.dbk:634 msgid "Stable, testing, and unstable" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:689 +#: resources.dbk:636 msgid "" "There are always distributions called <emphasis>stable</emphasis> (residing " "in <filename>dists/stable</filename>), <emphasis>testing</emphasis> " -"(residing in <filename>dists/testing</filename>), and " -"<emphasis>unstable</emphasis> (residing in " -"<filename>dists/unstable</filename>). This reflects the development process " -"of the Debian project." +"(residing in <filename>dists/testing</filename>), and <emphasis>unstable</" +"emphasis> (residing in <filename>dists/unstable</filename>). This reflects " +"the development process of the Debian project." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:696 +#: resources.dbk:643 msgid "" "Active development is done in the <emphasis>unstable</emphasis> distribution " "(that's why this distribution is sometimes called the <emphasis>development " @@ -1003,7 +919,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:705 +#: resources.dbk:652 msgid "" "The <link linkend=\"testing\">testing</link> distribution is generated " "automatically by taking packages from unstable if they satisfy certain " @@ -1013,7 +929,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:712 +#: resources.dbk:659 msgid "" "After a period of development, once the release manager deems fit, the " "<emphasis>testing</emphasis> distribution is frozen, meaning that the " @@ -1029,32 +945,32 @@ msgid "" "<emphasis>stable</emphasis>, and a new copy is created for the new " "<emphasis>testing</emphasis>, and the previous <emphasis>stable</emphasis> " "is renamed to <emphasis>oldstable</emphasis> and stays there until it is " -"finally archived. On archiving, the contents are moved to " -"<literal>archive.debian.org</literal>)." +"finally archived. On archiving, the contents are moved to <literal>&archive-" +"host;</literal>)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:729 +#: resources.dbk:676 msgid "" "This development cycle is based on the assumption that the " -"<emphasis>unstable</emphasis> distribution becomes " -"<emphasis>stable</emphasis> after passing a period of being in " -"<emphasis>testing</emphasis>. Even once a distribution is considered " -"stable, a few bugs inevitably remain — that's why the stable distribution is " -"updated every now and then. However, these updates are tested very " -"carefully and have to be introduced into the archive individually to reduce " -"the risk of introducing new bugs. You can find proposed additions to " -"<emphasis>stable</emphasis> in the <filename>proposed-updates</filename> " -"directory. Those packages in <filename>proposed-updates</filename> that " -"pass muster are periodically moved as a batch into the stable distribution " -"and the revision level of the stable distribution is incremented (e.g., " -"‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ becomes ‘2.2r5’, and so forth). Please refer " -"to <link linkend=\"upload-stable\">uploads to the " -"<emphasis>stable</emphasis> distribution</link> for details." +"<emphasis>unstable</emphasis> distribution becomes <emphasis>stable</" +"emphasis> after passing a period of being in <emphasis>testing</emphasis>. " +"Even once a distribution is considered stable, a few bugs inevitably remain " +"— that's why the stable distribution is updated every now and then. " +"However, these updates are tested very carefully and have to be introduced " +"into the archive individually to reduce the risk of introducing new bugs. " +"You can find proposed additions to <emphasis>stable</emphasis> in the " +"<filename>proposed-updates</filename> directory. Those packages in " +"<filename>proposed-updates</filename> that pass muster are periodically " +"moved as a batch into the stable distribution and the revision level of the " +"stable distribution is incremented (e.g., ‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ " +"becomes ‘2.2r5’, and so forth). Please refer to <link linkend=\"upload-" +"stable\">uploads to the <emphasis>stable</emphasis> distribution</link> for " +"details." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:746 +#: resources.dbk:693 msgid "" "Note that development under <emphasis>unstable</emphasis> continues during " "the freeze period, since the <emphasis>unstable</emphasis> distribution " @@ -1062,31 +978,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:753 +#: resources.dbk:700 msgid "More information about the testing distribution" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:755 +#: resources.dbk:702 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:759 +#: resources.dbk:706 msgid "" "For more details, please see the <link linkend=\"testing\">information about " "the testing distribution</link>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:765 +#: resources.dbk:712 msgid "Experimental" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:767 +#: resources.dbk:714 msgid "" "The <emphasis>experimental</emphasis> distribution is a special " "distribution. It is not a full distribution in the same sense as `stable' " @@ -1101,25 +1017,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:778 +#: resources.dbk:725 msgid "" "These are the <citerefentry> <refentrytitle>sources.list</refentrytitle> " -"<manvolnum>5</manvolnum> </citerefentry> lines for " -"<emphasis>experimental</emphasis>:" +"<manvolnum>5</manvolnum> </citerefentry> lines for <emphasis>experimental</" +"emphasis>:" msgstr "" -# type: Content of: <chapter><section><section><section><screen> -#: resources.dbk:783 +# type: Content of: <chapter><section><section><section><programlisting> +#: resources.dbk:730 #, no-wrap msgid "" -"http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental " -"main\n" -"deb-src http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ " -"experimental main" +"deb http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental main\n" +"deb-src http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental main" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:787 +#: resources.dbk:734 msgid "" "If there is a chance that the software could do grave damage to a system, it " "is likely to be better to put it into <emphasis>experimental</emphasis>. " @@ -1128,7 +1042,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:793 +#: resources.dbk:740 msgid "" "Whenever there is a new upstream version of a package that introduces new " "features but breaks a lot of old ones, it should either not be uploaded, or " @@ -1141,7 +1055,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:803 +#: resources.dbk:750 msgid "" "Some experimental software can still go into <emphasis>unstable</emphasis>, " "with a few warnings in the description, but that isn't recommended because " @@ -1149,67 +1063,67 @@ msgid "" "<emphasis>testing</emphasis> and thus to <emphasis>stable</emphasis>. You " "should not be afraid to use <emphasis>experimental</emphasis> since it does " "not cause any pain to the ftpmasters, the experimental packages are " -"automatically removed once you upload the package in " -"<emphasis>unstable</emphasis> with a higher version number." +"automatically removed once you upload the package in <emphasis>unstable</" +"emphasis> with a higher version number." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:813 +#: resources.dbk:760 msgid "" "New software which isn't likely to damage your system can go directly into " "<emphasis>unstable</emphasis>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:817 +#: resources.dbk:764 msgid "" "An alternative to <emphasis>experimental</emphasis> is to use your personal " "web space on <literal>people.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:821 +#: resources.dbk:768 msgid "" "When uploading to unstable a package which had bugs fixed in experimental, " -"please consider using the option <literal>-v</literal> to " -"<command>dpkg-buildpackage</command> to finally get them closed." +"please consider using the option <literal>-v</literal> to <command>dpkg-" +"buildpackage</command> to finally get them closed." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:830 +#: resources.dbk:777 msgid "Release code names" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:832 +#: resources.dbk:779 msgid "" "Every released Debian distribution has a <emphasis>code name</emphasis>: " "Debian 1.1 is called `buzz'; Debian 1.2, `rex'; Debian 1.3, `bo'; Debian " "2.0, `hamm'; Debian 2.1, `slink'; Debian 2.2, `potato'; Debian 3.0, `woody'; " -"Debian 3.1, sarge; Debian 4.0, etch. There is also a " -"``pseudo-distribution'', called `sid', which is the current `unstable' " -"distribution; since packages are moved from `unstable' to `testing' as they " -"approach stability, `sid' itself is never released. As well as the usual " -"contents of a Debian distribution, `sid' contains packages for architectures " -"which are not yet officially supported or released by Debian. These " -"architectures are planned to be integrated into the mainstream distribution " -"at some future date." +"Debian 3.1, sarge; Debian 4.0, etch. There is also a ``pseudo-" +"distribution'', called `sid', which is the current `unstable' distribution; " +"since packages are moved from `unstable' to `testing' as they approach " +"stability, `sid' itself is never released. As well as the usual contents of " +"a Debian distribution, `sid' contains packages for architectures which are " +"not yet officially supported or released by Debian. These architectures are " +"planned to be integrated into the mainstream distribution at some future " +"date." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:844 +#: resources.dbk:791 msgid "" "Since Debian has an open development model (i.e., everyone can participate " "and follow the development) even the `unstable' and `testing' distributions " "are distributed to the Internet through the Debian FTP and HTTP server " "network. Thus, if we had called the directory which contains the release " "candidate version `testing', then we would have to rename it to `stable' " -"when the version is released, which would cause all FTP mirrors to " -"re-retrieve the whole distribution (which is quite large)." +"when the version is released, which would cause all FTP mirrors to re-" +"retrieve the whole distribution (which is quite large)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:853 +#: resources.dbk:800 msgid "" "On the other hand, if we called the distribution directories " "<emphasis>Debian-x.y</emphasis> from the beginning, people would think that " @@ -1220,7 +1134,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:861 +#: resources.dbk:808 msgid "" "Thus, the names of the distribution directories in the archive are " "determined by their code names and not their release status (e.g., " @@ -1233,12 +1147,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:875 +#: resources.dbk:822 msgid "Debian mirrors" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:877 +#: resources.dbk:824 msgid "" "The various download archives and the web site have several mirrors " "available in order to relieve our canonical servers from heavy load. In " @@ -1252,17 +1166,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:888 +#: resources.dbk:835 msgid "" "All the information on Debian mirrors, including a list of the available " -"public FTP/HTTP servers, can be found at <ulink " -"url=\"http://www.debian.org/mirror/\"></ulink>. This useful page also " -"includes information and tools which can be helpful if you are interested in " -"setting up your own mirror, either for internal or public access." +"public FTP/HTTP servers, can be found at <ulink url=\"&url-debian-mirrors;" +"\"></ulink>. This useful page also includes information and tools which can " +"be helpful if you are interested in setting up your own mirror, either for " +"internal or public access." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:895 +#: resources.dbk:842 msgid "" "Note that mirrors are generally run by third-parties who are interested in " "helping Debian. As such, developers generally do not have accounts on these " @@ -1270,154 +1184,147 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:902 +#: resources.dbk:849 msgid "The Incoming system" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:904 +#: resources.dbk:851 msgid "" "The Incoming system is responsible for collecting updated packages and " "installing them in the Debian archive. It consists of a set of directories " -"and scripts that are installed on <literal>ftp-master.debian.org</literal>." +"and scripts that are installed on <literal>&ftp-master-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:909 +#: resources.dbk:856 msgid "" "Packages are uploaded by all the maintainers into a directory called " "<filename>UploadQueue</filename>. This directory is scanned every few " -"minutes by a daemon called <command>queued</command>, " -"<filename>*.command</filename>-files are executed, and remaining and " -"correctly signed <filename>*.changes</filename>-files are moved together " -"with their corresponding files to the <filename>unchecked</filename> " -"directory. This directory is not visible for most Developers, as ftp-master " -"is restricted; it is scanned every 15 minutes by the " -"<command>katie</command> script, which verifies the integrity of the " -"uploaded packages and their cryptographic signatures. If the package is " -"considered ready to be installed, it is moved into the " +"minutes by a daemon called <command>queued</command>, <filename>*.command</" +"filename>-files are executed, and remaining and correctly signed <filename>*." +"changes</filename>-files are moved together with their corresponding files " +"to the <filename>unchecked</filename> directory. This directory is not " +"visible for most Developers, as ftp-master is restricted; it is scanned " +"every 15 minutes by the <command>katie</command> script, which verifies the " +"integrity of the uploaded packages and their cryptographic signatures. If " +"the package is considered ready to be installed, it is moved into the " "<filename>accepted</filename> directory. If this is the first upload of the " -"package (or it has new binary packages), it is moved to the " -"<filename>new</filename> directory, where it waits for approval by the " -"ftpmasters. If the package contains files to be installed by hand it is " -"moved to the <filename>byhand</filename> directory, where it waits for " -"manual installation by the ftpmasters. Otherwise, if any error has been " -"detected, the package is refused and is moved to the " -"<filename>reject</filename> directory." +"package (or it has new binary packages), it is moved to the <filename>new</" +"filename> directory, where it waits for approval by the ftpmasters. If the " +"package contains files to be installed by hand it is moved to the " +"<filename>byhand</filename> directory, where it waits for manual " +"installation by the ftpmasters. Otherwise, if any error has been detected, " +"the package is refused and is moved to the <filename>reject</filename> " +"directory." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:928 +#: resources.dbk:875 msgid "" "Once the package is accepted, the system sends a confirmation mail to the " "maintainer and closes all the bugs marked as fixed by the upload, and the " "auto-builders may start recompiling it. The package is now publicly " -"accessible at <ulink url=\"http://incoming.debian.org/\"></ulink> until it " -"is really installed in the Debian archive. This happens only once a day " -"(and is also called the `dinstall run' for historical reasons); the package " -"is then removed from incoming and installed in the pool along with all the " -"other packages. Once all the other updates (generating new " -"<filename>Packages</filename> and <filename>Sources</filename> index files " -"for example) have been made, a special script is called to ask all the " -"primary mirrors to update themselves." +"accessible at <ulink url=\"&url-incoming;\"></ulink> until it is really " +"installed in the Debian archive. This happens only once a day (and is also " +"called the `dinstall run' for historical reasons); the package is then " +"removed from incoming and installed in the pool along with all the other " +"packages. Once all the other updates (generating new <filename>Packages</" +"filename> and <filename>Sources</filename> index files for example) have " +"been made, a special script is called to ask all the primary mirrors to " +"update themselves." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:940 +#: resources.dbk:887 msgid "" "The archive maintenance software will also send the OpenPGP/GnuPG signed " "<filename>.changes</filename> file that you uploaded to the appropriate " -"mailing lists. If a package is released with the " -"<literal>Distribution:</literal> set to `stable', the announcement is sent " -"to <email>debian-changes@lists.debian.org</email>. If a package is released " -"with <literal>Distribution:</literal> set to `unstable' or `experimental', " -"the announcement will be posted to " -"<email>debian-devel-changes@lists.debian.org</email> instead." +"mailing lists. If a package is released with the <literal>Distribution:</" +"literal> set to `stable', the announcement is sent to &email-debian-" +"changes;. If a package is released with <literal>Distribution:</literal> " +"set to `unstable' or `experimental', the announcement will be posted to " +"&email-debian-devel-changes; instead." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:950 +#: resources.dbk:897 msgid "" "Though ftp-master is restricted, a copy of the installation is available to " -"all developers on <literal>merkel.debian.org</literal>." +"all developers on <literal>&ftp-master-mirror;</literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:956 +#: resources.dbk:960 msgid "Package information" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:958 +#: resources.dbk:962 msgid "On the web" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:960 +#: resources.dbk:964 msgid "" -"Each package has several dedicated web pages. " -"<literal>http://packages.debian.org/<replaceable>package-name</replaceable></literal> " -"displays each version of the package available in the various " -"distributions. Each version links to a page which provides information, " -"including the package description, the dependencies, and package download " -"links." +"Each package has several dedicated web pages. <literal>http://&packages-" +"host;/<replaceable>package-name</replaceable></literal> displays each " +"version of the package available in the various distributions. Each version " +"links to a page which provides information, including the package " +"description, the dependencies, and package download links." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:967 +#: resources.dbk:971 msgid "" "The bug tracking system tracks bugs for each package. You can view the bugs " -"of a given package at the URL " -"<literal>http://bugs.debian.org/<replaceable>package-name</replaceable></literal>." +"of a given package at the URL <literal>http://&bugs-host;/" +"<replaceable>package-name</replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:974 +#: resources.dbk:978 msgid "The <command>madison</command> utility" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:976 +#: resources.dbk:980 msgid "" "<command>madison</command> is a command-line utility that is available on " -"<literal>ftp-master.debian.org</literal>, and on the mirror on " -"<literal>merkel.debian.org</literal>. It uses a single argument " -"corresponding to a package name. In result it displays which version of the " -"package is available for each architecture and distribution combination. An " -"example will explain it better." +"<literal>&ftp-master-host;</literal>, and on the mirror on <literal>&ftp-" +"master-mirror;</literal>. It uses a single argument corresponding to a " +"package name. In result it displays which version of the package is " +"available for each architecture and distribution combination. An example " +"will explain it better." msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:984 +#: resources.dbk:988 #, no-wrap msgid "" "$ madison libdbd-mysql-perl\n" -"libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, " -"m68k, powerpc, sparc\n" -"libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, " -"ia64, m68k, mips, mipsel, powerpc, s390, sparc\n" +"libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, m68k, powerpc, sparc\n" +"libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc\n" "libdbd-mysql-perl | 1.2216-2.0.1 | testing | alpha\n" -"libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, " -"i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc" +"libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:991 +#: resources.dbk:995 msgid "" -"In this example, you can see that the version in " -"<emphasis>unstable</emphasis> differs from the version in " -"<emphasis>testing</emphasis> and that there has been a binary-only NMU of " -"the package for the alpha architecture. Each version of the package has " -"been recompiled on most of the architectures." +"In this example, you can see that the version in <emphasis>unstable</" +"emphasis> differs from the version in <emphasis>testing</emphasis> and that " +"there has been a binary-only NMU of the package for the alpha architecture. " +"Each version of the package has been recompiled on most of the architectures." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1001 +#: resources.dbk:1005 msgid "The Package Tracking System" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1003 +#: resources.dbk:1007 msgid "" "The Package Tracking System (PTS) is an email-based tool to track the " "activity of a source package. This really means that you can get the same " @@ -1426,67 +1333,67 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1008 +#: resources.dbk:1012 msgid "" "Each email sent through the PTS is classified under one of the keywords " "listed below. This will let you select the mails that you want to receive." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1012 +#: resources.dbk:1016 msgid "By default you will get:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1019 +#: resources.dbk:1023 msgid "All the bug reports and following discussions." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1027 +#: resources.dbk:1031 msgid "" -"The email notifications from <email>control@bugs.debian.org</email> about " -"bug report status changes." +"The email notifications from <email>control@&bugs-host;</email> about bug " +"report status changes." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1036 +#: resources.dbk:1040 msgid "" "The email notification from <command>katie</command> when an uploaded source " "package is accepted." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1045 +#: resources.dbk:1049 msgid "" "Other warning and error emails from <command>katie</command> (such as an " "override disparity for the section and/or the priority field)." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1054 +#: resources.dbk:1058 msgid "" "Any non-automatic email sent to the PTS by people who wanted to contact the " "subscribers of the package. This can be done by sending mail to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " -"In order to prevent spam, all messages sent to these addresses must contain " -"the <literal>X-PTS-Approved</literal> header with a non-empty value." +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. In " +"order to prevent spam, all messages sent to these addresses must contain the " +"<literal>X-PTS-Approved</literal> header with a non-empty value." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1066 +#: resources.dbk:1070 msgid "" "Regular summary emails about the package's status. Currently, only " "progression in <emphasis>testing</emphasis> is sent." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1073 +#: resources.dbk:1077 msgid "You can also decide to receive additional information:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1080 +#: resources.dbk:1084 msgid "" "The email notification from <command>katie</command> when an uploaded binary " "package is accepted. In other words, whenever a build daemon or a porter " @@ -1495,51 +1402,51 @@ msgid "" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1091 +#: resources.dbk:1095 msgid "" "CVS commit notifications, if the package has a CVS repository and the " "maintainer has set up forwarding commit notifications to the PTS." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1100 +#: resources.dbk:1104 msgid "" "Translations of descriptions or debconf templates submitted to the Debian " "Description Translation Project." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1109 +#: resources.dbk:1113 msgid "" "Information about changes made to the package in derivative distributions " "(for example Ubuntu)." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1116 +#: resources.dbk:1120 msgid "The PTS email interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1118 +#: resources.dbk:1122 msgid "" "You can control your subscription(s) to the PTS by sending various commands " "to <email>pts@qa.debian.org</email>." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1126 +#: resources.dbk:1130 msgid "" "Subscribes <replaceable>email</replaceable> to communications related to the " "source package <replaceable>sourcepackage</replaceable>. Sender address is " -"used if the second argument is not present. If " -"<replaceable>sourcepackage</replaceable> is not a valid source package, " -"you'll get a warning. However if it's a valid binary package, the PTS will " -"subscribe you to the corresponding source package." +"used if the second argument is not present. If <replaceable>sourcepackage</" +"replaceable> is not a valid source package, you'll get a warning. However " +"if it's a valid binary package, the PTS will subscribe you to the " +"corresponding source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1139 +#: resources.dbk:1143 msgid "" "Removes a previous subscription to the source package " "<replaceable>sourcepackage</replaceable> using the specified email address " @@ -1547,21 +1454,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1149 +#: resources.dbk:1153 msgid "" "Removes all subscriptions of the specified email address or the sender " "address if the second argument is left out." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1158 +#: resources.dbk:1162 msgid "" "Lists all subscriptions for the sender or the email address optionally " "specified." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1167 +#: resources.dbk:1171 msgid "" "Tells you the keywords that you are accepting. For an explanation of " "keywords, <link linkend=\"pkg-tracking-system\">see above</link>. Here's a " @@ -1569,78 +1476,79 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1174 -msgid "<literal>bts</literal>: mails coming from the Debian Bug Tracking System" +#: resources.dbk:1178 +msgid "" +"<literal>bts</literal>: mails coming from the Debian Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1179 +#: resources.dbk:1183 msgid "" -"<literal>bts-control</literal>: reply to mails sent to " -"<email>control@bugs.debian.org</email>" +"<literal>bts-control</literal>: reply to mails sent to &email-bts-control;" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1185 +#: resources.dbk:1189 msgid "" "<literal>summary</literal>: automatic summary mails about the state of a " "package" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1191 +#: resources.dbk:1195 msgid "<literal>cvs</literal>: notification of CVS commits" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1196 -msgid "<literal>ddtp</literal>: translations of descriptions and debconf templates" +#: resources.dbk:1200 +msgid "" +"<literal>ddtp</literal>: translations of descriptions and debconf templates" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1201 +#: resources.dbk:1205 msgid "" "<literal>derivatives</literal>: changes made on the package by derivative " "distributions" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1207 +#: resources.dbk:1211 msgid "" "<literal>upload-source</literal>: announce of a new source upload that has " "been accepted" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1213 +#: resources.dbk:1217 msgid "" "<literal>upload-binary</literal>: announce of a new binary-only upload " "(porting)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1219 +#: resources.dbk:1223 msgid "" "<literal>katie-other</literal>: other mails from ftpmasters (override " "disparity, etc.)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1225 +#: resources.dbk:1229 msgid "" "<literal>default</literal>: all the other mails (those which aren't " "automatic)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1235 +#: resources.dbk:1239 msgid "" "Same as the previous item but for the given source package, since you may " "select a different set of keywords for each source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1244 +#: resources.dbk:1248 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the default set of " @@ -1648,7 +1556,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1254 +#: resources.dbk:1258 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the set of accepted " @@ -1656,19 +1564,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1264 +#: resources.dbk:1268 msgid "" "Same as previous item but overrides the keywords list for the indicated " "source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1273 +#: resources.dbk:1277 msgid "Stops processing commands. All following lines are ignored by the bot." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1279 +#: resources.dbk:1283 msgid "" "The <command>pts-subscribe</command> command-line utility (from the " "<systemitem role=\"package\">devscripts</systemitem> package) can be handy " @@ -1677,45 +1585,45 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1287 +#: resources.dbk:1291 msgid "Filtering PTS mails" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1289 +#: resources.dbk:1293 msgid "" "Once you are subscribed to a package, you will get the mails sent to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. " "Those mails have special headers appended to let you filter them in a " "special mailbox (e.g. with <command>procmail</command>). The added headers " -"are <literal>X-Loop</literal>, <literal>X-PTS-Package</literal>, " -"<literal>X-PTS-Keyword</literal> and <literal>X-Unsubscribe</literal>." +"are <literal>X-Loop</literal>, <literal>X-PTS-Package</literal>, <literal>X-" +"PTS-Keyword</literal> and <literal>X-Unsubscribe</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1297 +#: resources.dbk:1301 msgid "" "Here is an example of added headers for a source upload notification on the " "<systemitem role=\"package\">dpkg</systemitem> package:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1301 +#: resources.dbk:1305 #, no-wrap msgid "" -"-Loop: dpkg@packages.qa.debian.org\n" +"X-Loop: dpkg@&pts-host;\n" "X-PTS-Package: dpkg\n" "X-PTS-Keyword: upload-source\n" "X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1309 +#: resources.dbk:1313 msgid "Forwarding CVS commits in the PTS" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1311 +#: resources.dbk:1315 msgid "" "If you use a publicly accessible CVS repository for maintaining your Debian " "package, you may want to forward the commit notification to the PTS so that " @@ -1724,43 +1632,43 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1317 +#: resources.dbk:1321 msgid "" "Once you set up the CVS repository to generate commit notifications, you " "just have to make sure it sends a copy of those mails to " -"<literal><replaceable>sourcepackage</replaceable>_cvs@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>_cvs@&pts-host;</literal>. " "Only the people who accept the <emphasis>cvs</emphasis> keyword will receive " "these notifications." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1326 +#: resources.dbk:1330 msgid "The PTS web interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1328 +#: resources.dbk:1332 msgid "" -"The PTS has a web interface at <ulink " -"url=\"http://packages.qa.debian.org/\"></ulink> that puts together a lot of " -"information about each source package. It features many useful links (BTS, " -"QA stats, contact information, DDTP translation status, buildd logs) and " -"gathers much more information from various places (30 latest changelog " -"entries, testing status, ...). It's a very useful tool if you want to know " -"what's going on with a specific source package. Furthermore there's a form " -"that allows easy subscription to the PTS via email." +"The PTS has a web interface at <ulink url=\"http://&pts-host;/\"></ulink> " +"that puts together a lot of information about each source package. It " +"features many useful links (BTS, QA stats, contact information, DDTP " +"translation status, buildd logs) and gathers much more information from " +"various places (30 latest changelog entries, testing status, ...). It's a " +"very useful tool if you want to know what's going on with a specific source " +"package. Furthermore there's a form that allows easy subscription to the " +"PTS via email." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1338 +#: resources.dbk:1342 msgid "" "You can jump directly to the web page concerning a specific source package " -"with a URL like " -"<literal>http://packages.qa.debian.org/<replaceable>sourcepackage</replaceable></literal>." +"with a URL like <literal>http://&pts-host;/<replaceable>sourcepackage</" +"replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1343 +#: resources.dbk:1347 msgid "" "This web interface has been designed like a portal for the development of " "packages: you can add custom content on your packages' pages. You can add " @@ -1769,95 +1677,96 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1349 +#: resources.dbk:1353 msgid "Static news items can be used to indicate:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1354 +#: resources.dbk:1358 msgid "" -"the availability of a project hosted on <link " -"linkend=\"alioth\">Alioth</link> for co-maintaining the package" +"the availability of a project hosted on <link linkend=\"alioth\">Alioth</" +"link> for co-maintaining the package" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1360 +#: resources.dbk:1364 msgid "a link to the upstream web site" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1365 +#: resources.dbk:1369 msgid "a link to the upstream bug tracker" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1370 +#: resources.dbk:1374 msgid "the existence of an IRC channel dedicated to the software" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1375 +#: resources.dbk:1379 msgid "" "any other available resource that could be useful in the maintenance of the " "package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1381 +#: resources.dbk:1385 msgid "Usual news items may be used to announce that:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1386 +#: resources.dbk:1390 msgid "beta packages are available for testing" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1391 +#: resources.dbk:1395 msgid "final packages are expected for next week" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1396 +#: resources.dbk:1400 msgid "the packaging is about to be redone from scratch" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1401 +#: resources.dbk:1405 msgid "backports are available" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1406 -msgid "the maintainer is on vacation (if they wish to publish this information)" +#: resources.dbk:1410 +msgid "" +"the maintainer is on vacation (if they wish to publish this information)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1411 +#: resources.dbk:1415 msgid "a NMU is being worked on" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1416 +#: resources.dbk:1420 msgid "something important will affect the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1421 +#: resources.dbk:1425 msgid "" "Both kinds of news are generated in a similar manner: you just have to send " "an email either to <email>pts-static-news@qa.debian.org</email> or to " "<email>pts-news@qa.debian.org</email>. The mail should indicate which " "package is concerned by having the name of the source package in a " -"<literal>X-PTS-Package</literal> mail header or in a " -"<literal>Package</literal> pseudo-header (like the BTS reports). If a URL " -"is available in the <literal>X-PTS-Url</literal> mail header or in the " -"<literal>Url</literal> pseudo-header, then the result is a link to that URL " -"instead of a complete news item." +"<literal>X-PTS-Package</literal> mail header or in a <literal>Package</" +"literal> pseudo-header (like the BTS reports). If a URL is available in the " +"<literal>X-PTS-Url</literal> mail header or in the <literal>Url</literal> " +"pseudo-header, then the result is a link to that URL instead of a complete " +"news item." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1432 +#: resources.dbk:1436 msgid "" "Here are a few examples of valid mails used to generate news items in the " "PTS. The first one adds a link to the cvsweb interface of debian-cd in the " @@ -1865,19 +1774,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1437 +#: resources.dbk:1441 #, no-wrap msgid "" -": Raphael Hertzog <hertzog@debian.org>\n" +"From: Raphael Hertzog <hertzog@debian.org>\n" "To: pts-static-news@qa.debian.org\n" "Subject: Browse debian-cd CVS repository with cvsweb\n" "\n" "Package: debian-cd\n" -"Url: http://cvs.debian.org/debian-cd/" +"Url: &url-cvsweb;debian-cd/" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1445 +#: resources.dbk:1449 msgid "" "The second one is an announcement sent to a mailing list which is also sent " "to the PTS so that it is published on the PTS web page of the package. Note " @@ -1885,25 +1794,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1450 +#: resources.dbk:1454 #, no-wrap msgid "" ": Raphael Hertzog <hertzog@debian.org>\n" -"To: debian-gtk-gnome@lists.debian.org\n" +"To: debian-gtk-gnome@&lists-host;\n" "Bcc: pts-news@qa.debian.org\n" "Subject: Galeon 2.0 backported for woody\n" "X-PTS-Package: galeon\n" "\n" "Hello gnomers!\n" "\n" -"I'm glad to announce that galeon has been backported for woody. You'll " -"find\n" +"I'm glad to announce that galeon has been backported for woody. You'll find\n" "everything here:\n" "..." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1463 +#: resources.dbk:1467 msgid "" "Think twice before adding a news item to the PTS because you won't be able " "to remove it later and you won't be able to edit it either. The only thing " @@ -1912,24 +1820,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1473 +#: resources.dbk:1477 msgid "Developer's packages overview" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1475 +#: resources.dbk:1479 msgid "" -"A QA (quality assurance) web portal is available at <ulink " -"url=\"http://qa.debian.org/developer.php\"></ulink> which displays a table " -"listing all the packages of a single developer (including those where the " -"party is listed as a co-maintainer). The table gives a good summary about " -"the developer's packages: number of bugs by severity, list of available " -"versions in each distribution, testing status and much more including links " -"to any other useful information." +"A QA (quality assurance) web portal is available at <ulink url=\"&url-ddpo;" +"\"></ulink> which displays a table listing all the packages of a single " +"developer (including those where the party is listed as a co-maintainer). " +"The table gives a good summary about the developer's packages: number of " +"bugs by severity, list of available versions in each distribution, testing " +"status and much more including links to any other useful information." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1484 +#: resources.dbk:1488 msgid "" "It is a good idea to look up your own data regularly so that you don't " "forget any open bugs, and so that you don't forget which packages are your " @@ -1937,12 +1844,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1491 +#: resources.dbk:1495 msgid "Debian *Forge: Alioth" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1493 +#: resources.dbk:1497 msgid "" "Alioth is a fairly new Debian service, based on a slightly modified version " "of the GForge software (which evolved from SourceForge). This software " @@ -1952,7 +1859,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1500 +#: resources.dbk:1504 msgid "" "It is intended to provide facilities to free software projects backed or led " "by Debian, facilitate contributions from external developers to projects " @@ -1961,7 +1868,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1506 +#: resources.dbk:1510 msgid "" "All Debian developers automatically have an account on Alioth. They can " "activate it by using the recover password facility. External developers can " @@ -1969,27 +1876,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1511 -msgid "" -"For more information please visit <ulink " -"url=\"http://alioth.debian.org/\"></ulink>." +#: resources.dbk:1515 +msgid "For more information please visit <ulink url=\"&url-alioth;\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1517 +#: resources.dbk:1521 msgid "Goodies for Developers" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1519 +#: resources.dbk:1523 msgid "LWN Subscriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1521 +#: resources.dbk:1525 msgid "" "Since October of 2002, HP has sponsored a subscription to LWN for all " "interested Debian developers. Details on how to get access to this benefit " -"are in <ulink " -"url=\"http://lists.debian.org/debian-devel-announce/2002/10/msg00018.html\"></ulink>." +"are in <ulink url=\"http://&lists-host;/debian-devel-announce/2002/10/" +"msg00018.html\"></ulink>." msgstr "" + diff --git a/po4a/fr/scope.po b/po4a/fr/scope.po index 2154e96..35bf6ac 100644 --- a/po4a/fr/scope.po +++ b/po4a/fr/scope.po @@ -1,72 +1,89 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:12+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 22:30+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: scope.dbk:5 +#: scope.dbk:7 msgid "Scope of This Document" -msgstr "" +msgstr "Portée de ce document" # type: Content of: <chapter><para> -#: scope.dbk:7 +#: scope.dbk:9 msgid "" "The purpose of this document is to provide an overview of the recommended " "procedures and the available resources for Debian developers." -msgstr "" +msgstr "Le but de ce document est de donner une vue d'ensemble des procédures à " +"suivre et des ressources mises à la disposition des développeurs Debian." # type: Content of: <chapter><para> -#: scope.dbk:11 +#: scope.dbk:14 msgid "" "The procedures discussed within include how to become a maintainer (<xref " -"linkend=\"new-maintainer\"/> ); how to create new packages (<xref " -"linkend=\"newpackage\"/> ) and how to upload packages (<xref " -"linkend=\"upload\"/> ); how to handle bug reports (<xref " -"linkend=\"bug-handling\"/> ); how to move, remove, or orphan packages (<xref " -"linkend=\"archive-manip\"/> ); how to port packages (<xref " -"linkend=\"porting\"/> ); and how and when to do interim releases of other " -"maintainers' packages (<xref linkend=\"nmu\"/> )." -msgstr "" +"linkend=\"new-maintainer\"/> ); how to create new packages (<xref linkend=" +"\"newpackage\"/> ) and how to upload packages (<xref linkend=\"upload\"/> ); " +"how to handle bug reports (<xref linkend=\"bug-handling\"/> ); how to move, " +"remove, or orphan packages (<xref linkend=\"archive-manip\"/> ); how to port " +"packages (<xref linkend=\"porting\"/> ); and how and when to do interim " +"releases of other maintainers' packages (<xref linkend=\"nmu\"/> )." +msgstr "Les procédures décrites ci-après expliquent comment devenir responsable" +"Debian (<xref linkend=\"new-maintainer\"/>), comment créer de nouveaux paquets" +"(<xref linkend=\"newpackage\"/>) et comment les installer dans l'archive (<xref linkend=\"upload\"/>), comment gérer les rapports de bogues (<xref linkend=\"bug-handling\"/>), comment déplacer, effacer ou abandonner un paquet" +"(<xref linkend=\"archive-manip\"/>), comment faire le portage d'un paquet (<xref linkend=\"porting\"/>), quand et comment faire la mise à jour du paquet d'un" +"autre responsable (<xref linkend=\"nmu\"/>)." # type: Content of: <chapter><para> -#: scope.dbk:20 +#: scope.dbk:23 msgid "" "The resources discussed in this reference include the mailing lists (<xref " -"linkend=\"mailing-lists\"/> ) and servers (<xref " -"linkend=\"server-machines\"/> ); a discussion of the structure of the Debian " -"archive (<xref linkend=\"archive\"/> ); explanation of the different servers " -"which accept package uploads (<xref linkend=\"upload-ftp-master\"/> ); and a " -"discussion of resources which can help maintainers with the quality of their " -"packages (<xref linkend=\"tools\"/> )." -msgstr "" +"linkend=\"mailing-lists\"/> ) and servers (<xref linkend=\"server-machines\"/" +"> ); a discussion of the structure of the Debian archive (<xref linkend=" +"\"archive\"/> ); explanation of the different servers which accept package " +"uploads (<xref linkend=\"upload-ftp-master\"/> ); and a discussion of " +"resources which can help maintainers with the quality of their packages " +"(<xref linkend=\"tools\"/> )." +msgstr "Les ressources présentées dans ce manuel incluent les listes de" +"diffusion (<xref linkend=\"mailing-lists\"/>) et les serveurs (<xref linkend=\"server-machines\"/>), une présentation de la structure de l'archive" +"Debian (<xref linkend=\"archive\"/>), des explications sur les serveurs qui" +"acceptent les mises à jour de paquets (<xref linkend=\"upload-ftp-master\"/>) et" +"une présentation des outils qui peuvent aider un responsable à améliorer" +"la qualité de ses paquets (<xref linkend=\"tools\"/>)." # type: Content of: <chapter><para> -#: scope.dbk:28 +#: scope.dbk:31 msgid "" "It should be clear that this reference does not discuss the technical " "details of Debian packages nor how to generate them. Nor does this " "reference detail the standards to which Debian software must comply. All of " -"such information can be found in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>." -msgstr "" +"such information can be found in the <ulink url=\"&url-debian-policy;" +"\">Debian Policy Manual</ulink>." +msgstr "Ce manuel de référence ne présente pas les aspects techniques liés aux" +"paquets Debian, ni comment les créer. Il ne décrit pas non plus les" +"règles que doivent respecter les paquets Debian. Cette information est" +"disponible dans la <ulink url=\"&url-debian-policy;\">charte Debian</ulink>." # type: Content of: <chapter><para> -#: scope.dbk:35 +#: scope.dbk:38 msgid "" -"Furthermore, this document is <emphasis>not an expression of formal " -"policy</emphasis>. It contains documentation for the Debian system and " -"generally agreed-upon best practices. Thus, it is not what is called a " -"``normative'' document." -msgstr "" +"Furthermore, this document is <emphasis>not an expression of formal policy</" +"emphasis>. It contains documentation for the Debian system and generally " +"agreed-upon best practices. Thus, it is not what is called a ``normative'' " +"document." +msgstr "De plus ce document <emphasis>n'est pas l'expression d'une politique" +"officielle</emphasis>. Il contient de la documentation sur le système Debian" +"et des conseils pratiques largement suivis. Ce n'est donc pas une sorte" +"de guide de normes." + diff --git a/po4a/fr/tools.po b/po4a/fr/tools.po index 7cca30a..f9f4802 100644 --- a/po4a/fr/tools.po +++ b/po4a/fr/tools.po @@ -1,41 +1,47 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:16+0000\n" +"PO-Revision-Date: 2007-07-01 23:19+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <appendix><title> -#: tools.dbk:5 +#: tools.dbk:7 msgid "Overview of Debian Maintainer Tools" -msgstr "" +msgstr "Aperçu des outils du responsable Debian" # type: Content of: <appendix><para> -#: tools.dbk:7 +#: tools.dbk:9 msgid "" "This section contains a rough overview of the tools available to " "maintainers. The following is by no means complete or definitive, but just " "a guide to some of the more popular tools." -msgstr "" +msgstr "Cette section contient un aperçu rapide des outils dont dispose le" +"responsable. Cette liste n'est ni complète, ni définitive, il s'agit" +"juste d'un guide des outils les plus utilisés." # type: Content of: <appendix><para> -#: tools.dbk:12 +#: tools.dbk:14 msgid "" "Debian maintainer tools are meant to aid developers and free their time for " "critical tasks. As Larry Wall says, there's more than one way to do it." -msgstr "" +msgstr "Les outils du responsable Debian sont destinés à aider les responsables" +"et libérer leur temps pour des tâches plus cruciales. Comme le dit Larry" +"Wall, il y a plus d'une manière de le faire." # type: Content of: <appendix><para> -#: tools.dbk:16 +#: tools.dbk:18 msgid "" "Some people prefer to use high-level package maintenance tools and some do " "not. Debian is officially agnostic on this issue; any tool which gets the " @@ -43,39 +49,49 @@ msgid "" "anyone which tools they should use or how they should go about their duties " "of maintainership. Nor is it meant to endorse any particular tool to the " "exclusion of a competing tool." -msgstr "" +msgstr "Certaines personnes préfèrent utiliser des outils de haut niveau," +"d'autres pas. Debian n'a pas de position officielle sur la" +"question ; tout outil conviendra du moment qu'il fait le" +"boulot. C'est pourquoi cette section n'a pas été conçue pour indiquer à" +"chacun quel outil il doit utiliser ou comment il devrait faire pour" +"gérer sa charge de responsable Debian. Elle n'est pas non plus destinée" +"à favoriser l'utilisation d'un outil aux dépens d'un autre." # type: Content of: <appendix><para> -#: tools.dbk:24 +#: tools.dbk:26 msgid "" "Most of the descriptions of these packages come from the actual package " "descriptions themselves. Further information can be found in the package " "documentation itself. You can also see more info with the command " -"<literal>apt-cache show <package-name></literal>." -msgstr "" +"<command>apt-cache show <package-name></command>." +msgstr "La plupart des descriptions de ces outils proviennent des descriptions" +"de leurs paquets. Vous trouverez plus d'informations dans les" +"documentations de ces paquets. Vous pouvez aussi obtenir plus" +"d'informations avec la commande <literal>apt-cache show" +"<nom_paquet></literal>." # type: Content of: <appendix><section><title> -#: tools.dbk:30 +#: tools.dbk:32 msgid "Core tools" -msgstr "" +msgstr "Outils de base" # type: Content of: <appendix><section><para> -#: tools.dbk:32 +#: tools.dbk:34 msgid "The following tools are pretty much required for any maintainer." -msgstr "" +msgstr "Les outils suivants sont pratiquement nécessaires à tout responsable." # type: Content of: <appendix><section><section><para> -#: tools.dbk:37 +#: tools.dbk:39 msgid "" "<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools " "(including <command>dpkg-source</command>) required to unpack, build, and " -"upload Debian source packages. These utilities contain the fundamental, " -"low-level functionality required to create and manipulate packages; as such, " +"upload Debian source packages. These utilities contain the fundamental, low-" +"level functionality required to create and manipulate packages; as such, " "they are essential for any Debian maintainer." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:48 +#: tools.dbk:50 msgid "" "<systemitem role=\"package\">debconf</systemitem> provides a consistent " "interface to configuring packages interactively. It is user interface " @@ -85,14 +101,14 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:54 +#: tools.dbk:56 msgid "" -"You can find documentation for this package in the <systemitem " -"role=\"package\">debconf-doc</systemitem> package." +"You can find documentation for this package in the <systemitem role=\"package" +"\">debconf-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:58 +#: tools.dbk:60 msgid "" "Many feel that this system should be used for all packages which require " "interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . " @@ -101,7 +117,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:68 +#: tools.dbk:70 msgid "" "<systemitem role=\"package\">fakeroot</systemitem> simulates root " "privileges. This enables you to build packages without being root (packages " @@ -111,12 +127,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:79 +#: tools.dbk:81 msgid "Package lint tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:81 +#: tools.dbk:83 msgid "" "According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a " "Unix C language processor which carries out more thorough checks on the code " @@ -126,7 +142,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:89 +#: tools.dbk:91 msgid "" "<systemitem role=\"package\">lintian</systemitem> dissects Debian packages " "and emits information about bugs and policy violations. It contains " @@ -135,33 +151,33 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:95 +#: tools.dbk:97 msgid "" -"You should periodically get the newest <systemitem " -"role=\"package\">lintian</systemitem> from `unstable' and check over all " -"your packages. Notice that the <literal>-i</literal> option provides " -"detailed explanations of what each error or warning means, what its basis in " -"Policy is, and commonly how you can fix the problem." +"You should periodically get the newest <systemitem role=\"package\">lintian</" +"systemitem> from `unstable' and check over all your packages. Notice that " +"the <literal>-i</literal> option provides detailed explanations of what each " +"error or warning means, what its basis in Policy is, and commonly how you " +"can fix the problem." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:102 +#: tools.dbk:104 msgid "" "Refer to <xref linkend=\"sanitycheck\"/> for more information on how and " "when to use Lintian." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:106 +#: tools.dbk:108 msgid "" "You can also see a summary of all problems reported by Lintian on your " -"packages at <ulink url=\"http://lintian.debian.org/\"></ulink>. These " -"reports contain the latest <command>lintian</command> output for the whole " -"development distribution (unstable)." +"packages at <ulink url=\"&url-lintian;\"></ulink>. These reports contain " +"the latest <command>lintian</command> output for the whole development " +"distribution (unstable)." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:116 +#: tools.dbk:118 msgid "" "<systemitem role=\"package\">linda</systemitem> is another package linter. " "It is similar to <systemitem role=\"package\">lintian</systemitem> but has a " @@ -169,74 +185,72 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:125 +#: tools.dbk:127 msgid "" -"<command>debdiff</command> (from the <systemitem " -"role=\"package\">devscripts</systemitem> package, <xref " -"linkend=\"devscripts\"/> ) compares file lists and control files of two " -"packages. It is a simple regression test, as it will help you notice if the " -"number of binary packages has changed since the last upload, or if something " -"has changed in the control file. Of course, some of the changes it reports " -"will be all right, but it can help you prevent various accidents." +"<command>debdiff</command> (from the <systemitem role=\"package" +"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) " +"compares file lists and control files of two packages. It is a simple " +"regression test, as it will help you notice if the number of binary packages " +"has changed since the last upload, or if something has changed in the " +"control file. Of course, some of the changes it reports will be all right, " +"but it can help you prevent various accidents." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:134 +#: tools.dbk:136 msgid "You can run it over a pair of binary packages:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:137 +#: tools.dbk:139 #, no-wrap -msgid "package_1-1_arch.deb package_2-1_arch.deb" +msgid "debdiff package_1-1_arch.deb package_2-1_arch.deb" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:140 +#: tools.dbk:142 msgid "Or even a pair of changes files:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:143 +#: tools.dbk:145 #, no-wrap -msgid "package_1-1_arch.changes package_2-1_arch.changes" +msgid "debdiff package_1-1_arch.changes package_2-1_arch.changes" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:146 +#: tools.dbk:148 msgid "" -"For more information please see <citerefentry> " -"<refentrytitle>debdiff</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry>." +"For more information please see <citerefentry> <refentrytitle>debdiff</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:155 +#: tools.dbk:157 msgid "Helpers for <filename>debian/rules</filename>" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:157 +#: tools.dbk:159 msgid "" -"Package building tools make the process of writing " -"<filename>debian/rules</filename> files easier. See <xref " -"linkend=\"helper-scripts\"/> for more information about why these might or " -"might not be desired." +"Package building tools make the process of writing <filename>debian/rules</" +"filename> files easier. See <xref linkend=\"helper-scripts\"/> for more " +"information about why these might or might not be desired." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:165 +#: tools.dbk:167 msgid "" "<systemitem role=\"package\">debhelper</systemitem> is a collection of " "programs which can be used in <filename>debian/rules</filename> to automate " -"common tasks related to building binary Debian packages. <systemitem " -"role=\"package\">debhelper</systemitem> includes programs to install various " +"common tasks related to building binary Debian packages. <systemitem role=" +"\"package\">debhelper</systemitem> includes programs to install various " "files into your package, compress files, fix file permissions, and integrate " "your package with the Debian menu system." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:173 +#: tools.dbk:175 msgid "" "Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> " "is broken into several small, simple commands which act in a consistent " @@ -245,81 +259,79 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:179 +#: tools.dbk:181 msgid "" -"There are a number of little <systemitem " -"role=\"package\">debhelper</systemitem> add-on packages, too transient to " -"document. You can see the list of most of them by doing <literal>apt-cache " -"search ^dh-</literal>." +"There are a number of little <systemitem role=\"package\">debhelper</" +"systemitem> add-on packages, too transient to document. You can see the " +"list of most of them by doing <literal>apt-cache search ^dh-</literal>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:188 +#: tools.dbk:190 msgid "" "<systemitem role=\"package\">debmake</systemitem>, a precursor to " -"<systemitem role=\"package\">debhelper</systemitem>, is a more " -"coarse-grained <filename>debian/rules</filename> assistant. It includes two " -"main programs: <command>deb-make</command>, which can be used to help a " +"<systemitem role=\"package\">debhelper</systemitem>, is a more coarse-" +"grained <filename>debian/rules</filename> assistant. It includes two main " +"programs: <command>deb-make</command>, which can be used to help a " "maintainer convert a regular (non-Debian) source archive into a Debian " "source package; and <command>debstd</command>, which incorporates in one big " -"shot the same sort of automated functions that one finds in <systemitem " -"role=\"package\">debhelper</systemitem>." +"shot the same sort of automated functions that one finds in <systemitem role=" +"\"package\">debhelper</systemitem>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:198 +#: tools.dbk:200 msgid "" "The consensus is that <systemitem role=\"package\">debmake</systemitem> is " -"now deprecated in favor of <systemitem " -"role=\"package\">debhelper</systemitem>. It is a bug to use <systemitem " -"role=\"package\">debmake</systemitem> in new packages. New packages using " -"<systemitem role=\"package\">debmake</systemitem> will be rejected from the " -"archive." +"now deprecated in favor of <systemitem role=\"package\">debhelper</" +"systemitem>. It is a bug to use <systemitem role=\"package\">debmake</" +"systemitem> in new packages. New packages using <systemitem role=\"package" +"\">debmake</systemitem> will be rejected from the archive." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:209 +#: tools.dbk:211 msgid "" "The <systemitem role=\"package\">dh-make</systemitem> package contains " "<command>dh_make</command>, a program that creates a skeleton of files " "necessary to build a Debian package out of a source tree. As the name " -"suggests, <command>dh_make</command> is a rewrite of <systemitem " -"role=\"package\">debmake</systemitem> and its template files use dh_* " -"programs from <systemitem role=\"package\">debhelper</systemitem>." +"suggests, <command>dh_make</command> is a rewrite of <systemitem role=" +"\"package\">debmake</systemitem> and its template files use dh_* programs " +"from <systemitem role=\"package\">debhelper</systemitem>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:217 +#: tools.dbk:219 msgid "" "While the rules files generated by <command>dh_make</command> are in general " "a sufficient basis for a working package, they are still just the " "groundwork: the burden still lies on the maintainer to finely tune the " -"generated files and make the package entirely functional and " -"Policy-compliant." +"generated files and make the package entirely functional and Policy-" +"compliant." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:227 +#: tools.dbk:229 msgid "" "<systemitem role=\"package\">yada</systemitem> is another packaging helper " "tool. It uses a <filename>debian/packages</filename> file to auto-generate " "<filename>debian/rules</filename> and other necessary files in the " -"<filename>debian/</filename> subdirectory. The " -"<filename>debian/packages</filename> file contains instruction to build " -"packages and there is no need to create any <filename>Makefile</filename> " -"files. There is possibility to use macro engine similar to the one used in " -"SPECS files from RPM source packages." +"<filename>debian/</filename> subdirectory. The <filename>debian/packages</" +"filename> file contains instruction to build packages and there is no need " +"to create any <filename>Makefile</filename> files. There is possibility to " +"use macro engine similar to the one used in SPECS files from RPM source " +"packages." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:237 +#: tools.dbk:239 msgid "" -"For more informations see <literal><ulink " -"url=\"http://yada.alioth.debian.org/\">YADA site</ulink></literal>." +"For more informations see <literal><ulink url=\"http://yada.alioth.debian." +"org/\">YADA site</ulink></literal>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:245 +#: tools.dbk:247 msgid "" "<systemitem role=\"package\">equivs</systemitem> is another package for " "making packages. It is often suggested for local use if you need to make a " @@ -329,12 +341,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:256 +#: tools.dbk:258 msgid "Package builders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:258 +#: tools.dbk:260 msgid "" "The following packages help with the package building process, general " "driving <command>dpkg-buildpackage</command> as well as handling supporting " @@ -342,7 +354,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:264 +#: tools.dbk:266 msgid "" "<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the " "capability to inject or import Debian source packages into a CVS repository, " @@ -351,7 +363,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:270 +#: tools.dbk:272 msgid "" "These utilities provide an infrastructure to facilitate the use of CVS by " "Debian maintainers. This allows one to keep separate CVS branches of a " @@ -361,7 +373,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:281 +#: tools.dbk:283 msgid "" "The <systemitem role=\"package\">debootstrap</systemitem> package and script " "allows you to bootstrap a Debian base system into any part of your " @@ -370,7 +382,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:287 +#: tools.dbk:289 msgid "" "Having a system like this can be useful in many ways. For instance, you can " "<command>chroot</command> into it if you want to test your build " @@ -379,7 +391,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:297 +#: tools.dbk:299 msgid "" "<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted " "system, and builds a package inside the chroot. It is very useful to check " @@ -389,7 +401,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:303 +#: tools.dbk:305 msgid "" "A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, " "which goes even further by doing the build within a User Mode Linux " @@ -397,31 +409,31 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:312 +#: tools.dbk:314 msgid "" "<systemitem role=\"package\">sbuild</systemitem> is another automated " -"builder. It can use chrooted environments as well. It can be used " -"stand-alone, or as part of a networked, distributed build environment. As " -"the latter, it is part of the system used by porters to build binary " -"packages for all the available architectures. See <xref " -"linkend=\"buildd\"/> for more information, and <ulink " -"url=\"http://buildd.debian.org/\"></ulink> to see the system in action." +"builder. It can use chrooted environments as well. It can be used stand-" +"alone, or as part of a networked, distributed build environment. As the " +"latter, it is part of the system used by porters to build binary packages " +"for all the available architectures. See <xref linkend=\"buildd\"/> for " +"more information, and <ulink url=\"&url-buildd;\"></ulink> to see the system " +"in action." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:324 +#: tools.dbk:326 msgid "Package uploaders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:326 +#: tools.dbk:328 msgid "" "The following packages help automate or simplify the process of uploading " "packages into the official archive." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:332 +#: tools.dbk:334 msgid "" "<systemitem role=\"package\">dupload</systemitem> is a package and a script " "to automatically upload Debian packages to the Debian archive, to log the " @@ -430,18 +442,18 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:342 +#: tools.dbk:344 msgid "" "The <systemitem role=\"package\">dput</systemitem> package and script does " "much the same thing as <systemitem role=\"package\">dupload</systemitem>, " -"but in a different way. It has some features over <systemitem " -"role=\"package\">dupload</systemitem>, such as the ability to check the " -"GnuPG signature and checksums before uploading, and the possibility of " -"running <command>dinstall</command> in dry-run mode after the upload." +"but in a different way. It has some features over <systemitem role=\"package" +"\">dupload</systemitem>, such as the ability to check the GnuPG signature " +"and checksums before uploading, and the possibility of running " +"<command>dinstall</command> in dry-run mode after the upload." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:354 +#: tools.dbk:356 msgid "" "The <systemitem role=\"package\">dcut</systemitem> script (part of the " "package <xref linkend=\"dput\"/> ) helps in removing files from the ftp " @@ -449,12 +461,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:362 +#: tools.dbk:364 msgid "Maintenance automation" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:364 +#: tools.dbk:366 msgid "" "The following tools help automate different maintenance tasks, from adding " "changelog entries or signature lines and looking up bugs in Emacs to making " @@ -462,24 +474,23 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:371 +#: tools.dbk:373 msgid "" "<systemitem role=\"package\">devscripts</systemitem> is a package containing " "wrappers and tools which are very helpful for maintaining your Debian " "packages. Example scripts include <command>debchange</command> and " -"<command>dch</command>, which manipulate your " -"<filename>debian/changelog</filename> file from the command-line, and " -"<command>debuild</command>, which is a wrapper around " -"<command>dpkg-buildpackage</command>. The <command>bts</command> utility is " -"also very helpful to update the state of bug reports on the command line. " -"<command>uscan</command> can be used to watch for new upstream versions of " -"your packages. <command>debrsign</command> can be used to remotely sign a " -"package prior to upload, which is nice when the machine you build the " -"package on is different from where your GPG keys are." +"<command>dch</command>, which manipulate your <filename>debian/changelog</" +"filename> file from the command-line, and <command>debuild</command>, which " +"is a wrapper around <command>dpkg-buildpackage</command>. The <command>bts</" +"command> utility is also very helpful to update the state of bug reports on " +"the command line. <command>uscan</command> can be used to watch for new " +"upstream versions of your packages. <command>debrsign</command> can be used " +"to remotely sign a package prior to upload, which is nice when the machine " +"you build the package on is different from where your GPG keys are." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:385 +#: tools.dbk:387 msgid "" "See the <citerefentry> <refentrytitle>devscripts</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of " @@ -487,18 +498,17 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:394 +#: tools.dbk:396 msgid "" "<systemitem role=\"package\">autotools-dev</systemitem> contains best " -"practices for people who maintain packages which use " -"<command>autoconf</command> and/or <command>automake</command>. Also " -"contains canonical <filename>config.sub</filename> and " -"<filename>config.guess</filename> files which are known to work on all " -"Debian ports." +"practices for people who maintain packages which use <command>autoconf</" +"command> and/or <command>automake</command>. Also contains canonical " +"<filename>config.sub</filename> and <filename>config.guess</filename> files " +"which are known to work on all Debian ports." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:405 +#: tools.dbk:407 msgid "" "<command>dpkg-repack</command> creates Debian package file out of a package " "that has already been installed. If any changes have been made to the " @@ -507,7 +517,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:411 +#: tools.dbk:413 msgid "" "This utility can make it easy to copy packages from one computer to another, " "or to recreate packages which are installed on your system but no longer " @@ -516,7 +526,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:420 +#: tools.dbk:422 msgid "" "<command>alien</command> converts binary packages between various packaging " "formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, " @@ -524,7 +534,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:429 +#: tools.dbk:431 msgid "" "<command>debsums</command> checks installed packages against their MD5 " "sums. Note that not all packages have MD5 sums, since they aren't required " @@ -532,7 +542,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:437 +#: tools.dbk:439 msgid "" "<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp " "package which provides assistance when editing some of the files in the " @@ -542,16 +552,16 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:448 +#: tools.dbk:450 msgid "" -"<command>dpkg-depcheck</command> (from the <systemitem " -"role=\"package\">devscripts</systemitem> package, <xref " -"linkend=\"devscripts\"/> ) runs a command under <command>strace</command> " -"to determine all the packages that were used by the said command." +"<command>dpkg-depcheck</command> (from the <systemitem role=\"package" +"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) runs a " +"command under <command>strace</command> to determine all the packages that " +"were used by the said command." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:454 +#: tools.dbk:456 msgid "" "For Debian packages, this is useful when you have to compose a " "<literal>Build-Depends</literal> line for your new package: running the " @@ -560,70 +570,68 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:460 +#: tools.dbk:462 #, no-wrap -msgid "-depcheck -b debian/rules build" +msgid "dpkg-depcheck -b debian/rules build" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:463 +#: tools.dbk:465 msgid "" "<command>dpkg-depcheck</command> can also be used to check for run-time " "dependencies, especially if your package uses exec(2) to run other programs." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:467 +#: tools.dbk:469 msgid "" -"For more information please see <citerefentry> " -"<refentrytitle>dpkg-depcheck</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry>." +"For more information please see <citerefentry> <refentrytitle>dpkg-depcheck</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:476 +#: tools.dbk:478 msgid "Porting tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:478 +#: tools.dbk:480 msgid "The following tools are helpful for porters and for cross-compilation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:483 +#: tools.dbk:485 msgid "" "<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the " "differences from one architecture to another. For instance, it could tell " -"you which packages need to be ported for architecture " -"<replaceable>Y</replaceable>, based on architecture " -"<replaceable>X</replaceable>." +"you which packages need to be ported for architecture <replaceable>Y</" +"replaceable>, based on architecture <replaceable>X</replaceable>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:493 +#: tools.dbk:495 msgid "" "<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for " "installing libraries and headers for cross-compiling in a way similar to " "<systemitem role=\"package\">dpkg</systemitem>. Furthermore, the " -"functionality of <command>dpkg-buildpackage</command> and " -"<command>dpkg-shlibdeps</command> is enhanced to support cross-compiling." +"functionality of <command>dpkg-buildpackage</command> and <command>dpkg-" +"shlibdeps</command> is enhanced to support cross-compiling." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:504 +#: tools.dbk:506 msgid "Documentation and information" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:506 +#: tools.dbk:508 msgid "" "The following packages provide information for maintainers or help with " "building documentation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:512 +#: tools.dbk:514 msgid "" "<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the " "DebianDoc SGML DTD, which is commonly used for Debian documentation. This " @@ -632,23 +640,24 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:518 +#: tools.dbk:520 msgid "" -"Documentation for the DTD can be found in the <systemitem " -"role=\"package\">debiandoc-sgml-doc</systemitem> package." +"Documentation for the DTD can be found in the <systemitem role=\"package" +"\">debiandoc-sgml-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:526 +#: tools.dbk:544 msgid "" "Contains the public GPG and PGP keys of Debian developers. See <xref " "linkend=\"key-maint\"/> and the package documentation for more information." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:534 +#: tools.dbk:552 msgid "" "<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for " "viewing Debian binary packages. This lets you examine a package without " "unpacking it." msgstr "" + diff --git a/po4a/ja/best-pkging-practices.po b/po4a/ja/best-pkging-practices.po index afae0ad..c3dc93b 100644 --- a/po4a/ja/best-pkging-practices.po +++ b/po4a/ja/best-pkging-practices.po @@ -6,33 +6,33 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: best-pkging-practices.dbk:5 +#: best-pkging-practices.dbk:7 msgid "Best Packaging Practices" msgstr "" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:7 +#: best-pkging-practices.dbk:9 msgid "" -"Debian's quality is largely due to the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>, " -"which defines explicit baseline requirements which all Debian packages must " -"fulfill. Yet there is also a shared history of experience which goes beyond " -"the Debian Policy, an accumulation of years of experience in packaging. " -"Many very talented people have created great tools, tools which help you, " -"the Debian maintainer, create and maintain excellent packages." +"Debian's quality is largely due to the <ulink url=\"&url-debian-policy;" +"\">Debian Policy</ulink>, which defines explicit baseline requirements which " +"all Debian packages must fulfill. Yet there is also a shared history of " +"experience which goes beyond the Debian Policy, an accumulation of years of " +"experience in packaging. Many very talented people have created great " +"tools, tools which help you, the Debian maintainer, create and maintain " +"excellent packages." msgstr "" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:16 +#: best-pkging-practices.dbk:18 msgid "" "This chapter provides some best practices for Debian developers. All " "recommendations are merely that, and are not requirements or policy. These " @@ -41,12 +41,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:22 +#: best-pkging-practices.dbk:24 msgid "Best practices for <filename>debian/rules</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:24 +#: best-pkging-practices.dbk:26 msgid "" "The following recommendations apply to the <filename>debian/rules</filename> " "file. Since <filename>debian/rules</filename> controls the build process " @@ -55,27 +55,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:30 +#: best-pkging-practices.dbk:32 msgid "Helper scripts" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:32 +#: best-pkging-practices.dbk:34 msgid "" "The rationale for using helper scripts in <filename>debian/rules</filename> " "is that they let maintainers use and share common logic among many " "packages. Take for instance the question of installing menu entries: you " -"need to put the file into <filename>/usr/lib/menu</filename> (or " -"<filename>/usr/lib/menu</filename> for executable binary menufiles, if this " -"is needed), and add commands to the maintainer scripts to register and " -"unregister the menu entries. Since this is a very common thing for packages " -"to do, why should each maintainer rewrite all this on their own, sometimes " -"with bugs? Also, supposing the menu directory changed, every package would " -"have to be changed." +"need to put the file into <filename>/usr/lib/menu</filename> (or <filename>/" +"usr/lib/menu</filename> for executable binary menufiles, if this is needed), " +"and add commands to the maintainer scripts to register and unregister the " +"menu entries. Since this is a very common thing for packages to do, why " +"should each maintainer rewrite all this on their own, sometimes with bugs? " +"Also, supposing the menu directory changed, every package would have to be " +"changed." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:43 +#: best-pkging-practices.dbk:45 msgid "" "Helper scripts take care of these issues. Assuming you comply with the " "conventions expected by the helper script, the helper takes care of all the " @@ -85,56 +85,55 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:50 +#: best-pkging-practices.dbk:52 msgid "" "<xref linkend=\"tools\"/> contains a couple of different helpers. The most " -"common and best (in our opinion) helper system is <systemitem " -"role=\"package\">debhelper</systemitem>. Previous helper systems, such as " -"<systemitem role=\"package\">debmake</systemitem>, were monolithic: you " -"couldn't pick and choose which part of the helper you found useful, but had " -"to use the helper to do everything. <systemitem " -"role=\"package\">debhelper</systemitem>, however, is a number of separate " -"little <command>dh_*</command> programs. For instance, " -"<command>dh_installman</command> installs and compresses man pages, " -"<command>dh_installmenu</command> installs menu files, and so on. Thus, it " -"offers enough flexibility to be able to use the little helper scripts, where " -"useful, in conjunction with hand-crafted commands in " +"common and best (in our opinion) helper system is <systemitem role=\"package" +"\">debhelper</systemitem>. Previous helper systems, such as <systemitem " +"role=\"package\">debmake</systemitem>, were monolithic: you couldn't pick " +"and choose which part of the helper you found useful, but had to use the " +"helper to do everything. <systemitem role=\"package\">debhelper</" +"systemitem>, however, is a number of separate little <command>dh_*</command> " +"programs. For instance, <command>dh_installman</command> installs and " +"compresses man pages, <command>dh_installmenu</command> installs menu files, " +"and so on. Thus, it offers enough flexibility to be able to use the little " +"helper scripts, where useful, in conjunction with hand-crafted commands in " "<filename>debian/rules</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:64 +#: best-pkging-practices.dbk:66 msgid "" "You can get started with <systemitem role=\"package\">debhelper</systemitem> " "by reading <citerefentry> <refentrytitle>debhelper</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry>, and looking at the examples that " "come with the package. <command>dh_make</command>, from the <systemitem " -"role=\"package\">dh-make</systemitem> package (see <xref " -"linkend=\"dh-make\"/> ), can be used to convert a vanilla source package to " -"a <systemitem role=\"package\">debhelper</systemitem>ized package. This " -"shortcut, though, should not convince you that you do not need to bother " -"understanding the individual <command>dh_*</command> helpers. If you are " -"going to use a helper, you do need to take the time to learn to use that " -"helper, to learn its expectations and behavior." +"role=\"package\">dh-make</systemitem> package (see <xref linkend=\"dh-make\"/" +"> ), can be used to convert a vanilla source package to a <systemitem role=" +"\"package\">debhelper</systemitem>ized package. This shortcut, though, " +"should not convince you that you do not need to bother understanding the " +"individual <command>dh_*</command> helpers. If you are going to use a " +"helper, you do need to take the time to learn to use that helper, to learn " +"its expectations and behavior." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:77 +#: 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=\"http://arch.debian.org/arch/private/srivasta/\"></ulink>." +"<ulink url=\"&url-rules-files;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:86 +#: best-pkging-practices.dbk:88 msgid "Separating your patches into multiple files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:88 +#: best-pkging-practices.dbk:90 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 " @@ -146,20 +145,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:97 +#: best-pkging-practices.dbk:99 msgid "" "Unfortunately, the packaging system as such currently doesn't provide for " "separating the patches into several files. Nevertheless, there are ways to " "separate patches: the patch files are shipped within the Debian patch file " -"(<filename>.diff.gz</filename>), usually within the " -"<filename>debian/</filename> directory. The only difference is that they " -"aren't applied immediately by dpkg-source, but by the " -"<literal>build</literal> rule of <filename>debian/rules</filename>. " -"Conversely, they are reverted in the <literal>clean</literal> rule." +"(<filename>.diff.gz</filename>), usually within the <filename>debian/</" +"filename> directory. The only difference is that they aren't applied " +"immediately by dpkg-source, but by the <literal>build</literal> rule of " +"<filename>debian/rules</filename>. Conversely, they are reverted in the " +"<literal>clean</literal> rule." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:107 +#: best-pkging-practices.dbk:109 msgid "" "<command>dbs</command> is one of the more popular approaches to this. It " "does all of the above, and provides a facility for creating new and updating " @@ -169,67 +168,66 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:114 +#: best-pkging-practices.dbk:116 msgid "" "<command>dpatch</command> also provides these facilities, but it's intended " -"to be even easier to use. See the package <systemitem " -"role=\"package\">dpatch</systemitem> for documentation and examples (in " -"<filename>/usr/share/doc/dpatch</filename>)." +"to be even easier to use. See the package <systemitem role=\"package" +"\">dpatch</systemitem> for documentation and examples (in <filename>/usr/" +"share/doc/dpatch</filename>)." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:122 +#: best-pkging-practices.dbk:124 msgid "Multiple binary packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:124 +#: best-pkging-practices.dbk:126 msgid "" "A single source package will often build several binary packages, either to " -"provide several flavors of the same software (e.g., the <systemitem " -"role=\"package\">vim</systemitem> source package) or to make several small " +"provide several flavors of the same software (e.g., the <systemitem role=" +"\"package\">vim</systemitem> source package) or to make several small " "packages instead of a big one (e.g., so the user can install only the subset " "needed, and thus save some disk space)." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:131 +#: best-pkging-practices.dbk:133 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 " -"the package's temporary trees. You can do this using " -"<command>install</command> or <command>dh_install</command> from <systemitem " -"role=\"package\">debhelper</systemitem>. Be sure to check the different " -"permutations of the various packages, ensuring that you have the " -"inter-package dependencies set right in <filename>debian/control</filename>." +"the package's temporary trees. You can do this using <command>install</" +"command> or <command>dh_install</command> from <systemitem role=\"package" +"\">debhelper</systemitem>. Be sure to check the different permutations of " +"the various packages, ensuring that you have the inter-package dependencies " +"set right in <filename>debian/control</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:140 +#: best-pkging-practices.dbk:142 msgid "" "The first case is a bit more difficult since it involves multiple recompiles " "of the same software but with different configuration options. The " "<systemitem role=\"package\">vim</systemitem> source package is an example " -"of how to manage this using an hand-crafted " -"<filename>debian/rules</filename> file." +"of how to manage this using an hand-crafted <filename>debian/rules</" +"filename> file." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:150 +#: best-pkging-practices.dbk:154 msgid "Best practices for <filename>debian/control</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:152 +#: best-pkging-practices.dbk:156 msgid "" -"The following practices are relevant to the " -"<filename>debian/control</filename> file. They supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-binary.html#s-descriptions\">Policy " -"on package descriptions</ulink>." +"The following practices are relevant to the <filename>debian/control</" +"filename> file. They supplement the <ulink url=\"&url-debian-policy;ch-" +"binary.html#s-descriptions\">Policy on package descriptions</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:158 +#: best-pkging-practices.dbk:162 msgid "" "The description of the package, as defined by the corresponding field in the " "<filename>control</filename> file, contains both the package synopsis and " @@ -241,12 +239,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:167 +#: best-pkging-practices.dbk:171 msgid "General guidelines for package descriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:169 +#: best-pkging-practices.dbk:173 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, " @@ -256,16 +254,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:176 +#: best-pkging-practices.dbk:180 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 " -"non-technical users. Unless your package really is only for technical " -"users, this is a problem." +"descriptions are technical, that is, are not written to make sense for non-" +"technical users. Unless your package really is only for technical users, " +"this is a problem." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:182 +#: best-pkging-practices.dbk:186 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 — " @@ -275,7 +273,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:189 +#: best-pkging-practices.dbk:193 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 " @@ -283,37 +281,36 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:194 +#: best-pkging-practices.dbk:198 msgid "" "References to the names of any other software packages, protocol names, " "standards, or specifications should use their canonical forms, if one " -"exists. For example, use X Window System, X11, or X; not X Windows, " -"X-Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. " -"Use PostScript, not Postscript or postscript." +"exists. For example, use X Window System, X11, or X; not X Windows, X-" +"Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. Use " +"PostScript, not Postscript or postscript." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:201 +#: best-pkging-practices.dbk:205 msgid "" "If you are having problems writing your description, you may wish to send it " -"along to <email>debian-l10n-english@lists.debian.org</email> and request " -"feedback." +"along to &email-debian-l10n-english; and request feedback." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:208 +#: best-pkging-practices.dbk:211 msgid "The package synopsis, or short description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:210 +#: best-pkging-practices.dbk:213 msgid "" "The synopsis line (the short description) should be concise. It must not " "repeat the package's name (this is policy)." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:214 +#: best-pkging-practices.dbk:217 msgid "" "It's a good idea to think of the synopsis as an appositive clause, not a " "full sentence. An appositive clause is defined in WordNet as a grammatical " @@ -326,48 +323,42 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:223 +#: best-pkging-practices.dbk:226 msgid "" "It might help to imagine that the synopsis is combined with the package name " "in the following way:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:227 +#: best-pkging-practices.dbk:230 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> is a " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> is a <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:230 +#: best-pkging-practices.dbk:233 msgid "Alternatively, it might make sense to think of it as" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:233 +#: best-pkging-practices.dbk:236 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> is " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> is <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:236 +#: best-pkging-practices.dbk:239 msgid "or, if the package name itself is a plural (such as developers-tools)" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:239 +#: best-pkging-practices.dbk:242 #, no-wrap -msgid "" -"<replaceable>package-name</replaceable> are " -"<replaceable>synopsis</replaceable>." +msgid "<replaceable>package-name</replaceable> are <replaceable>synopsis</replaceable>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:242 +#: best-pkging-practices.dbk:245 msgid "" "This way of forming a sentence from the package name and synopsis should be " "considered as a heuristic and not a strict rule. There are some cases where " @@ -375,12 +366,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:249 +#: best-pkging-practices.dbk:252 msgid "The long description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:251 +#: best-pkging-practices.dbk:254 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 " @@ -389,12 +380,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:257 +#: best-pkging-practices.dbk:260 msgid "The long description should consist of full and complete sentences." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:260 +#: best-pkging-practices.dbk:263 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 " @@ -403,7 +394,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:266 +#: best-pkging-practices.dbk:269 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 " @@ -414,42 +405,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:274 +#: best-pkging-practices.dbk:277 msgid "" -"Be careful to avoid spelling and grammar mistakes. Ensure that you " -"spell-check it. Both <command>ispell</command> and " -"<command>aspell</command> have special modes for checking " -"<filename>debian/control</filename> files:" +"Be careful to avoid spelling and grammar mistakes. Ensure that you spell-" +"check it. Both <command>ispell</command> and <command>aspell</command> have " +"special modes for checking <filename>debian/control</filename> files:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:279 +#: best-pkging-practices.dbk:282 #, no-wrap -msgid "-d american -g debian/control" +msgid "ispell -d american -g debian/control" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:282 +#: best-pkging-practices.dbk:285 #, no-wrap -msgid "-d en -D -c debian/control" +msgid "aspell -d en -D -c debian/control" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:285 +#: best-pkging-practices.dbk:288 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:290 +#: best-pkging-practices.dbk:293 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:296 +#: best-pkging-practices.dbk:299 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 " @@ -457,14 +447,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:303 +#: best-pkging-practices.dbk:306 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:309 +#: best-pkging-practices.dbk:312 msgid "" "If the package is experimental, or there are other reasons it should not be " "used, if there are other packages that should be used instead, it should be " @@ -472,7 +462,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:316 +#: best-pkging-practices.dbk:319 msgid "" "How is this package different from the competition? Is it a better " "implementation? more features? different features? Why should I choose this " @@ -480,12 +470,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:325 +#: best-pkging-practices.dbk:332 msgid "Upstream home page" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:327 +#: best-pkging-practices.dbk:334 msgid "" "We recommend that you add the URL for the package's home page to the package " "description in <filename>debian/control</filename>. This information should " @@ -493,7 +483,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:332 +#: best-pkging-practices.dbk:339 #, no-wrap msgid "" ".\n" @@ -501,52 +491,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:336 +#: best-pkging-practices.dbk:343 msgid "" "Note the spaces prepending the line, which serves to break the lines " -"correctly. To see an example of how this displays, see <ulink " -"url=\"http://packages.debian.org/unstable/web/wml\"></ulink>." +"correctly. To see an example of how this displays, see <ulink url=\"&url-eg-" +"desc-upstream-info;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:341 +#: best-pkging-practices.dbk:348 msgid "" -"If there is no home page for the software, this should naturally be left " -"out." +"If there is no home page for the software, this should naturally be left out." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:344 +#: best-pkging-practices.dbk:351 msgid "" "Note that we expect this field will eventually be replaced by a proper " -"<filename>debian/control</filename> field understood by " -"<command>dpkg</command> and <literal>packages.debian.org</literal>. If you " -"don't want to bother migrating the home page from the description to this " -"field, you should probably wait until that is available. Please make sure " -"that this line matches the regular expression <literal>/^ Homepage: [^ " -"]*$/</literal>, as this allows <filename>packages.debian.org</filename> to " -"parse it correctly." +"<filename>debian/control</filename> field understood by <command>dpkg</" +"command> and <literal>&packages-host;</literal>. If you don't want to " +"bother migrating the home page from the description to this field, you " +"should probably wait until that is available. Please make sure that this " +"line matches the regular expression <literal>/^ Homepage: [^ ]*$/</literal>, " +"as this allows <filename>&packages-host;</filename> to parse it correctly." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:355 +#: best-pkging-practices.dbk:362 msgid "Version Control System location" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:357 +#: best-pkging-practices.dbk:364 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:361 +#: best-pkging-practices.dbk:368 msgid "XS-Vcs-Browser" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:363 +#: best-pkging-practices.dbk:370 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 " @@ -554,7 +542,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:368 +#: best-pkging-practices.dbk:375 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 " @@ -562,12 +550,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:375 +#: best-pkging-practices.dbk:382 msgid "XS-Vcs-*" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:377 +#: best-pkging-practices.dbk:384 msgid "" "Value of this field should be a string identifying unequivocally the " "location of the Version Control System repository used to maintain the given " @@ -577,12 +565,11 @@ msgid "" "<literal>cvs</literal>, <literal>darcs</literal>, <literal>git</literal>, " "<literal>hg</literal> (Mercurial), <literal>mtn</literal> (Monotone), " "<literal>svn</literal> (Subversion). It is allowed to specify different VCS " -"fields for the same package: they will all be shown in the PTS web " -"interface." +"fields for the same package: they will all be shown in the PTS web interface." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:388 +#: best-pkging-practices.dbk:395 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 " @@ -596,18 +583,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:399 +#: best-pkging-practices.dbk:406 msgid "" "In the following example, an instance of the field for a Subversion " "repository of the <systemitem role=\"package\">vim</systemitem> package is " "shown. Note how the URL is in the <literal>svn://</literal> scheme (instead " -"of <literal>svn+ssh://</literal>) and how it points to the " -"<filename>trunk/</filename> branch. The use of the " -"<literal>XS-Vcs-Browser</literal> field described above is also shown." +"of <literal>svn+ssh://</literal>) and how it points to the <filename>trunk/</" +"filename> branch. The use of the <literal>XS-Vcs-Browser</literal> field " +"described above is also shown." msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:407 +#: best-pkging-practices.dbk:414 #, no-wrap msgid "" "Source: vim\n" @@ -619,33 +606,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:421 +#: best-pkging-practices.dbk:428 msgid "Best practices for <filename>debian/changelog</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:423 +#: best-pkging-practices.dbk:430 msgid "" -"The following practices supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html#s-changelogs\">Policy " -"on changelog files</ulink>." +"The following practices supplement the <ulink url=\"&url-debian-policy;ch-" +"docs.html#s-changelogs\">Policy on changelog files</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:428 +#: best-pkging-practices.dbk:435 msgid "Writing useful changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:430 +#: best-pkging-practices.dbk:437 msgid "" "The changelog entry for a package revision documents changes in that " -"revision, and only them. Concentrate on describing significant and " -"user-visible changes that were made since the last version." +"revision, and only them. Concentrate on describing significant and user-" +"visible changes that were made since the last version." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:435 +#: best-pkging-practices.dbk:442 msgid "" "Focus on <emphasis>what</emphasis> was changed — who, how and when are " "usually less important. Having said that, remember to politely attribute " @@ -654,7 +640,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:441 +#: best-pkging-practices.dbk:448 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 " @@ -664,7 +650,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:448 +#: best-pkging-practices.dbk:455 msgid "" "Use common English so that the majority of readers can comprehend it. Avoid " "abbreviations, tech-speak and jargon when explaining changes that close " @@ -673,7 +659,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:454 +#: best-pkging-practices.dbk:461 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 " @@ -682,20 +668,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:460 +#: best-pkging-practices.dbk:467 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 " -"linkend=\"upload-bugfix\"/> for more information." +"how it was fixed, and append the closes: #nnnnn string. See <xref linkend=" +"\"upload-bugfix\"/> for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:467 +#: best-pkging-practices.dbk:474 msgid "Common misconceptions about changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:469 +#: best-pkging-practices.dbk:476 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> " "document generic packaging issues (Hey, if you're looking for foo.conf, it's " @@ -706,7 +692,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:477 +#: best-pkging-practices.dbk:484 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 " @@ -714,7 +700,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:482 +#: best-pkging-practices.dbk:489 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> be " "used for random discussion with bug reporters (I don't see segfaults when " @@ -728,7 +714,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:493 +#: best-pkging-practices.dbk:500 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 " @@ -737,73 +723,73 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:501 +#: best-pkging-practices.dbk:508 msgid "Common errors in changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:503 +#: best-pkging-practices.dbk:510 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:507 +#: best-pkging-practices.dbk:514 #, no-wrap msgid "* Fixed all outstanding bugs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:510 +#: best-pkging-practices.dbk:517 msgid "This doesn't tell readers anything too useful, obviously." msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:513 +#: best-pkging-practices.dbk:520 #, no-wrap msgid "* Applied patch from Jane Random." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:516 +#: best-pkging-practices.dbk:523 msgid "What was the patch about?" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:519 +#: best-pkging-practices.dbk:526 #, no-wrap msgid "* Late night install target overhaul." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:522 +#: best-pkging-practices.dbk:529 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:526 +#: best-pkging-practices.dbk:533 #, no-wrap msgid "* Fix vsync FU w/ ancient CRTs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:529 +#: best-pkging-practices.dbk:536 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:533 +#: best-pkging-practices.dbk:540 #, no-wrap msgid "* This is not a bug, closes: #nnnnnn." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:536 +#: best-pkging-practices.dbk:543 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 " @@ -811,13 +797,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:541 +#: best-pkging-practices.dbk:548 #, no-wrap msgid "* Has been fixed for ages, but I forgot to close; closes: #54321." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:544 +#: best-pkging-practices.dbk:551 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 " @@ -828,25 +814,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:551 +#: best-pkging-practices.dbk:558 #, no-wrap msgid "* Closes: #12345, #12346, #15432" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:554 +#: best-pkging-practices.dbk:561 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:560 +#: best-pkging-practices.dbk:567 msgid "Supplementing changelogs with NEWS.Debian files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:562 +#: best-pkging-practices.dbk:569 msgid "" "Important news about changes in a package can also be put in NEWS.Debian " "files. The news will be displayed by tools like apt-listchanges, before all " @@ -858,7 +844,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:571 +#: best-pkging-practices.dbk:578 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 " @@ -869,31 +855,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:579 +#: best-pkging-practices.dbk:586 #, no-wrap msgid "" -"(3.0pl1-74) unstable; urgency=low\n" +"cron (3.0pl1-74) unstable; urgency=low\n" "\n" " The checksecurity script is no longer included with the cron package:\n" " it now has its own package, checksecurity. If you liked the\n" " functionality provided with that script, please install the new\n" " package.\n" "\n" -" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 " -"-0500" +" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 -0500" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:589 +#: best-pkging-practices.dbk:596 msgid "" -"The NEWS.Debian file is installed as " -"/usr/share/doc/<package>/NEWS.Debian.gz. It is compressed, and always " -"has that name even in Debian native packages. If you use debhelper, " -"dh_installchangelogs will install debian/NEWS files for you." +"The NEWS.Debian file is installed as /usr/share/doc/<package>/NEWS." +"Debian.gz. It is compressed, and always has that name even in Debian native " +"packages. If you use debhelper, dh_installchangelogs will install debian/" +"NEWS files for you." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:595 +#: best-pkging-practices.dbk:602 msgid "" "Unlike changelog files, you need not update NEWS.Debian files with every " "release. Only update them if you have something particularly newsworthy " @@ -902,24 +887,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:605 +#: best-pkging-practices.dbk:623 msgid "Best practices for maintainer scripts" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:607 +#: best-pkging-practices.dbk:625 msgid "" "Maintainer scripts include the files <filename>debian/postinst</filename>, " "<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and " "<filename>debian/postrm</filename>. These scripts take care of any package " "installation or deinstallation setup which isn't handled merely by the " "creation or removal of files and directories. The following instructions " -"supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>." +"supplement the <ulink url=\"&url-debian-policy;\">Debian Policy</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:615 +#: best-pkging-practices.dbk:633 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 " @@ -927,34 +911,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:620 +#: best-pkging-practices.dbk:638 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:624 +#: best-pkging-practices.dbk:642 msgid "" "All prompting or interactive configuration should be kept to a minimum. " -"When it is necessary, you should use the <systemitem " -"role=\"package\">debconf</systemitem> package for the interface. Remember " -"that prompting in any case can only be in the <literal>configure</literal> " -"stage of the <filename>postinst</filename> script." +"When it is necessary, you should use the <systemitem role=\"package" +"\">debconf</systemitem> package for the interface. Remember that prompting " +"in any case can only be in the <literal>configure</literal> stage of the " +"<filename>postinst</filename> script." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:631 +#: best-pkging-practices.dbk:649 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 " "maintainer script must have a bash shebang line. POSIX shell or Bash are " -"preferred to Perl, since they enable <systemitem " -"role=\"package\">debhelper</systemitem> to easily add bits to the scripts." +"preferred to Perl, since they enable <systemitem role=\"package\">debhelper</" +"systemitem> to easily add bits to the scripts." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:638 +#: best-pkging-practices.dbk:656 msgid "" "If you change your maintainer scripts, be sure to test package removal, " "double installation, and purging. Be sure that a purged package is " @@ -963,73 +947,55 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:644 +#: best-pkging-practices.dbk:662 msgid "" "If you need to check for the existence of a command, you should use " "something like" msgstr "" -# type: Content of: <chapter><section><screen> -#: best-pkging-practices.dbk:648 +# type: Content of: <chapter><section><programlisting> +#: best-pkging-practices.dbk:665 #, no-wrap -msgid "[ -x /usr/sbin/install-docs ]; then ..." +msgid "if [ -x /usr/sbin/install-docs ]; then ..." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:651 +#: best-pkging-practices.dbk:667 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><screen> -#: best-pkging-practices.dbk:655 -#, no-wrap -msgid "" -"() {\n" -" OLDIFS=$IFS\n" -" IFS=:\n" -" for p in $PATH; do\n" -" if [ -x $p/$* ]; then\n" -" IFS=$OLDIFS\n" -" return 0\n" -" fi\n" -" done\n" -" IFS=$OLDIFS\n" -" return 1\n" -"}" -msgstr "" - # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:669 +#: best-pkging-practices.dbk:672 msgid "" "You can use this function to search <literal>$PATH</literal> for a command " "name, passed as an argument. It returns true (zero) if the command was " "found, and false if not. This is really the most portable way, since " -"<literal>command -v</literal>, <command>type</command>, and " -"<command>which</command> are not POSIX." +"<literal>command -v</literal>, <command>type</command>, and <command>which</" +"command> are not POSIX." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:676 +#: best-pkging-practices.dbk:679 msgid "" "While <command>which</command> is an acceptable alternative, since it is " "from the required <systemitem role=\"package\">debianutils</systemitem> " -"package, it's not on the root partition. That is, it's in " -"<filename>/usr/bin</filename> rather than <filename>/bin</filename>, so one " -"can't use it in scripts which are run before the <filename>/usr</filename> " -"partition is mounted. Most scripts won't have this problem, though." +"package, it's not on the root partition. That is, it's in <filename>/usr/" +"bin</filename> rather than <filename>/bin</filename>, so one can't use it in " +"scripts which are run before the <filename>/usr</filename> partition is " +"mounted. Most scripts won't have this problem, though." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:686 +#: best-pkging-practices.dbk:689 msgid "" -"Configuration management with <systemitem " -"role=\"package\">debconf</systemitem>" +"Configuration management with <systemitem role=\"package\">debconf</" +"systemitem>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:688 +#: best-pkging-practices.dbk:691 msgid "" "<systemitem role=\"package\">Debconf</systemitem> is a configuration " "management system which can be used by all the various packaging scripts " @@ -1040,17 +1006,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:696 +#: best-pkging-practices.dbk:699 msgid "" "Debconf is a great tool but it is often poorly used. Many common mistakes " -"are listed in the <citerefentry> " -"<refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry> man page. It is something that you must read if you decide " -"to use debconf. Also, we document some best practices here." +"are listed in the <citerefentry> <refentrytitle>debconf-devel</" +"refentrytitle> <manvolnum>7</manvolnum> </citerefentry> man page. It is " +"something that you must read if you decide to use debconf. Also, we " +"document some best practices here." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:703 +#: best-pkging-practices.dbk:706 msgid "" "These guidelines include some writing style and typography recommendations, " "general considerations about debconf usage as well as more specific " @@ -1059,12 +1025,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:709 +#: best-pkging-practices.dbk:712 msgid "Do not abuse debconf" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:711 +#: best-pkging-practices.dbk:714 msgid "" "Since debconf appeared in Debian, it has been widely abused and several " "criticisms received by the Debian distribution come from debconf abuse with " @@ -1073,7 +1039,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:717 +#: best-pkging-practices.dbk:720 msgid "" "Keep usage notes to what they belong: the NEWS.Debian, or README.Debian " "file. Only use notes for important notes which may directly affect the " @@ -1082,47 +1048,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:723 +#: best-pkging-practices.dbk:726 msgid "" "Carefully choose the questions priorities in maintainer scripts. See " -"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " -"<manvolnum>7</manvolnum> </citerefentry> for details about priorities. Most " -"questions should use medium and low priorities." +"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> for details about priorities. Most questions " +"should use medium and low priorities." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:731 +#: best-pkging-practices.dbk:734 msgid "General recommendations for authors and translators" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:733 +#: best-pkging-practices.dbk:736 msgid "Write correct English" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:735 +#: best-pkging-practices.dbk:738 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:739 +#: best-pkging-practices.dbk:742 msgid "" -"Please use (and abuse) <email>debian-l10n-english@lists.debian.org</email> " -"mailing list. Have your templates proofread." +"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:743 +#: best-pkging-practices.dbk:746 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:747 +#: best-pkging-practices.dbk:750 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 " @@ -1131,12 +1097,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:755 +#: best-pkging-practices.dbk:758 msgid "Be kind to translators" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:757 +#: best-pkging-practices.dbk:760 msgid "" "Debconf templates may be translated. Debconf, along with its sister package " "<command>po-debconf</command> offers a simple framework for getting " @@ -1144,15 +1110,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:762 +#: best-pkging-practices.dbk:765 msgid "" -"Please use gettext-based templates. Install <systemitem " -"role=\"package\">po-debconf</systemitem> on your development system and read " -"its documentation (man po-debconf is a good start)." +"Please use gettext-based templates. Install <systemitem role=\"package\">po-" +"debconf</systemitem> on your development system and read its documentation " +"(man po-debconf is a good start)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:767 +#: best-pkging-practices.dbk:770 msgid "" "Avoid changing templates too often. Changing templates text induces more " "work to translators which will get their translation fuzzied. If you plan " @@ -1164,7 +1130,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:776 +#: best-pkging-practices.dbk:779 msgid "" "The use of the <command>podebconf-report-po</command> from the po-debconf " "package is highly recommended to warn translators which have incomplete " @@ -1172,69 +1138,68 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:781 +#: best-pkging-practices.dbk:784 msgid "" "If in doubt, you may also contact the translation team for a given language " -"(debian-l10n-xxxxx@lists.debian.org), or the " -"<email>debian-i18n@lists.debian.org</email> mailing list." +"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:786 +#: best-pkging-practices.dbk:789 msgid "" -"Calls for translations posted to <email>debian-i18n@lists.debian.org</email> " -"with the <filename>debian/po/templates.pot</filename> file attached or " -"referenced in a URL are encouraged. Be sure to mentions in these calls for " -"new translations which languages you have existing translations for, in " -"order to avoid duplicate work." +"Calls for translations posted to &email-debian-i18n; with the " +"<filename>debian/po/templates.pot</filename> file attached or referenced in " +"a URL are encouraged. Be sure to mentions in these calls for new " +"translations which languages you have existing translations for, in order to " +"avoid duplicate work." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:795 +#: best-pkging-practices.dbk:798 msgid "Unfuzzy complete translations when correcting typos and spelling" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:797 +#: best-pkging-practices.dbk:800 msgid "" -"When the text of a debconf template is corrected and you are <emphasis " -"role=\"strong\">sure</emphasis> that the change does <emphasis " -"role=\"strong\">not</emphasis> affect translations, please be kind to " -"translators and unfuzzy their translations." +"When the text of a debconf template is corrected and you are <emphasis role=" +"\"strong\">sure</emphasis> that the change does <emphasis role=\"strong" +"\">not</emphasis> affect translations, please be kind to translators and " +"unfuzzy their translations." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:803 +#: best-pkging-practices.dbk:806 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:807 +#: best-pkging-practices.dbk:810 msgid "" "To <emphasis role=\"strong\">unfuzzy</emphasis> translations, you can " "proceed the following way:" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:813 +#: best-pkging-practices.dbk:816 msgid "" "Put all incomplete PO files out of the way. You can check the completeness " "by using (needs the <systemitem role=\"package\">gettext</systemitem> " "package installed):" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> -#: best-pkging-practices.dbk:818 +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> +#: best-pkging-practices.dbk:820 #, no-wrap msgid "" -"i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" +"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" "--statistics $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:824 +#: best-pkging-practices.dbk:825 msgid "" "move all files which report either fuzzy strings to a temporary place. " "Files which report no fuzzy strings (only translated and untranslated) will " @@ -1242,7 +1207,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:831 +#: best-pkging-practices.dbk:832 msgid "" "now <emphasis role=\"strong\">and now only</emphasis>, modify the template " "for the typos and check again that translation are not impacted (typos, " @@ -1250,51 +1215,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:838 +#: best-pkging-practices.dbk:839 msgid "" "run <command>debconf-updatepo</command>. This will fuzzy all strings you " "modified in translations. You can see this by running the above again" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:844 +#: best-pkging-practices.dbk:845 msgid "use the following command:" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> #: best-pkging-practices.dbk:847 #, no-wrap -msgid "i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" +msgid "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:852 +#: best-pkging-practices.dbk:851 msgid "" -"move back to debian/po the files which showed fuzzy strings in the first " -"step" +"move back to debian/po the files which showed fuzzy strings in the first step" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:857 +#: best-pkging-practices.dbk:856 msgid "run <command>debconf-updatepo</command> again" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:864 +#: best-pkging-practices.dbk:863 msgid "Do not make assumptions about interfaces" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:866 +#: best-pkging-practices.dbk:865 msgid "" "Templates text should not make reference to widgets belonging to some " "debconf interfaces. Sentences like If you answer Yes... have no meaning " -"for users of graphical interfaces which use checkboxes for boolean " -"questions." +"for users of graphical interfaces which use checkboxes for boolean questions." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:871 +#: best-pkging-practices.dbk:870 msgid "" "String templates should also avoid mentioning the default values in their " "description. First, because this is redundant with the values seen by the " @@ -1303,19 +1266,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:877 +#: best-pkging-practices.dbk:876 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:883 +#: best-pkging-practices.dbk:882 msgid "Do not use first person" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:885 +#: best-pkging-practices.dbk:884 msgid "" "You should avoid the use of first person (I will do this... or We " "recommend...). The computer is not a person and the Debconf templates do " @@ -1327,52 +1290,53 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:895 +#: best-pkging-practices.dbk:894 msgid "Be gender neutral" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:897 +#: best-pkging-practices.dbk:896 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:905 +#: best-pkging-practices.dbk:904 msgid "Templates fields definition" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:907 +#: best-pkging-practices.dbk:906 msgid "" "This part gives some information which is mostly taken from the " -"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " -"<manvolnum>7</manvolnum> </citerefentry> manual page." +"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> manual page." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:912 +#: best-pkging-practices.dbk:911 msgid "Type" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:914 +#: best-pkging-practices.dbk:913 msgid "string:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:916 -msgid "Results in a free-form input field that the user can type any string into." +#: best-pkging-practices.dbk:915 +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:921 +#: best-pkging-practices.dbk:920 msgid "password:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:923 +#: best-pkging-practices.dbk:922 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 " @@ -1380,24 +1344,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:930 +#: best-pkging-practices.dbk:929 msgid "boolean:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:932 +#: best-pkging-practices.dbk:931 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:938 +#: best-pkging-practices.dbk:937 msgid "select:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:940 +#: best-pkging-practices.dbk:939 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 " @@ -1405,24 +1369,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:947 +#: best-pkging-practices.dbk:946 msgid "multiselect:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:949 +#: best-pkging-practices.dbk:948 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:955 +#: best-pkging-practices.dbk:954 msgid "note:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:957 +#: best-pkging-practices.dbk:956 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 " @@ -1432,22 +1396,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:966 +#: best-pkging-practices.dbk:965 msgid "text:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:968 +#: best-pkging-practices.dbk:967 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:973 +#: best-pkging-practices.dbk:972 msgid "error:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:975 +#: best-pkging-practices.dbk:974 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 " @@ -1455,26 +1419,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:980 +#: best-pkging-practices.dbk:979 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:988 +#: best-pkging-practices.dbk:987 msgid "Description: short and extended description" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:990 +#: best-pkging-practices.dbk:989 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:994 +#: best-pkging-practices.dbk:993 msgid "" "The short description should be kept short (50 characters or so) so that it " "may be accomodated by most debconf interfaces. Keeping it short also helps " @@ -1483,7 +1447,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1000 +#: best-pkging-practices.dbk:999 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 " @@ -1492,14 +1456,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1006 +#: best-pkging-practices.dbk:1005 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:1010 +#: best-pkging-practices.dbk:1009 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 " @@ -1509,7 +1473,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1017 +#: best-pkging-practices.dbk:1016 msgid "" "The extended description should use complete sentences. Paragraphs should " "be kept short for improved readability. Do not mix two ideas in the same " @@ -1517,7 +1481,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1022 +#: best-pkging-practices.dbk:1021 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 " @@ -1526,26 +1490,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1028 +#: best-pkging-practices.dbk:1027 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:1032 +#: best-pkging-practices.dbk:1031 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:1038 +#: best-pkging-practices.dbk:1037 msgid "Choices" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1040 +#: best-pkging-practices.dbk:1039 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 " @@ -1553,12 +1517,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1047 +#: best-pkging-practices.dbk:1046 msgid "Default" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1049 +#: best-pkging-practices.dbk:1048 msgid "" "This field is optional. It contains the default answer for string, select " "and multiselect templates. For multiselect templates, it may contain a " @@ -1566,50 +1530,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1058 +#: best-pkging-practices.dbk:1057 msgid "Templates fields specific style guide" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1060 +#: best-pkging-practices.dbk:1059 msgid "Type field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1062 +#: best-pkging-practices.dbk:1061 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:1068 +#: best-pkging-practices.dbk:1067 msgid "Description field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1070 +#: best-pkging-practices.dbk:1069 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:1074 +#: best-pkging-practices.dbk:1073 msgid "String/password templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1078 +#: best-pkging-practices.dbk:1077 msgid "" -"The short description is a prompt and <emphasis " -"role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP " -"Address?) in favour of opened prompts (IP address:). The use of colons is " -"recommended." +"The short description is a prompt and <emphasis role=\"strong\">not</" +"emphasis> a title. Avoid question style prompts (IP Address?) in favour of " +"opened prompts (IP address:). The use of colons is recommended." msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1085 +#: best-pkging-practices.dbk:1084 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 " @@ -1618,12 +1581,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1095 +#: best-pkging-practices.dbk:1094 msgid "Boolean templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1099 +#: best-pkging-practices.dbk:1098 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 " @@ -1632,28 +1595,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1107 +#: best-pkging-practices.dbk:1106 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:1115 +#: best-pkging-practices.dbk:1114 msgid "Select/Multiselect" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1119 +#: best-pkging-practices.dbk:1118 msgid "" -"The short description is a prompt and <emphasis " -"role=\"strong\">not</emphasis> a title. Do <emphasis " -"role=\"strong\">not</emphasis> use useless Please choose... constructions. " -"Users are clever enough to figure out they have to choose something...:)" +"The short description is a prompt and <emphasis role=\"strong\">not</" +"emphasis> a title. Do <emphasis role=\"strong\">not</emphasis> use useless " +"Please choose... constructions. Users are clever enough to figure out they " +"have to choose something...:)" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1127 +#: best-pkging-practices.dbk:1126 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 " @@ -1662,24 +1625,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1137 +#: best-pkging-practices.dbk:1136 msgid "Notes" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1141 +#: best-pkging-practices.dbk:1140 msgid "The short description should be considered to be a *title*." msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1146 +#: best-pkging-practices.dbk:1145 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:1152 +#: best-pkging-practices.dbk:1151 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: " @@ -1691,12 +1654,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1167 +#: best-pkging-practices.dbk:1166 msgid "Choices field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1169 +#: best-pkging-practices.dbk:1168 msgid "" "If the Choices are likely to change often, please consider using the " "__Choices trick. This will split each individual choice into a single " @@ -1704,12 +1667,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1176 best-pkging-practices.dbk:1214 +#: best-pkging-practices.dbk:1175 best-pkging-practices.dbk:1213 msgid "Default field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1178 +#: best-pkging-practices.dbk:1177 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 " @@ -1717,7 +1680,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1183 +#: best-pkging-practices.dbk:1182 msgid "" "This special field allow translators to put the most appropriate choice " "according to their own language. It will become the default choice when " @@ -1726,21 +1689,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1189 +#: best-pkging-practices.dbk:1188 msgid "Example, taken from the geneweb package templates:" msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:1192 +#: best-pkging-practices.dbk:1191 #, no-wrap msgid "" -": geneweb/lang\n" +"Template: geneweb/lang\n" "Type: select\n" -"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech " -"(cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), " -"Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian " -"(it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian " -"(ro), Russian (ru), Spanish (es), Swedish (sv)\n" +"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech (cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian (it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Spanish (es), Swedish (sv)\n" "# This is the default choice. Translators may put their own language here\n" "# instead of the default.\n" "# WARNING : you MUST use the ENGLISH FORM of your language\n" @@ -1750,7 +1709,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1203 +#: best-pkging-practices.dbk:1202 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 " @@ -1758,21 +1717,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1208 +#: best-pkging-practices.dbk:1207 msgid "" "The comments are needed as the DefaultChoice 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:1216 +#: best-pkging-practices.dbk:1215 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:1220 +#: best-pkging-practices.dbk:1219 msgid "" "If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, " "see 2.2), consider making this field translatable, if you think it may be " @@ -1780,27 +1739,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1225 +#: best-pkging-practices.dbk:1224 msgid "" "If the default value may vary depending on language/country (for instance " "the default value for a language choice), consider using the special " -"_DefaultChoice type documented in <citerefentry> " -"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry>)." +"_DefaultChoice type documented in <citerefentry> <refentrytitle>po-debconf</" +"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)." msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1237 +#: best-pkging-practices.dbk:1236 msgid "Internationalization" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1239 +#: best-pkging-practices.dbk:1238 msgid "Handling debconf translations" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1241 +#: best-pkging-practices.dbk:1240 msgid "" "Like porters, translators have a difficult task. They work on many packages " "and must collaborate with many different maintainers. Moreover, most of the " @@ -1809,43 +1767,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1247 +#: best-pkging-practices.dbk:1246 msgid "" "The goal of <systemitem role=\"package\">debconf</systemitem> was to make " "packages configuration easier for maintainers and for users. Originally, " -"translation of debconf templates was handled with " -"<command>debconf-mergetemplate</command>. However, that technique is now " -"deprecated; the best way to accomplish <systemitem " -"role=\"package\">debconf</systemitem> internationalization is by using the " -"<systemitem role=\"package\">po-debconf</systemitem> package. This method " -"is easier both for maintainer and translators; transition scripts are " -"provided." +"translation of debconf templates was handled with <command>debconf-" +"mergetemplate</command>. However, that technique is now deprecated; the " +"best way to accomplish <systemitem role=\"package\">debconf</systemitem> " +"internationalization is by using the <systemitem role=\"package\">po-" +"debconf</systemitem> package. This method is easier both for maintainer and " +"translators; transition scripts are provided." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1257 +#: best-pkging-practices.dbk:1256 msgid "" "Using <systemitem role=\"package\">po-debconf</systemitem>, the translation " -"is stored in <filename>po</filename> files (drawing from " -"<command>gettext</command> translation techniques). Special template files " -"contain the original messages and mark which fields are translatable. When " -"you change the value of a translatable field, by calling " -"<command>debconf-updatepo</command>, the translation is marked as needing " -"attention from the translators. Then, at build time, the " -"<command>dh_installdebconf</command> program takes care of all the needed " -"magic to add the template along with the up-to-date translations into the " -"binary packages. Refer to the <citerefentry> " -"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> " -"</citerefentry> manual page for details." +"is stored in <filename>po</filename> files (drawing from <command>gettext</" +"command> translation techniques). Special template files contain the " +"original messages and mark which fields are translatable. When you change " +"the value of a translatable field, by calling <command>debconf-updatepo</" +"command>, the translation is marked as needing attention from the " +"translators. Then, at build time, the <command>dh_installdebconf</command> " +"program takes care of all the needed magic to add the template along with " +"the up-to-date translations into the binary packages. Refer to the " +"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</" +"manvolnum> </citerefentry> manual page for details." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1273 +#: best-pkging-practices.dbk:1272 msgid "Internationalized documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1275 +#: best-pkging-practices.dbk:1274 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 " @@ -1853,7 +1809,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1280 +#: best-pkging-practices.dbk:1279 msgid "" "If you maintain documentation of any size, its easier for translators if " "they have access to a source control system. That lets translators see the " @@ -1861,18 +1817,16 @@ msgid "" "they can see what needs to be retranslated. It is recommended that the " "translated documentation maintain a note about what source control revision " "the translation is based on. An interesting system is provided by <ulink " -"url=\"http://cvs.debian.org/boot-floppies/documentation/doc-check?rev=HEAD\\|[amp " -"]\\|content-type=text/vnd.viewcvs-markup\">doc-check</ulink> in the " -"<systemitem role=\"package\">boot-floppies</systemitem> package, which shows " -"an overview of the translation status for any given language, using " -"structured comments for the current revision of the file to be translated " -"and, for a translated file, the revision of the original file the " -"translation is based on. You might wish to adapt and provide that in your " -"CVS area." +"url=\"&url-i18n-doc-check;\">doc-check</ulink> in the <systemitem role=" +"\"package\">boot-floppies</systemitem> package, which shows an overview of " +"the translation status for any given language, using structured comments for " +"the current revision of the file to be translated and, for a translated " +"file, the revision of the original file the translation is based on. You " +"might wish to adapt and provide that in your CVS area." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1295 +#: best-pkging-practices.dbk:1293 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 " @@ -1881,36 +1835,35 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1305 +#: best-pkging-practices.dbk:1303 msgid "Common packaging situations" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1307 +#: best-pkging-practices.dbk:1314 msgid "Packages using <command>autoconf</command>/<command>automake</command>" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1309 +#: best-pkging-practices.dbk:1316 msgid "" "Keeping <command>autoconf</command>'s <filename>config.sub</filename> and " "<filename>config.guess</filename> files up to date is critical for porters, " "especially on more volatile architectures. Some very good packaging " "practices for any package using <command>autoconf</command> and/or " -"<command>automake</command> have been synthesized in " -"<filename>/usr/share/doc/autotools-dev/README.Debian.gz</filename> from the " -"<systemitem role=\"package\">autotools-dev</systemitem> package. You're " -"strongly encouraged to read this file and to follow the given " +"<command>automake</command> have been synthesized in &file-bpp-autotools; " +"from the <systemitem role=\"package\">autotools-dev</systemitem> package. " +"You're strongly encouraged to read this file and to follow the given " "recommendations." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1321 +#: best-pkging-practices.dbk:1328 msgid "Libraries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1323 +#: best-pkging-practices.dbk:1330 msgid "" "Libraries are always difficult to package for various reasons. The policy " "imposes many constraints to ease their maintenance and to make sure upgrades " @@ -1919,28 +1872,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1329 +#: best-pkging-practices.dbk:1336 msgid "" -"Good practices for library packaging have been grouped in <ulink " -"url=\"http://www.netfort.gr.jp/~dancer/column/libpkg-guide/\">the library " -"packaging guide</ulink>." +"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><section><title> -#: best-pkging-practices.dbk:1336 +#: best-pkging-practices.dbk:1343 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1338 +#: best-pkging-practices.dbk:1345 msgid "" -"Be sure to follow the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html\">Policy on " -"documentation</ulink>." +"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:1343 +#: best-pkging-practices.dbk:1350 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 " @@ -1948,7 +1899,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1348 +#: best-pkging-practices.dbk:1355 msgid "" "Policy specifies that documentation should be shipped in HTML format. We " "also recommend shipping documentation in PDF and plain text format if " @@ -1958,93 +1909,86 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1355 +#: best-pkging-practices.dbk:1362 msgid "" -"Major shipped manuals should register themselves with <systemitem " -"role=\"package\">doc-base</systemitem> on installation. See the <systemitem " -"role=\"package\">doc-base</systemitem> package documentation for more " -"information." +"Major shipped manuals should register themselves with <systemitem role=" +"\"package\">doc-base</systemitem> on installation. See the <systemitem role=" +"\"package\">doc-base</systemitem> package documentation for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1363 +#: best-pkging-practices.dbk:1370 msgid "Specific types of packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1365 +#: best-pkging-practices.dbk:1372 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:1371 +#: best-pkging-practices.dbk:1378 msgid "" -"Perl related packages have a <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/perl-policy/\">Perl " -"policy</ulink>, some examples of packages following that policy are " -"<systemitem role=\"package\">libdbd-pg-perl</systemitem> (binary perl " -"module) or <systemitem role=\"package\">libmldbm-perl</systemitem> (arch " -"independent perl module)." +"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl policy</" +"ulink>, some examples of packages following that policy are <systemitem role=" +"\"package\">libdbd-pg-perl</systemitem> (binary perl module) or <systemitem " +"role=\"package\">libmldbm-perl</systemitem> (arch independent perl module)." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1380 +#: best-pkging-practices.dbk:1387 msgid "" -"Python related packages have their python policy; see " -"<filename>/usr/share/doc/python/python-policy.txt.gz</filename> in the " -"<systemitem role=\"package\">python</systemitem> package." +"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:1387 +#: best-pkging-practices.dbk:1394 msgid "" -"Emacs related packages have the <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/debian-emacs-policy\">emacs " +"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:1394 +#: best-pkging-practices.dbk:1401 msgid "" -"Java related packages have their <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/java-policy/\">java " +"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:1401 +#: best-pkging-practices.dbk:1408 msgid "" -"Ocaml related packages have their own policy, found in " -"<filename>/usr/share/doc/ocaml/ocaml_packaging_policy.gz</filename> from the " -"<systemitem role=\"package\">ocaml</systemitem> package. A good example is " -"the <systemitem role=\"package\">camlzip</systemitem> source package." +"Ocaml related packages have their own policy, found in &file-ocaml-policy; " +"from the <systemitem role=\"package\">ocaml</systemitem> package. A good " +"example is the <systemitem role=\"package\">camlzip</systemitem> source " +"package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1409 +#: best-pkging-practices.dbk:1416 msgid "" "Packages providing XML or SGML DTDs should conform to the recommendations " -"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> " -"package." +"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1415 +#: best-pkging-practices.dbk:1422 msgid "" -"Lisp packages should register themselves with <systemitem " -"role=\"package\">common-lisp-controller</systemitem>, about which see " -"<filename>/usr/share/doc/common-lisp-controller/README.packaging</filename>." +"Lisp packages should register themselves with <systemitem role=\"package" +"\">common-lisp-controller</systemitem>, about which see &file-lisp-" +"controller;." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1424 +#: best-pkging-practices.dbk:1452 msgid "Architecture-independent data" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1426 +#: best-pkging-practices.dbk:1454 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, " @@ -2054,12 +1998,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1433 +#: best-pkging-practices.dbk:1461 msgid "" "However, if the size of the data is considerable, consider splitting it out " "into a separate, architecture-independent package (_all.deb). By doing " -"this, you avoid needless duplication of the same data into eleven or more " -".debs, one per each architecture. While this adds some extra overhead into " +"this, you avoid needless duplication of the same data into eleven or more ." +"debs, one per each architecture. While this adds some extra overhead into " "the <filename>Packages</filename> files, it saves a lot of disk space on " "Debian mirrors. Separating out architecture-independent data also reduces " "processing time of <command>lintian</command> or <command>linda</command> " @@ -2068,48 +2012,48 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1445 +#: best-pkging-practices.dbk:1473 msgid "Needing a certain locale during build" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1447 +#: best-pkging-practices.dbk:1475 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:1451 +#: best-pkging-practices.dbk:1479 msgid "" -"If you set LOCPATH to the equivalent of /usr/lib/locale, and LC_ALL to the " -"name of the locale you generate, you should get what you want without being " -"root. Something like this:" +"If you set <varname>LOCPATH</varname> to the equivalent of <filename>/usr/" +"lib/locale</filename>, and <varname>LC_ALL</varname> to the name of the " +"locale you generate, you should get what you want without being root. " +"Something like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1456 +#: best-pkging-practices.dbk:1484 #, no-wrap msgid "" -"=debian/tmpdir/usr/lib/locale\n" +"LOCALE_PATH=debian/tmpdir/usr/lib/locale\n" "LOCALE_NAME=en_IN\n" "LOCALE_CHARSET=UTF-8\n" "\n" "mkdir -p $LOCALE_PATH\n" -"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET " -"$LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n" +"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET $LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n" "\n" "# Using the locale\n" "LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1469 +#: best-pkging-practices.dbk:1497 msgid "Make transition packages deborphan compliant" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1471 +#: best-pkging-practices.dbk:1499 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 " @@ -2119,7 +2063,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1478 +#: best-pkging-practices.dbk:1506 msgid "" "For example, with --guess-dummy, deborphan tries to search all transitional " "packages which were needed for upgrade but which can now safely be removed. " @@ -2128,76 +2072,56 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1484 +#: best-pkging-practices.dbk:1512 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><screen> -#: best-pkging-practices.dbk:1488 -#, no-wrap -msgid "-cache search .|grep dummy" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1491 -msgid "or" -msgstr "" - -# type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1494 -#, no-wrap -msgid "-cache search .|grep transitional" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1497 -msgid "." +"to your short description. If you are looking for examples, just run: " +"<command>apt-cache search .|grep dummy</command> or <command>apt-cache " +"search .|grep transitional</command>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1502 +#: best-pkging-practices.dbk:1520 msgid "Best practices for <filename>orig.tar.gz</filename> files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1504 +#: best-pkging-practices.dbk:1522 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:1508 +#: best-pkging-practices.dbk:1526 msgid "Pristine source" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1510 +#: best-pkging-practices.dbk:1528 msgid "" -"The defining characteristic of a pristine source tarball is that the " -".orig.tar.gz file is byte-for-byte identical to a tarball officially " -"distributed by the upstream author. <footnote>" +"The defining characteristic of a pristine source tarball is that the .orig." +"tar.gz file is byte-for-byte identical to a tarball officially distributed " +"by the upstream author. <footnote>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1512 +#: best-pkging-practices.dbk:1530 msgid "" "We cannot prevent upstream authors from changing the tarball they distribute " "without also incrementing the version number, so there can be no guarantee " -"that a pristine tarball is identical to what upstream " -"<emphasis>currently</emphasis> distributing at any point in time. All that " -"can be expected is that it is identical to something that upstream once " -"<emphasis>did</emphasis> distribute. If a difference arises later (say, if " -"upstream notices that he wasn't using maximal comression in his original " -"distribution and then re-<literal>gzip</literal>s it), that's just too bad. " -"Since there is no good way to upload a new .orig.tar.gz for the same " -"version, there is not even any point in treating this situation as a bug." +"that a pristine tarball is identical to what upstream <emphasis>currently</" +"emphasis> distributing at any point in time. All that can be expected is " +"that it is identical to something that upstream once <emphasis>did</" +"emphasis> distribute. If a difference arises later (say, if upstream " +"notices that he wasn't using maximal comression in his original distribution " +"and then re-<literal>gzip</literal>s it), that's just too bad. Since there " +"is no good way to upload a new .orig.tar.gz for the same version, there is " +"not even any point in treating this situation as a bug." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1522 +#: best-pkging-practices.dbk:1540 msgid "" "</footnote> This makes it possible to use checksums to easily verify that " "all changes between Debian's version and upstream's are contained in the " @@ -2207,28 +2131,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1530 +#: best-pkging-practices.dbk:1548 msgid "" "There is no universally accepted guidelines that upstream authors follow " -"regarding to the directory structure inside their tarball, but " -"<command>dpkg-source</command> is nevertheless able to deal with most " -"upstream tarballs as pristine source. Its strategy is equivalent to the " -"following:" +"regarding to the directory structure inside their tarball, but <command>dpkg-" +"source</command> is nevertheless able to deal with most upstream tarballs as " +"pristine source. Its strategy is equivalent to the following:" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1538 +#: best-pkging-practices.dbk:1556 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:1541 +#: best-pkging-practices.dbk:1559 #, no-wrap -msgid "path/to/<packagename>_<upstream-version>.orig.tar.gz | tar xf -" +msgid "zcat path/to/<packagename>_<upstream-version>.orig.tar.gz | tar xf -" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1546 +#: best-pkging-practices.dbk:1564 msgid "" "If, after this, the temporary directory contains nothing but one directory " "and no other files, <command>dpkg-source</command> renames that directory to " @@ -2238,74 +2161,73 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1555 +#: best-pkging-practices.dbk:1573 msgid "" -"Otherwise, the upstream tarball must have been packaged without a common " -"top-level directory (shame on the upstream author!). In this case, " +"Otherwise, the upstream tarball must have been packaged without a common top-" +"level directory (shame on the upstream author!). In this case, " "<command>dpkg-source</command> renames the temporary directory " -"<emphasis>itself</emphasis> to " -"<literal><packagename>-<upstream-version>(.orig)</literal>." +"<emphasis>itself</emphasis> to <literal><packagename>-<upstream-" +"version>(.orig)</literal>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1566 +#: best-pkging-practices.dbk:1584 msgid "Repackaged upstream source" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1568 +#: best-pkging-practices.dbk:1586 msgid "" "You <emphasis role=\"strong\">should</emphasis> upload packages with a " "pristine source tarball if possible, but there are various reasons why it " "might not be possible. This is the case if upstream does not distribute the " -"source as gzipped tar at all, or if upstream's tarball contains " -"non-DFSG-free material that you must remove before uploading." +"source as gzipped tar at all, or if upstream's tarball contains non-DFSG-" +"free material that you must remove before uploading." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1575 +#: best-pkging-practices.dbk:1593 msgid "" "In these cases the developer must construct a suitable .orig.tar.gz file " "himself. We refer to such a tarball as a repackaged upstream source. Note " "that a repackaged upstream source is different from a Debian-native " "package. A repackaged source still comes with Debian-specific changes in a " "separate <literal>.diff.gz</literal> and still has a version number composed " -"of <literal><upstream-version></literal> and " -"<literal><debian-revision></literal>." +"of <literal><upstream-version></literal> and <literal><debian-" +"revision></literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1584 +#: best-pkging-practices.dbk:1602 msgid "" "There may be cases where it is desirable to repackage the source even though " "upstream distributes a <literal>.tar.gz</literal> that could in principle be " -"used in its pristine form. The most obvious is if " -"<emphasis>significant</emphasis> space savings can be achieved by " -"recompressing the tar archive or by removing genuinely useless cruft from " -"the upstream archive. Use your own discretion here, but be prepared to " -"defend your decision if you repackage source that could have been pristine." +"used in its pristine form. The most obvious is if <emphasis>significant</" +"emphasis> space savings can be achieved by recompressing the tar archive or " +"by removing genuinely useless cruft from the upstream archive. Use your own " +"discretion here, but be prepared to defend your decision if you repackage " +"source that could have been pristine." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1593 +#: best-pkging-practices.dbk:1611 msgid "A repackaged .orig.tar.gz" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1598 +#: best-pkging-practices.dbk:1616 msgid "" "<emphasis role=\"strong\">must</emphasis> contain detailed information how " "the repackaged source was obtained, and how this can be reproduced in the " "<filename>debian/copyright</filename>. It is also a good idea to provide a " -"<literal>get-orig-source</literal> target in your " -"<filename>debian/rules</filename> file that repeats the process, as " -"described in the Policy Manual, <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules\">Main " -"building script: debian/rules</ulink>." +"<literal>get-orig-source</literal> target in your <filename>debian/rules</" +"filename> file that repeats the process, as described in the Policy Manual, " +"<ulink url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building " +"script: debian/rules</ulink>." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote> -#: best-pkging-practices.dbk:1610 +#: best-pkging-practices.dbk:1628 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 " @@ -2313,7 +2235,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para> -#: best-pkging-practices.dbk:1612 +#. or similarly named +#: best-pkging-practices.dbk:1630 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 " @@ -2325,7 +2248,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1623 +#: best-pkging-practices.dbk:1642 msgid "" "<emphasis role=\"strong\">should</emphasis>, except where impossible for " "legal reasons, preserve the entire building and portablility infrastructure " @@ -2337,86 +2260,75 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1632 +#: best-pkging-practices.dbk:1651 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 " -"mirror rather than trying to locate a canonical upstream distribution " -"point)." +"mirror rather than trying to locate a canonical upstream distribution point)." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1639 +#: best-pkging-practices.dbk:1658 msgid "" -"<emphasis role=\"strong\">should</emphasis> use " -"<literal><packagename>-<upstream-version>.orig</literal> as the " -"name of the top-level directory in its tarball. This makes it possible to " -"distinguish pristine tarballs from repackaged ones." +"<emphasis role=\"strong\">should</emphasis> use <literal><packagename>-" +"<upstream-version>.orig</literal> as the name of the top-level " +"directory in its tarball. This makes it possible to distinguish pristine " +"tarballs from repackaged ones." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1647 +#: best-pkging-practices.dbk:1666 msgid "" "<emphasis role=\"strong\">should</emphasis> be gzipped with maximal " "compression." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1652 +#: best-pkging-practices.dbk:1671 msgid "" -"The canonical way to meet the latter two points is to let " -"<literal>dpkg-source -b</literal> construct the repackaged tarball from an " -"unpacked directory." +"The canonical way to meet the latter two points is to let <literal>dpkg-" +"source -b</literal> construct the repackaged tarball from an unpacked " +"directory." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1658 +#: best-pkging-practices.dbk:1677 msgid "Changing binary files in <literal>diff.gz</literal>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1660 +#: best-pkging-practices.dbk:1679 msgid "" "Sometimes it is necessary to change binary files contained in the original " "tarball, or to add binary files that are not in it. If this is done by " -"simply copying the files into the debianized source tree, " -"<command>dpkg-source</command> will not be able to handle this. On the " -"other hand, according to the guidelines given above, you cannot include such " -"a changed binary file in a repackaged <filename>orig.tar.gz</filename>. " -"Instead, include the file in the <filename>debian</filename> directory in " +"simply copying the files into the debianized source tree, <command>dpkg-" +"source</command> will not be able to handle this. On the other hand, " +"according to the guidelines given above, you cannot include such a changed " +"binary file in a repackaged <filename>orig.tar.gz</filename>. Instead, " +"include the file in the <filename>debian</filename> directory in " "<command>uuencode</command>d (or similar) form <footnote>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1667 +#: best-pkging-practices.dbk:1686 msgid "" "The file should have a name that makes it clear which binary file it " "encodes. Usually, some postfix indicating the encoding should be appended " "to the original filename. Note that you don't need to depend on <systemitem " -"role=\"package\">sharutils</systemitem> to get the " -"<command>uudecode</command> program if you use <command>perl</command>'s " -"<literal>pack</literal> function. The code could look like" -msgstr "" - -# type: Content of: <chapter><section><section><section><para><footnote><screen> -#: best-pkging-practices.dbk:1673 -#, no-wrap -msgid "" -"-file: perl -ne 'print(pack u, $$_);'\n" -"$(file) > $(file).uuencoded uudecode-file: perl -ne 'print(unpack u, " -"$$_);'\n" -"$(file).uuencoded > $(file)" +"role=\"package\">sharutils</systemitem> to get the <command>uudecode</" +"command> program if you use <command>perl</command>'s <literal>pack</" +"literal> function. The code could look like" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1675 +#: best-pkging-practices.dbk:1694 msgid "" -"</footnote>. The file would then be decoded and copied to its place during " -"the build process. Thus the change will be visible quite easy." +"&example-uu; </footnote>. The file would then be decoded and copied to its " +"place during the build process. Thus the change will be visible quite easy." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1680 +#: best-pkging-practices.dbk:1700 msgid "" "Some packages use <command>dbs</command> to manage patches to their upstream " "source, and always create a new <literal>orig.tar.gz</literal> file that " @@ -2428,12 +2340,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1693 +#: best-pkging-practices.dbk:1713 msgid "Best practices for debug packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1695 +#: best-pkging-practices.dbk:1715 msgid "" "A debug package is a package with a name ending in -dbg, that contains " "additional information that gdb can use. Since Debian binaries are stripped " @@ -2444,7 +2356,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1703 +#: best-pkging-practices.dbk:1723 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 " @@ -2457,7 +2369,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1713 +#: best-pkging-practices.dbk:1733 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 " @@ -2467,40 +2379,38 @@ msgid "" "<emphasis>path</emphasis> is the path to the executable or library. For " "example, debugging symbols for <filename>/usr/bin/foo</filename> go in " "<filename>/usr/lib/debug/usr/bin/foo</filename>, and debugging symbols for " -"<filename>/usr/lib/libfoo.so.1</filename> go in " -"<filename>/usr/lib/debug/usr/lib/libfoo.so.1</filename>." +"<filename>/usr/lib/libfoo.so.1</filename> go in <filename>/usr/lib/debug/usr/" +"lib/libfoo.so.1</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1725 +#: best-pkging-practices.dbk:1745 msgid "" -"The debugging symbols can be extracted from an object file using objcopy " -"--only-keep-debug. Then the object file can be stripped, and objcopy " -"--add-gnu-debuglink used to specify the path to the debugging symbol file. " -"<citerefentry> <refentrytitle>objcopy</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> explains in detail how this works." +"The debugging symbols can be extracted from an object file using objcopy --" +"only-keep-debug. Then the object file can be stripped, and objcopy --add-" +"gnu-debuglink used to specify the path to the debugging symbol file. " +"<citerefentry> <refentrytitle>objcopy</refentrytitle> <manvolnum>1</" +"manvolnum> </citerefentry> explains in detail how this works." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1732 +#: best-pkging-practices.dbk:1752 msgid "" "The dh_strip command in debhelper supports creating debug packages, and can " "take care of using objcopy to separate out the debugging symbols for you. " -"If your package uses debhelper, all you need to do is call dh_strip " -"--dbg-package=libfoo-dbg, and add an entry to debian/control for the debug " -"package." +"If your package uses debhelper, all you need to do is call dh_strip --dbg-" +"package=libfoo-dbg, and add an entry to debian/control for the debug package." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1739 +#: best-pkging-practices.dbk:1759 msgid "" "Note that the Debian package should depend on the package that it provides " -"debugging symbols for, and this dependency should be versioned. For " -"example:" +"debugging symbols for, and this dependency should be versioned. For example:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1743 +#: best-pkging-practices.dbk:1763 #, no-wrap -msgid ": libfoo-dbg (= ${binary:Version})" +msgid "Depends: libfoo-dbg (= ${binary:Version})" msgstr "" diff --git a/po4a/ja/beyond-pkging.po b/po4a/ja/beyond-pkging.po index 586c3ca..4d063b1 100644 --- a/po4a/ja/beyond-pkging.po +++ b/po4a/ja/beyond-pkging.po @@ -6,21 +6,21 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: beyond-pkging.dbk:5 +#: beyond-pkging.dbk:7 msgid "Beyond Packaging" msgstr "" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:7 +#: beyond-pkging.dbk:9 msgid "" "Debian is about a lot more than just packaging software and maintaining " "those packages. This chapter contains information about ways, often really " @@ -29,7 +29,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:12 +#: beyond-pkging.dbk:14 msgid "" "As a volunteer organization, Debian relies on the discretion of its members " "in choosing what they want to work on and in choosing the most critical " @@ -37,12 +37,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:17 +#: beyond-pkging.dbk:19 msgid "Bug reporting" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:19 +#: beyond-pkging.dbk:21 msgid "" "We encourage you to file bugs as you find them in Debian packages. In fact, " "Debian developers are often the first line testers. Finding and reporting " @@ -50,15 +50,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:24 +#: beyond-pkging.dbk:26 msgid "" -"Read the <ulink url=\"http://www.debian.org/Bugs/Reporting\">instructions " -"for reporting bugs</ulink> in the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>." +"Read the <ulink url=\"&url-bts-report;\">instructions for reporting bugs</" +"ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking system</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:29 +#: beyond-pkging.dbk:31 msgid "" "Try to submit the bug from a normal user account at which you are likely to " "receive mail, so that people can reach you if they need further information " @@ -66,28 +65,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:34 +#: beyond-pkging.dbk:36 msgid "" -"You can use a tool like <citerefentry> " -"<refentrytitle>reportbug</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry> to submit bugs. It can automate and generally ease the " -"process." +"You can use a tool like <citerefentry> <refentrytitle>reportbug</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry> to submit bugs. It " +"can automate and generally ease the process." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:39 +#: beyond-pkging.dbk:41 msgid "" "Make sure the bug is not already filed against a package. Each package has " -"a bug list easily reachable at " -"<literal>http://bugs.debian.org/<replaceable>packagename</replaceable></literal> " -"Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> can also provide you with this " -"information (and <command>reportbug</command> will usually invoke " -"<command>querybts</command> before sending, too)." +"a bug list easily reachable at <literal>http://&bugs-host;/" +"<replaceable>packagename</replaceable></literal> Utilities like " +"<citerefentry> <refentrytitle>querybts</refentrytitle> <manvolnum>1</" +"manvolnum> </citerefentry> can also provide you with this information (and " +"<command>reportbug</command> will usually invoke <command>querybts</command> " +"before sending, too)." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:48 +#: beyond-pkging.dbk:50 msgid "" "Try to direct your bugs to the proper location. When for example your bug " "is about a package which overwrites files from another package, check the " @@ -96,7 +94,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:54 +#: beyond-pkging.dbk:56 msgid "" "For extra credit, you can go through other packages, merging bugs which are " "reported more than once, or tagging bugs `fixed' when they have already been " @@ -106,72 +104,70 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:61 +#: beyond-pkging.dbk:63 msgid "" "From time to time you may want to check what has been going on with the bug " "reports that you submitted. Take this opportunity to close those that you " "can't reproduce anymore. To find out all the bugs you submitted, you just " -"have to visit " -"<literal>http://bugs.debian.org/from:<replaceable><your-email-addr></replaceable></literal>." +"have to visit <literal>http://&bugs-host;/from:<replaceable><your-email-" +"addr></replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:68 +#: beyond-pkging.dbk:70 msgid "Reporting lots of bugs at once (mass bug filing)" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:70 +#: beyond-pkging.dbk:72 msgid "" "Reporting a great number of bugs for the same problem on a great number of " "different packages — i.e., more than 10 — is a deprecated practice. Take " "all possible steps to avoid submitting bulk bugs at all. For instance, if " "checking for the problem can be automated, add a new check to <systemitem " -"role=\"package\">lintian</systemitem> so that an error or warning is " -"emitted." +"role=\"package\">lintian</systemitem> so that an error or warning is emitted." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:77 +#: beyond-pkging.dbk:79 msgid "" "If you report more than 10 bugs on the same topic at once, it is recommended " -"that you send a message to <email>debian-devel@lists.debian.org</email> " -"describing your intention before submitting the report, and mentioning the " -"fact in the subject of your mail. This will allow other developers to " -"verify that the bug is a real problem. In addition, it will help prevent a " -"situation in which several maintainers start filing the same bug report " -"simultaneously." +"that you send a message to &email-debian-devel; describing your intention " +"before submitting the report, and mentioning the fact in the subject of your " +"mail. This will allow other developers to verify that the bug is a real " +"problem. In addition, it will help prevent a situation in which several " +"maintainers start filing the same bug report simultaneously." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:85 +#: beyond-pkging.dbk:87 msgid "" "Please use the programms <command>dd-list</command> and if appropriate " "<command>whodepends</command> (from the package devscripts) to generate a " -"list of all affected packages, and include the output in your mail to " -"<email>debian-devel@lists.debian.org</email>." +"list of all affected packages, and include the output in your mail to &email-" +"debian-devel;." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:91 +#: beyond-pkging.dbk:93 msgid "" "Note that when sending lots of bugs on the same subject, you should send the " -"bug report to <email>maintonly@bugs.debian.org</email> so that the bug " -"report is not forwarded to the bug distribution mailing list." +"bug report to <email>maintonly@&bugs-host;</email> so that the bug report is " +"not forwarded to the bug distribution mailing list." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:100 +#: beyond-pkging.dbk:102 msgid "Quality Assurance effort" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:102 +#: beyond-pkging.dbk:104 msgid "Daily work" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:104 +#: beyond-pkging.dbk:106 msgid "" "Even though there is a dedicated group of people for Quality Assurance, QA " "duties are not reserved solely for them. You can participate in this effort " @@ -180,30 +176,29 @@ msgid "" "possible, then you should consider orphaning some of your packages (see " "<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of " "other people in order to catch up with the backlog of bugs that you have " -"(you can ask for help on <email>debian-qa@lists.debian.org</email> or " -"<email>debian-devel@lists.debian.org</email>). At the same time, you can " -"look for co-maintainers (see <xref linkend=\"collaborative-maint\"/> )." +"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the " +"same time, you can look for co-maintainers (see <xref linkend=" +"\"collaborative-maint\"/> )." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:118 +#: beyond-pkging.dbk:120 msgid "Bug squashing parties" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:120 +#: beyond-pkging.dbk:122 msgid "" "From time to time the QA group organizes bug squashing parties to get rid of " -"as many problems as possible. They are announced on " -"<email>debian-devel-announce@lists.debian.org</email> and the announcement " -"explains which area will be the focus of the party: usually they focus on " -"release critical bugs but it may happen that they decide to help finish a " -"major upgrade (like a new perl version which requires recompilation of all " -"the binary modules)." +"as many problems as possible. They are announced on &email-debian-devel-" +"announce; and the announcement explains which area will be the focus of the " +"party: usually they focus on release critical bugs but it may happen that " +"they decide to help finish a major upgrade (like a new perl version which " +"requires recompilation of all the binary modules)." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:129 +#: beyond-pkging.dbk:131 msgid "" "The rules for non-maintainer uploads differ during the parties because the " "announcement of the party is considered prior notice for NMU. If you have " @@ -216,7 +211,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:138 +#: beyond-pkging.dbk:140 msgid "" "People participating in the party have special rules for NMU, they can NMU " "without prior notice if they upload their NMU to DELAYED/3-day at least. " @@ -227,19 +222,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:145 +#: beyond-pkging.dbk:147 msgid "" "If you don't feel confident about doing an NMU, just send a patch to the " "BTS. It's far better than a broken NMU." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:153 +#: beyond-pkging.dbk:155 msgid "Contacting other maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:155 +#: beyond-pkging.dbk:157 msgid "" "During your lifetime within Debian, you will have to contact other " "maintainers for various reasons. You may want to discuss a new way of " @@ -248,32 +243,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:161 +#: beyond-pkging.dbk:163 msgid "" "Looking up the email address of the maintainer for the package can be " -"distracting. Fortunately, there is a simple email alias, " -"<literal><package>@packages.debian.org</literal>, which provides a way " -"to email the maintainer, whatever their individual email address (or " -"addresses) may be. Replace <literal><package></literal> with the " -"name of a source or a binary package." +"distracting. Fortunately, there is a simple email alias, <literal><" +"package>@&packages-host;</literal>, which provides a way to email the " +"maintainer, whatever their individual email address (or addresses) may be. " +"Replace <literal><package></literal> with the name of a source or a " +"binary package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:169 +#: beyond-pkging.dbk:171 msgid "" "You may also be interested in contacting the persons who are subscribed to a " "given source package via <xref linkend=\"pkg-tracking-system\"/> . You can " -"do so by using the <literal><package>@packages.qa.debian.org</literal> " -"email address." +"do so by using the <literal><package>@&pts-host;</literal> email " +"address." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:177 +#: beyond-pkging.dbk:180 msgid "Dealing with inactive and/or unreachable maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:179 +#: beyond-pkging.dbk:182 msgid "" "If you notice that a package is lacking maintenance, you should make sure " "that the maintainer is active and will continue to work on their packages. " @@ -283,32 +278,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:186 +#: beyond-pkging.dbk:189 msgid "" "There is a simple system (the MIA database) in which information about " "maintainers who are deemed Missing In Action is recorded. When a member of " "the QA group contacts an inactive maintainer or finds more information about " -"one, this is recorded in the MIA database. This system is available in " -"/org/qa.debian.org/mia on the host qa.debian.org, and can be queried with a " -"tool known as <command>mia-query</command>. Use" -msgstr "" - -# type: Content of: <chapter><section><screen> -#: beyond-pkging.dbk:194 -#, no-wrap -msgid "-query --help" -msgstr "" - -# type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:197 -msgid "" -"to see how to query the database. If you find that no information has been " -"recorded about an inactive maintainer yet, or that you can add more " +"one, this is recorded in the MIA database. This system is available in /org/" +"qa.debian.org/mia on the host qa.debian.org, and can be queried with a tool " +"known as <command>mia-query</command>. Use <command>mia-query --help</" +"command> to see how to query the database. If you find that no information " +"has been recorded about an inactive maintainer yet, or that you can add more " "information, you should generally proceed as follows." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:202 +#: beyond-pkging.dbk:200 msgid "" "The first step is to politely contact the maintainer, and wait a reasonable " "time for a response. It is quite hard to define reasonable time, but it is " @@ -317,7 +301,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:208 +#: beyond-pkging.dbk:206 msgid "" "If the maintainer doesn't reply within four weeks (a month), one can assume " "that a response will probably not happen. If that happens, you should " @@ -326,17 +310,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:216 +#: beyond-pkging.dbk:214 msgid "" -"The echelon information available through the <ulink " -"url=\"https://db.debian.org/\">developers' LDAP database</ulink>, which " -"indicates when the developer last posted to a Debian mailing list. (This " -"includes uploads via debian-*-changes lists.) Also, remember to check " -"whether the maintainer is marked as on vacation in the database." +"The echelon information available through the <ulink url=\"&url-debian-db;" +"\">developers' LDAP database</ulink>, which indicates when the developer " +"last posted to a Debian mailing list. (This includes uploads via debian-*-" +"changes lists.) Also, remember to check whether the maintainer is marked as " +"on vacation in the database." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:225 +#: beyond-pkging.dbk:223 msgid "" "The number of packages this maintainer is responsible for, and the condition " "of those packages. In particular, are there any RC bugs that have been open " @@ -346,7 +330,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:234 +#: beyond-pkging.dbk:232 msgid "" "Is there any activity of the maintainer outside of Debian? For example, they " "might have posted something recently to non-Debian mailing lists or news " @@ -354,7 +338,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:241 +#: beyond-pkging.dbk:239 msgid "" "A bit of a problem are packages which were sponsored — the maintainer is not " "an official Debian developer. The echelon information is not available for " @@ -365,28 +349,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:249 +#: beyond-pkging.dbk:247 msgid "" -"It is also allowed to post a query to " -"<email>debian-devel@lists.debian.org</email>, asking if anyone is aware of " -"the whereabouts of the missing maintainer. Please Cc: the person in " -"question." +"It is also allowed to post a query to &email-debian-devel;, asking if anyone " +"is aware of the whereabouts of the missing maintainer. Please Cc: the " +"person in question." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:254 +#: beyond-pkging.dbk:252 msgid "" -"Once you have gathered all of this, you can contact " -"<email>mia@qa.debian.org</email>. People on this alias will use the " -"information you provide in order to decide how to proceed. For example, " -"they might orphan one or all of the packages of the maintainer. If a " -"package has been NMUed, they might prefer to contact the NMUer before " -"orphaning the package — perhaps the person who has done the NMU is " -"interested in the package." +"Once you have gathered all of this, you can contact &email-mia;. People on " +"this alias will use the information you provide in order to decide how to " +"proceed. For example, they might orphan one or all of the packages of the " +"maintainer. If a package has been NMUed, they might prefer to contact the " +"NMUer before orphaning the package — perhaps the person who has done the NMU " +"is interested in the package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:262 +#: beyond-pkging.dbk:260 msgid "" "One last word: please remember to be polite. We are all volunteers and " "cannot dedicate all of our time to Debian. Also, you are not aware of the " @@ -397,7 +379,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:270 +#: beyond-pkging.dbk:268 msgid "" "On the other hand, although we are volunteers, we do have a responsibility. " "So you can stress the importance of the greater good — if a maintainer does " @@ -406,21 +388,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:276 +#: beyond-pkging.dbk:274 msgid "" "If you are interested in working in the MIA team, please have a look at the " "README file in /org/qa.debian.org/mia on qa.debian.org where the technical " -"details and the MIA procedures are documented and contact " -"<email>mia@qa.debian.org</email>." +"details and the MIA procedures are documented and contact &email-mia;." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:284 +#: beyond-pkging.dbk:282 msgid "Interacting with prospective Debian developers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:286 +#: beyond-pkging.dbk:284 msgid "" "Debian's success depends on its ability to attract and retain new and " "talented volunteers. If you are an experienced developer, we recommend that " @@ -429,12 +410,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:292 +#: beyond-pkging.dbk:290 msgid "Sponsoring packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:294 +#: beyond-pkging.dbk:292 msgid "" "Sponsoring a package means uploading a package for a maintainer who is not " "able to do it on their own, a new maintainer applicant. Sponsoring a " @@ -442,7 +423,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:299 +#: beyond-pkging.dbk:303 msgid "" "New maintainers usually have certain difficulties creating Debian packages — " "this is quite understandable. That is why the sponsor is there, to check " @@ -452,7 +433,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:306 +#: beyond-pkging.dbk:310 msgid "" "Sponsoring merely by signing the upload or just recompiling is <emphasis " "role=\"strong\">definitely not recommended</emphasis>. You need to build " @@ -463,7 +444,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:313 +#: beyond-pkging.dbk:317 msgid "" "If you are an application manager for a prospective developer, you can also " "be their sponsor. That way you can also verify how the applicant is " @@ -471,12 +452,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:320 +#: beyond-pkging.dbk:324 msgid "Managing sponsored packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:322 +#: beyond-pkging.dbk:326 msgid "" "By uploading a sponsored package to Debian, you are certifying that the " "package meets minimum Debian standards. That implies that you must build " @@ -484,19 +465,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:327 +#: beyond-pkging.dbk:331 msgid "" "You cannot simply upload a binary <filename>.deb</filename> from the " "sponsoree. In theory, you should only ask for the diff file and the " "location of the original source tarball, and then you should download the " "source and apply the diff yourself. In practice, you may want to use the " "source package built by your sponsoree. In that case, you have to check " -"that they haven't altered the upstream files in the " -"<filename>.orig.tar.gz</filename> file that they're providing." +"that they haven't altered the upstream files in the <filename>.orig.tar.gz</" +"filename> file that they're providing." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:336 +#: beyond-pkging.dbk:340 msgid "" "Do not be afraid to write the sponsoree back and point out changes that need " "to be made. It often takes several rounds of back-and-forth email before " @@ -504,18 +485,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:341 +#: beyond-pkging.dbk:345 msgid "Once the package meets Debian standards, build and sign it with" msgstr "" # type: Content of: <chapter><section><section><screen> -#: beyond-pkging.dbk:344 +#: beyond-pkging.dbk:348 #, no-wrap -msgid "-buildpackage -k<replaceable>KEY-ID</replaceable>" +msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:347 +#: beyond-pkging.dbk:351 msgid "" "before uploading it to the incoming directory. Of course, you can also use " "any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique " @@ -523,7 +504,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:352 +#: beyond-pkging.dbk:356 msgid "" "The Maintainer field of the <filename>control</filename> file and the " "<filename>changelog</filename> should list the person who did the packaging, " @@ -532,41 +513,39 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:358 +#: beyond-pkging.dbk:362 msgid "" "If you prefer to leave a more evident trace of your sponsorship job, you can " "add a line stating it in the most recent changelog entry." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:362 +#: beyond-pkging.dbk:366 msgid "" "You are encouraged to keep tabs on the package you sponsor using <xref " "linkend=\"pkg-tracking-system\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:368 +#: beyond-pkging.dbk:372 msgid "Advocating new developers" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:370 +#: beyond-pkging.dbk:374 msgid "" -"See the page about <ulink " -"url=\"http://www.debian.org/devel/join/nm-advocate\">advocating a " +"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a " "prospective developer</ulink> at the Debian web site." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:377 +#: beyond-pkging.dbk:381 msgid "Handling new maintainer applications" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:379 +#: beyond-pkging.dbk:383 msgid "" -"Please see <ulink " -"url=\"http://www.debian.org/devel/join/nm-amchecklist\">Checklist for " +"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for " "Application Managers</ulink> at the Debian web site." msgstr "" diff --git a/po4a/ja/developer-duties.po b/po4a/ja/developer-duties.po index 487ca81..21ed3d3 100644 --- a/po4a/ja/developer-duties.po +++ b/po4a/ja/developer-duties.po @@ -6,59 +6,59 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: developer-duties.dbk:5 +#: developer-duties.dbk:7 msgid "Debian Developer's Duties" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:7 +#: developer-duties.dbk:9 msgid "Maintaining your Debian information" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:9 +#: developer-duties.dbk:11 msgid "" "There's a LDAP database containing information about Debian developers at " -"<ulink url=\"https://db.debian.org/\"></ulink>. You should enter your " -"information there and update it as it changes. Most notably, make sure that " -"the address where your debian.org email gets forwarded to is always up to " -"date, as well as the address where you get your debian-private subscription " -"if you choose to subscribe there." +"<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information " +"there and update it as it changes. Most notably, make sure that the address " +"where your debian.org email gets forwarded to is always up to date, as well " +"as the address where you get your debian-private subscription if you choose " +"to subscribe there." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:17 +#: developer-duties.dbk:19 msgid "" -"For more information about the database, please see <xref " -"linkend=\"devel-db\"/> ." +"For more information about the database, please see <xref linkend=\"devel-db" +"\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:23 +#: developer-duties.dbk:25 msgid "Maintaining your public key" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:25 +#: developer-duties.dbk:27 msgid "" "Be very careful with your private keys. Do not place them on any public " -"servers or multiuser machines, such as the Debian servers (see <xref " -"linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. " -"Read the documentation that comes with your software; read the <ulink " -"url=\"http://www.cam.ac.uk.pgp.net/pgpnet/pgp-faq/\">PGP FAQ</ulink>." +"servers or multiuser machines, such as the Debian servers (see <xref linkend=" +"\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the " +"documentation that comes with your software; read the <ulink url=\"&url-pgp-" +"faq;\">PGP FAQ</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:32 +#: developer-duties.dbk:34 msgid "" "You need to ensure not only that your key is secure against being stolen, " "but also that it is secure against being lost. Generate and make a copy " @@ -67,90 +67,87 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:38 +#: developer-duties.dbk:40 msgid "" "If you add signatures to your public key, or add user identities, you can " "update the Debian key ring by sending your key to the key server at " -"<literal>keyring.debian.org</literal>." +"<literal>&keyserver-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:43 +#: developer-duties.dbk:45 msgid "" "If you need to add a completely new key or remove an old key, you need to " "get the new key signed by another developer. If the old key is compromised " "or invalid, you also have to add the revocation certificate. If there is no " "real reason for a new key, the Keyring Maintainers might reject the new " -"key. Details can be found at <ulink " -"url=\"http://keyring.debian.org/replacing_keys.html\"></ulink>." +"key. Details can be found at <ulink url=\"http://&keyserver-host;/" +"replacing_keys.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:51 +#: developer-duties.dbk:53 msgid "" -"The same key extraction routines discussed in <xref " -"linkend=\"registering\"/> apply." +"The same key extraction routines discussed in <xref linkend=\"registering\"/" +"> apply." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:55 +#: developer-duties.dbk:57 msgid "" "You can find a more in-depth discussion of Debian key maintenance in the " -"documentation of the <systemitem " -"role=\"package\">debian-keyring</systemitem> package." +"documentation of the <systemitem role=\"package\">debian-keyring</" +"systemitem> package." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:62 +#: developer-duties.dbk:64 msgid "Voting" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:64 +#: developer-duties.dbk:66 msgid "" "Even though Debian isn't really a democracy, we use a democratic process to " "elect our leaders and to approve general resolutions. These procedures are " -"defined by the <ulink " -"url=\"http://www.debian.org/devel/constitution\">Debian " -"Constitution</ulink>." +"defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:70 +#: developer-duties.dbk:72 msgid "" "Other than the yearly leader election, votes are not routinely held, and " "they are not undertaken lightly. Each proposal is first discussed on the " -"<email>debian-vote@lists.debian.org</email> mailing list and it requires " -"several endorsements before the project secretary starts the voting " -"procedure." +"&email-debian-vote; mailing list and it requires several endorsements before " +"the project secretary starts the voting procedure." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:76 +#: developer-duties.dbk:78 msgid "" "You don't have to track the pre-vote discussions, as the secretary will " -"issue several calls for votes on " -"<email>debian-devel-announce@lists.debian.org</email> (and all developers " -"are expected to be subscribed to that list). Democracy doesn't work well if " -"people don't take part in the vote, which is why we encourage all developers " -"to vote. Voting is conducted via GPG-signed/encrypted email messages." +"issue several calls for votes on &email-debian-devel-announce; (and all " +"developers are expected to be subscribed to that list). Democracy doesn't " +"work well if people don't take part in the vote, which is why we encourage " +"all developers to vote. Voting is conducted via GPG-signed/encrypted email " +"messages." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:84 +#: developer-duties.dbk:86 msgid "" -"The list of all proposals (past and current) is available on the <ulink " -"url=\"http://www.debian.org/vote/\">Debian Voting Information</ulink> page, " -"along with information on how to make, second and vote on proposals." +"The list of all proposals (past and current) is available on the <ulink url=" +"\"&url-vote;\">Debian Voting Information</ulink> page, along with " +"information on how to make, second and vote on proposals." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:91 +#: developer-duties.dbk:93 msgid "Going on vacation gracefully" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:93 +#: developer-duties.dbk:95 msgid "" "It is common for developers to have periods of absence, whether those are " "planned vacations or simply being buried in other work. The important thing " @@ -160,7 +157,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:100 +#: developer-duties.dbk:102 msgid "" "Usually this means that other developers are allowed to NMU (see <xref " "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, " @@ -170,30 +167,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote> -#: developer-duties.dbk:107 +#: developer-duties.dbk:109 msgid "" "In order to inform the other developers, there are two things that you " -"should do. First send a mail to " -"<email>debian-private@lists.debian.org</email> with [VAC] prepended to the " -"subject of your message<footnote>" +"should do. First send a mail to <email>debian-private@&lists-host;</email> " +"with [VAC] prepended to the subject of your message<footnote>" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: developer-duties.dbk:109 +#: developer-duties.dbk:111 msgid "" "This is so that the message can be easily filtered by people who don't want " "to read vacation notices." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:111 +#: developer-duties.dbk:113 msgid "" "</footnote> and state the period of time when you will be on vacation. You " "can also give some special instructions on what to do if a problem occurs." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:116 +#: developer-duties.dbk:118 msgid "" "The other thing to do is to mark yourself as on vacation in the <link " "linkend=\"devel-db\">Debian developers' LDAP database</link> (this " @@ -202,22 +198,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:122 +#: developer-duties.dbk:124 msgid "" -"Ideally, you should sign up at the <ulink " -"url=\"http://nm.debian.org/gpg.php\">GPG coordination site</ulink> when " -"booking a holiday and check if anyone there is looking for signing. This is " -"especially important when people go to exotic places where we don't have any " -"developers yet but where there are people who are interested in applying." +"Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php" +"\">GPG coordination site</ulink> when booking a holiday and check if anyone " +"there is looking for signing. This is especially important when people go " +"to exotic places where we don't have any developers yet but where there are " +"people who are interested in applying." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:131 +#: developer-duties.dbk:133 msgid "Coordination with upstream developers" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:133 +#: developer-duties.dbk:135 msgid "" "A big part of your job as Debian maintainer will be to stay in contact with " "the upstream developers. Debian users will sometimes report bugs that are " @@ -227,7 +223,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:140 +#: developer-duties.dbk:142 msgid "" "While it's not your job to fix non-Debian specific bugs, you may freely do " "so if you're able. When you make such fixes, be sure to pass them on to the " @@ -237,7 +233,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:147 +#: developer-duties.dbk:149 msgid "" "If you need to modify the upstream sources in order to build a policy " "compliant package, then you should propose a nice fix to the upstream " @@ -247,12 +243,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:156 +#: developer-duties.dbk:158 msgid "Managing release-critical bugs" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:158 +#: developer-duties.dbk:160 msgid "" "Generally you should deal with bug reports on your packages as described in " "<xref linkend=\"bug-handling\"/> . However, there's a special category of " @@ -266,47 +262,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:169 +#: developer-duties.dbk:171 msgid "" -"Developers who are part of the <ulink url=\"http://qa.debian.org/\">Quality " +"Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality " "Assurance</ulink> group are following all such bugs, and trying to help " "whenever possible. If, for any reason, you aren't able fix an RC bug in a " "package of yours within 2 weeks, you should either ask for help by sending a " -"mail to the Quality Assurance (QA) group " -"<email>debian-qa@lists.debian.org</email>, or explain your difficulties and " -"present a plan to fix them by sending a mail to the bug report. Otherwise, " -"people from the QA group may want to do a Non-Maintainer Upload (see <xref " -"linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long " -"as usual before they do their NMU if they have seen no recent activity from " -"you in the BTS)." +"mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</" +"email>, or explain your difficulties and present a plan to fix them by " +"sending a mail to the bug report. Otherwise, people from the QA group may " +"want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after " +"trying to contact you (they might not wait as long as usual before they do " +"their NMU if they have seen no recent activity from you in the BTS)." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:184 +#: developer-duties.dbk:186 msgid "Retiring" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:186 +#: developer-duties.dbk:188 msgid "" "If you choose to leave the Debian project, you should make sure you do the " "following steps:" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:192 -msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ." +#: developer-duties.dbk:194 +msgid "" +"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:197 +#: developer-duties.dbk:199 msgid "" "Send an gpg-signed email about why you are leaving the project to " -"<email>debian-private@lists.debian.org</email>." +"<email>debian-private@&lists-host;</email>." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:203 +#: developer-duties.dbk:205 msgid "" "Notify the Debian key ring maintainers that you are leaving by opening a " "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the " diff --git a/po4a/ja/index.po b/po4a/ja/index.po index 012c27e..54caab8 100644 --- a/po4a/ja/index.po +++ b/po4a/ja/index.po @@ -8,91 +8,99 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" -"PO-Revision-Date: 2007-06-27 23:32+0000\n" +"POT-Creation-Date: 2007-07-01 22:36+0000\n" +"PO-Revision-Date: 2007-07-01 23:36+0000\n" "Last-Translator: <>\n" "Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: " # type: Attribute 'lang' of: <book> -#: index.dbk:4 +#: index.dbk:7 msgid "en" msgstr "ja" # type: Content of: <book><title> -#: index.dbk:6 +#: index.dbk:9 msgid "Debian Developer's Reference" msgstr "Debian デベロッパーズリファレンス" # type: Content of: <book><bookinfo><releaseinfo> -#: index.dbk:27 -msgid "ver. 3.3.9, 16 June, 2007" -msgstr "ver.·3.3.9,·16·June,·2007" +#: index.dbk:30 +msgid "ver. &version;" +msgstr "ver.·&version;" + +# type: Content of: <book><bookinfo><pubdate> +#: index.dbk:31 +msgid "&pubdate;" +msgstr "&pubdate;" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:34 +#: index.dbk:37 msgid "Andreas Barth" msgstr "Andreas·Barth" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:43 +#: index.dbk:46 msgid "Adam Di Carlo" msgstr "Adam·Di·Carlo" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:48 +#: index.dbk:51 msgid "Raphaël Hertzog" msgstr "Raphaël·Hertzog" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:53 +#: index.dbk:56 msgid "Christian Schwarz" msgstr "Christian·Schwarz" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:57 +#: index.dbk:60 msgid "" "This manual is free software; you may redistribute it and/or modify it under " "the terms of the GNU General Public License as published by the Free " -"Software Foundation; either version 2, or (at your option) any later " -"version." -msgstr "このマニュアルはフリーソフトウェアです。あなたは、Free Software Foundation" -"が公表した GNU 一般公有使用許諾の第二版あるいはそれ以降のいずれかの版の" -"条件に基づいて、本文書の再配付および変更を行うことが可能です。" +"Software Foundation; either version 2, or (at your option) any later version." +msgstr "" +"このマニュアルはフリーソフトウェアです。あなたは、Free Software Foundationが" +"公表した GNU 一般公有使用許諾の第二版あるいはそれ以降のいずれかの版の条件に基" +"づいて、本文書の再配付および変更を行うことが可能です。" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:62 +#: index.dbk:65 msgid "" "This is distributed in the hope that it will be useful, but " "<emphasis>without any warranty</emphasis>; without even the implied warranty " "of merchantability or fitness for a particular purpose. See the GNU General " "Public License for more details." -msgstr "本文書はその有用性が期待されて配付されるものですが、" -"市場性や特定の目的への適合性に関する暗黙の保証も含め、" -"<emphasis>いかなる保証も行ないません</emphasis>。" -"詳細については GNU 一般公有使用許諾書をお読みください。" +msgstr "" +"本文書はその有用性が期待されて配付されるものですが、市場性や特定の目的への適" +"合性に関する暗黙の保証も含め、<emphasis>いかなる保証も行ないません</" +"emphasis>。詳細については GNU 一般公有使用許諾書をお読みください。" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:68 +#: index.dbk:71 msgid "" -"A copy of the GNU General Public License is available as " -"<filename>/usr/share/common-licenses/GPL</filename> in the Debian GNU/Linux " -"distribution or on the World Wide Web at <ulink " -"url=\"http://www.gnu.org/copyleft/gpl.html\">the GNU web site</ulink>. You " -"can also obtain it by writing to the Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA." -msgstr "GNU 一般公有使用許諾の写しは、Debian GNU/Linux ディストリビューションの" -"<filename>/usr/share/common-licenses/GPL</filename> や、WWW 上では <ulink url=\"http://www.gnu.org/copyleft/gpl.html\">GNU ウェブサイト</ulink>" -"にあります。また Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA へ手紙 (英語) で依頼し入手することもできます。" +"A copy of the GNU General Public License is available as &file-GPL; in the " +"&debian-formal; distribution or on the World Wide Web at <ulink url=\"&url-" +"gpl;\">the GNU web site</ulink>. You can also obtain it by writing to the " +"&fsf-addr;." +msgstr "" +"GNU 一般公有使用許諾の写しは、Debian GNU/Linux ディストリビューションの&file-" +"GPL; や、WWW 上では <ulink url=\"&url-gpl;\">GNU ウェブサイト</ulink>にありま" +"す。また &fsf-addr; へ手紙 (英語) で依頼し入手することもできます。" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:76 +#. TODO: Maybe better: "This document has originally been written +#. in English. Translations into different languages are available." +#: index.dbk:78 msgid "" -"If you want to print this reference, you should use the <ulink " -"url=\"developers-reference.pdf\">pdf version</ulink>. This page is also " +"If you want to print this reference, you should use the <ulink url=" +"\"developers-reference.pdf\">pdf version</ulink>. This page is also " "available in <ulink url=\"index.fr.html\">French</ulink>." msgstr "なお、この日本語訳については遠藤 美純 (1999 å¹´) に著作権があります。" +# type: Content of: <book><bookinfo><releaseinfo> +#~ msgid "ver. 3.3.9, 16 June, 2007" +#~ msgstr "ver.·3.3.9,·16·June,·2007" diff --git a/po4a/ja/l10n.po b/po4a/ja/l10n.po index d09b196..3b257f8 100644 --- a/po4a/ja/l10n.po +++ b/po4a/ja/l10n.po @@ -6,23 +6,22 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: l10n.dbk:5 +#: l10n.dbk:7 msgid "" -"Internationalizing, translating, being internationalized and being " -"translated" +"Internationalizing, translating, being internationalized and being translated" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:7 +#: l10n.dbk:9 msgid "" "Debian supports an ever-increasing number of natural languages. Even if you " "are a native English speaker and do not speak any other language, it is part " @@ -33,19 +32,19 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:15 +#: l10n.dbk:17 msgid "" -"According to <ulink " -"url=\"http://www.debian.org/doc/manuals/intro-i18n/\">Introduction to " -"i18n</ulink> from Tomohiro KUBOTA, I18N (internationalization) means " -"modification of a software or related technologies so that a software can " -"potentially handle multiple languages, customs, and so on in the world. " -"while L10N (localization) means implementation of a specific language for an " -"already internationalized software." +"According to <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/" +"\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N " +"(internationalization) means modification of a software or related " +"technologies so that a software can potentially handle multiple languages, " +"customs, and so on in the world. while L10N (localization) means " +"implementation of a specific language for an already internationalized " +"software." msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:24 +#: l10n.dbk:26 msgid "" "l10n and i18n are interconnected, but the difficulties related to each of " "them are very different. It's not really difficult to allow a program to " @@ -56,7 +55,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:32 +#: l10n.dbk:34 msgid "" "Setting aside the i18n problems, where no general guideline can be given, " "there is actually no central infrastructure for l10n within Debian which " @@ -65,36 +64,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:38 +#: l10n.dbk:40 msgid "How translations are handled within Debian" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:40 +#: l10n.dbk:42 msgid "" "Handling translation of the texts contained in a package is still a manual " -"task, and the process depends on the kind of text you want to see " -"translated." +"task, and the process depends on the kind of text you want to see translated." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:44 +#: l10n.dbk:46 msgid "" "For program messages, the gettext infrastructure is used most of the time. " "Most of the time, the translation is handled upstream within projects like " "the <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">Free " -"Translation Project</ulink>, the <ulink " -"url=\"http://developer.gnome.org/projects/gtp/\">Gnome translation " -"Project</ulink> or the <ulink url=\"http://i18n.kde.org/\">KDE one</ulink>. " -"The only centralized resource within Debian is the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " -"statistics</ulink>, where you can find some statistics about the translation " -"files found in the actual packages, but no real infrastructure to ease the " -"translation process." +"Translation Project</ulink>, the <ulink url=\"http://developer.gnome.org/" +"projects/gtp/\">Gnome translation Project</ulink> or the <ulink url=\"http://" +"i18n.kde.org/\">KDE one</ulink>. The only centralized resource within " +"Debian is the <ulink url=\"http://&www-debian-org;/intl/l10n/\">Central " +"Debian translation statistics</ulink>, where you can find some statistics " +"about the translation files found in the actual packages, but no real " +"infrastructure to ease the translation process." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:57 +#: l10n.dbk:59 msgid "" "An effort to translate the package descriptions started long ago, even if " "very little support is offered by the tools to actually use them (i.e., only " @@ -104,26 +101,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:64 +#: l10n.dbk:66 msgid "" "For debconf templates, maintainers should use the po-debconf package to ease " "the work of translators, who could use the DDTP to do their work (but the " "French and Brazilian teams don't). Some statistics can be found both on the " -"DDTP site (about what is actually translated), and on the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " +"DDTP site (about what is actually translated), and on the <ulink url=" +"\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink> site (about what is integrated in the packages)." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:72 +#: l10n.dbk:74 msgid "" "For web pages, each l10n team has access to the relevant CVS, and the " -"statistics are available from the Central Debian translation statistics " -"site." +"statistics are available from the Central Debian translation statistics site." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:76 +#: l10n.dbk:78 msgid "" "For general documentation about Debian, the process is more or less the same " "as for the web pages (the translators have access to the CVS), but there are " @@ -131,34 +127,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:81 +#: l10n.dbk:83 msgid "" "For package-specific documentation (man pages, info documents, other " "formats), almost everything remains to be done." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:85 +#: l10n.dbk:87 msgid "" "Most notably, the KDE project handles translation of its documentation in " "the same way as its program messages." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:89 +#: l10n.dbk:91 msgid "" -"There is an effort to handle Debian-specific man pages within a <ulink " -"url=\"http://cvs.debian.org/manpages/?cvsroot=debian-doc\">specific CVS " -"repository</ulink>." +"There is an effort to handle Debian-specific man pages within a <ulink url=" +"\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS repository</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:96 +#: l10n.dbk:98 msgid "I18N & L10N FAQ for maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:98 +#: l10n.dbk:100 msgid "" "This is a list of problems that maintainers may face concerning i18n and " "l10n. While reading this, keep in mind that there is no real consensus on " @@ -168,12 +163,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:105 +#: l10n.dbk:107 msgid "How to get a given text translated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:107 +#: l10n.dbk:109 msgid "" "To translate package descriptions or debconf templates, you have nothing to " "do; the DDTP infrastructure will dispatch the material to translate to " @@ -181,7 +176,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:112 +#: l10n.dbk:114 msgid "" "For all other material (gettext files, man pages, or other documentation), " "the best solution is to put your text somewhere on the Internet, and ask on " @@ -192,12 +187,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:122 +#: l10n.dbk:124 msgid "How to get a given translation reviewed" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:124 +#: l10n.dbk:126 msgid "" "From time to time, individuals translate some texts in your package and will " "ask you for inclusion of the translation in the package. This can become " @@ -208,12 +203,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:134 +#: l10n.dbk:136 msgid "How to get a given translation updated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:136 +#: l10n.dbk:138 msgid "" "If you have some translations of a given text lying around, each time you " "update the original, you should ask the previous translator to update the " @@ -222,7 +217,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:142 +#: l10n.dbk:144 msgid "" "If the translator is unresponsive, you may ask for help on the corresponding " "l10n mailing list. If everything fails, don't forget to put a warning in " @@ -231,7 +226,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:148 +#: l10n.dbk:150 msgid "" "Avoid removing a translation completely because it is outdated. Old " "documentation is often better than no documentation at all for non-English " @@ -239,12 +234,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:155 +#: l10n.dbk:157 msgid "How to handle a bug report concerning a translation" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:157 +#. TODO: add the i18n tag to the bug? +#: l10n.dbk:159 msgid "" "The best solution may be to mark the bug as forwarded to upstream, and " "forward it to both the previous translator and his/her team (using the " @@ -252,12 +248,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:166 +#: l10n.dbk:169 msgid "I18N & L10N FAQ for translators" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:168 +#: l10n.dbk:171 msgid "" "While reading this, please keep in mind that there is no general procedure " "within Debian concerning these points, and that in any case, you should " @@ -265,12 +261,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:173 +#: l10n.dbk:176 msgid "How to help the translation effort" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:175 +#: l10n.dbk:178 msgid "" "Choose what you want to translate, make sure that nobody is already working " "on it (using your debian-l10n-XXX mailing list), translate it, get it " @@ -279,12 +275,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:183 +#: l10n.dbk:186 msgid "How to provide a translation for inclusion in a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:185 +#: l10n.dbk:188 msgid "" "Make sure your translation is correct (asking for review on your l10n " "mailing list) before providing it for inclusion. It will save time for " @@ -293,7 +289,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:191 +#: l10n.dbk:194 msgid "" "The best solution is to file a regular bug containing the translation " "against the package. Make sure to use the 'PATCH' tag, and to not use a " @@ -302,12 +298,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:201 +#: l10n.dbk:204 msgid "Best current practice concerning l10n" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:205 +#: l10n.dbk:208 msgid "" "As a maintainer, never edit the translations in any way (even to reformat " "the layout) without asking on the corresponding l10n mailing list. You risk " @@ -316,7 +312,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:213 +#: l10n.dbk:216 msgid "" "As a translator, if you find an error in the original text, make sure to " "report it. Translators are often the most attentive readers of a given " @@ -324,7 +320,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:220 +#: l10n.dbk:223 msgid "" "In any case, remember that the major issue with l10n is that it requires " "several people to cooperate, and that it is very easy to start a flamewar " @@ -335,8 +331,8 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:230 +#: l10n.dbk:233 msgid "" -"In any case, cooperation can only be achieved with <emphasis " -"role=\"strong\">mutual respect</emphasis>." +"In any case, cooperation can only be achieved with <emphasis role=\"strong" +"\">mutual respect</emphasis>." msgstr "" diff --git a/po4a/ja/new-maintainer.po b/po4a/ja/new-maintainer.po index a48fcef..1dea9a5 100644 --- a/po4a/ja/new-maintainer.po +++ b/po4a/ja/new-maintainer.po @@ -1,56 +1,56 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:18+0000\n" +"PO-Revision-Date: 2007-07-01 23:37+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: new-maintainer.dbk:5 +#: new-maintainer.dbk:7 msgid "Applying to Become a Maintainer" -msgstr "" +msgstr "開発者になるための申し込み" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:7 +#: new-maintainer.dbk:9 msgid "Getting started" -msgstr "" +msgstr "はじめよう" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:9 +#: new-maintainer.dbk:11 msgid "" -"So, you've read all the documentation, you've gone through the <ulink " -"url=\"http://www.debian.org/doc/maint-guide/\">Debian New Maintainers' " -"Guide</ulink>, understand what everything in the <systemitem " -"role=\"package\">hello</systemitem> example package is for, and you're about " -"to Debianize your favorite piece of software. How do you actually become a " -"Debian developer so that your work can be incorporated into the Project?" +"So, you've read all the documentation, you've gone through the <ulink url=" +"\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, understand " +"what everything in the <systemitem role=\"package\">hello</systemitem> " +"example package is for, and you're about to Debianize your favorite piece of " +"software. How do you actually become a Debian developer so that your work " +"can be incorporated into the Project?" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:17 +#: new-maintainer.dbk:19 msgid "" -"Firstly, subscribe to <email>debian-devel@lists.debian.org</email> if you " -"haven't already. Send the word <literal>subscribe</literal> in the " -"<emphasis>Subject</emphasis> of an email to " -"<email>debian-devel-REQUEST@lists.debian.org</email>. In case of problems, " -"contact the list administrator at " -"<email>listmaster@lists.debian.org</email>. More information on available " -"mailing lists can be found in <xref linkend=\"mailing-lists\"/> . " -"<email>debian-devel-announce@lists.debian.org</email> is another list which " -"is mandatory for anyone who wishes to follow Debian's development." +"Firstly, subscribe to &email-debian-devel; if you haven't already. Send the " +"word <literal>subscribe</literal> in the <emphasis>Subject</emphasis> of an " +"email to &email-debian-devel-req;. In case of problems, contact the list " +"administrator at &email-listmaster;. More information on available mailing " +"lists can be found in <xref linkend=\"mailing-lists\"/> . &email-debian-" +"devel-announce; is another list which is mandatory for anyone who wishes to " +"follow Debian's development." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:28 +#: new-maintainer.dbk:29 msgid "" "You should subscribe and lurk (that is, read without posting) for a bit " "before doing any coding, and you should post about your intentions to work " @@ -58,43 +58,39 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:33 +#: new-maintainer.dbk:34 msgid "" -"Another good list to subscribe to is " -"<email>debian-mentors@lists.debian.org</email>. See <xref " -"linkend=\"mentors\"/> for details. The IRC channel " -"<literal>#debian</literal> can also be helpful; see <xref " -"linkend=\"irc-channels\"/> ." +"Another good list to subscribe to is &email-debian-mentors;. See <xref " +"linkend=\"mentors\"/> for details. The IRC channel <literal>#debian</" +"literal> can also be helpful; see <xref linkend=\"irc-channels\"/> ." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:39 +#: new-maintainer.dbk:40 msgid "" -"When you know how you want to contribute to Debian GNU/Linux, you should get " +"When you know how you want to contribute to &debian-formal;, you should get " "in contact with existing Debian maintainers who are working on similar " "tasks. That way, you can learn from experienced developers. For example, " "if you are interested in packaging existing software for Debian, you should " "try to get a sponsor. A sponsor will work together with you on your package " "and upload it to the Debian archive once they are happy with the packaging " -"work you have done. You can find a sponsor by mailing the " -"<email>debian-mentors@lists.debian.org</email> mailing list, describing your " -"package and yourself and asking for a sponsor (see <xref " -"linkend=\"sponsoring\"/> and <ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"for more information on sponsoring). On the other hand, if you are " -"interested in porting Debian to alternative architectures or kernels you can " -"subscribe to port specific mailing lists and ask there how to get started. " -"Finally, if you are interested in documentation or Quality Assurance (QA) " -"work you can join maintainers already working on these tasks and submit " -"patches and improvements." +"work you have done. You can find a sponsor by mailing the &email-debian-" +"mentors; mailing list, describing your package and yourself and asking for a " +"sponsor (see <xref linkend=\"sponsoring\"/> and <ulink url=\"&url-mentors;" +"\"></ulink> for more information on sponsoring). On the other hand, if you " +"are interested in porting Debian to alternative architectures or kernels you " +"can subscribe to port specific mailing lists and ask there how to get " +"started. Finally, if you are interested in documentation or Quality " +"Assurance (QA) work you can join maintainers already working on these tasks " +"and submit patches and improvements." msgstr "" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:57 msgid "" "One pitfall could be a too-generic local part in your mailadress: Terms like " -"mail, admin, root, master should be avoided, please see <ulink " -"url=\"http://www.debian.org/MailingLists/\"></ulink> for details." +"mail, admin, root, master should be avoided, please see <ulink url=\"&url-" +"debian-lists;\"></ulink> for details." msgstr "" # type: Content of: <chapter><section><title> @@ -105,10 +101,10 @@ msgstr "" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:66 msgid "" -"The mailing list <email>debian-mentors@lists.debian.org</email> has been set " -"up for novice maintainers who seek help with initial packaging and other " -"developer-related issues. Every new developer is invited to subscribe to " -"that list (see <xref linkend=\"mailing-lists\"/> for details)." +"The mailing list &email-debian-mentors; has been set up for novice " +"maintainers who seek help with initial packaging and other developer-related " +"issues. Every new developer is invited to subscribe to that list (see <xref " +"linkend=\"mailing-lists\"/> for details)." msgstr "" # type: Content of: <chapter><section><para> @@ -118,7 +114,14 @@ msgid "" "to that list and an experienced developer will volunteer to help." msgstr "" +# +# +# +# # type: Content of: <chapter><section><para> +#. FIXME - out of order +#. Those who are seeking a +#. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/"></ulink>. #: new-maintainer.dbk:76 msgid "" "In addition, if you have some packages ready for inclusion in Debian, but " @@ -126,53 +129,50 @@ msgid "" "able find a sponsor to upload your package for you. Sponsors are people who " "are official Debian Developers, and who are willing to criticize and upload " "your packages for you. Please read the unofficial debian-mentors FAQ at " -"<ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"first." +"<ulink url=\"&url-mentors;\"></ulink> first." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:84 +#: new-maintainer.dbk:89 msgid "" "If you wish to be a mentor and/or sponsor, more information is available in " "<xref linkend=\"newmaint\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:90 +#: new-maintainer.dbk:95 msgid "Registering as a Debian developer" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:92 +#: new-maintainer.dbk:97 msgid "" -"Before you decide to register with Debian GNU/Linux, you will need to read " -"all the information available at the <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink>. It describes in detail the preparations you have to do " -"before you can register to become a Debian developer. For example, before " -"you apply, you have to read the <ulink " -"url=\"http://www.debian.org/social_contract\">Debian Social " -"Contract</ulink>. Registering as a developer means that you agree with and " -"pledge to uphold the Debian Social Contract; it is very important that " -"maintainers are in accord with the essential ideas behind Debian GNU/Linux. " -"Reading the <ulink url=\"http://www.gnu.org/gnu/manifesto.html\">GNU " +"Before you decide to register with &debian-formal;, you will need to read " +"all the information available at the <ulink url=\"&url-newmaint;\">New " +"Maintainer's Corner</ulink>. It describes in detail the preparations you " +"have to do before you can register to become a Debian developer. For " +"example, before you apply, you have to read the <ulink url=\"&url-social-" +"contract;\">Debian Social Contract</ulink>. Registering as a developer " +"means that you agree with and pledge to uphold the Debian Social Contract; " +"it is very important that maintainers are in accord with the essential ideas " +"behind &debian-formal;. Reading the <ulink url=\"&url-gnu-manifesto;\">GNU " "Manifesto</ulink> would also be a good idea." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:105 +#: new-maintainer.dbk:111 msgid "" "The process of registering as a developer is a process of verifying your " "identity and intentions, and checking your technical skills. As the number " -"of people working on Debian GNU/Linux has grown to over 900 and our systems " -"are used in several very important places, we have to be careful about being " -"compromised. Therefore, we need to verify new maintainers before we can " -"give them accounts on our servers and let them upload packages." +"of people working on &debian-formal; has grown to over &number-of-" +"maintainers; and our systems are used in several very important places, we " +"have to be careful about being compromised. Therefore, we need to verify " +"new maintainers before we can give them accounts on our servers and let them " +"upload packages." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:113 +#: new-maintainer.dbk:120 msgid "" "Before you actually register you should have shown that you can do competent " "work and will be a good contributor. You show this by submitting patches " @@ -184,23 +184,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:122 +#: new-maintainer.dbk:129 msgid "" "Registration requires that you are familiar with Debian's philosophy and " "technical documentation. Furthermore, you need a GnuPG key which has been " "signed by an existing Debian maintainer. If your GnuPG key is not signed " "yet, you should try to meet a Debian Developer in person to get your key " -"signed. There's a <ulink url=\"http://nm.debian.org/gpg.php\">GnuPG Key " -"Signing Coordination page</ulink> which should help you find a Debian " -"Developer close to you. (If there is no Debian Developer close to you, " -"alternative ways to pass the ID check may be permitted as an absolute " -"exception on a case-by-case-basis. See the <ulink " -"url=\"http://www.debian.org/devel/join/nm-step2\">identification " +"signed. There's a <ulink url=\"&url-gpg-coord;\">GnuPG Key Signing " +"Coordination page</ulink> which should help you find a Debian Developer " +"close to you. (If there is no Debian Developer close to you, alternative " +"ways to pass the ID check may be permitted as an absolute exception on a " +"case-by-case-basis. See the <ulink url=\"&url-newmaint-id;\">identification " "page</ulink> for more information.)" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:135 +#: new-maintainer.dbk:142 msgid "" "If you do not have an OpenPGP key yet, generate one. Every developer needs " "an OpenPGP key in order to sign and verify package uploads. You should read " @@ -212,17 +211,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:143 +#: new-maintainer.dbk:150 msgid "" "Debian uses the <command>GNU Privacy Guard</command> (package <systemitem " "role=\"package\">gnupg</systemitem> version 1 or better) as its baseline " "standard. You can use some other implementation of OpenPGP as well. Note " -"that OpenPGP is an open standard based on <ulink " -"url=\"http://www.rfc-editor.org/rfc/rfc2440.txt\">RFC 2440</ulink>." +"that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC " +"2440</ulink>." msgstr "" # type: Content of: <chapter><section><para><footnote> -#: new-maintainer.dbk:150 +#: new-maintainer.dbk:157 msgid "" "You need a version 4 key for use in Debian Development. Your key length " "must be at least 1024 bits; there is no reason to use a smaller key, and " @@ -230,7 +229,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:152 +#: new-maintainer.dbk:159 msgid "" "Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC " "2440. Version 4 is the key type that has always been created when using " @@ -239,7 +238,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:156 +#: new-maintainer.dbk:163 msgid "" "Version 4 (primary) keys can either use the RSA or the DSA algorithms, so " "this has nothing to do with GnuPG's question about which kind of key do you " @@ -248,27 +247,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:160 +#: new-maintainer.dbk:167 msgid "" "The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) " "key is to look at the fingerprint: Fingerprints of version 4 keys are the " "SHA-1 hash of some key matieral, so they are 40 hex digits, usually grouped " "in blocks of 4. Fingerprints of older key format versions used MD5 and are " "generally shown in blocks of 2 hex digits. For example if your fingerprint " -"looks like " -"<literal>5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F</literal> then " -"it's a v4 key." +"looks like <literal>5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F</" +"literal> then it's a v4 key." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:167 +#: new-maintainer.dbk:174 msgid "" "Another possibility is to pipe the key into <command>pgpdump</command>, " "which will say something like Public Key Packet - Ver 4." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:169 +#: new-maintainer.dbk:176 msgid "" "Also note that your key must be self-signed (i.e. it has to sign all its " "own user IDs; this prevents user ID tampering). All modern OpenPGP software " @@ -277,18 +275,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:175 +#: new-maintainer.dbk:182 msgid "" -"If your public key isn't on a public key server such as " -"<literal>subkeys.pgp.net</literal>, please read the documentation available " -"at <ulink url=\"http://www.debian.org/devel/join/nm-step2\">NM Step 2: " -"Identification</ulink>. That document contains instructions on how to put " -"your key on the public key servers. The New Maintainer Group will put your " -"public key on the servers if it isn't already there." +"If your public key isn't on a public key server such as &pgp-keyserv;, " +"please read the documentation available at <ulink url=\"&url-newmaint-id;" +"\">NM Step 2: Identification</ulink>. That document contains instructions " +"on how to put your key on the public key servers. The New Maintainer Group " +"will put your public key on the servers if it isn't already there." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:183 +#: new-maintainer.dbk:190 msgid "" "Some countries restrict the use of cryptographic software by their " "citizens. This need not impede one's activities as a Debian package " @@ -299,7 +296,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:191 +#: new-maintainer.dbk:198 msgid "" "To apply as a new maintainer, you need an existing Debian Developer to " "support your application (an <emphasis>advocate</emphasis>). After you have " @@ -310,24 +307,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:198 +#: new-maintainer.dbk:205 msgid "" "When you have found an advocate, have your GnuPG key signed and have already " "contributed to Debian for a while, you're ready to apply. You can simply " -"register on our <ulink url=\"http://nm.debian.org/newnm.php\">application " -"page</ulink>. After you have signed up, your advocate has to confirm your " +"register on our <ulink url=\"&url-newmaint-apply;\">application page</" +"ulink>. After you have signed up, your advocate has to confirm your " "application. When your advocate has completed this step you will be " "assigned an Application Manager who will go with you through the necessary " "steps of the New Maintainer process. You can always check your status on " -"the <ulink url=\"http://nm.debian.org/\">applications status board</ulink>." +"the <ulink url=\"&url-newmaint-db;\">applications status board</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:208 +#: new-maintainer.dbk:215 msgid "" -"For more details, please consult <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink> at the Debian web site. Make sure that you are familiar with " -"the necessary steps of the New Maintainer process before actually applying. " -"If you are well prepared, you can save a lot of time later on." +"For more details, please consult <ulink url=\"&url-newmaint;\">New " +"Maintainer's Corner</ulink> at the Debian web site. Make sure that you are " +"familiar with the necessary steps of the New Maintainer process before " +"actually applying. If you are well prepared, you can save a lot of time " +"later on." msgstr "" + diff --git a/po4a/ja/pkgs.po b/po4a/ja/pkgs.po index 994e65d..8af09ab 100644 --- a/po4a/ja/pkgs.po +++ b/po4a/ja/pkgs.po @@ -6,45 +6,44 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: pkgs.dbk:5 +#: pkgs.dbk:7 msgid "Managing Packages" msgstr "" # type: Content of: <chapter><para> -#: pkgs.dbk:7 +#: pkgs.dbk:9 msgid "" "This chapter contains information related to creating, uploading, " "maintaining, and porting packages." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:11 +#: pkgs.dbk:13 msgid "New packages" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:13 +#: pkgs.dbk:15 msgid "" "If you want to create a new package for the Debian distribution, you should " -"first check the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " +"first check the <ulink url=\"&url-wnpp;\">Work-Needing and Prospective " "Packages (WNPP)</ulink> list. Checking the WNPP list ensures that no one is " "already working on packaging that software, and that effort is not " -"duplicated. Read the <ulink url=\"http://www.debian.org/devel/wnpp/\">WNPP " -"web pages</ulink> for more information." +"duplicated. Read the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink> for " +"more information." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:21 +#: pkgs.dbk:23 msgid "" "Assuming no one else is already working on your prospective package, you " "must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the " @@ -55,31 +54,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:29 +#: pkgs.dbk:31 msgid "" -"You should set the subject of the bug to ``ITP: " -"<replaceable>foo</replaceable> -- <replaceable>short " -"description</replaceable>'', substituting the name of the new package for " -"<replaceable>foo</replaceable>. The severity of the bug report must be set " -"to <emphasis>wishlist</emphasis>. If you feel it's necessary, send a copy " -"to <email>debian-devel@lists.debian.org</email> by putting the address in " -"the <literal>X-Debbugs-CC:</literal> header of the message (no, don't use " -"<literal>CC:</literal>, because that way the message's subject won't " -"indicate the bug number)." +"You should set the subject of the bug to ``ITP: <replaceable>foo</" +"replaceable> -- <replaceable>short description</replaceable>'', substituting " +"the name of the new package for <replaceable>foo</replaceable>. The " +"severity of the bug report must be set to <emphasis>wishlist</emphasis>. If " +"you feel it's necessary, send a copy to &email-debian-devel; by putting the " +"address in the <literal>X-Debbugs-CC:</literal> header of the message (no, " +"don't use <literal>CC:</literal>, because that way the message's subject " +"won't indicate the bug number)." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:39 +#: pkgs.dbk:41 msgid "" -"Please include a <literal>Closes: " -"bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the " -"new package in order for the bug report to be automatically closed once the " -"new package is installed in the archive (see <xref " -"linkend=\"upload-bugfix\"/> )." +"Please include a <literal>Closes: bug#<replaceable>nnnnn</replaceable></" +"literal> entry in the changelog of the new package in order for the bug " +"report to be automatically closed once the new package is installed in the " +"archive (see <xref linkend=\"upload-bugfix\"/> )." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:45 +#: pkgs.dbk:47 msgid "" "When closing security bugs include CVE numbers as well as the Closes: " "#nnnnn. This is useful for the security team to track vulnerabilities. If " @@ -90,14 +87,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:53 +#: pkgs.dbk:55 msgid "" "There are a number of reasons why we ask maintainers to announce their " "intentions:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:59 +#: pkgs.dbk:61 msgid "" "It helps the (potentially new) maintainer to tap into the experience of " "people on the list, and lets them know if anyone else is working on it " @@ -105,14 +102,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:65 +#: pkgs.dbk:67 msgid "" "It lets other people thinking about working on the package know that there " "already is a volunteer, so efforts may be shared." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:71 +#: pkgs.dbk:73 msgid "" "It lets the rest of the maintainers know more about the package than the one " "line description and the usual changelog entry ``Initial release'' that gets " @@ -120,98 +117,96 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:78 +#: pkgs.dbk:80 msgid "" "It is helpful to the people who live off unstable (and form our first line " "of testers). We should encourage these people." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:84 +#: pkgs.dbk:86 msgid "" "The announcements give maintainers and other interested parties a better " "feel of what is going on, and what is new, in the project." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:90 +#: pkgs.dbk:92 msgid "" -"Please see <ulink " -"url=\"http://ftp-master.debian.org/REJECT-FAQ.html\"></ulink> for common " -"rejection reasons for a new package." +"Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> " +"for common rejection reasons for a new package." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:96 +#: pkgs.dbk:98 msgid "Recording changes in the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:98 +#: pkgs.dbk:100 msgid "" "Changes that you make to the package need to be recorded in the " "<filename>debian/changelog</filename>. These changes should provide a " "concise description of what was changed, why (if it's in doubt), and note if " "any bugs were closed. They also record when the package was completed. " -"This file will be installed in " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.Debian.gz</filename>, " -"or " -"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</filename> " -"for native packages." +"This file will be installed in <filename>/usr/share/doc/" +"<replaceable>package</replaceable>/changelog.Debian.gz</filename>, or " +"<filename>/usr/share/doc/<replaceable>package</replaceable>/changelog.gz</" +"filename> for native packages." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:109 +#: pkgs.dbk:111 msgid "" "The <filename>debian/changelog</filename> file conforms to a certain " "structure, with a number of different fields. One field of note, the " -"<emphasis>distribution</emphasis>, is described in <xref " -"linkend=\"distribution\"/> . More information about the structure of this " -"file can be found in the Debian Policy section titled " -"<filename>debian/changelog</filename>." +"<emphasis>distribution</emphasis>, is described in <xref linkend=" +"\"distribution\"/> . More information about the structure of this file can " +"be found in the Debian Policy section titled <filename>debian/changelog</" +"filename>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:117 +#: pkgs.dbk:119 msgid "" "Changelog entries can be used to automatically close Debian bugs when the " -"package is installed into the archive. See <xref " -"linkend=\"upload-bugfix\"/> ." +"package is installed into the archive. See <xref linkend=\"upload-bugfix\"/" +"> ." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:121 +#: pkgs.dbk:123 msgid "" "It is conventional that the changelog entry of a package that contains a new " "upstream version of the software looks like this:" msgstr "" # type: Content of: <chapter><section><screen> -#: pkgs.dbk:125 +#: pkgs.dbk:127 #, no-wrap msgid "* new upstream version" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:128 +#: pkgs.dbk:130 msgid "" "There are tools to help you create entries and finalize the " -"<filename>changelog</filename> for release — see <xref " -"linkend=\"devscripts\"/> and <xref linkend=\"dpkg-dev-el\"/> ." +"<filename>changelog</filename> for release — see <xref linkend=\"devscripts" +"\"/> and <xref linkend=\"dpkg-dev-el\"/> ." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:133 +#: pkgs.dbk:135 msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:138 +#: pkgs.dbk:140 msgid "Testing the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:140 +#: pkgs.dbk:142 msgid "" "Before you upload your package, you should do basic testing on it. At a " "minimum, you should try the following activities (you'll need to have an " @@ -219,7 +214,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:147 +#: pkgs.dbk:149 msgid "" "Install the package and make sure the software works, or upgrade the package " "from an older version to your new version if a Debian package for it already " @@ -227,53 +222,52 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:154 +#: pkgs.dbk:156 msgid "" "Run <command>lintian</command> over the package. You can run " "<command>lintian</command> as follows: <literal>lintian -v " "<replaceable>package-version</replaceable>.changes</literal>. This will " "check the source package as well as the binary package. If you don't " "understand the output that <command>lintian</command> generates, try adding " -"the <literal>-i</literal> switch, which will cause " -"<command>lintian</command> to output a very verbose description of the " -"problem." +"the <literal>-i</literal> switch, which will cause <command>lintian</" +"command> to output a very verbose description of the problem." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:163 +#: pkgs.dbk:165 msgid "" "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes " "lintian to emit errors (they will start with <literal>E</literal>)." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:167 +#: pkgs.dbk:169 msgid "" -"For more information on <command>lintian</command>, see <xref " -"linkend=\"lintian\"/> ." +"For more information on <command>lintian</command>, see <xref linkend=" +"\"lintian\"/> ." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:173 +#: pkgs.dbk:175 msgid "" "Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older " "version, if one exists." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:179 +#: pkgs.dbk:181 msgid "" "Downgrade the package to the previous version (if one exists) — this tests " "the <filename>postrm</filename> and <filename>prerm</filename> scripts." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:185 +#: pkgs.dbk:187 msgid "Remove the package, then reinstall it." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:190 +#: pkgs.dbk:192 msgid "" "Copy the source package in a different directory and try unpacking it and " "rebuilding it. This tests if the package relies on existing files outside " @@ -282,42 +276,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:200 +#: pkgs.dbk:202 msgid "Layout of the source package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:202 +#: pkgs.dbk:204 msgid "There are two types of Debian source packages:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:207 +#: pkgs.dbk:209 msgid "" "the so-called <emphasis>native</emphasis> packages, where there is no " "distinction between the original sources and the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:213 +#: pkgs.dbk:215 msgid "" "the (more common) packages where there's an original source tarball file " "accompanied by another file that contains the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:219 +#: pkgs.dbk:221 msgid "" "For the native packages, the source package includes a Debian source control " -"file (<literal>.dsc</literal>) and the source tarball " -"(<literal>.tar.gz</literal>). A source package of a non-native package " -"includes a Debian source control file, the original source tarball " -"(<literal>.orig.tar.gz</literal>) and the Debian patches " -"(<literal>.diff.gz</literal>)." +"file (<literal>.dsc</literal>) and the source tarball (<literal>.tar.gz</" +"literal>). A source package of a non-native package includes a Debian " +"source control file, the original source tarball (<literal>.orig.tar.gz</" +"literal>) and the Debian patches (<literal>.diff.gz</literal>)." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:227 +#: pkgs.dbk:229 msgid "" "Whether a package is native or not is determined when it is built by " "<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle> " @@ -326,38 +319,37 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:233 +#: pkgs.dbk:235 msgid "" "The first time a version is uploaded which corresponds to a particular " "upstream version, the original source tar file should be uploaded and " "included in the <filename>.changes</filename> file. Subsequently, this very " -"same tar file should be used to build the new diffs and " -"<filename>.dsc</filename> files, and will not need to be re-uploaded." +"same tar file should be used to build the new diffs and <filename>.dsc</" +"filename> files, and will not need to be re-uploaded." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:240 +#: pkgs.dbk:242 msgid "" -"By default, <command>dpkg-genchanges</command> and " -"<command>dpkg-buildpackage</command> will include the original source tar " -"file if and only if the Debian revision part of the source version number is " -"0 or 1, indicating a new upstream version. This behavior may be modified by " -"using <literal>-sa</literal> to always include it or <literal>-sd</literal> " -"to always leave it out." +"By default, <command>dpkg-genchanges</command> and <command>dpkg-" +"buildpackage</command> will include the original source tar file if and only " +"if the Debian revision part of the source version number is 0 or 1, " +"indicating a new upstream version. This behavior may be modified by using " +"<literal>-sa</literal> to always include it or <literal>-sd</literal> to " +"always leave it out." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:248 +#: pkgs.dbk:250 msgid "" -"If no original source is included in the upload, the original source " -"tar-file used by <command>dpkg-source</command> when constructing the " -"<filename>.dsc</filename> file and diff to be uploaded " -"<emphasis>must</emphasis> be byte-for-byte identical with the one already in " -"the archive." +"If no original source is included in the upload, the original source tar-" +"file used by <command>dpkg-source</command> when constructing the <filename>." +"dsc</filename> file and diff to be uploaded <emphasis>must</emphasis> be " +"byte-for-byte identical with the one already in the archive." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:255 +#: pkgs.dbk:257 msgid "" "Please notice that, in non-native packages, permissions on files that are " "not present in the .orig.tar.gz will not be preserved, as diff does not " @@ -365,12 +357,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:262 +#: pkgs.dbk:264 msgid "Picking a distribution" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:264 +#: pkgs.dbk:266 msgid "" "Each upload needs to specify which distribution the package is intended " "for. The package build process extracts this information from the first " @@ -380,7 +372,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:270 +#: pkgs.dbk:272 msgid "" "There are several possible values for this field: `stable', `unstable', " "`testing-proposed-updates' and `experimental'. Normally, packages are " @@ -388,7 +380,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:275 +#: pkgs.dbk:277 msgid "" "Actually, there are two other possible distributions: `stable-security' and " "`testing-security', but read <xref linkend=\"bug-security\"/> for more " @@ -396,19 +388,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:280 +#: pkgs.dbk:282 msgid "" "It is not possible to upload a package into several distributions at the " "same time." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:284 +#: pkgs.dbk:286 msgid "Special case: uploads to the <emphasis>stable</emphasis> distribution" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:286 +#: pkgs.dbk:288 msgid "" "Uploading to <emphasis>stable</emphasis> means that the package will " "transfered to the <emphasis>p-u-new</emphasis>-queue for review by the " @@ -419,7 +411,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:294 +#: pkgs.dbk:296 msgid "" "Extra care should be taken when uploading to <emphasis>stable</emphasis>. " "Basically, a package should only be uploaded to stable if one of the " @@ -427,22 +419,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:301 +#: pkgs.dbk:303 msgid "a truly critical functionality problem" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:306 +#: pkgs.dbk:308 msgid "the package becomes uninstallable" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:311 +#: pkgs.dbk:313 msgid "a released architecture lacks the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:316 +#: pkgs.dbk:318 msgid "" "In the past, uploads to <emphasis>stable</emphasis> were used to address " "security problems as well. However, this practice is deprecated, as uploads " @@ -453,84 +445,81 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:324 +#: pkgs.dbk:326 msgid "" "Changing anything else in the package that isn't important is discouraged, " "because even trivial fixes can cause bugs later on." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:328 +#: pkgs.dbk:330 msgid "" "Packages uploaded to <emphasis>stable</emphasis> need to be compiled on " "systems running <emphasis>stable</emphasis>, so that their dependencies are " -"limited to the libraries (and other packages) available in " -"<emphasis>stable</emphasis>; for example, a package uploaded to " -"<emphasis>stable</emphasis> that depends on a library package that only " -"exists in unstable will be rejected. Making changes to dependencies of " -"other packages (by messing with <literal>Provides</literal> or shlibs " -"files), possibly making those other packages uninstallable, is strongly " -"discouraged." +"limited to the libraries (and other packages) available in <emphasis>stable</" +"emphasis>; for example, a package uploaded to <emphasis>stable</emphasis> " +"that depends on a library package that only exists in unstable will be " +"rejected. Making changes to dependencies of other packages (by messing with " +"<literal>Provides</literal> or shlibs files), possibly making those other " +"packages uninstallable, is strongly discouraged." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:338 +#: pkgs.dbk:340 msgid "" -"The Release Team (which can be reached at " -"<email>debian-release@lists.debian.org</email>) will regularly evaluate the " -"uploads To <emphasis>stable-proposed-updates</emphasis> and decide if your " -"package can be included in <emphasis>stable</emphasis>. Please be clear " -"(and verbose, if necessary) in your changelog entries for uploads to " -"<emphasis>stable</emphasis>, because otherwise the package won't be " -"considered for inclusion." +"The Release Team (which can be reached at &email-debian-release;) will " +"regularly evaluate the uploads To <emphasis>stable-proposed-updates</" +"emphasis> and decide if your package can be included in <emphasis>stable</" +"emphasis>. Please be clear (and verbose, if necessary) in your changelog " +"entries for uploads to <emphasis>stable</emphasis>, because otherwise the " +"package won't be considered for inclusion." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:347 +#: pkgs.dbk:349 msgid "" "It's best practice to speak with the stable release manager " -"<emphasis>before</emphasis> uploading to " -"<emphasis>stable</emphasis>/<emphasis>stable-proposed-updates</emphasis>, so " -"that the uploaded package fits the needs of the next point release." +"<emphasis>before</emphasis> uploading to <emphasis>stable</emphasis>/" +"<emphasis>stable-proposed-updates</emphasis>, so that the uploaded package " +"fits the needs of the next point release." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:355 +#: pkgs.dbk:357 msgid "" -"Special case: uploads to " -"<emphasis>testing/testing-proposed-updates</emphasis>" +"Special case: uploads to <emphasis>testing/testing-proposed-updates</" +"emphasis>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:357 +#: pkgs.dbk:359 msgid "" -"Please see the information in the <link linkend=\"t-p-u\">testing " -"section</link> for details." +"Please see the information in the <link linkend=\"t-p-u\">testing section</" +"link> for details." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:365 +#: pkgs.dbk:367 msgid "Uploading a package" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:367 +#: pkgs.dbk:369 msgid "Uploading to <literal>ftp-master</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:369 +#: pkgs.dbk:371 msgid "" "To upload a package, you should upload the files (including the signed " -"changes and dsc-file) with anonymous ftp to " -"<literal>ftp-master.debian.org</literal> in the directory <ulink " -"url=\"ftp://ftp-master.debian.org/pub/UploadQueue/\">/pub/UploadQueue/</ulink>. " -"To get the files processed there, they need to be signed with a key in the " -"debian keyring." +"changes and dsc-file) with anonymous ftp to <literal>&ftp-master-host;</" +"literal> in the directory <ulink url=\"ftp://&ftp-master-host;&upload-queue;" +"\">&upload-queue;</ulink>. To get the files processed there, they need to " +"be signed with a key in the debian keyring." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:377 +#: pkgs.dbk:379 msgid "" "Please note that you should transfer the changes file last. Otherwise, your " "upload may be rejected because the archive maintenance software will parse " @@ -538,7 +527,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:382 +#: pkgs.dbk:384 msgid "" "You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref " "linkend=\"dput\"/> useful when uploading packages. These handy programs " @@ -546,45 +535,43 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:387 +#: pkgs.dbk:389 msgid "" "For removing packages, please see the README file in that ftp directory, and " "the Debian package <xref linkend=\"dcut\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:393 +#: pkgs.dbk:395 msgid "Uploading to <literal>non-US</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:395 +#: pkgs.dbk:397 msgid "" -"<emphasis>Note:</emphasis> non-us was discontinued with the release of " -"sarge." +"<emphasis>Note:</emphasis> non-us was discontinued with the release of sarge." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:400 +#: pkgs.dbk:402 msgid "Delayed uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:402 +#: pkgs.dbk:404 msgid "" "Delayed uploads are done for the moment via the delayed queue at gluck. The " -"upload-directory is " -"<literal>gluck:~tfheen/DELAYED/[012345678]-day</literal>. 0-day is uploaded " -"multiple times per day to ftp-master." +"upload-directory is <literal>gluck:~tfheen/DELAYED/[012345678]-day</" +"literal>. 0-day is uploaded multiple times per day to ftp-master." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:407 +#: pkgs.dbk:409 msgid "With a fairly recent dput, this section" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:410 +#: pkgs.dbk:412 #, no-wrap msgid "" "[tfheen_delayed]\n" @@ -594,64 +581,64 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:416 +#: pkgs.dbk:418 msgid "in ~/.dput.cf should work fine for uploading to the DELAYED queue." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:419 +#: pkgs.dbk:421 msgid "" -"<emphasis>Note:</emphasis> Since this upload queue goes to " -"<literal>ftp-master</literal>, the prescription found in <xref " -"linkend=\"upload-ftp-master\"/> applies here as well." +"<emphasis>Note:</emphasis> Since this upload queue goes to <literal>ftp-" +"master</literal>, the prescription found in <xref linkend=\"upload-ftp-master" +"\"/> applies here as well." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:426 +#: pkgs.dbk:428 msgid "Security uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:428 +#: pkgs.dbk:430 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " "authorization from the security team. If the package does not exactly meet " "the team's requirements, it will cause many problems and delays in dealing " -"with the unwanted upload. For details, please see section <xref " -"linkend=\"bug-security\"/> ." +"with the unwanted upload. For details, please see section <xref linkend=" +"\"bug-security\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:438 +#: pkgs.dbk:440 msgid "Other upload queues" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:440 +#: pkgs.dbk:442 msgid "" "The scp queues on ftp-master, and security are mostly unusable due to the " "login restrictions on those hosts." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:444 +#: pkgs.dbk:446 msgid "" "The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are " "currently down. Work is underway to resurrect them." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:448 +#: pkgs.dbk:450 msgid "" "The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and " "ftp.chiark.greenend.org.uk are down permanently, and will not be " -"resurrected. The queue in Japan will be replaced with a new queue on " -"hp.debian.or.jp some day." +"resurrected. The queue in Japan will be replaced with a new queue on hp." +"debian.or.jp some day." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:454 +#: pkgs.dbk:456 msgid "" "For the time being, the anonymous ftp queue on auric.debian.org (the former " "ftp-master) works, but it is deprecated and will be removed at some point in " @@ -659,12 +646,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:461 +#: pkgs.dbk:463 msgid "Notification that a new package has been installed" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:463 +#: pkgs.dbk:465 msgid "" "The Debian archive maintainers are responsible for handling package " "uploads. For the most part, uploads are automatically handled on a daily " @@ -677,7 +664,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:472 +#: pkgs.dbk:474 msgid "" "In any case, you will receive an email notification indicating that the " "package has been added to the archive, which also indicates which bugs will " @@ -686,7 +673,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:478 +#: pkgs.dbk:480 msgid "" "The installation notification also includes information on what section the " "package was inserted into. If there is a disparity, you will receive a " @@ -694,135 +681,131 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:483 +#: pkgs.dbk:485 msgid "" "Note that if you upload via queues, the queue daemon software will also send " "you a notification by email." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:491 +#: pkgs.dbk:493 msgid "Specifying the package section, subsection and priority" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:493 +#: pkgs.dbk:495 msgid "" "The <filename>debian/control</filename> file's <literal>Section</literal> " "and <literal>Priority</literal> fields do not actually specify where the " "file will be placed in the archive, nor its priority. In order to retain " "the overall integrity of the archive, it is the archive maintainers who have " -"control over these fields. The values in the " -"<filename>debian/control</filename> file are actually just hints." +"control over these fields. The values in the <filename>debian/control</" +"filename> file are actually just hints." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:501 +#: pkgs.dbk:503 msgid "" "The archive maintainers keep track of the canonical sections and priorities " "for packages in the <emphasis>override file</emphasis>. If there is a " "disparity between the <emphasis>override file</emphasis> and the package's " "fields as indicated in <filename>debian/control</filename>, then you will " "receive an email noting the divergence when the package is installed into " -"the archive. You can either correct your " -"<filename>debian/control</filename> file for your next upload, or else you " -"may wish to make a change in the <emphasis>override file</emphasis>." +"the archive. You can either correct your <filename>debian/control</" +"filename> file for your next upload, or else you may wish to make a change " +"in the <emphasis>override file</emphasis>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:511 +#: pkgs.dbk:513 msgid "" "To alter the actual section that a package is put in, you need to first make " "sure that the <filename>debian/control</filename> file in your package is " -"accurate. Next, send an email <email>override-change@debian.org</email> or " -"submit a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem> requesting that the section or " -"priority for your package be changed from the old section or priority to the " -"new one. Be sure to explain your reasoning." +"accurate. Next, send an email &email-override; or submit a bug against " +"<systemitem role=\"package\">ftp.debian.org</systemitem> requesting that the " +"section or priority for your package be changed from the old section or " +"priority to the new one. Be sure to explain your reasoning." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:519 +#: pkgs.dbk:521 msgid "" "For more information about <emphasis>override files</emphasis>, see " "<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> " -"<manvolnum>1</manvolnum> </citerefentry> and <ulink " -"url=\"http://www.debian.org/Bugs/Developer#maintincorrect\"></ulink>." +"<manvolnum>1</manvolnum> </citerefentry> and <ulink url=\"&url-bts-devel;" +"#maintincorrect\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:525 +#: pkgs.dbk:527 msgid "" "Note that the <literal>Section</literal> field describes both the section as " -"well as the subsection, which are described in <xref " -"linkend=\"archive-sections\"/> . If the section is main, it should be " -"omitted. The list of allowable subsections can be found in <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections\"></ulink>." +"well as the subsection, which are described in <xref linkend=\"archive-" +"sections\"/> . If the section is main, it should be omitted. The list of " +"allowable subsections can be found in <ulink url=\"&url-debian-policy;ch-" +"archive.html#s-subsections\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:534 +#: pkgs.dbk:536 msgid "Handling bugs" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:536 +#: pkgs.dbk:538 msgid "" -"Every developer has to be able to work with the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>. This " -"includes knowing how to file bug reports properly (see <xref " -"linkend=\"submit-bug\"/> ), how to update them and reorder them, and how to " -"process and close them." +"Every developer has to be able to work with the Debian <ulink url=\"&url-bts;" +"\">bug tracking system</ulink>. This includes knowing how to file bug " +"reports properly (see <xref linkend=\"submit-bug\"/> ), how to update them " +"and reorder them, and how to process and close them." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:542 +#: pkgs.dbk:544 msgid "" -"The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for " -"developers</ulink>. This includes closing bugs, sending followup messages, " -"assigning severities and tags, marking bugs as forwarded, and other issues." +"The bug tracking system's features are described in the <ulink url=\"&url-" +"bts-devel;\">BTS documentation for developers</ulink>. This includes " +"closing bugs, sending followup messages, assigning severities and tags, " +"marking bugs as forwarded, and other issues." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:548 +#: pkgs.dbk:550 msgid "" "Operations such as reassigning bugs to other packages, merging separate bug " "reports about the same issue, or reopening bugs when they are prematurely " "closed, are handled using the so-called control mail server. All of the " -"commands available on this server are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " -"documentation</ulink>." +"commands available on this server are described in the <ulink url=\"&url-bts-" +"control;\">BTS control server documentation</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:556 +#: pkgs.dbk:558 msgid "Monitoring bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:558 +#: pkgs.dbk:560 msgid "" "If you want to be a good maintainer, you should periodically check the " -"<ulink url=\"http://www.debian.org/Bugs/\">Debian bug tracking system " -"(BTS)</ulink> for your packages. The BTS contains all the open bugs against " -"your packages. You can check them by browsing this page: " -"<literal>http://bugs.debian.org/<replaceable>yourlogin</replaceable>@debian.org</literal>." +"<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your " +"packages. The BTS contains all the open bugs against your packages. You " +"can check them by browsing this page: <literal>http://&bugs-host;/" +"<replaceable>yourlogin</replaceable>@debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:565 +#: pkgs.dbk:567 msgid "" -"Maintainers interact with the BTS via email addresses at " -"<literal>bugs.debian.org</literal>. Documentation on available commands can " -"be found at <ulink url=\"http://www.debian.org/Bugs/\"></ulink>, or, if you " -"have installed the <systemitem role=\"package\">doc-debian</systemitem> " -"package, you can look at the local files " -"<filename>/usr/share/doc/debian/bug-*</filename>." +"Maintainers interact with the BTS via email addresses at <literal>&bugs-host;" +"</literal>. Documentation on available commands can be found at <ulink url=" +"\"&url-bts;\"></ulink>, or, if you have installed the <systemitem role=" +"\"package\">doc-debian</systemitem> package, you can look at the local files " +"&file-bts-docs;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:572 +#: pkgs.dbk:574 msgid "" "Some find it useful to get periodic reports on open bugs. You can add a " "cron job such as the following if you want to get a weekly email outlining " @@ -830,86 +813,83 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:577 +#: pkgs.dbk:579 #, no-wrap msgid "" "# ask for weekly reports of bugs in my packages\n" -"0 17 * * fri echo index maint <replaceable>address</replaceable> | mail " -"request@bugs.debian.org" +"&cron-bug-report;" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:581 +#: pkgs.dbk:583 msgid "" "Replace <replaceable>address</replaceable> with your official Debian " "maintainer address." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:587 +#: pkgs.dbk:589 msgid "Responding to bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:589 +#: pkgs.dbk:591 msgid "" "When responding to bugs, make sure that any discussion you have about bugs " -"is sent both to the original submitter of the bug, and to the bug itself " -"(e.g., <email>123@bugs.debian.org</email>). If you're writing a new mail " -"and you don't remember the submitter email address, you can use the " -"<email>123-submitter@bugs.debian.org</email> email to contact the submitter " -"<emphasis>and</emphasis> to record your mail within the bug log (that means " -"you don't need to send a copy of the mail to " -"<email>123@bugs.debian.org</email>)." +"is sent both to the original submitter of the bug, and to the bug itself (e." +"g., <email>123@&bugs-host;</email>). If you're writing a new mail and you " +"don't remember the submitter email address, you can use the <email>123-" +"submitter@&bugs-host;</email> email to contact the submitter <emphasis>and</" +"emphasis> to record your mail within the bug log (that means you don't need " +"to send a copy of the mail to <email>123@&bugs-host;</email>)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:598 +#: pkgs.dbk:600 msgid "" "If you get a bug which mentions FTBFS, this means Fails to build from " "source. Porters frequently use this acronym." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:602 +#: pkgs.dbk:604 msgid "" "Once you've dealt with a bug report (e.g. fixed it), mark it as " "<emphasis>done</emphasis> (close it) by sending an explanation message to " -"<email>123-done@bugs.debian.org</email>. If you're fixing a bug by changing " -"and uploading the package, you can automate bug closing as described in " -"<xref linkend=\"upload-bugfix\"/> ." +"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and " +"uploading the package, you can automate bug closing as described in <xref " +"linkend=\"upload-bugfix\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:609 +#: pkgs.dbk:611 msgid "" "You should <emphasis>never</emphasis> close bugs via the bug server " -"<literal>close</literal> command sent to " -"<email>control@bugs.debian.org</email>. If you do so, the original " -"submitter will not receive any information about why the bug was closed." +"<literal>close</literal> command sent to &email-bts-control;. If you do so, " +"the original submitter will not receive any information about why the bug " +"was closed." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:617 +#: pkgs.dbk:619 msgid "Bug housekeeping" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:619 +#: pkgs.dbk:621 msgid "" "As a package maintainer, you will often find bugs in other packages or have " "bugs reported against your packages which are actually bugs in other " "packages. The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for Debian " -"developers</ulink>. Operations such as reassigning, merging, and tagging " -"bug reports are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " +"url=\"&url-bts-devel;\">BTS documentation for Debian developers</ulink>. " +"Operations such as reassigning, merging, and tagging bug reports are " +"described in the <ulink url=\"&url-bts-control;\">BTS control server " "documentation</ulink>. This section contains some guidelines for managing " "your own bugs, based on the collective Debian developer experience." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:630 +#: pkgs.dbk:632 msgid "" "Filing bugs for problems that you find in other packages is one of the civic " "obligations of maintainership, see <xref linkend=\"submit-bug\"/> for " @@ -918,12 +898,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:635 +#: pkgs.dbk:637 msgid "Here's a list of steps that you may follow to handle a bug report:" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:640 +#: pkgs.dbk:642 msgid "" "Decide whether the report corresponds to a real bug or not. Sometimes users " "are just calling a program in the wrong way because they haven't read the " @@ -936,7 +916,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:650 +#: pkgs.dbk:652 msgid "" "If the bug submitter disagrees with your decision to close the bug, they may " "reopen it until you find an agreement on how to handle it. If you don't " @@ -946,24 +926,23 @@ msgid "" "decision of the technical committee by reassigning the bug to <systemitem " "role=\"package\">tech-ctte</systemitem> (you may use the clone command of " "the BTS if you wish to keep it reported against your package). Before doing " -"so, please read the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">recommended procedure</ulink>." +"so, please read the <ulink url=\"&url-tech-ctte;\">recommended procedure</" +"ulink>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:664 +#: pkgs.dbk:666 msgid "" "If the bug is real but it's caused by another package, just reassign the bug " "to the right package. If you don't know which package it should be " -"reassigned to, you should ask for help on <link " -"linkend=\"irc-channels\">IRC</link> or on " -"<email>debian-devel@lists.debian.org</email>. Please make sure that the " +"reassigned to, you should ask for help on <link linkend=\"irc-channels" +"\">IRC</link> or on &email-debian-devel;. Please make sure that the " "maintainer(s) of the package the bug is reassigned to know why you " "reassigned it." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:672 +#: pkgs.dbk:674 msgid "" "Sometimes you also have to adjust the severity of the bug so that it matches " "our definition of the severity. That's because people tend to inflate the " @@ -973,7 +952,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:680 +#: pkgs.dbk:682 msgid "" "If the bug is real but the same problem has already been reported by someone " "else, then the two relevant bug reports should be merged into one using the " @@ -985,7 +964,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:691 +#: pkgs.dbk:693 msgid "" "The bug submitter may have forgotten to provide some information, in which " "case you have to ask them for the required information. You may use the " @@ -997,22 +976,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:702 +#: pkgs.dbk:704 msgid "" "If the bug is related to the packaging, you just fix it. If you are not " "able to fix it yourself, then tag the bug as <literal>help</literal>. You " -"can also ask for help on <email>debian-devel@lists.debian.org</email> or " -"<email>debian-qa@lists.debian.org</email>. If it's an upstream problem, you " -"have to forward it to the upstream author. Forwarding a bug is not enough, " -"you have to check at each release if the bug has been fixed or not. If it " -"has, you just close it, otherwise you have to remind the author about it. " -"If you have the required skills you can prepare a patch that fixes the bug " -"and send it to the author at the same time. Make sure to send the patch to " -"the BTS and to tag the bug as <literal>patch</literal>." +"can also ask for help on &email-debian-devel; or &email-debian-qa;. If it's " +"an upstream problem, you have to forward it to the upstream author. " +"Forwarding a bug is not enough, you have to check at each release if the bug " +"has been fixed or not. If it has, you just close it, otherwise you have to " +"remind the author about it. If you have the required skills you can prepare " +"a patch that fixes the bug and send it to the author at the same time. Make " +"sure to send the patch to the BTS and to tag the bug as <literal>patch</" +"literal>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:716 +#: pkgs.dbk:718 msgid "" "If you have fixed a bug in your local copy, or if a fix has been committed " "to the CVS repository, you may tag the bug as <literal>pending</literal> to " @@ -1023,7 +1002,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:726 +#: pkgs.dbk:728 msgid "" "Once a corrected package is available in the <emphasis>unstable</emphasis> " "distribution, you can close the bug. This can be done automatically, read " @@ -1031,12 +1010,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:735 +#: pkgs.dbk:737 msgid "When bugs are closed by new uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:737 +#: pkgs.dbk:739 msgid "" "As bugs and problems are fixed in your packages, it is your responsibility " "as the package maintainer to close these bugs. However, you should not " @@ -1047,19 +1026,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:745 +#: pkgs.dbk:747 msgid "" "However, it's possible to avoid having to manually close bugs after the " -"upload — just list the fixed bugs in your " -"<filename>debian/changelog</filename> file, following a certain syntax, and " -"the archive maintenance software will close the bugs for you. For example:" +"upload — just list the fixed bugs in your <filename>debian/changelog</" +"filename> file, following a certain syntax, and the archive maintenance " +"software will close the bugs for you. For example:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:751 +#: pkgs.dbk:753 #, no-wrap msgid "" -"-cannon (3.1415) unstable; urgency=low\n" +"acme-cannon (3.1415) unstable; urgency=low\n" "\n" " * Frobbed with options (closes: Bug#98339)\n" " * Added safety to prevent operator dismemberment, closes: bug#98765,\n" @@ -1068,32 +1047,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:759 +#: pkgs.dbk:761 msgid "" "Technically speaking, the following Perl regular expression describes how " "bug closing changelogs are identified:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:763 +#: pkgs.dbk:765 #, no-wrap msgid "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:766 +#: pkgs.dbk:768 msgid "" "We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> " "syntax, as it is the most concise entry and the easiest to integrate with " "the text of the <filename>changelog</filename>. Unless specified different " -"by the <replaceable>-v</replaceable>-switch to " -"<command>dpkg-buildpackage</command>, only the bugs closed in the most " -"recent changelog entry are closed (basically, exactly the bugs mentioned in " -"the changelog-part in the <filename>.changes</filename> file are closed)." +"by the <replaceable>-v</replaceable>-switch to <command>dpkg-buildpackage</" +"command>, only the bugs closed in the most recent changelog entry are closed " +"(basically, exactly the bugs mentioned in the changelog-part in the " +"<filename>.changes</filename> file are closed)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:775 +#: pkgs.dbk:777 msgid "" "Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer " "upload (NMU)</link> were tagged <literal>fixed</literal> instead of being " @@ -1102,48 +1081,45 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:781 +#: pkgs.dbk:783 msgid "" "If you happen to mistype a bug number or forget a bug in the changelog " "entries, don't hesitate to undo any damage the error caused. To reopen " -"wrongly closed bugs, send a <literal>reopen " -"<replaceable>XXX</replaceable></literal> command to the bug tracking " -"system's control address, <email>control@bugs.debian.org</email>. To close " -"any remaining bugs that were fixed by your upload, email the " -"<filename>.changes</filename> file to " -"<email>XXX-done@bugs.debian.org</email>, where " -"<replaceable>XXX</replaceable> is the bug number, and put Version: YYY and " -"an empty line as the first two lines of the body of the email, where " -"<replaceable>YYY</replaceable> is the first version where the bug has been " -"fixed." +"wrongly closed bugs, send a <literal>reopen <replaceable>XXX</replaceable></" +"literal> command to the bug tracking system's control address, &email-bts-" +"control;. To close any remaining bugs that were fixed by your upload, email " +"the <filename>.changes</filename> file to <email>XXX-done@&bugs-host;</" +"email>, where <replaceable>XXX</replaceable> is the bug number, and put " +"Version: YYY and an empty line as the first two lines of the body of the " +"email, where <replaceable>YYY</replaceable> is the first version where the " +"bug has been fixed." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:793 +#: pkgs.dbk:795 msgid "" "Bear in mind that it is not obligatory to close bugs using the changelog as " "described above. If you simply want to close bugs that don't have anything " "to do with an upload you made, do it by emailing an explanation to " -"<email>XXX-done@bugs.debian.org</email>. Do <emphasis " -"role=\"strong\">not</emphasis> close bugs in the changelog entry of a " -"version if the changes in that version of the package don't have any bearing " -"on the bug." +"<email>XXX-done@&bugs-host;</email>. Do <emphasis role=\"strong\">not</" +"emphasis> close bugs in the changelog entry of a version if the changes in " +"that version of the package don't have any bearing on the bug." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:801 +#: pkgs.dbk:803 msgid "" "For general information on how to write your changelog entries, see <xref " "linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:807 +#: pkgs.dbk:809 msgid "Handling security-related bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:809 +#: pkgs.dbk:811 msgid "" "Due to their sensitive nature, security-related bugs must be handled " "carefully. The Debian Security Team exists to coordinate this activity, " @@ -1153,18 +1129,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:816 +#: pkgs.dbk:820 msgid "" "When you become aware of a security-related bug in a Debian package, whether " "or not you are the maintainer, collect pertinent information about the " -"problem, and promptly contact the security team at " -"<email>team@security.debian.org</email> as soon as possible. <emphasis " -"role=\"strong\">DO NOT UPLOAD</emphasis> any packages for stable; the " -"security team will do that. Useful information includes, for example:" +"problem, and promptly contact the security team at &email-security-team; as " +"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any " +"packages for stable; the security team will do that. Useful information " +"includes, for example:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:826 +#: pkgs.dbk:830 msgid "" "Which versions of the package are known to be affected by the bug. Check " "each version that is present in a supported Debian release, as well as " @@ -1172,39 +1148,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:833 -msgid "The nature of the fix, if any is available (patches are especially helpful)" +#: pkgs.dbk:837 +msgid "" +"The nature of the fix, if any is available (patches are especially helpful)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:838 +#: pkgs.dbk:842 msgid "" -"Any fixed packages that you have prepared yourself (send only the " -"<literal>.diff.gz</literal> and <literal>.dsc</literal> files and read <xref " -"linkend=\"bug-security-building\"/> first)" +"Any fixed packages that you have prepared yourself (send only the <literal>." +"diff.gz</literal> and <literal>.dsc</literal> files and read <xref linkend=" +"\"bug-security-building\"/> first)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:845 +#: pkgs.dbk:849 msgid "" "Any assistance you can provide to help with testing (exploits, regression " "testing, etc.)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:851 +#: pkgs.dbk:855 msgid "" -"Any information needed for the advisory (see <xref " -"linkend=\"bug-security-advisories\"/> )" +"Any information needed for the advisory (see <xref linkend=\"bug-security-" +"advisories\"/> )" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:857 +#: pkgs.dbk:861 msgid "Confidentiality" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:859 +#: pkgs.dbk:863 msgid "" "Unlike most other activities within Debian, information about security " "issues must sometimes be kept private for a time. This allows software " @@ -1215,27 +1192,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:866 +#: pkgs.dbk:870 msgid "There are several ways developers can learn of a security problem:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:871 +#: pkgs.dbk:875 msgid "they notice it on a public forum (mailing list, web site, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:876 +#: pkgs.dbk:880 msgid "someone files a bug report" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:881 +#: pkgs.dbk:885 msgid "someone informs them via private email" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:886 +#: pkgs.dbk:890 msgid "" "In the first two cases, the information is public and it is important to " "have a fix as soon as possible. In the last case, however, it might not be " @@ -1244,14 +1221,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:894 +#: pkgs.dbk:898 msgid "" "If the security exposure is minor, there is sometimes no need to keep the " "problem a secret and a fix should be made and released." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:900 +#: pkgs.dbk:904 msgid "" "If the problem is severe, it is preferable to share the information with " "other vendors and coordinate a release. The security team keeps in contact " @@ -1259,7 +1236,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:907 +#: pkgs.dbk:911 msgid "" "In all cases if the person who reports the problem asks that it not be " "disclosed, such requests should be honored, with the obvious exception of " @@ -1269,7 +1246,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:914 +#: pkgs.dbk:918 msgid "" "Please note that if secrecy is needed you may not upload a fix to unstable " "(or anywhere else, such as a public CVS repository). It is not sufficient " @@ -1278,7 +1255,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:920 +#: pkgs.dbk:924 msgid "" "There are two reasons for releasing information even though secrecy is " "requested: the problem has been known for a while, or the problem or exploit " @@ -1286,91 +1263,90 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:927 +#: pkgs.dbk:931 msgid "Security Advisories" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:929 +#: pkgs.dbk:933 msgid "" "Security advisories are only issued for the current, released stable " "distribution, and <emphasis>not</emphasis> for testing or unstable. When " -"released, advisories are sent to the " -"<email>debian-security-announce@lists.debian.org</email> mailing list and " -"posted on <ulink url=\"http://www.debian.org/security/\">the security web " -"page</ulink>. Security advisories are written and posted by the security " -"team. However they certainly do not mind if a maintainer can supply some of " -"the information for them, or write part of the text. Information that " -"should be in an advisory includes:" +"released, advisories are sent to the &email-debian-security-announce; " +"mailing list and posted on <ulink url=\"&url-debian-security-advisories;" +"\">the security web page</ulink>. Security advisories are written and " +"posted by the security team. However they certainly do not mind if a " +"maintainer can supply some of the information for them, or write part of the " +"text. Information that should be in an advisory includes:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:942 +#: pkgs.dbk:946 msgid "A description of the problem and its scope, including:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:947 +#: pkgs.dbk:951 msgid "The type of problem (privilege escalation, denial of service, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:952 +#: pkgs.dbk:956 msgid "What privileges may be gained, and by whom (if any)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:957 +#: pkgs.dbk:961 msgid "How it can be exploited" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:962 +#: pkgs.dbk:966 msgid "Whether it is remotely or locally exploitable" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:967 +#: pkgs.dbk:971 msgid "How the problem was fixed" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:972 +#: pkgs.dbk:976 msgid "This information allows users to assess the threat to their systems." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:977 +#: pkgs.dbk:981 msgid "Version numbers of affected packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:982 +#: pkgs.dbk:986 msgid "Version numbers of fixed packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:987 +#: pkgs.dbk:991 msgid "" "Information on where to obtain the updated packages (usually from the Debian " "security archive)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:993 +#: pkgs.dbk:997 msgid "" -"References to upstream advisories, <ulink " -"url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other " -"information useful in cross-referencing the vulnerability" +"References to upstream advisories, <ulink url=\"http://cve.mitre.org\">CVE</" +"ulink> identifiers, and any other information useful in cross-referencing " +"the vulnerability" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1002 +#: pkgs.dbk:1006 msgid "Preparing packages to address security issues" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1004 +#: pkgs.dbk:1008 msgid "" "One way that you can assist the security team in their duties is to provide " "them with fixed packages suitable for a security advisory for the stable " @@ -1378,7 +1354,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1009 +#: pkgs.dbk:1013 msgid "" "When an update is made to the stable release, care must be taken to avoid " "changing system behavior or introducing new bugs. In order to do this, make " @@ -1389,7 +1365,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1017 +#: pkgs.dbk:1021 msgid "" "This means that moving to a new upstream version is not a good solution. " "Instead, the relevant changes should be back-ported to the version present " @@ -1399,7 +1375,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1023 +#: pkgs.dbk:1027 msgid "" "In some cases, it is not possible to back-port a security fix, for example " "when large amounts of source code need to be modified or rewritten. If this " @@ -1409,7 +1385,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1030 +#: pkgs.dbk:1034 msgid "" "Related to this is another important guideline: always test your changes. " "If you have an exploit available, try it and see if it indeed succeeds on " @@ -1419,53 +1395,51 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1037 +#: pkgs.dbk:1041 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your " "package which are not directly related to fixing the vulnerability. These " "will only need to be reverted, and this wastes time. If there are other " -"bugs in your package that you would like to fix, make an upload to " -"proposed-updates in the usual way, after the security advisory is issued. " -"The security update mechanism is not a means for introducing changes to your " +"bugs in your package that you would like to fix, make an upload to proposed-" +"updates in the usual way, after the security advisory is issued. The " +"security update mechanism is not a means for introducing changes to your " "package which would otherwise be rejected from the stable release, so please " "do not attempt to do this." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1047 +#: pkgs.dbk:1051 msgid "" "Review and test your changes as much as possible. Check the differences " "from the previous version repeatedly (<command>interdiff</command> from the " "<systemitem role=\"package\">patchutils</systemitem> package and " -"<command>debdiff</command> from <systemitem " -"role=\"package\">devscripts</systemitem> are useful tools for this, see " -"<xref linkend=\"debdiff\"/> )." +"<command>debdiff</command> from <systemitem role=\"package\">devscripts</" +"systemitem> are useful tools for this, see <xref linkend=\"debdiff\"/> )." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1055 +#: pkgs.dbk:1059 msgid "Be sure to verify the following items:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1060 -msgid "" -"Target the right distribution in your " -"<filename>debian/changelog</filename>. For stable this is " -"<literal>stable-security</literal> and for testing this is " -"<literal>testing-security</literal>, and for the previous stable release, " -"this is <literal>oldstable-security</literal>. Do not target " -"<replaceable>distribution</replaceable>-proposed-updates or " +#: pkgs.dbk:1064 +msgid "" +"Target the right distribution in your <filename>debian/changelog</" +"filename>. For stable this is <literal>stable-security</literal> and for " +"testing this is <literal>testing-security</literal>, and for the previous " +"stable release, this is <literal>oldstable-security</literal>. Do not " +"target <replaceable>distribution</replaceable>-proposed-updates or " "<literal>stable</literal>!" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1070 +#: pkgs.dbk:1074 msgid "The upload should have urgency=high." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1075 +#: pkgs.dbk:1079 msgid "" "Make descriptive, meaningful changelog entries. Others will rely on them to " "determine whether a particular bug was fixed. Always include an external " @@ -1478,7 +1452,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1087 +#: pkgs.dbk:1091 msgid "" "Make sure the version number is proper. It must be greater than the current " "package, but less than package versions in later distributions. If in " @@ -1491,17 +1465,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1099 +#: pkgs.dbk:1103 msgid "" "Do not make source-only uploads if your package has any binary-all packages " -"(do not use the <literal>-S</literal> option to " -"<command>dpkg-buildpackage</command>). The <command>buildd</command> " -"infrastructure will not build those. This point applies to normal package " -"uploads as well." +"(do not use the <literal>-S</literal> option to <command>dpkg-buildpackage</" +"command>). The <command>buildd</command> infrastructure will not build " +"those. This point applies to normal package uploads as well." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1108 +#: pkgs.dbk:1112 msgid "" "Unless the upstream source has been uploaded to security.debian.org before " "(by a previous security update), build the upload with full upstream source " @@ -1511,7 +1484,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1117 +#: pkgs.dbk:1121 msgid "" "Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in " "the normal archive, otherwise it is not possible to move the security fix " @@ -1519,22 +1492,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1124 +#: pkgs.dbk:1128 msgid "" "Build the package on a clean system which only has packages installed from " "the distribution you are building for. If you do not have such a system " -"yourself, you can use a debian.org machine (see <xref " -"linkend=\"server-machines\"/> ) or setup a chroot (see <xref " -"linkend=\"pbuilder\"/> and <xref linkend=\"debootstrap\"/> )." +"yourself, you can use a debian.org machine (see <xref linkend=\"server-" +"machines\"/> ) or setup a chroot (see <xref linkend=\"pbuilder\"/> and <xref " +"linkend=\"debootstrap\"/> )." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1135 +#: pkgs.dbk:1139 msgid "Uploading the fixed package" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1137 +#: pkgs.dbk:1141 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " @@ -1544,11 +1517,11 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1144 +#: pkgs.dbk:1148 msgid "" -"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to " -"proposed-updates without coordinating with the security team. Packages from " -"security.debian.org will be copied into the proposed-updates directory " +"Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to proposed-" +"updates without coordinating with the security team. Packages from security." +"debian.org will be copied into the proposed-updates directory " "automatically. If a package with the same or a higher version number is " "already installed into the archive, the security update will be rejected by " "the archive system. That way, the stable distribution will end up without a " @@ -1556,17 +1529,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1153 +#: pkgs.dbk:1157 msgid "" "Once you have created and tested the new package and it has been approved by " "the security team, it needs to be uploaded so that it can be installed in " "the archives. For security uploads, the place to upload to is " -"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal> " -"." +"<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</" +"literal> ." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1159 +#: pkgs.dbk:1163 msgid "" "Once an upload to the security queue has been accepted, the package will " "automatically be rebuilt for all architectures and stored for verification " @@ -1574,7 +1547,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1164 +#: pkgs.dbk:1168 msgid "" "Uploads which are waiting for acceptance or verification are only accessible " "by the security team. This is necessary since there might be fixes for " @@ -1582,7 +1555,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1169 +#: pkgs.dbk:1173 msgid "" "If a member of the security team accepts a package, it will be installed on " "security.debian.org as well as proposed for the proper " @@ -1590,12 +1563,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1180 +#: pkgs.dbk:1184 msgid "Moving, removing, renaming, adopting, and orphaning packages" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1182 +#: pkgs.dbk:1186 msgid "" "Some archive manipulation operations are not automated in the Debian upload " "process. These procedures should be manually followed by maintainers. This " @@ -1603,12 +1576,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1187 +#: pkgs.dbk:1191 msgid "Moving packages" msgstr "" # type: Content of: <chapter><section><section><para><footnote> -#: pkgs.dbk:1189 +#: pkgs.dbk:1193 msgid "" "Sometimes a package will change its section. For instance, a package from " "the `non-free' section might be GPL'd in a later version, in which case the " @@ -1616,20 +1589,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para><footnote><para> -#: pkgs.dbk:1191 +#: pkgs.dbk:1195 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for guidelines on what section a package belongs in." +"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"guidelines on what section a package belongs in." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1196 +#: pkgs.dbk:1200 msgid "" "If you need to change the section for one of your packages, change the " "package control information to place the package in the desired section, and " -"re-upload the package (see the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). You must ensure that you include the " +"re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian " +"Policy Manual</ulink> for details). You must ensure that you include the " "<filename>.orig.tar.gz</filename> in your upload (even if you are not " "uploading a new upstream version), or it will not appear in the new section " "together with the rest of the package. If your new section is valid, it " @@ -1638,51 +1610,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1208 +#: pkgs.dbk:1212 msgid "" -"If, on the other hand, you need to change the " -"<emphasis>subsection</emphasis> of one of your packages (e.g., ``devel'', " -"``admin''), the procedure is slightly different. Correct the subsection as " -"found in the control file of the package, and re-upload that. Also, you'll " -"need to get the override file updated, as described in <xref " -"linkend=\"override-file\"/> ." +"If, on the other hand, you need to change the <emphasis>subsection</" +"emphasis> of one of your packages (e.g., ``devel'', ``admin''), the " +"procedure is slightly different. Correct the subsection as found in the " +"control file of the package, and re-upload that. Also, you'll need to get " +"the override file updated, as described in <xref linkend=\"override-file\"/" +"> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1217 +#: pkgs.dbk:1221 msgid "Removing packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1219 +#: pkgs.dbk:1223 msgid "" "If for some reason you want to completely remove a package (say, if it is an " "old compatibility library which is no longer required), you need to file a " "bug against <literal>ftp.debian.org</literal> asking that the package be " "removed; as all bugs, this bug should normally have normal severity. Make " "sure you indicate which distribution the package should be removed from. " -"Normally, you can only have packages removed from " -"<emphasis>unstable</emphasis> and <emphasis>experimental</emphasis>. " -"Packages are not removed from <emphasis>testing</emphasis> directly. " -"Rather, they will be removed automatically after the package has been " -"removed from <emphasis>unstable</emphasis> and no package in " -"<emphasis>testing</emphasis> depends on it." +"Normally, you can only have packages removed from <emphasis>unstable</" +"emphasis> and <emphasis>experimental</emphasis>. Packages are not removed " +"from <emphasis>testing</emphasis> directly. Rather, they will be removed " +"automatically after the package has been removed from <emphasis>unstable</" +"emphasis> and no package in <emphasis>testing</emphasis> depends on it." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1232 +#: pkgs.dbk:1236 msgid "" "There is one exception when an explicit removal request is not necessary: If " -"a (source or binary) package is an orphan, it will be removed " -"semi-automatically. For a binary-package, this means if there is no longer " -"any source package producing this binary package; if the binary package is " -"just no longer produced on some architectures, a removal request is still " +"a (source or binary) package is an orphan, it will be removed semi-" +"automatically. For a binary-package, this means if there is no longer any " +"source package producing this binary package; if the binary package is just " +"no longer produced on some architectures, a removal request is still " "necessary. For a source-package, this means that all binary packages it " "refers to have been taken over by another source package." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1241 +#: pkgs.dbk:1245 msgid "" "In your removal request, you have to detail the reasons justifying the " "request. This is to avoid unwanted removals and to keep a trace of why a " @@ -1691,7 +1662,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1247 +#: pkgs.dbk:1251 msgid "" "Usually you only ask for the removal of a package maintained by yourself. " "If you want to remove another package, you have to get the approval of its " @@ -1699,79 +1670,76 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1252 +#: pkgs.dbk:1256 msgid "" "Further information relating to these and other package removal related " -"topics may be found at <ulink " -"url=\"http://wiki.debian.org/ftpmaster_Removals\"></ulink> and <ulink " -"url=\"http://qa.debian.org/howto-remove.html\"></ulink>." +"topics may be found at <ulink url=\"http://wiki.debian.org/ftpmaster_Removals" +"\"></ulink> and <ulink url=\"&url-debian-qa;howto-remove.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1257 +#: pkgs.dbk:1261 msgid "" -"If in doubt concerning whether a package is disposable, email " -"<email>debian-devel@lists.debian.org</email> asking for opinions. Also of " -"interest is the <command>apt-cache</command> program from the <systemitem " -"role=\"package\">apt</systemitem> package. When invoked as " -"<literal>apt-cache showpkg <replaceable>package</replaceable></literal>, the " -"program will show details for <replaceable>package</replaceable>, including " -"reverse depends. Other useful programs include <literal>apt-cache " -"rdepends</literal>, <command>apt-rdepends</command> and " -"<command>grep-dctrl</command>. Removal of orphaned packages is discussed on " -"<email>debian-qa@lists.debian.org</email>." +"If in doubt concerning whether a package is disposable, email &email-debian-" +"devel; asking for opinions. Also of interest is the <command>apt-cache</" +"command> program from the <systemitem role=\"package\">apt</systemitem> " +"package. When invoked as <literal>apt-cache showpkg <replaceable>package</" +"replaceable></literal>, the program will show details for " +"<replaceable>package</replaceable>, including reverse depends. Other useful " +"programs include <literal>apt-cache rdepends</literal>, <command>apt-" +"rdepends</command> and <command>grep-dctrl</command>. Removal of orphaned " +"packages is discussed on &email-debian-qa;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1268 +#: pkgs.dbk:1272 msgid "" "Once the package has been removed, the package's bugs should be handled. " "They should either be reassigned to another package in the case where the " -"actual code has evolved into another package (e.g. " -"<literal>libfoo12</literal> was removed because <literal>libfoo13</literal> " -"supersedes it) or closed if the software is simply no longer part of Debian." +"actual code has evolved into another package (e.g. <literal>libfoo12</" +"literal> was removed because <literal>libfoo13</literal> supersedes it) or " +"closed if the software is simply no longer part of Debian." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1275 +#: pkgs.dbk:1279 msgid "Removing packages from <filename>Incoming</filename>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1277 +#: pkgs.dbk:1281 msgid "" -"In the past, it was possible to remove packages from " -"<filename>incoming</filename>. However, with the introduction of the new " -"incoming system, this is no longer possible. Instead, you have to upload a " -"new revision of your package with a higher version than the package you want " -"to replace. Both versions will be installed in the archive but only the " -"higher version will actually be available in <emphasis>unstable</emphasis> " -"since the previous version will immediately be replaced by the higher. " -"However, if you do proper testing of your packages, the need to replace a " -"package should not occur too often anyway." +"In the past, it was possible to remove packages from <filename>incoming</" +"filename>. However, with the introduction of the new incoming system, this " +"is no longer possible. Instead, you have to upload a new revision of your " +"package with a higher version than the package you want to replace. Both " +"versions will be installed in the archive but only the higher version will " +"actually be available in <emphasis>unstable</emphasis> since the previous " +"version will immediately be replaced by the higher. However, if you do " +"proper testing of your packages, the need to replace a package should not " +"occur too often anyway." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1292 +#: pkgs.dbk:1296 msgid "Replacing or renaming packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1294 +#: pkgs.dbk:1298 msgid "" "When you make a mistake naming your package, you should follow a two-step " "process to rename it. First, set your <filename>debian/control</filename> " "file to replace and conflict with the obsolete name of the package (see the " -"<ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). Once you've uploaded the package and the " -"package has moved into the archive, file a bug against " -"<literal>ftp.debian.org</literal> asking to remove the package with the " -"obsolete name. Do not forget to properly reassign the package's bugs at the " -"same time." +"<ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"details). Once you've uploaded the package and the package has moved into " +"the archive, file a bug against <literal>ftp.debian.org</literal> asking to " +"remove the package with the obsolete name. Do not forget to properly " +"reassign the package's bugs at the same time." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1304 +#: pkgs.dbk:1308 msgid "" "At other times, you may make a mistake in constructing your package and wish " "to replace it. The only way to do this is to increase the version number " @@ -1779,70 +1747,68 @@ msgid "" "manner. Note that this applies to each part of your package, including the " "sources: if you wish to replace the upstream source tarball of your package, " "you will need to upload it with a different version. An easy possibility is " -"to replace <filename>foo_1.00.orig.tar.gz</filename> with " -"<filename>foo_1.00+0.orig.tar.gz</filename>. This restriction gives each " -"file on the ftp site a unique name, which helps to ensure consistency across " -"the mirror network." +"to replace <filename>foo_1.00.orig.tar.gz</filename> with <filename>foo_1.00" +"+0.orig.tar.gz</filename>. This restriction gives each file on the ftp site " +"a unique name, which helps to ensure consistency across the mirror network." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1318 +#: pkgs.dbk:1322 msgid "Orphaning a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1320 +#: pkgs.dbk:1324 msgid "" "If you can no longer maintain a package, you need to inform others, and see " "that the package is marked as orphaned. You should set the package " -"maintainer to <literal>Debian QA Group " -"<packages@qa.debian.org></literal> and submit a bug report against the " -"pseudo package <systemitem role=\"package\">wnpp</systemitem>. The bug " -"report should be titled <literal>O: <replaceable>package</replaceable> -- " -"<replaceable>short description</replaceable></literal> indicating that the " -"package is now orphaned. The severity of the bug should be set to " -"<emphasis>normal</emphasis>; if the package has a priority of standard or " -"higher, it should be set to important. If you feel it's necessary, send a " -"copy to <email>debian-devel@lists.debian.org</email> by putting the address " -"in the X-Debbugs-CC: header of the message (no, don't use CC:, because that " -"way the message's subject won't indicate the bug number)." +"maintainer to <literal>Debian QA Group &orphan-address;</literal> and submit " +"a bug report against the pseudo package <systemitem role=\"package\">wnpp</" +"systemitem>. The bug report should be titled <literal>O: " +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal> indicating that the package is now orphaned. The " +"severity of the bug should be set to <emphasis>normal</emphasis>; if the " +"package has a priority of standard or higher, it should be set to " +"important. If you feel it's necessary, send a copy to &email-debian-devel; " +"by putting the address in the X-Debbugs-CC: header of the message (no, don't " +"use CC:, because that way the message's subject won't indicate the bug " +"number)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1335 +#: pkgs.dbk:1339 msgid "" "If you just intend to give the package away, but you can keep maintainership " "for the moment, then you should instead submit a bug against <systemitem " "role=\"package\">wnpp</systemitem> and title it <literal>RFA: " -"<replaceable>package</replaceable> -- <replaceable>short " -"description</replaceable></literal>. <literal>RFA</literal> stands for " -"<emphasis>Request For Adoption</emphasis>." +"<replaceable>package</replaceable> -- <replaceable>short description</" +"replaceable></literal>. <literal>RFA</literal> stands for <emphasis>Request " +"For Adoption</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1343 +#: pkgs.dbk:1347 msgid "" -"More information is on the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">WNPP web pages</ulink>." +"More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1349 +#: pkgs.dbk:1353 msgid "Adopting a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1351 +#: pkgs.dbk:1355 msgid "" "A list of packages in need of a new maintainer is available in the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " -"Packages list (WNPP)</ulink>. If you wish to take over maintenance of any " -"of the packages listed in the WNPP, please take a look at the aforementioned " -"page for information and procedures." +"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list (WNPP)</" +"ulink>. If you wish to take over maintenance of any of the packages listed " +"in the WNPP, please take a look at the aforementioned page for information " +"and procedures." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1358 +#: pkgs.dbk:1362 msgid "" "It is not OK to simply take over a package that you feel is neglected — that " "would be package hijacking. You can, of course, contact the current " @@ -1852,20 +1818,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1364 +#: pkgs.dbk:1368 msgid "" "Generally, you may not take over the package without the assent of the " "current maintainer. Even if they ignore you, that is still not grounds to " "take over a package. Complaints about maintainers should be brought up on " "the developers' mailing list. If the discussion doesn't end with a positive " "conclusion, and the issue is of a technical nature, consider bringing it to " -"the attention of the technical committee (see the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">technical committee web " -"page</ulink> for more information)." +"the attention of the technical committee (see the <ulink url=\"&url-tech-" +"ctte;\">technical committee web page</ulink> for more information)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1374 +#: pkgs.dbk:1378 msgid "" "If you take over an old package, you probably want to be listed as the " "package's official maintainer in the bug system. This will happen " @@ -1878,12 +1843,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1388 +#: pkgs.dbk:1392 msgid "Porting and being ported" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1390 +#: pkgs.dbk:1394 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 " @@ -1892,23 +1857,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1396 +#: pkgs.dbk:1400 msgid "" "Porting is the act of building Debian packages for architectures that are " "different from the original architecture of the package maintainer's binary " "package. It is a unique and essential activity. In fact, porters do most " "of the actual compiling of Debian packages. For instance, for a single " "<emphasis>i386</emphasis> binary package, there must be a recompile for each " -"architecture, which amounts to 12 more builds." +"architecture, which amounts to &number-of-arches; more builds." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1404 +#: pkgs.dbk:1408 msgid "Being kind to porters" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1406 +#: pkgs.dbk:1410 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 " @@ -1919,7 +1884,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1414 +#: pkgs.dbk:1418 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 " @@ -1929,7 +1894,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1421 +#: pkgs.dbk:1425 msgid "" "By far, most of the problems encountered by porters are caused by " "<emphasis>packaging bugs</emphasis> in the source packages. Here is a " @@ -1937,49 +1902,46 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1428 -msgid "" -"Make sure that your <literal>Build-Depends</literal> and " -"<literal>Build-Depends-Indep</literal> settings in " -"<filename>debian/control</filename> are set properly. The best way to " -"validate this is to use the <systemitem " -"role=\"package\">debootstrap</systemitem> package to create an unstable " -"chroot environment (see <xref linkend=\"debootstrap\"/> ). Within that " -"chrooted environment, install the <systemitem " -"role=\"package\">build-essential</systemitem> package and any package " -"dependencies mentioned in <literal>Build-Depends</literal> and/or " -"<literal>Build-Depends-Indep</literal>. Finally, try building your package " -"within that chrooted environment. These steps can be automated by the use " -"of the <command>pbuilder</command> program which is provided by the package " -"of the same name (see <xref linkend=\"pbuilder\"/> )." +#: pkgs.dbk:1432 +msgid "" +"Make sure that your <literal>Build-Depends</literal> and <literal>Build-" +"Depends-Indep</literal> settings in <filename>debian/control</filename> are " +"set properly. The best way to validate this is to use the <systemitem role=" +"\"package\">debootstrap</systemitem> package to create an unstable chroot " +"environment (see <xref linkend=\"debootstrap\"/> ). Within that chrooted " +"environment, install the <systemitem role=\"package\">build-essential</" +"systemitem> package and any package dependencies mentioned in <literal>Build-" +"Depends</literal> and/or <literal>Build-Depends-Indep</literal>. Finally, " +"try building your package within that chrooted environment. These steps can " +"be automated by the use of the <command>pbuilder</command> program which is " +"provided by the package of the same name (see <xref linkend=\"pbuilder\"/> )." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1442 +#: pkgs.dbk:1446 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:1446 +#: pkgs.dbk:1450 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for instructions on setting build dependencies." +"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:1452 +#: pkgs.dbk:1456 msgid "" "Don't set architecture to a value other than ``all'' or ``any'' unless you " "really mean it. In too many cases, maintainers don't follow the " -"instructions in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>. Setting your architecture to ``i386'' is usually incorrect." +"instructions in the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</" +"ulink>. Setting your architecture to ``i386'' is usually incorrect." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1460 +#: pkgs.dbk:1464 msgid "" "Make sure your source package is correct. Do <literal>dpkg-source -x " "<replaceable>package</replaceable>.dsc</literal> to make sure your source " @@ -1988,33 +1950,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1468 +#: pkgs.dbk:1472 msgid "" -"Make sure you don't ship your source package with the " -"<filename>debian/files</filename> or <filename>debian/substvars</filename> " -"files. They should be removed by the `clean' target of " -"<filename>debian/rules</filename>." +"Make sure you don't ship your source package with the <filename>debian/" +"files</filename> or <filename>debian/substvars</filename> files. They " +"should be removed by the `clean' target of <filename>debian/rules</filename>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1476 +#: pkgs.dbk:1480 msgid "" "Make sure you don't rely on locally installed or hacked configurations or " -"programs. For instance, you should never be calling programs in " -"<filename>/usr/local/bin</filename> or the like. Try not to rely on " -"programs being setup in a special way. Try building your package on another " -"machine, even if it's the same architecture." +"programs. For instance, you should never be calling programs in <filename>/" +"usr/local/bin</filename> or the like. Try not to rely on programs being " +"setup in a special way. Try building your package on another machine, even " +"if it's the same architecture." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1485 +#: pkgs.dbk:1489 msgid "" -"Don't depend on the package you're building being installed already (a " -"sub-case of the above issue)." +"Don't depend on the package you're building being installed already (a sub-" +"case of the above issue)." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1491 +#: pkgs.dbk:1495 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 " @@ -2023,22 +1984,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1499 +#: pkgs.dbk:1503 msgid "" -"Make sure your debian/rules contains separate ``binary-arch'' and " -"``binary-indep'' targets, as the Debian Policy Manual requires. Make sure " -"that both targets work independently, that is, that you can call the target " -"without having called the other before. To test this, try to run " -"<literal>dpkg-buildpackage -B</literal>." +"Make sure your debian/rules contains separate ``binary-arch'' and ``binary-" +"indep'' targets, as the Debian Policy Manual requires. Make sure that both " +"targets work independently, that is, that you can call the target without " +"having called the other before. To test this, try to run <literal>dpkg-" +"buildpackage -B</literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1510 +#: pkgs.dbk:1514 msgid "Guidelines for porter uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1512 +#: pkgs.dbk:1516 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 " @@ -2049,7 +2010,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1520 +#: pkgs.dbk:1524 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 " @@ -2057,34 +2018,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1525 +#: pkgs.dbk:1529 msgid "" -"The way to invoke <command>dpkg-buildpackage</command> is as " -"<literal>dpkg-buildpackage -B " -"-m<replaceable>porter-email</replaceable></literal>. Of course, set " -"<replaceable>porter-email</replaceable> to your email address. This will do " -"a binary-only build of only the architecture-dependent portions of the " -"package, using the `binary-arch' target in " -"<filename>debian/rules</filename>." +"The way to invoke <command>dpkg-buildpackage</command> is as <literal>dpkg-" +"buildpackage -B -m<replaceable>porter-email</replaceable></literal>. Of " +"course, set <replaceable>porter-email</replaceable> to your email address. " +"This will do a binary-only build of only the architecture-dependent portions " +"of the package, using the `binary-arch' target in <filename>debian/rules</" +"filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1533 +#: pkgs.dbk:1537 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 " "<command>debsign</command> on your <filename>.changes</filename> file to " -"have it signed conveniently, or use the remote signing mode of " -"<command>dpkg-sig</command>." +"have it signed conveniently, or use the remote signing mode of <command>dpkg-" +"sig</command>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1540 +#: pkgs.dbk:1544 msgid "Recompilation or binary-only NMU" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1542 +#: pkgs.dbk:1546 msgid "" "Sometimes the initial porter upload is problematic because the environment " "in which the package was built was not good enough (outdated or obsolete " @@ -2096,24 +2056,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1551 +#: pkgs.dbk:1555 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 " -"arch-dependent and arch-independent packages that depend on each other via " +"uninstallable. This could happen when a source package generates arch-" +"dependent and arch-independent packages that depend on each other via " "$(Source-Version)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1557 +#: pkgs.dbk:1561 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 " -"architectures to consider themselves out of date or requiring recompilation." +"Despite the required modification of the changelog, these are called binary-" +"only NMUs — there is no need in this case to trigger all other architectures " +"to consider themselves out of date or requiring recompilation." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1562 +#: pkgs.dbk:1566 msgid "" "Such recompilations require special ``magic'' version numbering, so that the " "archive maintenance tools recognize that, even though there is a new Debian " @@ -2123,7 +2083,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: pkgs.dbk:1569 +#: pkgs.dbk:1573 msgid "" "The ``magic'' for a recompilation-only NMU is triggered by using a suffix " "appended to the package version number, following the form b<number>. " @@ -2134,7 +2094,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: pkgs.dbk:1574 +#: pkgs.dbk:1578 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 " @@ -2144,20 +2104,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1582 +#: pkgs.dbk:1586 msgid "" -"Similar to initial porter uploads, the correct way of invoking " -"<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage " -"-B</literal> to only build the architecture-dependent parts of the package." +"Similar to initial porter uploads, the correct way of invoking <command>dpkg-" +"buildpackage</command> is <literal>dpkg-buildpackage -B</literal> to only " +"build the architecture-dependent parts of the package." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1589 +#: pkgs.dbk:1593 msgid "When to do a source NMU if you are a porter" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1591 +#: pkgs.dbk:1595 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 " @@ -2170,7 +2130,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1600 +#: pkgs.dbk:1604 msgid "" "If you are a porter doing an NMU for `unstable', the above guidelines for " "porting should be followed, with two variations. Firstly, the acceptable " @@ -2184,7 +2144,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1611 +#: pkgs.dbk:1615 msgid "" "Secondly, porters doing source NMUs should make sure that the bug they " "submit to the BTS should be of severity `serious' or greater. This ensures " @@ -2195,7 +2155,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1619 +#: pkgs.dbk:1623 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 " @@ -2206,7 +2166,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1627 +#: pkgs.dbk:1631 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 " @@ -2215,12 +2175,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1637 +#: pkgs.dbk:1641 msgid "Porting infrastructure and automation" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1639 +#: pkgs.dbk:1643 msgid "" "There is infrastructure and several tools to help automate package porting. " "This section contains a brief overview of this automation and porting to " @@ -2229,40 +2189,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1644 +#: pkgs.dbk:1648 msgid "Mailing lists and web pages" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1646 +#: pkgs.dbk:1650 msgid "" -"Web pages containing the status of each port can be found at <ulink " -"url=\"http://www.debian.org/ports/\"></ulink>." +"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:1650 +#: pkgs.dbk:1654 msgid "" "Each port of Debian has a mailing list. The list of porting mailing lists " -"can be found at <ulink url=\"http://lists.debian.org/ports.html\"></ulink>. " -"These lists are used to coordinate porters, and to connect the users of a " -"given port with the porters." +"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These " +"lists are used to coordinate porters, and to connect the users of a given " +"port with the porters." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1658 +#: pkgs.dbk:1662 msgid "Porter tools" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1660 +#: pkgs.dbk:1664 msgid "" -"Descriptions of several porting tools can be found in <xref " -"linkend=\"tools-porting\"/> ." +"Descriptions of several porting tools can be found in <xref linkend=\"tools-" +"porting\"/> ." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1668 +#: pkgs.dbk:1672 msgid "" "The <systemitem role=\"package\">buildd</systemitem> system is used as a " "distributed, client-server build distribution system. It is usually used in " @@ -2274,32 +2234,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1677 +#: pkgs.dbk:1681 msgid "" "<systemitem role=\"package\">buildd</systemitem> is not yet available as a " "package; however, most porting efforts are either using it currently or " "planning to use it in the near future. The actual automated builder is " "packaged as <systemitem role=\"package\">sbuild</systemitem>, see its " -"description in <xref linkend=\"sbuild\"/> . The complete <systemitem " -"role=\"package\">buildd</systemitem> system also collects a number of as yet " +"description in <xref linkend=\"sbuild\"/> . The complete <systemitem role=" +"\"package\">buildd</systemitem> system also collects a number of as yet " "unpackaged components which are currently very useful and in use " -"continually, such as <command>andrea</command> and " -"<command>wanna-build</command>." +"continually, such as <command>andrea</command> and <command>wanna-build</" +"command>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1687 +#: pkgs.dbk:1691 msgid "" -"Some of the data produced by <systemitem " -"role=\"package\">buildd</systemitem> which is generally useful to porters is " -"available on the web at <ulink url=\"http://buildd.debian.org/\"></ulink>. " -"This data includes nightly updated information from " -"<command>andrea</command> (source dependencies) and <systemitem " -"role=\"package\">quinn-diff</systemitem> (packages needing recompilation)." +"Some of the data produced by <systemitem role=\"package\">buildd</" +"systemitem> which is generally useful to porters is available on the web at " +"<ulink url=\"&url-buildd;\"></ulink>. This data includes nightly updated " +"information from <command>andrea</command> (source dependencies) and " +"<systemitem role=\"package\">quinn-diff</systemitem> (packages needing " +"recompilation)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1695 +#: pkgs.dbk:1699 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 " @@ -2309,36 +2269,36 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1702 +#: pkgs.dbk:1706 msgid "" "The buildds admins of each arch can be contacted at the mail address " "$arch@buildd.debian.org." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1710 +#: pkgs.dbk:1714 msgid "When your package is <emphasis>not</emphasis> portable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1712 +#: pkgs.dbk:1716 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 " -"within a reasonable amount of time. An example is a package that is " -"SVGA-specific (only i386), or uses other hardware-specific features not " -"supported on all architectures." +"within a reasonable amount of time. An example is a package that is SVGA-" +"specific (only i386), or uses other hardware-specific features not supported " +"on all architectures." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1719 +#: pkgs.dbk:1723 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:1725 +#: pkgs.dbk:1729 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 " @@ -2350,7 +2310,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1733 +#: pkgs.dbk:1737 msgid "" "Additionally, if you believe the list of supported architectures is pretty " "constant, you should change 'any' to a list of supported architectures in " @@ -2359,35 +2319,35 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1741 +#: pkgs.dbk:1745 msgid "" "In order to prevent autobuilders from needlessly trying to build your " "package, it must be included in <filename>packages-arch-specific</filename>, " "a list used by the <command>wanna-build</command> script. The current " -"version is available as <ulink " -"url=\"http://cvs.debian.org/srcdep/Packages-arch-specific?cvsroot=dak\"></ulink>; " -"please see the top of the file for whom to contact for changes." +"version is available as <ulink url=\"&url-cvsweb;srcdep/Packages-arch-" +"specific?cvsroot=dak\"></ulink>; please see the top of the file for whom to " +"contact for changes." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1751 +#: pkgs.dbk:1755 msgid "" -"Please note that it is insufficient to only add your package to " -"Packages-arch-specific without making it fail to build on unsupported " -"architectures: A porter or any other person trying to build your package " -"might accidently upload it without noticing it doesn't work. If in the past " -"some binary packages were uploaded on unsupported architectures, request " -"their removal by filing a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem>" +"Please note that it is insufficient to only add your package to Packages-" +"arch-specific without making it fail to build on unsupported architectures: " +"A porter or any other person trying to build your package might accidently " +"upload it without noticing it doesn't work. If in the past some binary " +"packages were uploaded on unsupported architectures, request their removal " +"by filing a bug against <systemitem role=\"package\">ftp.debian.org</" +"systemitem>" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1764 +#: pkgs.dbk:1768 msgid "Non-Maintainer Uploads (NMUs)" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1766 +#: pkgs.dbk:1770 msgid "" "Under certain circumstances it is necessary for someone other than the " "official package maintainer to make a release of a package. This is called " @@ -2395,17 +2355,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1771 +#: pkgs.dbk:1775 msgid "" "This section handles only source NMUs, i.e. NMUs which upload a new version " "of the package. For binary-only NMUs by porters or QA members, please see " "<xref linkend=\"binary-only-nmu\"/> . If a buildd builds and uploads a " -"package, that too is strictly speaking a binary NMU. See <xref " -"linkend=\"buildd\"/> for some more information." +"package, that too is strictly speaking a binary NMU. See <xref linkend=" +"\"buildd\"/> for some more information." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1778 +#: pkgs.dbk:1782 msgid "" "The main reason why NMUs are done is when a developer needs to fix another " "developer's package in order to address serious problems or crippling bugs " @@ -2414,7 +2374,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1783 +#: pkgs.dbk:1787 msgid "" "First and foremost, it is critical that NMU patches to source should be as " "non-disruptive as possible. Do not do housekeeping tasks, do not change the " @@ -2426,20 +2386,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1792 +#: pkgs.dbk:1796 msgid "" "And please remember the Hippocratic Oath: Above all, do no harm. It is " -"better to leave a package with an open grave bug than applying a " -"non-functional patch, or one that hides the bug instead of resolving it." +"better to leave a package with an open grave bug than applying a non-" +"functional patch, or one that hides the bug instead of resolving it." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1797 +#: pkgs.dbk:1801 msgid "How to do a NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1799 +#: pkgs.dbk:1803 msgid "" "NMUs which fix important, serious or higher severity bugs are encouraged and " "accepted. You should endeavor to reach the current maintainer of the " @@ -2448,7 +2408,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1805 +#: pkgs.dbk:1809 msgid "" "NMUs should be made to assist a package's maintainer in resolving bugs. " "Maintainers should be thankful for that help, and NMUers should respect the " @@ -2457,14 +2417,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1811 +#: pkgs.dbk:1815 msgid "" "A NMU should follow all conventions, written down in this section. For an " "upload to testing or unstable, this order of steps is recommended:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1817 +#: pkgs.dbk:1821 msgid "" "Make sure that the package's bugs that the NMU is meant to address are all " "filed in the Debian Bug Tracking System (BTS). If they are not, submit them " @@ -2472,7 +2432,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1824 +#: pkgs.dbk:1828 msgid "" "Wait a few days for the response from the maintainer. If you don't get any " "response, you may want to help them by sending the patch that fixes the " @@ -2480,7 +2440,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1831 +#: pkgs.dbk:1835 msgid "" "Wait a few more days. If you still haven't got an answer from the " "maintainer, send them a mail announcing your intent to NMU the package. " @@ -2491,7 +2451,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1841 +#: pkgs.dbk:1845 msgid "" "Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. " "<xref linkend=\"delayed-incoming\"/> ), send the final patch to the " @@ -2500,7 +2460,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1849 +#: pkgs.dbk:1853 msgid "" "Follow what happens, you're responsible for any bug that you introduced with " "your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> " @@ -2508,7 +2468,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1856 +#: pkgs.dbk:1860 msgid "" "At times, the release manager or an organized group of developers can " "announce a certain period of time in which the NMU rules are relaxed. This " @@ -2520,7 +2480,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1865 +#: pkgs.dbk:1869 msgid "" "For the testing distribution, the rules may be changed by the release " "managers. Please take additional care, and acknowledge that the usual way " @@ -2528,7 +2488,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1870 +#: pkgs.dbk:1874 msgid "" "For the stable distribution, please take extra care. Of course, the release " "managers may also change the rules here. Please verify before you upload " @@ -2537,7 +2497,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1876 +#: pkgs.dbk:1880 msgid "" "When a security bug is detected, the security team may do an NMU, using " "their own rules. Please refer to <xref linkend=\"bug-security\"/> for more " @@ -2545,14 +2505,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1881 +#: pkgs.dbk:1885 msgid "" -"For the differences for Porters NMUs, please see <xref " -"linkend=\"source-nmu-when-porter\"/> ." +"For the differences for Porters NMUs, please see <xref linkend=\"source-nmu-" +"when-porter\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1885 +#: pkgs.dbk:1889 msgid "" "Of course, it is always possible to agree on special rules with a maintainer " "(like the maintainer asking please upload this fix directly for me, and no " @@ -2560,20 +2520,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1892 +#: pkgs.dbk:1896 msgid "NMU version numbering" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1894 +#: pkgs.dbk:1898 msgid "" "Whenever you have made a change to a package, no matter how trivial, the " -"version number needs to change. This enables our packing system to " -"function." +"version number needs to change. This enables our packing system to function." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1898 +#: pkgs.dbk:1902 msgid "" "If you are doing a non-maintainer upload (NMU), you should add a new minor " "version number to the <replaceable>debian-revision</replaceable> part of the " @@ -2582,12 +2541,12 @@ msgid "" "version 1.1-3. In the archive, the source package control file would be " "<filename>foo_1.1-3.dsc</filename>. The upstream version is `1.1' and the " "Debian revision is `3'. The next NMU would add a new minor number `.1' to " -"the Debian revision; the new source control file would be " -"<filename>foo_1.1-3.1.dsc</filename>." +"the Debian revision; the new source control file would be <filename>foo_1.1-" +"3.1.dsc</filename>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1909 +#: pkgs.dbk:1913 msgid "" "The Debian revision minor number is needed to avoid stealing one of the " "package maintainer's version numbers, which might disrupt their work. It " @@ -2596,7 +2555,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1915 +#: pkgs.dbk:1919 msgid "" "If there is no <replaceable>debian-revision</replaceable> component in the " "version number then one should be created, starting at `0.1' (but in case of " @@ -2609,7 +2568,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1925 +#: pkgs.dbk:1929 msgid "" "If you upload a package to testing or stable, sometimes, you need to fork " "the version number tree. For this, version numbers like 1.1-3sarge0.1 could " @@ -2617,12 +2576,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1932 +#: pkgs.dbk:1936 msgid "Source NMUs must have a new changelog entry" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1934 +#: pkgs.dbk:1938 msgid "" "Anyone who is doing a source NMU must create a changelog entry, describing " "which bugs are fixed by the NMU, and generally why the NMU was required and " @@ -2631,23 +2590,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1940 +#: pkgs.dbk:1944 msgid "By convention, source NMU changelog entries start with the line" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:1943 +#: pkgs.dbk:1947 #, no-wrap msgid "* Non-maintainer upload" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1948 +#: pkgs.dbk:1952 msgid "Source NMUs and the Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1950 +#: pkgs.dbk:1954 msgid "" "Maintainers other than the official package maintainer should make as few " "changes to the package as possible, and they should always send a patch as a " @@ -2656,7 +2615,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1956 +#: pkgs.dbk:1960 msgid "" "What if you are simply recompiling the package? If you just need to " "recompile it for a single architecture, then you may do a binary-only NMU as " @@ -2667,7 +2626,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1963 +#: pkgs.dbk:1967 msgid "" "Bugs fixed by source NMUs used to be tagged fixed instead of closed, but " "since version tracking is in place, such bugs are now also closed with the " @@ -2675,7 +2634,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1968 +#: pkgs.dbk:1972 msgid "" "Also, after doing an NMU, you have to send the information to the existing " "bugs that are fixed by your NMU, including the unified diff. Historically, " @@ -2690,7 +2649,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1979 +#: pkgs.dbk:1983 msgid "" "In addition, the normal maintainer should <emphasis>always</emphasis> retain " "the entry in the changelog file documenting the non-maintainer upload -- and " @@ -2699,12 +2658,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1987 +#: pkgs.dbk:1991 msgid "Building source NMUs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1989 +#: pkgs.dbk:1993 msgid "" "Source NMU packages are built normally. Pick a distribution using the same " "rules as found in <xref linkend=\"distribution\"/> , follow the other " @@ -2712,7 +2671,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1994 +#: pkgs.dbk:1998 msgid "" "Make sure you do <emphasis>not</emphasis> change the value of the maintainer " "in the <filename>debian/control</filename> file. Your name as given in the " @@ -2721,12 +2680,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2002 +#: pkgs.dbk:2006 msgid "Acknowledging an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2004 +#: pkgs.dbk:2008 msgid "" "If one of your packages has been NMU'ed, you have to incorporate the changes " "in your copy of the sources. This is easy, you just have to apply the patch " @@ -2740,7 +2699,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2015 +#: pkgs.dbk:2019 msgid "" "In any case, you should not be upset by the NMU. An NMU is not a personal " "attack against the maintainer. It is a proof that someone cares enough " @@ -2751,80 +2710,80 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2025 +#: pkgs.dbk:2029 msgid "NMU vs QA uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2027 +#: pkgs.dbk:2031 msgid "" "Unless you know the maintainer is still active, it is wise to check the " "package to see if it has been orphaned. The current list of orphaned " "packages which haven't had their maintainer set correctly is available at " -"<ulink url=\"http://qa.debian.org/orphaned.html\"></ulink>. If you perform " -"an NMU on an improperly orphaned package, please set the maintainer to " -"``Debian QA Group <packages@qa.debian.org>''." +"<ulink url=\"&url-debian-qa-orphaned;\"></ulink>. If you perform an NMU on " +"an improperly orphaned package, please set the maintainer to <literal>Debian " +"QA Group <packages@qa.debian.org></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2037 +#: pkgs.dbk:2041 msgid "Who can do an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2039 +#: pkgs.dbk:2043 msgid "" "Only official, registered Debian Developers can do binary or source NMUs. A " -"Debian Developer is someone who has their key in the Debian key ring. " -"Non-developers, however, are encouraged to download the source package and " -"start hacking on it to fix problems; however, rather than doing an NMU, they " +"Debian Developer is someone who has their key in the Debian key ring. Non-" +"developers, however, are encouraged to download the source package and start " +"hacking on it to fix problems; however, rather than doing an NMU, they " "should just submit worthwhile patches to the Bug Tracking System. " "Maintainers almost always appreciate quality patches and bug reports." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2049 +#: pkgs.dbk:2053 msgid "Terminology" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2051 +#: pkgs.dbk:2055 msgid "" "There are two new terms used throughout this section: ``binary-only NMU'' " "and ``source NMU''. These terms are used with specific technical meaning " "throughout this document. Both binary-only and source NMUs are similar, " "since they involve an upload of a package by a developer who is not the " -"official maintainer of that package. That is why it's a " -"<emphasis>non-maintainer</emphasis> upload." +"official maintainer of that package. That is why it's a <emphasis>non-" +"maintainer</emphasis> upload." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2059 +#: pkgs.dbk:2063 msgid "" "A source NMU is an upload of a package by a developer who is not the " "official maintainer, for the purposes of fixing a bug in the package. " "Source NMUs always involves changes to the source (even if it is just a " "change to <filename>debian/changelog</filename>). This can be either a " "change to the upstream source, or a change to the Debian bits of the " -"source. Note, however, that source NMUs may also include " -"architecture-dependent packages, as well as an updated Debian diff." +"source. Note, however, that source NMUs may also include architecture-" +"dependent packages, as well as an updated Debian diff." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2068 +#: pkgs.dbk:2072 msgid "" "A binary-only NMU is a recompilation and upload of a binary package for a " "given architecture. As such, it is usually part of a porting effort. A " "binary-only NMU is a non-maintainer uploaded binary version of a package, " "with no source changes required. There are many cases where porters must " "fix problems in the source in order to get them to compile for their target " -"architecture; that would be considered a source NMU rather than a " -"binary-only NMU. As you can see, we don't distinguish in terminology " -"between porter NMUs and non-porter NMUs." +"architecture; that would be considered a source NMU rather than a binary-" +"only NMU. As you can see, we don't distinguish in terminology between " +"porter NMUs and non-porter NMUs." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2078 +#: pkgs.dbk:2082 msgid "" "Both classes of NMUs, source and binary-only, can be lumped under the term " "``NMU''. However, this often leads to confusion, since most people think " @@ -2833,50 +2792,49 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2088 +#: pkgs.dbk:2092 msgid "Collaborative maintenance" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2090 +#: pkgs.dbk:2094 msgid "" "Collaborative maintenance is a term describing the sharing of Debian package " "maintenance duties by several people. This collaboration is almost always a " "good idea, since it generally results in higher quality and faster bug fix " "turnaround times. It is strongly recommended that packages with a priority " -"of <literal>Standard</literal> or which are part of the base set have " -"co-maintainers." +"of <literal>Standard</literal> or which are part of the base set have co-" +"maintainers." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2098 +#: pkgs.dbk:2102 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 " -"<literal>Maintainer</literal> field of the " -"<filename>debian/control</filename> file. Co-maintainers are all the other " -"maintainers." +"<literal>Maintainer</literal> field of the <filename>debian/control</" +"filename> file. Co-maintainers are all the other maintainers." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2104 +#: pkgs.dbk:2108 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:2110 +#: pkgs.dbk:2114 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 " -"control system, such as <command>CVS</command> or " -"<command>Subversion</command>. Alioth (see <xref linkend=\"alioth\"/> ) " -"provides such tools, amongst others." +"control system, such as <command>CVS</command> or <command>Subversion</" +"command>. Alioth (see <xref linkend=\"alioth\"/> ) provides such tools, " +"amongst others." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2118 +#: pkgs.dbk:2122 msgid "" "Add the co-maintainer's correct maintainer name and address to the " "<literal>Uploaders</literal> field in the global part of the " @@ -2884,20 +2842,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><screen> -#: pkgs.dbk:2123 +#: pkgs.dbk:2127 #, no-wrap -msgid ": John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>" +msgid "Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2128 +#: pkgs.dbk:2132 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:2134 +#: pkgs.dbk:2138 msgid "" "Another form of collaborative maintenance is team maintenance, which is " "recommended if you maintain several packages with the same group of " @@ -2907,7 +2865,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2143 +#: pkgs.dbk:2147 msgid "" "Put the team member mainly responsible for the package in the Maintainer " "field. In the Uploaders, put the mailing list address, and the team members " @@ -2915,7 +2873,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2150 +#: pkgs.dbk:2154 msgid "" "Put the mailing list address in the Maintainer field. In the Uploaders " "field, put the team members who care for the package. In this case, you " @@ -2924,7 +2882,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2158 +#: pkgs.dbk:2162 msgid "" "In any case, it is a bad idea to automatically put all team members in the " "Uploaders field. It clutters the Developer's Package Overview listing (see " @@ -2933,39 +2891,39 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2166 +#: pkgs.dbk:2170 msgid "The testing distribution" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2168 +#: pkgs.dbk:2172 msgid "Basics" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2170 +#: pkgs.dbk:2174 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2174 +#: pkgs.dbk:2178 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 " -"release-critical bugs at the time they're installed into testing. This way, " +"make them uninstallable; they also have to have generally no known release-" +"critical bugs at the time they're installed into testing. This way, " "`testing' should always be close to being a release candidate. Please see " "below for details." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2183 +#: pkgs.dbk:2187 msgid "Updates from unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2185 +#: pkgs.dbk:2189 msgid "" "The scripts that update the <emphasis>testing</emphasis> distribution are " "run each day after the installation of the updated packages; these scripts " @@ -2976,14 +2934,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2193 +#: pkgs.dbk:2197 msgid "" "The inclusion of a package from <emphasis>unstable</emphasis> is conditional " "on the following:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2199 +#: pkgs.dbk:2203 msgid "" "The package must have been available in <emphasis>unstable</emphasis> for 2, " "5 or 10 days, depending on the urgency (high, medium or low). Please note " @@ -2994,14 +2952,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2208 +#: pkgs.dbk:2212 msgid "" "It must have the same number or fewer release-critical bugs than the version " "currently available in <emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2214 +#: pkgs.dbk:2218 msgid "" "It must be available on all architectures on which it has previously been " "built in unstable. <xref linkend=\"madison\"/> may be of interest to check " @@ -3009,14 +2967,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2221 +#: pkgs.dbk:2225 msgid "" "It must not break any dependency of a package which is already available in " "<emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2227 +#: pkgs.dbk:2231 msgid "" "The packages on which it depends must either be available in " "<emphasis>testing</emphasis> or they must be accepted into " @@ -3025,32 +2983,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2235 +#: pkgs.dbk:2239 msgid "" "To find out whether a package is progressing into testing or not, see the " -"testing script output on the <ulink " -"url=\"http://www.debian.org/devel/testing\">web page of the testing " -"distribution</ulink>, or use the program <command>grep-excuses</command> " -"which is in the <systemitem role=\"package\">devscripts</systemitem> " -"package. This utility can easily be used in a <citerefentry> " -"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> " -"</citerefentry> to keep yourself informed of the progression of your " -"packages into <emphasis>testing</emphasis>." +"testing script output on the <ulink url=\"&url-testing-maint;\">web page of " +"the testing distribution</ulink>, or use the program <command>grep-excuses</" +"command> which is in the <systemitem role=\"package\">devscripts</" +"systemitem> package. This utility can easily be used in a <citerefentry> " +"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> </" +"citerefentry> to keep yourself informed of the progression of your packages " +"into <emphasis>testing</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2246 +#: pkgs.dbk:2250 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 " "own by looking for what would break with the inclusion of the package. The " -"<ulink url=\"http://www.debian.org/devel/testing\">testing web page</ulink> " -"gives some more information about the usual problems which may be causing " -"such troubles." +"<ulink url=\"&url-testing-maint;\">testing web page</ulink> gives some more " +"information about the usual problems which may be causing such troubles." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2253 +#: pkgs.dbk:2257 msgid "" "Sometimes, some packages never enter <emphasis>testing</emphasis> because " "the set of inter-relationship is too complicated and cannot be sorted out by " @@ -3058,20 +3014,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2258 +#: pkgs.dbk:2262 msgid "" -"Some further dependency analysis is shown on <ulink " -"url=\"http://bjorn.haxx.se/debian/\"></ulink> — but be warned, this page " -"also shows build dependencies which are not considered by britney." +"Some further dependency analysis is shown on <ulink url=\"http://bjorn.haxx." +"se/debian/\"></ulink> — but be warned, this page also shows build " +"dependencies which are not considered by britney." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2263 +#: pkgs.dbk:2267 msgid "out-of-date" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2265 +#. FIXME: better rename this file than document rampant professionalism? +#: pkgs.dbk:2270 msgid "" "For the testing migration script, outdated means: There are different " "versions in unstable for the release architectures (except for the " @@ -3081,47 +3038,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2272 +#: pkgs.dbk:2277 msgid "Consider this example:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2279 pkgs.dbk:2310 +#: pkgs.dbk:2284 pkgs.dbk:2315 msgid "alpha" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2280 pkgs.dbk:2311 +#: pkgs.dbk:2285 pkgs.dbk:2316 msgid "arm" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2285 pkgs.dbk:2317 pkgs.dbk:2377 +#: pkgs.dbk:2290 pkgs.dbk:2322 pkgs.dbk:2382 msgid "testing" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2286 pkgs.dbk:2291 pkgs.dbk:2318 pkgs.dbk:2319 pkgs.dbk:2326 +#: pkgs.dbk:2291 pkgs.dbk:2296 pkgs.dbk:2323 pkgs.dbk:2324 pkgs.dbk:2331 msgid "1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2287 pkgs.dbk:2320 pkgs.dbk:2325 +#: pkgs.dbk:2292 pkgs.dbk:2325 pkgs.dbk:2330 msgid "-" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2290 pkgs.dbk:2323 pkgs.dbk:2378 +#: pkgs.dbk:2295 pkgs.dbk:2328 pkgs.dbk:2383 msgid "unstable" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2292 pkgs.dbk:2324 +#: pkgs.dbk:2297 pkgs.dbk:2329 msgid "2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2298 +#: pkgs.dbk:2303 msgid "" "The package is out of date on alpha in unstable, and will not go to " "testing. And removing foo from testing would not help at all, the package " @@ -3129,17 +3086,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2303 +#: pkgs.dbk:2308 msgid "However, if ftp-master removes a package in unstable (here on arm):" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2312 +#: pkgs.dbk:2317 msgid "hurd-i386" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2332 +#: pkgs.dbk:2337 msgid "" "In this case, the package is up to date on all release architectures in " "unstable (and the extra hurd-i386 doesn't matter, as it's not a release " @@ -3147,7 +3104,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2337 +#: pkgs.dbk:2342 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 " @@ -3155,105 +3112,104 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2344 +#: pkgs.dbk:2349 msgid "Removals from testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2346 +#: pkgs.dbk:2351 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 " "every other sense. Suppose e.g. that <emphasis>a</emphasis> cannot be " -"installed with the new version of <emphasis>b</emphasis>; then " -"<emphasis>a</emphasis> may be removed to allow <emphasis>b</emphasis> in." +"installed with the new version of <emphasis>b</emphasis>; then <emphasis>a</" +"emphasis> may be removed to allow <emphasis>b</emphasis> in." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2353 +#: pkgs.dbk:2358 msgid "" "Of course, there is another reason to remove a package from testing: It's " "just too buggy (and having a single RC-bug is enough to be in this state)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2357 +#: pkgs.dbk:2362 msgid "" "Furthermore, if a package has been removed from unstable, and no package in " "testing depends on it any more, then it will automatically be removed." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2363 +#: pkgs.dbk:2368 msgid "circular dependencies" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2365 +#: pkgs.dbk:2370 msgid "" "A situation which is not handled very well by britney is if package " -"<emphasis>a</emphasis> depends on the new version of package " -"<emphasis>b</emphasis>, and vice versa." +"<emphasis>a</emphasis> depends on the new version of package <emphasis>b</" +"emphasis>, and vice versa." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2370 +#: pkgs.dbk:2375 msgid "An example of this is:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2383 +#: pkgs.dbk:2388 msgid "a" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2384 +#: pkgs.dbk:2389 msgid "1; depends: b=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2385 +#: pkgs.dbk:2390 msgid "2; depends: b=2" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2388 +#: pkgs.dbk:2393 msgid "b" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2389 +#: pkgs.dbk:2394 msgid "1; depends: a=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2390 +#: pkgs.dbk:2395 msgid "2; depends: a=2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2396 +#: pkgs.dbk:2401 msgid "" "Neither package <emphasis>a</emphasis> nor package <emphasis>b</emphasis> is " "considered for update." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2400 +#: pkgs.dbk:2405 msgid "" "Currently, this requires some manual hinting from the release team. Please " -"contact them by sending mail to " -"<email>debian-release@lists.debian.org</email> if this happens to one of " -"your packages." +"contact them by sending mail to &email-debian-release; if this happens to " +"one of your packages." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2407 +#: pkgs.dbk:2412 msgid "influence of package in testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2409 +#: pkgs.dbk:2414 msgid "" "Generally, there is nothing that the status of a package in testing means " "for transition of the next version from unstable to testing, with two " @@ -3267,7 +3223,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2419 +#: pkgs.dbk:2424 msgid "" "In summary this means: The only influence that a package being in testing " "has on a new version of the same package is that the new version might go in " @@ -3275,17 +3231,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2426 +#: pkgs.dbk:2431 msgid "details" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2428 +#: pkgs.dbk:2433 msgid "If you are interested in details, this is how britney works:" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2431 +#: pkgs.dbk:2436 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 " @@ -3298,7 +3254,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2440 +#: pkgs.dbk:2445 msgid "" "Now, the more complex part happens: Britney tries to update testing with the " "valid candidates; first, each package alone, and then larger and even larger " @@ -3309,29 +3265,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2448 +#: pkgs.dbk:2453 msgid "" -"If you want to see more details, you can look it up on " -"merkel:/org/ftp.debian.org/testing/update_out/ (or there in " -"~aba/testing/update_out to see a setup with a smaller packages file). Via " -"web, it's at <ulink " -"url=\"http://ftp-master.debian.org/testing/update_out_code/\"></ulink>" +"If you want to see more details, you can look it up on merkel:/org/&ftp-" +"debian-org;/testing/update_out/ (or there in ~aba/testing/update_out to see " +"a setup with a smaller packages file). Via web, it's at <ulink url=\"http://" +"&ftp-master-host;/testing/update_out_code/\"></ulink>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2455 +#: pkgs.dbk:2460 msgid "" -"The hints are available via <ulink " -"url=\"http://ftp-master.debian.org/testing/hints/\"></ulink>." +"The hints are available via <ulink url=\"http://&ftp-master-host;/testing/" +"hints/\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2463 +#: pkgs.dbk:2468 msgid "Direct updates to testing" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2465 +#: pkgs.dbk:2470 msgid "" "The testing distribution is fed with packages from unstable according to the " "rules explained above. However, in some cases, it is necessary to upload " @@ -3340,17 +3295,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2471 +#: pkgs.dbk:2476 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 " "have a good reason to upload there. In order to know what a good reason is " "in the release managers' eyes, you should read the instructions that they " -"regularly give on <email>debian-devel-announce@lists.debian.org</email>." +"regularly give on &email-debian-devel-announce;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2478 +#: pkgs.dbk:2483 msgid "" "You should not upload to <emphasis>testing-proposed-updates</emphasis> when " "you can update your packages through <emphasis>unstable</emphasis>. If you " @@ -3362,7 +3317,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2487 +#: pkgs.dbk:2492 msgid "" "Version numbers are usually selected by adding the codename of the testing " "distribution and a running number, like 1.2sarge1 for the first upload " @@ -3370,78 +3325,76 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2492 +#: pkgs.dbk:2497 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:2497 +#: pkgs.dbk:2502 msgid "" -"Make sure that your package really needs to go through " -"<emphasis>testing-proposed-updates</emphasis>, and can't go through " -"unstable;" +"Make sure that your package really needs to go through <emphasis>testing-" +"proposed-updates</emphasis>, and can't go through unstable;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2503 +#: pkgs.dbk:2508 msgid "Make sure that you included only the minimal amount of changes;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2508 -msgid "Make sure that you included an appropriate explanation in the changelog;" +#: pkgs.dbk:2513 +msgid "" +"Make sure that you included an appropriate explanation in the changelog;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2513 +#: pkgs.dbk:2518 msgid "" "Make sure that you've written <emphasis>testing</emphasis> or " "<emphasis>testing-proposed-updates</emphasis> into your target distribution;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2519 +#: pkgs.dbk:2524 msgid "" -"Make sure that you've built and tested your package in " -"<emphasis>testing</emphasis>, not in <emphasis>unstable</emphasis>;" +"Make sure that you've built and tested your package in <emphasis>testing</" +"emphasis>, not in <emphasis>unstable</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2525 +#: pkgs.dbk:2530 msgid "" "Make sure that your version number is higher than the version in " -"<emphasis>testing</emphasis> and " -"<emphasis>testing-proposed-updates</emphasis>, and lower than in " -"<emphasis>unstable</emphasis>;" +"<emphasis>testing</emphasis> and <emphasis>testing-proposed-updates</" +"emphasis>, and lower than in <emphasis>unstable</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2532 +#: pkgs.dbk:2537 msgid "" "After uploading and successful build on all platforms, contact the release " -"team at <email>debian-release@lists.debian.org</email> and ask them to " -"approve your upload." +"team at &email-debian-release; and ask them to approve your upload." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2541 +#: pkgs.dbk:2545 msgid "Frequently asked questions" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2543 +#: pkgs.dbk:2547 msgid "What are release-critical bugs, and how do they get counted?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2545 +#: pkgs.dbk:2549 msgid "" -"All bugs of some higher severities are by default considered " -"release-critical; currently, these are critical, grave, and serious bugs." +"All bugs of some higher severities are by default considered release-" +"critical; currently, these are critical, grave, and serious bugs." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2549 +#: pkgs.dbk:2553 msgid "" "Such bugs are presumed to have an impact on the chances that the package " "will be released with the stable release of Debian: in general, if a package " @@ -3450,7 +3403,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2555 +#: pkgs.dbk:2559 msgid "" "The unstable bug count are all release-critical bugs without either any " "release-tag (such as potato, woody) or with release-tag sid; also, only if " @@ -3460,19 +3413,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2562 +#: pkgs.dbk:2566 msgid "" "This will change post-sarge, as soon as we have versions in the bug tracking " "system." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2568 -msgid "How could installing a package into testing possibly break other packages?" +#: pkgs.dbk:2572 +msgid "" +"How could installing a package into testing possibly break other packages?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2570 +#: pkgs.dbk:2574 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 " @@ -3482,7 +3436,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2577 +#: pkgs.dbk:2581 msgid "" "However, the old version may have provided a binary package with an old " "soname of a library, such as libacme-foo0. Removing the old acmefoo will " @@ -3490,7 +3444,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2582 +#: pkgs.dbk:2586 msgid "" "Evidently, this mainly affects packages which provide changing sets of " "binary packages in different versions (in turn, mainly libraries). However, " @@ -3499,7 +3453,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2588 +#: pkgs.dbk:2592 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 " @@ -3512,7 +3466,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2598 +#: pkgs.dbk:2602 msgid "" "If you are having problems with complicated groups of packages like this, " "contact debian-devel or debian-release for help." diff --git a/po4a/ja/resources.po b/po4a/ja/resources.po index 856c359..ced083a 100644 --- a/po4a/ja/resources.po +++ b/po4a/ja/resources.po @@ -6,21 +6,21 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <chapter><title> -#: resources.dbk:5 +#: resources.dbk:7 msgid "Resources for Debian Developers" msgstr "" # type: Content of: <chapter><para> -#: resources.dbk:7 +#: resources.dbk:9 msgid "" "In this chapter you will find a very brief road map of the Debian mailing " "lists, the Debian machines which may be available to you as a developer, and " @@ -29,31 +29,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:12 +#: resources.dbk:14 msgid "Mailing lists" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:14 +#: resources.dbk:16 msgid "" "Much of the conversation between Debian developers (and users) is managed " -"through a wide array of mailing lists we host at <literal><ulink " -"url=\"http://lists.debian.org/\">lists.debian.org</ulink></literal>. To " -"find out more on how to subscribe or unsubscribe, how to post and how not to " -"post, where to find old posts and how to search them, how to contact the " -"list maintainers and see various other information about the mailing lists, " -"please read <ulink url=\"http://www.debian.org/MailingLists/\"></ulink>. " -"This section will only cover aspects of mailing lists that are of particular " -"interest to developers." +"through a wide array of mailing lists we host at <literal><ulink url=" +"\"http://&lists-host;/\">&lists-host;</ulink></literal>. To find out more " +"on how to subscribe or unsubscribe, how to post and how not to post, where " +"to find old posts and how to search them, how to contact the list " +"maintainers and see various other information about the mailing lists, " +"please read <ulink url=\"&url-debian-lists;\"></ulink>. This section will " +"only cover aspects of mailing lists that are of particular interest to " +"developers." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:24 +#: resources.dbk:27 msgid "Basic rules for use" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:26 +#: resources.dbk:29 msgid "" "When replying to messages on the mailing list, please do not send a carbon " "copy (<literal>CC</literal>) to the original poster unless they explicitly " @@ -62,175 +62,166 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:32 +#: resources.dbk:35 msgid "" "Cross-posting (sending the same message to multiple lists) is discouraged. " "As ever on the net, please trim down the quoting of articles you're replying " -"to. In general, please adhere to the usual conventions for posting " -"messages." +"to. In general, please adhere to the usual conventions for posting messages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:37 +#: resources.dbk:40 msgid "" -"Please read the <ulink " -"url=\"http://www.debian.org/MailingLists/#codeofconduct\">code of " +"Please read the <ulink url=\"&url-debian-lists;#codeofconduct\">code of " "conduct</ulink> for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:44 +#: resources.dbk:47 msgid "Core development mailing lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:46 +#: resources.dbk:49 msgid "The core Debian mailing lists that developers should use are:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:51 +#: resources.dbk:54 msgid "" -"<email>debian-devel-announce@lists.debian.org</email>, used to announce " -"important things to developers. All developers are expected to be " -"subscribed to this list." +"&email-debian-devel-announce;, used to announce important things to " +"developers. All developers are expected to be subscribed to this list." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:58 +#: resources.dbk:61 msgid "" -"<email>debian-devel@lists.debian.org</email>, used to discuss various " -"development related technical issues." +"&email-debian-devel;, used to discuss various development related technical " +"issues." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:64 +#: resources.dbk:67 msgid "" -"<email>debian-policy@lists.debian.org</email>, where the Debian Policy is " -"discussed and voted on." +"&email-debian-policy;, where the Debian Policy is discussed and voted on." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:70 +#: resources.dbk:73 msgid "" -"<email>debian-project@lists.debian.org</email>, used to discuss various " -"non-technical issues related to the project." +"&email-debian-project;, used to discuss various non-technical issues related " +"to the project." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:76 +#: resources.dbk:79 msgid "" "There are other mailing lists available for a variety of special topics; see " -"<ulink url=\"http://lists.debian.org/\"></ulink> for a list." +"<ulink url=\"http://&lists-host;/\"></ulink> for a list." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:82 +#: resources.dbk:85 msgid "Special lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:84 +#: resources.dbk:87 msgid "" -"<email>debian-private@lists.debian.org</email> is a special mailing list for " -"private discussions amongst Debian developers. It is meant to be used for " -"posts which for whatever reason should not be published publicly. As such, " -"it is a low volume list, and users are urged not to use " -"<email>debian-private@lists.debian.org</email> unless it is really " -"necessary. Moreover, do <emphasis>not</emphasis> forward email from that " -"list to anyone. Archives of this list are not available on the web for " -"obvious reasons, but you can see them using your shell account on " -"<literal>lists.debian.org</literal> and looking in the " -"<filename>~debian/archive/debian-private</filename> directory." +"&email-debian-private; is a special mailing list for private discussions " +"amongst Debian developers. It is meant to be used for posts which for " +"whatever reason should not be published publicly. As such, it is a low " +"volume list, and users are urged not to use &email-debian-private; unless it " +"is really necessary. Moreover, do <emphasis>not</emphasis> forward email " +"from that list to anyone. Archives of this list are not available on the " +"web for obvious reasons, but you can see them using your shell account on " +"<literal>&lists-host;</literal> and looking in the <filename>&file-debian-" +"private-archive;</filename> directory." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:96 +#: resources.dbk:99 msgid "" -"<email>debian-email@lists.debian.org</email> is a special mailing list used " -"as a grab-bag for Debian related correspondence such as contacting upstream " -"authors about licenses, bugs, etc. or discussing the project with others " -"where it might be useful to have the discussion archived somewhere." +"&email-debian-email; is a special mailing list used as a grab-bag for Debian " +"related correspondence such as contacting upstream authors about licenses, " +"bugs, etc. or discussing the project with others where it might be useful " +"to have the discussion archived somewhere." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:104 +#: resources.dbk:107 msgid "Requesting new development-related lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:106 +#: resources.dbk:109 msgid "" "Before requesting a mailing list that relates to the development of a " "package (or a small group of related packages), please consider if using an " "alias (via a .forward-aliasname file on master.debian.org, which translates " "into a reasonably nice <replaceable>you-aliasname@debian.org</replaceable> " -"address) or a self-managed mailing list on <link " -"linkend=\"alioth\">Alioth</link> is more appropriate." +"address) or a self-managed mailing list on <link linkend=\"alioth\">Alioth</" +"link> is more appropriate." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:114 +#: resources.dbk:117 msgid "" -"If you decide that a regular mailing list on lists.debian.org is really what " -"you want, go ahead and fill in a request, following <ulink " -"url=\"http://www.debian.org/MailingLists/HOWTO_start_list\">the " -"HOWTO</ulink>." +"If you decide that a regular mailing list on &lists-host; is really what you " +"want, go ahead and fill in a request, following <ulink url=\"&url-debian-" +"lists-new;\">the HOWTO</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:123 +#: resources.dbk:126 msgid "IRC channels" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:125 +#: resources.dbk:128 msgid "" "Several IRC channels are dedicated to Debian's development. They are mainly " -"hosted on the <ulink url=\"http://www.oftc.net/oftc/\">Open and free " -"technology community (OFTC)</ulink> network. The " -"<literal>irc.debian.org</literal> DNS entry is an alias to " -"<literal>irc.oftc.net</literal>." +"hosted on the <ulink url=\"&url-oftc;\">Open and free technology community " +"(OFTC)</ulink> network. The <literal>irc.debian.org</literal> DNS entry is " +"an alias to <literal>irc.oftc.net</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:131 +#: resources.dbk:134 msgid "" "The main channel for Debian in general is <emphasis>#debian</emphasis>. " "This is a large, general-purpose channel where users can find recent news in " "the topic and served by bots. <emphasis>#debian</emphasis> is for English " -"speakers; there are also <emphasis>#debian.de</emphasis>, " -"<emphasis>#debian-fr</emphasis>, <emphasis>#debian-br</emphasis> and other " -"similarly named channels for speakers of other languages." +"speakers; there are also <emphasis>#debian.de</emphasis>, <emphasis>#debian-" +"fr</emphasis>, <emphasis>#debian-br</emphasis> and other similarly named " +"channels for speakers of other languages." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:139 +#: resources.dbk:142 msgid "" -"The main channel for Debian development is " -"<emphasis>#debian-devel</emphasis>. It is a very active channel since " -"usually over 150 people are always logged in. It's a channel for people who " -"work on Debian, it's not a support channel (there's " -"<emphasis>#debian</emphasis> for that). It is however open to anyone who " -"wants to lurk (and learn). Its topic is commonly full of interesting " -"information for developers." +"The main channel for Debian development is <emphasis>#debian-devel</" +"emphasis>. It is a very active channel since usually over 150 people are " +"always logged in. It's a channel for people who work on Debian, it's not a " +"support channel (there's <emphasis>#debian</emphasis> for that). It is " +"however open to anyone who wants to lurk (and learn). Its topic is commonly " +"full of interesting information for developers." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:147 +#: resources.dbk:150 msgid "" "Since <emphasis>#debian-devel</emphasis> is an open channel, you should not " -"speak there of issues that are discussed in " -"<email>debian-private@lists.debian.org</email>. There's another channel for " -"this purpose, it's called <emphasis>#debian-private</emphasis> and it's " -"protected by a key. This key is available in the archives of debian-private " -"in <filename>master.debian.org:~debian/archive/debian-private/</filename>, " -"just <command>zgrep</command> for <emphasis>#debian-private</emphasis> in " -"all the files." +"speak there of issues that are discussed in &email-debian-private;. There's " +"another channel for this purpose, it's called <emphasis>#debian-private</" +"emphasis> and it's protected by a key. This key is available in the " +"archives of debian-private in <filename>master.debian.org:&file-debian-" +"private-archive;</filename>, just <command>zgrep</command> for " +"<emphasis>#debian-private</emphasis> in all the files." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:157 +#: resources.dbk:160 msgid "" "There are other additional channels dedicated to specific subjects. " "<emphasis>#debian-bugs</emphasis> is used for coordinating bug squashing " @@ -240,12 +231,12 @@ msgid "" "channels are dedicated to an architecture or a set of packages: " "<emphasis>#debian-bsd</emphasis>, <emphasis>#debian-kde</emphasis>, " "<emphasis>#debian-jr</emphasis>, <emphasis>#debian-edu</emphasis>, " -"<emphasis>#debian-sf</emphasis> (SourceForge package), " -"<emphasis>#debian-oo</emphasis> (OpenOffice package) ..." +"<emphasis>#debian-sf</emphasis> (SourceForge package), <emphasis>#debian-oo</" +"emphasis> (OpenOffice package) ..." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:169 +#: resources.dbk:172 msgid "" "Some non-English developers' channels exist as well, for example " "<emphasis>#debian-devel-fr</emphasis> for French speaking people interested " @@ -253,66 +244,64 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:174 +#: resources.dbk:177 msgid "" "Channels dedicated to Debian also exist on other IRC networks, notably on " -"the <ulink url=\"http://www.freenode.net/\">freenode</ulink> IRC network, " -"which was pointed at by the <literal>irc.debian.org</literal> alias until " -"4th June 2006." +"the <ulink url=\"&url-openprojects;\">freenode</ulink> IRC network, which " +"was pointed at by the <literal>irc.debian.org</literal> alias until 4th June " +"2006." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:179 +#: resources.dbk:183 msgid "" "To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a " "signed mail where you tell what your nick is. Put cloak somewhere in the " -"Subject: header. The nick should be registered: <ulink " -"url=\"http://freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. " -"The mail needs to be signed by a key in the Debian keyring. Please see " -"<ulink url=\"http://freenode.net/faq.shtml#projectcloak\">Freenodes " -"documentation</ulink> for more information about cloaks." +"Subject: header. The nick should be registered: <ulink url=\"http://" +"freenode.net/faq.shtml#nicksetup\">Nick Setup Page</ulink>. The mail needs " +"to be signed by a key in the Debian keyring. Please see <ulink url=\"http://" +"freenode.net/faq.shtml#projectcloak\">Freenodes documentation</ulink> for " +"more information about cloaks." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:190 +#: resources.dbk:194 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:192 +#: resources.dbk:196 msgid "" "This document contains a lot of information which is useful to Debian " "developers, but it cannot contain everything. Most of the other interesting " -"documents are linked from <ulink url=\"http://www.debian.org/devel/\">The " -"Developers' Corner</ulink>. Take the time to browse all the links, you will " -"learn many more things." +"documents are linked from <ulink url=\"&url-devel-docs;\">The Developers' " +"Corner</ulink>. Take the time to browse all the links, you will learn many " +"more things." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:201 +#: resources.dbk:205 msgid "Debian machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:203 +#: resources.dbk:207 msgid "" "Debian has several computers working as servers, most of which serve " "critical functions in the Debian project. Most of the machines are used for " -"porting activities, and they all have a permanent connection to the " -"Internet." +"porting activities, and they all have a permanent connection to the Internet." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:208 +#: resources.dbk:212 msgid "" "Most of the machines are available for individual developers to use, as long " -"as the developers follow the rules set forth in the <ulink " -"url=\"http://www.debian.org/devel/dmup\">Debian Machine Usage " -"Policies</ulink>." +"as the developers follow the rules set forth in the <ulink url=\"&url-dmup;" +"\">Debian Machine Usage Policies</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:213 +#: resources.dbk:217 msgid "" "Generally speaking, you can use these machines for Debian-related purposes " "as you see fit. Please be kind to system administrators, and do not use up " @@ -322,7 +311,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:220 +#: resources.dbk:224 msgid "" "Please take care to protect your Debian passwords and SSH keys installed on " "Debian machines. Avoid login or upload methods which send passwords over " @@ -330,162 +319,160 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:225 +#: resources.dbk:229 msgid "" "Please do not put any material that doesn't relate to Debian on the Debian " "servers, unless you have prior permission." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:229 +#: resources.dbk:233 msgid "" -"The current list of Debian machines is available at <ulink " -"url=\"http://db.debian.org/machines.cgi\"></ulink>. That web page contains " -"machine names, contact information, information about who can log in, SSH " -"keys etc." +"The current list of Debian machines is available at <ulink url=\"&url-devel-" +"machines;\"></ulink>. That web page contains machine names, contact " +"information, information about who can log in, SSH keys etc." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:235 +#: resources.dbk:239 msgid "" "If you have a problem with the operation of a Debian server, and you think " "that the system operators need to be notified of this problem, the Debian " -"system administrator team is reachable at " -"<email>debian-admin@lists.debian.org</email>." +"system administrator team is reachable at <email>debian-admin@&lists-host;</" +"email>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:241 +#: resources.dbk:245 msgid "" "If you have a problem with a certain service, not related to the system " "administration (such as packages to be removed from the archive, suggestions " -"for the web site, etc.), generally you'll report a bug against a " -"``pseudo-package''. See <xref linkend=\"submit-bug\"/> for information on " -"how to submit bugs." +"for the web site, etc.), generally you'll report a bug against a ``pseudo-" +"package''. See <xref linkend=\"submit-bug\"/> for information on how to " +"submit bugs." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:248 +#: resources.dbk:252 msgid "" "Some of the core servers are restricted, but the information from there is " "mirrored to another server." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:252 +#: resources.dbk:256 msgid "The bugs server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:254 +#: resources.dbk:258 msgid "" -"<literal>bugs.debian.org</literal> is the canonical location for the Bug " +"<literal>&bugs-host;</literal> is the canonical location for the Bug " "Tracking System (BTS)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:258 resources.dbk:276 +#: resources.dbk:262 resources.dbk:280 msgid "It is restricted; a mirror is available on <literal>merkel</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:261 +#: resources.dbk:265 msgid "" "If you plan on doing some statistical analysis or processing of Debian bugs, " -"this would be the place to do it. Please describe your plans on " -"<email>debian-devel@lists.debian.org</email> before implementing anything, " -"however, to reduce unnecessary duplication of effort or wasted processing " -"time." +"this would be the place to do it. Please describe your plans on &email-" +"debian-devel; before implementing anything, however, to reduce unnecessary " +"duplication of effort or wasted processing time." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:269 +#: resources.dbk:273 msgid "The ftp-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:271 +#: resources.dbk:275 msgid "" -"The <literal>ftp-master.debian.org</literal> server holds the canonical copy " -"of the Debian archive (excluding the non-US packages). Generally, package " +"The <literal>&ftp-master-host;</literal> server holds the canonical copy of " +"the Debian archive (excluding the non-US packages). Generally, package " "uploads go to this server; see <xref linkend=\"upload\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:279 +#: resources.dbk:283 msgid "" "Problems with the Debian FTP archive generally need to be reported as bugs " -"against the <systemitem role=\"package\">ftp.debian.org</systemitem> " -"pseudo-package or an email to <email>ftpmaster@debian.org</email>, but also " -"see the procedures in <xref linkend=\"archive-manip\"/> ." +"against the <systemitem role=\"package\">&ftp-debian-org;</systemitem> " +"pseudo-package or an email to &email-ftpmaster;, but also see the procedures " +"in <xref linkend=\"archive-manip\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:287 +#: resources.dbk:291 msgid "The non-US server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:289 +#: resources.dbk:293 msgid "" -"The non-US server <literal>non-us.debian.org</literal> was discontinued with " -"the release of sarge. The pseudo-package <systemitem " -"role=\"package\">nonus.debian.org</systemitem> still exists for now." +"The non-US server <literal>&non-us-host;</literal> was discontinued with the " +"release of sarge. The pseudo-package <systemitem role=\"package\">nonus." +"debian.org</systemitem> still exists for now." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:296 +#: resources.dbk:300 msgid "The www-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:298 +#: resources.dbk:302 msgid "" "The main web server is <literal>www-master.debian.org</literal>. It holds " "the official web pages, the face of Debian for most newbies." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:302 +#: resources.dbk:306 msgid "" "If you find a problem with the Debian web server, you should generally " -"submit a bug against the pseudo-package, <systemitem " -"role=\"package\">www.debian.org</systemitem>. Remember to check whether or " -"not someone else has already reported the problem to the <ulink " -"url=\"http://bugs.debian.org/www.debian.org\">Bug Tracking System</ulink>." +"submit a bug against the pseudo-package, <systemitem role=\"package\">www." +"debian.org</systemitem>. Remember to check whether or not someone else has " +"already reported the problem to the <ulink url=\"http://&bugs-host;/&www-" +"debian-org;\">Bug Tracking System</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:311 +#: resources.dbk:315 msgid "The people web server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:313 +#: resources.dbk:317 msgid "" "<literal>people.debian.org</literal> is the server used for developers' own " "web pages about anything related to Debian." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:317 +#: resources.dbk:321 msgid "" "If you have some Debian-specific information which you want to serve on the " -"web, you can do this by putting material in the " -"<filename>public_html</filename> directory under your home directory on " -"<literal>people.debian.org</literal>. This will be accessible at the URL " -"<literal>http://people.debian.org/~<replaceable>your-user-id</replaceable>/</literal>." +"web, you can do this by putting material in the <filename>public_html</" +"filename> directory under your home directory on <literal>people.debian.org</" +"literal>. This will be accessible at the URL <literal>http://people.debian." +"org/~<replaceable>your-user-id</replaceable>/</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:324 +#: resources.dbk:328 msgid "" "You should only use this particular location because it will be backed up, " "whereas on other hosts it won't." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:328 +#: resources.dbk:332 msgid "" "Usually the only reason to use a different host is when you need to publish " "materials subject to the U.S. export restrictions, in which case you can " @@ -493,24 +480,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:333 -msgid "" -"Send mail to <email>debian-devel@lists.debian.org</email> if you have any " -"questions." +#: resources.dbk:337 +msgid "Send mail to &email-debian-devel; if you have any questions." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:339 +#: resources.dbk:342 msgid "The CVS server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:341 +#: resources.dbk:345 msgid "Our CVS server is located on <literal>cvs.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:344 +#: resources.dbk:348 msgid "" "If you need to use a publicly accessible CVS server, for instance, to help " "coordinate work on a package between many different developers, you can " @@ -518,239 +503,172 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:349 +#: resources.dbk:353 msgid "" "Generally, <literal>cvs.debian.org</literal> offers a combination of local " "CVS access, anonymous client-server read-only access, and full client-server " "access through <command>ssh</command>. Also, the CVS area can be accessed " -"read-only via the Web at <ulink url=\"http://cvs.debian.org/\"></ulink>." +"read-only via the Web at <ulink url=\"&url-cvsweb;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:355 +#: resources.dbk:359 msgid "" -"To request a CVS area, send a request via email to " -"<email>debian-admin@debian.org</email>. Include the name of the requested " -"CVS area, the Debian account that should own the CVS root area, and why you " -"need it." +"To request a CVS area, send a request via email to &email-debian-admin;. " +"Include the name of the requested CVS area, the Debian account that should " +"own the CVS root area, and why you need it." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:363 +#: resources.dbk:367 msgid "chroots to different distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:365 +#: resources.dbk:369 msgid "" "On some machines, there are chroots to different distributions available. " "You can use them like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:369 +#: resources.dbk:373 #, no-wrap msgid "" -"% dchroot unstable\n" +"vore$ dchroot unstable\n" "Executing shell in chroot: /org/vore.debian.org/chroots/user/unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:373 +#: resources.dbk:377 msgid "" "In all chroots, the normal user home directories are available. You can " -"find out which chroots are available via " -"<literal>http://db.debian.org/machines.cgi</literal>." +"find out which chroots are available via <literal>&url-devel-machines;</" +"literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:382 +#: resources.dbk:386 msgid "The Developers Database" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:384 +#: resources.dbk:388 msgid "" -"The Developers Database, at <ulink url=\"https://db.debian.org/\"></ulink>, " -"is an LDAP directory for managing Debian developer attributes. You can use " -"this resource to search the list of Debian developers. Part of this " -"information is also available through the finger service on Debian servers, " -"try <command>finger yourlogin@db.debian.org</command> to see what it " -"reports." +"The Developers Database, at <ulink url=\"&url-debian-db;\"></ulink>, is an " +"LDAP directory for managing Debian developer attributes. You can use this " +"resource to search the list of Debian developers. Part of this information " +"is also available through the finger service on Debian servers, try " +"<command>finger yourlogin@db.debian.org</command> to see what it reports." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:391 +#: resources.dbk:396 msgid "" -"Developers can <ulink url=\"https://db.debian.org/login.html\">log into the " -"database</ulink> to change various information about themselves, such as:" +"Developers can <ulink url=\"&url-debian-db-login;\">log into the database</" +"ulink> to change various information about themselves, such as:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:397 +#: resources.dbk:402 msgid "forwarding address for your debian.org email" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:402 +#: resources.dbk:407 msgid "subscription to debian-private" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:407 +#: resources.dbk:412 msgid "whether you are on vacation" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:412 +#: resources.dbk:417 msgid "" "personal information such as your address, country, the latitude and " -"longitude of the place where you live for use in <ulink " -"url=\"http://www.debian.org/devel/developers.loc\">the world map of Debian " -"developers</ulink>, phone and fax numbers, IRC nickname and web page" +"longitude of the place where you live for use in <ulink url=\"&url-worldmap;" +"\">the world map of Debian developers</ulink>, phone and fax numbers, IRC " +"nickname and web page" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:420 +#: resources.dbk:425 msgid "password and preferred shell on Debian Project machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:425 +#: resources.dbk:430 msgid "" "Most of the information is not accessible to the public, naturally. For " "more information please read the online documentation that you can find at " -"<ulink url=\"http://db.debian.org/doc-general.html\"></ulink>." +"<ulink url=\"&url-debian-db-doc;\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:430 +#: resources.dbk:435 msgid "" "Developers can also submit their SSH keys to be used for authorization on " "the official Debian machines, and even add new *.debian.net DNS entries. " -"Those features are documented at <ulink " -"url=\"http://db.debian.org/doc-mail.html\"></ulink>." +"Those features are documented at <ulink url=\"&url-debian-db-mail-gw;\"></" +"ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:438 +#: resources.dbk:443 msgid "The Debian archive" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:440 +#: resources.dbk:445 msgid "" -"The Debian GNU/Linux distribution consists of a lot of packages " -"(<filename>.deb</filename>'s, currently around 9000) and a few additional " +"The &debian-formal; distribution consists of a lot of packages (<filename>." +"deb</filename>'s, currently around &number-of-pkgs;) and a few additional " "files (such as documentation and installation disk images)." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:445 +#: resources.dbk:451 msgid "Here is an example directory tree of a complete Debian archive:" msgstr "" -# type: Content of: <chapter><section><screen> -#: resources.dbk:448 -#, no-wrap -msgid "" -"/stable/main/\n" -"dists/stable/main/binary-i386/\n" -"dists/stable/main/binary-m68k/\n" -"dists/stable/main/binary-alpha/\n" -" ...\n" -"dists/stable/main/source/\n" -" ...\n" -"dists/stable/main/disks-i386/\n" -"dists/stable/main/disks-m68k/\n" -"dists/stable/main/disks-alpha/\n" -" ...\n" -"\n" -"dists/stable/contrib/\n" -"dists/stable/contrib/binary-i386/\n" -"dists/stable/contrib/binary-m68k/\n" -"dists/stable/contrib/binary-alpha/\n" -" ...\n" -"dists/stable/contrib/source/\n" -"\n" -"dists/stable/non-free/\n" -"dists/stable/non-free/binary-i386/\n" -"dists/stable/non-free/binary-m68k/\n" -"dists/stable/non-free/binary-alpha/\n" -" ...\n" -"dists/stable/non-free/source/\n" -"\n" -"dists/testing/\n" -"dists/testing/main/\n" -" ...\n" -"dists/testing/contrib/\n" -" ...\n" -"dists/testing/non-free/\n" -" ...\n" -"\n" -"dists/unstable\n" -"dists/unstable/main/\n" -" ...\n" -"dists/unstable/contrib/\n" -" ...\n" -"dists/unstable/non-free/\n" -" ...\n" -"\n" -"pool/\n" -"pool/main/a/\n" -"pool/main/a/apt/\n" -" ...\n" -"pool/main/b/\n" -"pool/main/b/bash/\n" -" ...\n" -"pool/main/liba/\n" -"pool/main/liba/libalias-perl/\n" -" ...\n" -"pool/main/m/\n" -"pool/main/m/mailx/\n" -" ...\n" -"pool/non-free/n/\n" -"pool/non-free/n/netscape/\n" -" ..." -msgstr "" - # type: Content of: <chapter><section><para> -#: resources.dbk:508 +#: resources.dbk:455 msgid "" "As you can see, the top-level directory contains two directories, " "<filename>dists/</filename> and <filename>pool/</filename>. The latter is a " "“pool” in which the packages actually are, and which is handled by the " "archive maintenance database and the accompanying programs. The former " -"contains the distributions, <emphasis>stable</emphasis>, " -"<emphasis>testing</emphasis> and <emphasis>unstable</emphasis>. The " -"<filename>Packages</filename> and <filename>Sources</filename> files in the " -"distribution subdirectories can reference files in the " -"<filename>pool/</filename> directory. The directory tree below each of the " -"distributions is arranged in an identical manner. What we describe below " -"for <emphasis>stable</emphasis> is equally applicable to the " -"<emphasis>unstable</emphasis> and <emphasis>testing</emphasis> " -"distributions." +"contains the distributions, <emphasis>stable</emphasis>, <emphasis>testing</" +"emphasis> and <emphasis>unstable</emphasis>. The <filename>Packages</" +"filename> and <filename>Sources</filename> files in the distribution " +"subdirectories can reference files in the <filename>pool/</filename> " +"directory. The directory tree below each of the distributions is arranged " +"in an identical manner. What we describe below for <emphasis>stable</" +"emphasis> is equally applicable to the <emphasis>unstable</emphasis> and " +"<emphasis>testing</emphasis> distributions." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:522 +#: resources.dbk:469 msgid "" "<filename>dists/stable</filename> contains three directories, namely " -"<filename>main</filename>, <filename>contrib</filename>, and " -"<filename>non-free</filename>." +"<filename>main</filename>, <filename>contrib</filename>, and <filename>non-" +"free</filename>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:527 +#: resources.dbk:474 msgid "" "In each of the areas, there is a directory for the source packages " "(<filename>source</filename>) and a directory for each supported " -"architecture (<filename>binary-i386</filename>, " -"<filename>binary-m68k</filename>, etc.)." +"architecture (<filename>binary-i386</filename>, <filename>binary-m68k</" +"filename>, etc.)." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:532 +#: resources.dbk:479 msgid "" "The <filename>main</filename> area contains additional directories which " "hold the disk images and some essential pieces of documentation required for " @@ -759,61 +677,59 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:538 +#: resources.dbk:485 msgid "Sections" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:540 +#: resources.dbk:487 msgid "" "The <emphasis>main</emphasis> section of the Debian archive is what makes up " -"the <emphasis role=\"strong\">official Debian GNU/Linux " -"distribution</emphasis>. The <emphasis>main</emphasis> section is official " -"because it fully complies with all our guidelines. The other two sections " -"do not, to different degrees; as such, they are <emphasis " -"role=\"strong\">not</emphasis> officially part of Debian GNU/Linux." +"the <emphasis role=\"strong\">official &debian-formal; distribution</" +"emphasis>. The <emphasis>main</emphasis> section is official because it " +"fully complies with all our guidelines. The other two sections do not, to " +"different degrees; as such, they are <emphasis role=\"strong\">not</" +"emphasis> officially part of &debian-formal;." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:548 +#: resources.dbk:495 msgid "" -"Every package in the main section must fully comply with the <ulink " -"url=\"http://www.debian.org/social_contract#guidelines\">Debian Free " -"Software Guidelines</ulink> (DFSG) and with all other policy requirements as " -"described in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>. The DFSG is our definition of “free software.” Check out " -"the Debian Policy Manual for details." +"Every package in the main section must fully comply with the <ulink url=" +"\"&url-dfsg;\">Debian Free Software Guidelines</ulink> (DFSG) and with all " +"other policy requirements as described in the <ulink url=\"&url-debian-" +"policy;\">Debian Policy Manual</ulink>. The DFSG is our definition of “free " +"software.” Check out the Debian Policy Manual for details." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:556 +#: resources.dbk:503 msgid "" "Packages in the <emphasis>contrib</emphasis> section have to comply with the " -"DFSG, but may fail other requirements. For instance, they may depend on " -"non-free packages." +"DFSG, but may fail other requirements. For instance, they may depend on non-" +"free packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:561 +#: resources.dbk:508 msgid "" -"Packages which do not conform to the DFSG are placed in the " -"<emphasis>non-free</emphasis> section. These packages are not considered as " -"part of the Debian distribution, though we support their use, and we provide " -"infrastructure (such as our bug-tracking system and mailing lists) for " -"non-free software packages." +"Packages which do not conform to the DFSG are placed in the <emphasis>non-" +"free</emphasis> section. These packages are not considered as part of the " +"Debian distribution, though we support their use, and we provide " +"infrastructure (such as our bug-tracking system and mailing lists) for non-" +"free software packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:568 +#: resources.dbk:515 msgid "" -"The <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> contains a more exact definition of the three sections. The " -"above discussion is just an introduction." +"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> contains " +"a more exact definition of the three sections. The above discussion is just " +"an introduction." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:573 +#: resources.dbk:520 msgid "" "The separation of the three sections at the top-level of the archive is " "important for all people who want to distribute Debian, either via FTP " @@ -824,7 +740,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:581 +#: resources.dbk:528 msgid "" "On the other hand, a CD-ROM vendor could easily check the individual package " "licenses of the packages in <emphasis>non-free</emphasis> and include as " @@ -833,24 +749,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:587 +#: resources.dbk:534 msgid "" "Note that the term section is also used to refer to categories which " "simplify the organization and browsing of available packages, e.g. " -"<emphasis>admin</emphasis>, <emphasis>net</emphasis>, " -"<emphasis>utils</emphasis> etc. Once upon a time, these sections " -"(subsections, rather) existed in the form of subdirectories within the " -"Debian archive. Nowadays, these exist only in the Section header fields of " -"packages." +"<emphasis>admin</emphasis>, <emphasis>net</emphasis>, <emphasis>utils</" +"emphasis> etc. Once upon a time, these sections (subsections, rather) " +"existed in the form of subdirectories within the Debian archive. Nowadays, " +"these exist only in the Section header fields of packages." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:597 +#: resources.dbk:544 msgid "Architectures" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:599 +#: resources.dbk:546 msgid "" "In the first days, the Linux kernel was only available for Intel i386 (or " "greater) platforms, and so was Debian. But as Linux became more and more " @@ -858,7 +773,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:604 +#: resources.dbk:551 msgid "" "The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola 680x0 " "(like Atari, Amiga and Macintoshes), MIPS, and PowerPC. The Linux 2.2 " @@ -867,59 +782,56 @@ msgid "" "Therefore, Debian has ports underway; in fact, we also have ports underway " "to non-Linux kernels. Aside from <emphasis>i386</emphasis> (our name for " "Intel x86), there is <emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, " -"<emphasis>powerpc</emphasis>, <emphasis>sparc</emphasis>, " -"<emphasis>hurd-i386</emphasis>, <emphasis>arm</emphasis>, " -"<emphasis>ia64</emphasis>, <emphasis>hppa</emphasis>, " -"<emphasis>s390</emphasis>, <emphasis>mips</emphasis>, " -"<emphasis>mipsel</emphasis> and <emphasis>sh</emphasis> as of this writing." +"<emphasis>powerpc</emphasis>, <emphasis>sparc</emphasis>, <emphasis>hurd-" +"i386</emphasis>, <emphasis>arm</emphasis>, <emphasis>ia64</emphasis>, " +"<emphasis>hppa</emphasis>, <emphasis>s390</emphasis>, <emphasis>mips</" +"emphasis>, <emphasis>mipsel</emphasis> and <emphasis>sh</emphasis> as of " +"this writing." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:618 +#: resources.dbk:565 msgid "" -"Debian GNU/Linux 1.3 is only available as <emphasis>i386</emphasis>. Debian " +"&debian-formal; 1.3 is only available as <emphasis>i386</emphasis>. Debian " "2.0 shipped for <emphasis>i386</emphasis> and <emphasis>m68k</emphasis> " "architectures. Debian 2.1 ships for the <emphasis>i386</emphasis>, " -"<emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, and " -"<emphasis>sparc</emphasis> architectures. Debian 2.2 added support for the " +"<emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, and <emphasis>sparc</" +"emphasis> architectures. Debian 2.2 added support for the " "<emphasis>powerpc</emphasis> and <emphasis>arm</emphasis> architectures. " -"Debian 3.0 added support of five new architectures: " -"<emphasis>ia64</emphasis>, <emphasis>hppa</emphasis>, " -"<emphasis>s390</emphasis>, <emphasis>mips</emphasis> and " -"<emphasis>mipsel</emphasis>." +"Debian 3.0 added support of five new architectures: <emphasis>ia64</" +"emphasis>, <emphasis>hppa</emphasis>, <emphasis>s390</emphasis>, " +"<emphasis>mips</emphasis> and <emphasis>mipsel</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:629 +#: resources.dbk:576 msgid "" "Information for developers and users about the specific ports are available " -"at the <ulink url=\"http://www.debian.org/ports/\">Debian Ports web " -"pages</ulink>." +"at the <ulink url=\"&url-debian-ports;\">Debian Ports web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:635 +#: resources.dbk:582 msgid "Packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:637 +#: resources.dbk:584 msgid "" "There are two types of Debian packages, namely <emphasis>source</emphasis> " "and <emphasis>binary</emphasis> packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:641 +#: resources.dbk:588 msgid "" -"Source packages consist of either two or three files: a " -"<filename>.dsc</filename> file, and either a <filename>.tar.gz</filename> " -"file or both an <filename>.orig.tar.gz</filename> and a " -"<filename>.diff.gz</filename> file." +"Source packages consist of either two or three files: a <filename>.dsc</" +"filename> file, and either a <filename>.tar.gz</filename> file or both an " +"<filename>.orig.tar.gz</filename> and a <filename>.diff.gz</filename> file." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:647 +#: resources.dbk:594 msgid "" "If a package is developed specially for Debian and is not distributed " "outside of Debian, there is just one <filename>.tar.gz</filename> file which " @@ -932,7 +844,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:657 +#: resources.dbk:604 msgid "" "The <filename>.dsc</filename> file lists all the files in the source package " "together with checksums (<command>md5sums</command>) and some additional " @@ -940,31 +852,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:664 +#: resources.dbk:611 msgid "Distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:666 +#: resources.dbk:613 msgid "" "The directory system described in the previous chapter is itself contained " "within <emphasis>distribution directories</emphasis>. Each distribution is " -"actually contained in the <filename>pool</filename> directory in the " -"top-level of the Debian archive itself." +"actually contained in the <filename>pool</filename> directory in the top-" +"level of the Debian archive itself." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:672 +#: resources.dbk:619 msgid "" "To summarize, the Debian archive has a root directory within an FTP server. " "For instance, at the mirror site, <literal>ftp.us.debian.org</literal>, the " -"Debian archive itself is contained in <ulink " -"url=\"ftp://ftp.us.debian.org/debian\">/debian</ulink>, which is a common " -"location (another is <filename>/pub/debian</filename>)." +"Debian archive itself is contained in <ulink url=\"ftp://ftp.us.debian.org/" +"debian\">/debian</ulink>, which is a common location (another is <filename>/" +"pub/debian</filename>)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:679 +#: resources.dbk:626 msgid "" "A distribution comprises Debian source and binary packages, and the " "respective <filename>Sources</filename> and <filename>Packages</filename> " @@ -975,23 +887,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:687 +#: resources.dbk:634 msgid "Stable, testing, and unstable" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:689 +#: resources.dbk:636 msgid "" "There are always distributions called <emphasis>stable</emphasis> (residing " "in <filename>dists/stable</filename>), <emphasis>testing</emphasis> " -"(residing in <filename>dists/testing</filename>), and " -"<emphasis>unstable</emphasis> (residing in " -"<filename>dists/unstable</filename>). This reflects the development process " -"of the Debian project." +"(residing in <filename>dists/testing</filename>), and <emphasis>unstable</" +"emphasis> (residing in <filename>dists/unstable</filename>). This reflects " +"the development process of the Debian project." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:696 +#: resources.dbk:643 msgid "" "Active development is done in the <emphasis>unstable</emphasis> distribution " "(that's why this distribution is sometimes called the <emphasis>development " @@ -1003,7 +914,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:705 +#: resources.dbk:652 msgid "" "The <link linkend=\"testing\">testing</link> distribution is generated " "automatically by taking packages from unstable if they satisfy certain " @@ -1013,7 +924,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:712 +#: resources.dbk:659 msgid "" "After a period of development, once the release manager deems fit, the " "<emphasis>testing</emphasis> distribution is frozen, meaning that the " @@ -1029,32 +940,32 @@ msgid "" "<emphasis>stable</emphasis>, and a new copy is created for the new " "<emphasis>testing</emphasis>, and the previous <emphasis>stable</emphasis> " "is renamed to <emphasis>oldstable</emphasis> and stays there until it is " -"finally archived. On archiving, the contents are moved to " -"<literal>archive.debian.org</literal>)." +"finally archived. On archiving, the contents are moved to <literal>&archive-" +"host;</literal>)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:729 +#: resources.dbk:676 msgid "" "This development cycle is based on the assumption that the " -"<emphasis>unstable</emphasis> distribution becomes " -"<emphasis>stable</emphasis> after passing a period of being in " -"<emphasis>testing</emphasis>. Even once a distribution is considered " -"stable, a few bugs inevitably remain — that's why the stable distribution is " -"updated every now and then. However, these updates are tested very " -"carefully and have to be introduced into the archive individually to reduce " -"the risk of introducing new bugs. You can find proposed additions to " -"<emphasis>stable</emphasis> in the <filename>proposed-updates</filename> " -"directory. Those packages in <filename>proposed-updates</filename> that " -"pass muster are periodically moved as a batch into the stable distribution " -"and the revision level of the stable distribution is incremented (e.g., " -"‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ becomes ‘2.2r5’, and so forth). Please refer " -"to <link linkend=\"upload-stable\">uploads to the " -"<emphasis>stable</emphasis> distribution</link> for details." +"<emphasis>unstable</emphasis> distribution becomes <emphasis>stable</" +"emphasis> after passing a period of being in <emphasis>testing</emphasis>. " +"Even once a distribution is considered stable, a few bugs inevitably remain " +"— that's why the stable distribution is updated every now and then. " +"However, these updates are tested very carefully and have to be introduced " +"into the archive individually to reduce the risk of introducing new bugs. " +"You can find proposed additions to <emphasis>stable</emphasis> in the " +"<filename>proposed-updates</filename> directory. Those packages in " +"<filename>proposed-updates</filename> that pass muster are periodically " +"moved as a batch into the stable distribution and the revision level of the " +"stable distribution is incremented (e.g., ‘3.0’ becomes ‘3.0r1’, ‘2.2r4’ " +"becomes ‘2.2r5’, and so forth). Please refer to <link linkend=\"upload-" +"stable\">uploads to the <emphasis>stable</emphasis> distribution</link> for " +"details." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:746 +#: resources.dbk:693 msgid "" "Note that development under <emphasis>unstable</emphasis> continues during " "the freeze period, since the <emphasis>unstable</emphasis> distribution " @@ -1062,31 +973,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:753 +#: resources.dbk:700 msgid "More information about the testing distribution" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:755 +#: resources.dbk:702 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:759 +#: resources.dbk:706 msgid "" "For more details, please see the <link linkend=\"testing\">information about " "the testing distribution</link>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:765 +#: resources.dbk:712 msgid "Experimental" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:767 +#: resources.dbk:714 msgid "" "The <emphasis>experimental</emphasis> distribution is a special " "distribution. It is not a full distribution in the same sense as `stable' " @@ -1101,25 +1012,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:778 +#: resources.dbk:725 msgid "" "These are the <citerefentry> <refentrytitle>sources.list</refentrytitle> " -"<manvolnum>5</manvolnum> </citerefentry> lines for " -"<emphasis>experimental</emphasis>:" +"<manvolnum>5</manvolnum> </citerefentry> lines for <emphasis>experimental</" +"emphasis>:" msgstr "" -# type: Content of: <chapter><section><section><section><screen> -#: resources.dbk:783 +# type: Content of: <chapter><section><section><section><programlisting> +#: resources.dbk:730 #, no-wrap msgid "" -"http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental " -"main\n" -"deb-src http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ " -"experimental main" +"deb http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental main\n" +"deb-src http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental main" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:787 +#: resources.dbk:734 msgid "" "If there is a chance that the software could do grave damage to a system, it " "is likely to be better to put it into <emphasis>experimental</emphasis>. " @@ -1128,7 +1037,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:793 +#: resources.dbk:740 msgid "" "Whenever there is a new upstream version of a package that introduces new " "features but breaks a lot of old ones, it should either not be uploaded, or " @@ -1141,7 +1050,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:803 +#: resources.dbk:750 msgid "" "Some experimental software can still go into <emphasis>unstable</emphasis>, " "with a few warnings in the description, but that isn't recommended because " @@ -1149,67 +1058,67 @@ msgid "" "<emphasis>testing</emphasis> and thus to <emphasis>stable</emphasis>. You " "should not be afraid to use <emphasis>experimental</emphasis> since it does " "not cause any pain to the ftpmasters, the experimental packages are " -"automatically removed once you upload the package in " -"<emphasis>unstable</emphasis> with a higher version number." +"automatically removed once you upload the package in <emphasis>unstable</" +"emphasis> with a higher version number." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:813 +#: resources.dbk:760 msgid "" "New software which isn't likely to damage your system can go directly into " "<emphasis>unstable</emphasis>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:817 +#: resources.dbk:764 msgid "" "An alternative to <emphasis>experimental</emphasis> is to use your personal " "web space on <literal>people.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:821 +#: resources.dbk:768 msgid "" "When uploading to unstable a package which had bugs fixed in experimental, " -"please consider using the option <literal>-v</literal> to " -"<command>dpkg-buildpackage</command> to finally get them closed." +"please consider using the option <literal>-v</literal> to <command>dpkg-" +"buildpackage</command> to finally get them closed." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:830 +#: resources.dbk:777 msgid "Release code names" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:832 +#: resources.dbk:779 msgid "" "Every released Debian distribution has a <emphasis>code name</emphasis>: " "Debian 1.1 is called `buzz'; Debian 1.2, `rex'; Debian 1.3, `bo'; Debian " "2.0, `hamm'; Debian 2.1, `slink'; Debian 2.2, `potato'; Debian 3.0, `woody'; " -"Debian 3.1, sarge; Debian 4.0, etch. There is also a " -"``pseudo-distribution'', called `sid', which is the current `unstable' " -"distribution; since packages are moved from `unstable' to `testing' as they " -"approach stability, `sid' itself is never released. As well as the usual " -"contents of a Debian distribution, `sid' contains packages for architectures " -"which are not yet officially supported or released by Debian. These " -"architectures are planned to be integrated into the mainstream distribution " -"at some future date." +"Debian 3.1, sarge; Debian 4.0, etch. There is also a ``pseudo-" +"distribution'', called `sid', which is the current `unstable' distribution; " +"since packages are moved from `unstable' to `testing' as they approach " +"stability, `sid' itself is never released. As well as the usual contents of " +"a Debian distribution, `sid' contains packages for architectures which are " +"not yet officially supported or released by Debian. These architectures are " +"planned to be integrated into the mainstream distribution at some future " +"date." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:844 +#: resources.dbk:791 msgid "" "Since Debian has an open development model (i.e., everyone can participate " "and follow the development) even the `unstable' and `testing' distributions " "are distributed to the Internet through the Debian FTP and HTTP server " "network. Thus, if we had called the directory which contains the release " "candidate version `testing', then we would have to rename it to `stable' " -"when the version is released, which would cause all FTP mirrors to " -"re-retrieve the whole distribution (which is quite large)." +"when the version is released, which would cause all FTP mirrors to re-" +"retrieve the whole distribution (which is quite large)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:853 +#: resources.dbk:800 msgid "" "On the other hand, if we called the distribution directories " "<emphasis>Debian-x.y</emphasis> from the beginning, people would think that " @@ -1220,7 +1129,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:861 +#: resources.dbk:808 msgid "" "Thus, the names of the distribution directories in the archive are " "determined by their code names and not their release status (e.g., " @@ -1233,12 +1142,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:875 +#: resources.dbk:822 msgid "Debian mirrors" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:877 +#: resources.dbk:824 msgid "" "The various download archives and the web site have several mirrors " "available in order to relieve our canonical servers from heavy load. In " @@ -1252,17 +1161,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:888 +#: resources.dbk:835 msgid "" "All the information on Debian mirrors, including a list of the available " -"public FTP/HTTP servers, can be found at <ulink " -"url=\"http://www.debian.org/mirror/\"></ulink>. This useful page also " -"includes information and tools which can be helpful if you are interested in " -"setting up your own mirror, either for internal or public access." +"public FTP/HTTP servers, can be found at <ulink url=\"&url-debian-mirrors;" +"\"></ulink>. This useful page also includes information and tools which can " +"be helpful if you are interested in setting up your own mirror, either for " +"internal or public access." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:895 +#: resources.dbk:842 msgid "" "Note that mirrors are generally run by third-parties who are interested in " "helping Debian. As such, developers generally do not have accounts on these " @@ -1270,154 +1179,147 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:902 +#: resources.dbk:849 msgid "The Incoming system" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:904 +#: resources.dbk:851 msgid "" "The Incoming system is responsible for collecting updated packages and " "installing them in the Debian archive. It consists of a set of directories " -"and scripts that are installed on <literal>ftp-master.debian.org</literal>." +"and scripts that are installed on <literal>&ftp-master-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:909 +#: resources.dbk:856 msgid "" "Packages are uploaded by all the maintainers into a directory called " "<filename>UploadQueue</filename>. This directory is scanned every few " -"minutes by a daemon called <command>queued</command>, " -"<filename>*.command</filename>-files are executed, and remaining and " -"correctly signed <filename>*.changes</filename>-files are moved together " -"with their corresponding files to the <filename>unchecked</filename> " -"directory. This directory is not visible for most Developers, as ftp-master " -"is restricted; it is scanned every 15 minutes by the " -"<command>katie</command> script, which verifies the integrity of the " -"uploaded packages and their cryptographic signatures. If the package is " -"considered ready to be installed, it is moved into the " +"minutes by a daemon called <command>queued</command>, <filename>*.command</" +"filename>-files are executed, and remaining and correctly signed <filename>*." +"changes</filename>-files are moved together with their corresponding files " +"to the <filename>unchecked</filename> directory. This directory is not " +"visible for most Developers, as ftp-master is restricted; it is scanned " +"every 15 minutes by the <command>katie</command> script, which verifies the " +"integrity of the uploaded packages and their cryptographic signatures. If " +"the package is considered ready to be installed, it is moved into the " "<filename>accepted</filename> directory. If this is the first upload of the " -"package (or it has new binary packages), it is moved to the " -"<filename>new</filename> directory, where it waits for approval by the " -"ftpmasters. If the package contains files to be installed by hand it is " -"moved to the <filename>byhand</filename> directory, where it waits for " -"manual installation by the ftpmasters. Otherwise, if any error has been " -"detected, the package is refused and is moved to the " -"<filename>reject</filename> directory." +"package (or it has new binary packages), it is moved to the <filename>new</" +"filename> directory, where it waits for approval by the ftpmasters. If the " +"package contains files to be installed by hand it is moved to the " +"<filename>byhand</filename> directory, where it waits for manual " +"installation by the ftpmasters. Otherwise, if any error has been detected, " +"the package is refused and is moved to the <filename>reject</filename> " +"directory." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:928 +#: resources.dbk:875 msgid "" "Once the package is accepted, the system sends a confirmation mail to the " "maintainer and closes all the bugs marked as fixed by the upload, and the " "auto-builders may start recompiling it. The package is now publicly " -"accessible at <ulink url=\"http://incoming.debian.org/\"></ulink> until it " -"is really installed in the Debian archive. This happens only once a day " -"(and is also called the `dinstall run' for historical reasons); the package " -"is then removed from incoming and installed in the pool along with all the " -"other packages. Once all the other updates (generating new " -"<filename>Packages</filename> and <filename>Sources</filename> index files " -"for example) have been made, a special script is called to ask all the " -"primary mirrors to update themselves." +"accessible at <ulink url=\"&url-incoming;\"></ulink> until it is really " +"installed in the Debian archive. This happens only once a day (and is also " +"called the `dinstall run' for historical reasons); the package is then " +"removed from incoming and installed in the pool along with all the other " +"packages. Once all the other updates (generating new <filename>Packages</" +"filename> and <filename>Sources</filename> index files for example) have " +"been made, a special script is called to ask all the primary mirrors to " +"update themselves." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:940 +#: resources.dbk:887 msgid "" "The archive maintenance software will also send the OpenPGP/GnuPG signed " "<filename>.changes</filename> file that you uploaded to the appropriate " -"mailing lists. If a package is released with the " -"<literal>Distribution:</literal> set to `stable', the announcement is sent " -"to <email>debian-changes@lists.debian.org</email>. If a package is released " -"with <literal>Distribution:</literal> set to `unstable' or `experimental', " -"the announcement will be posted to " -"<email>debian-devel-changes@lists.debian.org</email> instead." +"mailing lists. If a package is released with the <literal>Distribution:</" +"literal> set to `stable', the announcement is sent to &email-debian-" +"changes;. If a package is released with <literal>Distribution:</literal> " +"set to `unstable' or `experimental', the announcement will be posted to " +"&email-debian-devel-changes; instead." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:950 +#: resources.dbk:897 msgid "" "Though ftp-master is restricted, a copy of the installation is available to " -"all developers on <literal>merkel.debian.org</literal>." +"all developers on <literal>&ftp-master-mirror;</literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:956 +#: resources.dbk:960 msgid "Package information" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:958 +#: resources.dbk:962 msgid "On the web" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:960 +#: resources.dbk:964 msgid "" -"Each package has several dedicated web pages. " -"<literal>http://packages.debian.org/<replaceable>package-name</replaceable></literal> " -"displays each version of the package available in the various " -"distributions. Each version links to a page which provides information, " -"including the package description, the dependencies, and package download " -"links." +"Each package has several dedicated web pages. <literal>http://&packages-" +"host;/<replaceable>package-name</replaceable></literal> displays each " +"version of the package available in the various distributions. Each version " +"links to a page which provides information, including the package " +"description, the dependencies, and package download links." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:967 +#: resources.dbk:971 msgid "" "The bug tracking system tracks bugs for each package. You can view the bugs " -"of a given package at the URL " -"<literal>http://bugs.debian.org/<replaceable>package-name</replaceable></literal>." +"of a given package at the URL <literal>http://&bugs-host;/" +"<replaceable>package-name</replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:974 +#: resources.dbk:978 msgid "The <command>madison</command> utility" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:976 +#: resources.dbk:980 msgid "" "<command>madison</command> is a command-line utility that is available on " -"<literal>ftp-master.debian.org</literal>, and on the mirror on " -"<literal>merkel.debian.org</literal>. It uses a single argument " -"corresponding to a package name. In result it displays which version of the " -"package is available for each architecture and distribution combination. An " -"example will explain it better." +"<literal>&ftp-master-host;</literal>, and on the mirror on <literal>&ftp-" +"master-mirror;</literal>. It uses a single argument corresponding to a " +"package name. In result it displays which version of the package is " +"available for each architecture and distribution combination. An example " +"will explain it better." msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:984 +#: resources.dbk:988 #, no-wrap msgid "" "$ madison libdbd-mysql-perl\n" -"libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, " -"m68k, powerpc, sparc\n" -"libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, " -"ia64, m68k, mips, mipsel, powerpc, s390, sparc\n" +"libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, m68k, powerpc, sparc\n" +"libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc\n" "libdbd-mysql-perl | 1.2216-2.0.1 | testing | alpha\n" -"libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, " -"i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc" +"libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:991 +#: resources.dbk:995 msgid "" -"In this example, you can see that the version in " -"<emphasis>unstable</emphasis> differs from the version in " -"<emphasis>testing</emphasis> and that there has been a binary-only NMU of " -"the package for the alpha architecture. Each version of the package has " -"been recompiled on most of the architectures." +"In this example, you can see that the version in <emphasis>unstable</" +"emphasis> differs from the version in <emphasis>testing</emphasis> and that " +"there has been a binary-only NMU of the package for the alpha architecture. " +"Each version of the package has been recompiled on most of the architectures." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1001 +#: resources.dbk:1005 msgid "The Package Tracking System" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1003 +#: resources.dbk:1007 msgid "" "The Package Tracking System (PTS) is an email-based tool to track the " "activity of a source package. This really means that you can get the same " @@ -1426,67 +1328,67 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1008 +#: resources.dbk:1012 msgid "" "Each email sent through the PTS is classified under one of the keywords " "listed below. This will let you select the mails that you want to receive." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1012 +#: resources.dbk:1016 msgid "By default you will get:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1019 +#: resources.dbk:1023 msgid "All the bug reports and following discussions." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1027 +#: resources.dbk:1031 msgid "" -"The email notifications from <email>control@bugs.debian.org</email> about " -"bug report status changes." +"The email notifications from <email>control@&bugs-host;</email> about bug " +"report status changes." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1036 +#: resources.dbk:1040 msgid "" "The email notification from <command>katie</command> when an uploaded source " "package is accepted." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1045 +#: resources.dbk:1049 msgid "" "Other warning and error emails from <command>katie</command> (such as an " "override disparity for the section and/or the priority field)." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1054 +#: resources.dbk:1058 msgid "" "Any non-automatic email sent to the PTS by people who wanted to contact the " "subscribers of the package. This can be done by sending mail to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " -"In order to prevent spam, all messages sent to these addresses must contain " -"the <literal>X-PTS-Approved</literal> header with a non-empty value." +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. In " +"order to prevent spam, all messages sent to these addresses must contain the " +"<literal>X-PTS-Approved</literal> header with a non-empty value." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1066 +#: resources.dbk:1070 msgid "" "Regular summary emails about the package's status. Currently, only " "progression in <emphasis>testing</emphasis> is sent." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1073 +#: resources.dbk:1077 msgid "You can also decide to receive additional information:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1080 +#: resources.dbk:1084 msgid "" "The email notification from <command>katie</command> when an uploaded binary " "package is accepted. In other words, whenever a build daemon or a porter " @@ -1495,51 +1397,51 @@ msgid "" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1091 +#: resources.dbk:1095 msgid "" "CVS commit notifications, if the package has a CVS repository and the " "maintainer has set up forwarding commit notifications to the PTS." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1100 +#: resources.dbk:1104 msgid "" "Translations of descriptions or debconf templates submitted to the Debian " "Description Translation Project." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1109 +#: resources.dbk:1113 msgid "" "Information about changes made to the package in derivative distributions " "(for example Ubuntu)." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1116 +#: resources.dbk:1120 msgid "The PTS email interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1118 +#: resources.dbk:1122 msgid "" "You can control your subscription(s) to the PTS by sending various commands " "to <email>pts@qa.debian.org</email>." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1126 +#: resources.dbk:1130 msgid "" "Subscribes <replaceable>email</replaceable> to communications related to the " "source package <replaceable>sourcepackage</replaceable>. Sender address is " -"used if the second argument is not present. If " -"<replaceable>sourcepackage</replaceable> is not a valid source package, " -"you'll get a warning. However if it's a valid binary package, the PTS will " -"subscribe you to the corresponding source package." +"used if the second argument is not present. If <replaceable>sourcepackage</" +"replaceable> is not a valid source package, you'll get a warning. However " +"if it's a valid binary package, the PTS will subscribe you to the " +"corresponding source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1139 +#: resources.dbk:1143 msgid "" "Removes a previous subscription to the source package " "<replaceable>sourcepackage</replaceable> using the specified email address " @@ -1547,21 +1449,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1149 +#: resources.dbk:1153 msgid "" "Removes all subscriptions of the specified email address or the sender " "address if the second argument is left out." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1158 +#: resources.dbk:1162 msgid "" "Lists all subscriptions for the sender or the email address optionally " "specified." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1167 +#: resources.dbk:1171 msgid "" "Tells you the keywords that you are accepting. For an explanation of " "keywords, <link linkend=\"pkg-tracking-system\">see above</link>. Here's a " @@ -1569,78 +1471,79 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1174 -msgid "<literal>bts</literal>: mails coming from the Debian Bug Tracking System" +#: resources.dbk:1178 +msgid "" +"<literal>bts</literal>: mails coming from the Debian Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1179 +#: resources.dbk:1183 msgid "" -"<literal>bts-control</literal>: reply to mails sent to " -"<email>control@bugs.debian.org</email>" +"<literal>bts-control</literal>: reply to mails sent to &email-bts-control;" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1185 +#: resources.dbk:1189 msgid "" "<literal>summary</literal>: automatic summary mails about the state of a " "package" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1191 +#: resources.dbk:1195 msgid "<literal>cvs</literal>: notification of CVS commits" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1196 -msgid "<literal>ddtp</literal>: translations of descriptions and debconf templates" +#: resources.dbk:1200 +msgid "" +"<literal>ddtp</literal>: translations of descriptions and debconf templates" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1201 +#: resources.dbk:1205 msgid "" "<literal>derivatives</literal>: changes made on the package by derivative " "distributions" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1207 +#: resources.dbk:1211 msgid "" "<literal>upload-source</literal>: announce of a new source upload that has " "been accepted" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1213 +#: resources.dbk:1217 msgid "" "<literal>upload-binary</literal>: announce of a new binary-only upload " "(porting)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1219 +#: resources.dbk:1223 msgid "" "<literal>katie-other</literal>: other mails from ftpmasters (override " "disparity, etc.)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1225 +#: resources.dbk:1229 msgid "" "<literal>default</literal>: all the other mails (those which aren't " "automatic)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1235 +#: resources.dbk:1239 msgid "" "Same as the previous item but for the given source package, since you may " "select a different set of keywords for each source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1244 +#: resources.dbk:1248 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the default set of " @@ -1648,7 +1551,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1254 +#: resources.dbk:1258 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the set of accepted " @@ -1656,19 +1559,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1264 +#: resources.dbk:1268 msgid "" "Same as previous item but overrides the keywords list for the indicated " "source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1273 +#: resources.dbk:1277 msgid "Stops processing commands. All following lines are ignored by the bot." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1279 +#: resources.dbk:1283 msgid "" "The <command>pts-subscribe</command> command-line utility (from the " "<systemitem role=\"package\">devscripts</systemitem> package) can be handy " @@ -1677,45 +1580,45 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1287 +#: resources.dbk:1291 msgid "Filtering PTS mails" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1289 +#: resources.dbk:1293 msgid "" "Once you are subscribed to a package, you will get the mails sent to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. " "Those mails have special headers appended to let you filter them in a " "special mailbox (e.g. with <command>procmail</command>). The added headers " -"are <literal>X-Loop</literal>, <literal>X-PTS-Package</literal>, " -"<literal>X-PTS-Keyword</literal> and <literal>X-Unsubscribe</literal>." +"are <literal>X-Loop</literal>, <literal>X-PTS-Package</literal>, <literal>X-" +"PTS-Keyword</literal> and <literal>X-Unsubscribe</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1297 +#: resources.dbk:1301 msgid "" "Here is an example of added headers for a source upload notification on the " "<systemitem role=\"package\">dpkg</systemitem> package:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1301 +#: resources.dbk:1305 #, no-wrap msgid "" -"-Loop: dpkg@packages.qa.debian.org\n" +"X-Loop: dpkg@&pts-host;\n" "X-PTS-Package: dpkg\n" "X-PTS-Keyword: upload-source\n" "X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1309 +#: resources.dbk:1313 msgid "Forwarding CVS commits in the PTS" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1311 +#: resources.dbk:1315 msgid "" "If you use a publicly accessible CVS repository for maintaining your Debian " "package, you may want to forward the commit notification to the PTS so that " @@ -1724,43 +1627,43 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1317 +#: resources.dbk:1321 msgid "" "Once you set up the CVS repository to generate commit notifications, you " "just have to make sure it sends a copy of those mails to " -"<literal><replaceable>sourcepackage</replaceable>_cvs@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>_cvs@&pts-host;</literal>. " "Only the people who accept the <emphasis>cvs</emphasis> keyword will receive " "these notifications." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1326 +#: resources.dbk:1330 msgid "The PTS web interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1328 +#: resources.dbk:1332 msgid "" -"The PTS has a web interface at <ulink " -"url=\"http://packages.qa.debian.org/\"></ulink> that puts together a lot of " -"information about each source package. It features many useful links (BTS, " -"QA stats, contact information, DDTP translation status, buildd logs) and " -"gathers much more information from various places (30 latest changelog " -"entries, testing status, ...). It's a very useful tool if you want to know " -"what's going on with a specific source package. Furthermore there's a form " -"that allows easy subscription to the PTS via email." +"The PTS has a web interface at <ulink url=\"http://&pts-host;/\"></ulink> " +"that puts together a lot of information about each source package. It " +"features many useful links (BTS, QA stats, contact information, DDTP " +"translation status, buildd logs) and gathers much more information from " +"various places (30 latest changelog entries, testing status, ...). It's a " +"very useful tool if you want to know what's going on with a specific source " +"package. Furthermore there's a form that allows easy subscription to the " +"PTS via email." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1338 +#: resources.dbk:1342 msgid "" "You can jump directly to the web page concerning a specific source package " -"with a URL like " -"<literal>http://packages.qa.debian.org/<replaceable>sourcepackage</replaceable></literal>." +"with a URL like <literal>http://&pts-host;/<replaceable>sourcepackage</" +"replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1343 +#: resources.dbk:1347 msgid "" "This web interface has been designed like a portal for the development of " "packages: you can add custom content on your packages' pages. You can add " @@ -1769,95 +1672,96 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1349 +#: resources.dbk:1353 msgid "Static news items can be used to indicate:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1354 +#: resources.dbk:1358 msgid "" -"the availability of a project hosted on <link " -"linkend=\"alioth\">Alioth</link> for co-maintaining the package" +"the availability of a project hosted on <link linkend=\"alioth\">Alioth</" +"link> for co-maintaining the package" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1360 +#: resources.dbk:1364 msgid "a link to the upstream web site" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1365 +#: resources.dbk:1369 msgid "a link to the upstream bug tracker" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1370 +#: resources.dbk:1374 msgid "the existence of an IRC channel dedicated to the software" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1375 +#: resources.dbk:1379 msgid "" "any other available resource that could be useful in the maintenance of the " "package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1381 +#: resources.dbk:1385 msgid "Usual news items may be used to announce that:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1386 +#: resources.dbk:1390 msgid "beta packages are available for testing" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1391 +#: resources.dbk:1395 msgid "final packages are expected for next week" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1396 +#: resources.dbk:1400 msgid "the packaging is about to be redone from scratch" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1401 +#: resources.dbk:1405 msgid "backports are available" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1406 -msgid "the maintainer is on vacation (if they wish to publish this information)" +#: resources.dbk:1410 +msgid "" +"the maintainer is on vacation (if they wish to publish this information)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1411 +#: resources.dbk:1415 msgid "a NMU is being worked on" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1416 +#: resources.dbk:1420 msgid "something important will affect the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1421 +#: resources.dbk:1425 msgid "" "Both kinds of news are generated in a similar manner: you just have to send " "an email either to <email>pts-static-news@qa.debian.org</email> or to " "<email>pts-news@qa.debian.org</email>. The mail should indicate which " "package is concerned by having the name of the source package in a " -"<literal>X-PTS-Package</literal> mail header or in a " -"<literal>Package</literal> pseudo-header (like the BTS reports). If a URL " -"is available in the <literal>X-PTS-Url</literal> mail header or in the " -"<literal>Url</literal> pseudo-header, then the result is a link to that URL " -"instead of a complete news item." +"<literal>X-PTS-Package</literal> mail header or in a <literal>Package</" +"literal> pseudo-header (like the BTS reports). If a URL is available in the " +"<literal>X-PTS-Url</literal> mail header or in the <literal>Url</literal> " +"pseudo-header, then the result is a link to that URL instead of a complete " +"news item." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1432 +#: resources.dbk:1436 msgid "" "Here are a few examples of valid mails used to generate news items in the " "PTS. The first one adds a link to the cvsweb interface of debian-cd in the " @@ -1865,19 +1769,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1437 +#: resources.dbk:1441 #, no-wrap msgid "" -": Raphael Hertzog <hertzog@debian.org>\n" +"From: Raphael Hertzog <hertzog@debian.org>\n" "To: pts-static-news@qa.debian.org\n" "Subject: Browse debian-cd CVS repository with cvsweb\n" "\n" "Package: debian-cd\n" -"Url: http://cvs.debian.org/debian-cd/" +"Url: &url-cvsweb;debian-cd/" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1445 +#: resources.dbk:1449 msgid "" "The second one is an announcement sent to a mailing list which is also sent " "to the PTS so that it is published on the PTS web page of the package. Note " @@ -1885,25 +1789,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1450 +#: resources.dbk:1454 #, no-wrap msgid "" ": Raphael Hertzog <hertzog@debian.org>\n" -"To: debian-gtk-gnome@lists.debian.org\n" +"To: debian-gtk-gnome@&lists-host;\n" "Bcc: pts-news@qa.debian.org\n" "Subject: Galeon 2.0 backported for woody\n" "X-PTS-Package: galeon\n" "\n" "Hello gnomers!\n" "\n" -"I'm glad to announce that galeon has been backported for woody. You'll " -"find\n" +"I'm glad to announce that galeon has been backported for woody. You'll find\n" "everything here:\n" "..." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1463 +#: resources.dbk:1467 msgid "" "Think twice before adding a news item to the PTS because you won't be able " "to remove it later and you won't be able to edit it either. The only thing " @@ -1912,24 +1815,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1473 +#: resources.dbk:1477 msgid "Developer's packages overview" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1475 +#: resources.dbk:1479 msgid "" -"A QA (quality assurance) web portal is available at <ulink " -"url=\"http://qa.debian.org/developer.php\"></ulink> which displays a table " -"listing all the packages of a single developer (including those where the " -"party is listed as a co-maintainer). The table gives a good summary about " -"the developer's packages: number of bugs by severity, list of available " -"versions in each distribution, testing status and much more including links " -"to any other useful information." +"A QA (quality assurance) web portal is available at <ulink url=\"&url-ddpo;" +"\"></ulink> which displays a table listing all the packages of a single " +"developer (including those where the party is listed as a co-maintainer). " +"The table gives a good summary about the developer's packages: number of " +"bugs by severity, list of available versions in each distribution, testing " +"status and much more including links to any other useful information." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1484 +#: resources.dbk:1488 msgid "" "It is a good idea to look up your own data regularly so that you don't " "forget any open bugs, and so that you don't forget which packages are your " @@ -1937,12 +1839,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1491 +#: resources.dbk:1495 msgid "Debian *Forge: Alioth" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1493 +#: resources.dbk:1497 msgid "" "Alioth is a fairly new Debian service, based on a slightly modified version " "of the GForge software (which evolved from SourceForge). This software " @@ -1952,7 +1854,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1500 +#: resources.dbk:1504 msgid "" "It is intended to provide facilities to free software projects backed or led " "by Debian, facilitate contributions from external developers to projects " @@ -1961,7 +1863,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1506 +#: resources.dbk:1510 msgid "" "All Debian developers automatically have an account on Alioth. They can " "activate it by using the recover password facility. External developers can " @@ -1969,27 +1871,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1511 -msgid "" -"For more information please visit <ulink " -"url=\"http://alioth.debian.org/\"></ulink>." +#: resources.dbk:1515 +msgid "For more information please visit <ulink url=\"&url-alioth;\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1517 +#: resources.dbk:1521 msgid "Goodies for Developers" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1519 +#: resources.dbk:1523 msgid "LWN Subscriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1521 +#: resources.dbk:1525 msgid "" "Since October of 2002, HP has sponsored a subscription to LWN for all " "interested Debian developers. Details on how to get access to this benefit " -"are in <ulink " -"url=\"http://lists.debian.org/debian-devel-announce/2002/10/msg00018.html\"></ulink>." +"are in <ulink url=\"http://&lists-host;/debian-devel-announce/2002/10/" +"msg00018.html\"></ulink>." msgstr "" diff --git a/po4a/ja/scope.po b/po4a/ja/scope.po index 2154e96..5660821 100644 --- a/po4a/ja/scope.po +++ b/po4a/ja/scope.po @@ -1,72 +1,95 @@ # SOME DESCRIPTIVE TITLE -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# Copyright (C) 2007 Free Software Foundation, Inc. +# <>, 2007. +# , fuzzy +# # -#, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:12+0000\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" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2007-07-01 21:18+0000\n" +"PO-Revision-Date: 2007-07-01 23:36+0000\n" +"Last-Translator: <>\n" +"Language-Team: \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: " # type: Content of: <chapter><title> -#: scope.dbk:5 +#: scope.dbk:7 msgid "Scope of This Document" -msgstr "" +msgstr "この文書が扱う領域" # type: Content of: <chapter><para> -#: scope.dbk:7 +#: scope.dbk:9 msgid "" "The purpose of this document is to provide an overview of the recommended " "procedures and the available resources for Debian developers." -msgstr "" +msgstr "この文書の目的は、Debian 開発者に推奨される手続きと利用可能なリソースとに" +"関する概観を提供することにあります。" # type: Content of: <chapter><para> -#: scope.dbk:11 +#: scope.dbk:14 msgid "" "The procedures discussed within include how to become a maintainer (<xref " -"linkend=\"new-maintainer\"/> ); how to create new packages (<xref " -"linkend=\"newpackage\"/> ) and how to upload packages (<xref " -"linkend=\"upload\"/> ); how to handle bug reports (<xref " -"linkend=\"bug-handling\"/> ); how to move, remove, or orphan packages (<xref " -"linkend=\"archive-manip\"/> ); how to port packages (<xref " -"linkend=\"porting\"/> ); and how and when to do interim releases of other " -"maintainers' packages (<xref linkend=\"nmu\"/> )." -msgstr "" +"linkend=\"new-maintainer\"/> ); how to create new packages (<xref linkend=" +"\"newpackage\"/> ) and how to upload packages (<xref linkend=\"upload\"/> ); " +"how to handle bug reports (<xref linkend=\"bug-handling\"/> ); how to move, " +"remove, or orphan packages (<xref linkend=\"archive-manip\"/> ); how to port " +"packages (<xref linkend=\"porting\"/> ); and how and when to do interim " +"releases of other maintainers' packages (<xref linkend=\"nmu\"/> )." +msgstr "こちらで扱う諸手続きは、" +"開発者になる方法 (<xref linkend=\"new-maintainer\"/>) や、" +"新たなパッケージをアップロードする方法 (<xref linkend=\"upload\"/>)、" +"他の開発者によるパッケージを移植したり臨時リリースするには" +"いつどのようにしたらよいのか (<xref linkend=\"nmu\"/>)、" +"パッケージを移動、削除、みなしご化 (orphan) する方法 (<xref linkend=\"archive-manip\"/>)、バグ報告の扱い方 (<xref linkend=\"bug-handling\"/>)" +"にわたります。" # type: Content of: <chapter><para> -#: scope.dbk:20 +#: scope.dbk:23 msgid "" "The resources discussed in this reference include the mailing lists (<xref " -"linkend=\"mailing-lists\"/> ) and servers (<xref " -"linkend=\"server-machines\"/> ); a discussion of the structure of the Debian " -"archive (<xref linkend=\"archive\"/> ); explanation of the different servers " -"which accept package uploads (<xref linkend=\"upload-ftp-master\"/> ); and a " -"discussion of resources which can help maintainers with the quality of their " -"packages (<xref linkend=\"tools\"/> )." -msgstr "" +"linkend=\"mailing-lists\"/> ) and servers (<xref linkend=\"server-machines\"/" +"> ); a discussion of the structure of the Debian archive (<xref linkend=" +"\"archive\"/> ); explanation of the different servers which accept package " +"uploads (<xref linkend=\"upload-ftp-master\"/> ); and a discussion of " +"resources which can help maintainers with the quality of their packages " +"(<xref linkend=\"tools\"/> )." +msgstr "また、このリファレンスで触れるリソースには、" +"メーリングリストとサーバ (<xref linkend=\"server-machines\"/>)、" +"Debian アーカイブの構成に関する解説 (<xref linkend=\"archive\"/>)、" +"パッケージアップロードを受け付けるさまざまなサーバの説明" +"(<xref linkend=\"upload-ftp-master\"/>)、" +"パッケージの品質を高めるために開発者が利用できるリソースについての解説" +"(<xref linkend=\"tools\"/>) などがあります。" # type: Content of: <chapter><para> -#: scope.dbk:28 +#: scope.dbk:31 msgid "" "It should be clear that this reference does not discuss the technical " "details of Debian packages nor how to generate them. Nor does this " "reference detail the standards to which Debian software must comply. All of " -"such information can be found in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>." -msgstr "" +"such information can be found in the <ulink url=\"&url-debian-policy;" +"\">Debian Policy Manual</ulink>." +msgstr "初めに明らかにしておきたいのですが、" +"このリファレンスは、Debian パッケージに関する技術的な詳細や、" +"Debian パッケージの作成方法を説明するものではありません。" +"その情報については、<!-- OBSOLETE, please update translation" +"<ulink url=\"&url-pkg-manual;\">Debian パッケージングマニュアル</ulink> --> にて論じられています。" +"また、このリファレンスは Debian" +"ソフトウェアが準拠すべき基準を詳細に解説するようなものでもありません。" +"その情報については、<ulink url=\"&url-debian-policy;\">Debian ポリシーマニュアル</ulink> をご覧ください。" # type: Content of: <chapter><para> -#: scope.dbk:35 +#: scope.dbk:38 msgid "" -"Furthermore, this document is <emphasis>not an expression of formal " -"policy</emphasis>. It contains documentation for the Debian system and " -"generally agreed-upon best practices. Thus, it is not what is called a " -"``normative'' document." -msgstr "" +"Furthermore, this document is <emphasis>not an expression of formal policy</" +"emphasis>. It contains documentation for the Debian system and generally " +"agreed-upon best practices. Thus, it is not what is called a ``normative'' " +"document." +msgstr "さらに、この文書は<emphasis>公式なポリシーを明らかにするものではありません</emphasis>。" +"こちらに含まれるのは Debian システムに関する記述と、" +"一般的に認められている慣習に関する記述です。" + diff --git a/po4a/ja/tools.po b/po4a/ja/tools.po index 7cca30a..29733f6 100644 --- a/po4a/ja/tools.po +++ b/po4a/ja/tools.po @@ -6,21 +6,21 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:18+0000\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" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" -"Content-Transfer-Encoding: ENCODING" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: ENCODING\n" # type: Content of: <appendix><title> -#: tools.dbk:5 +#: tools.dbk:7 msgid "Overview of Debian Maintainer Tools" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:7 +#: tools.dbk:9 msgid "" "This section contains a rough overview of the tools available to " "maintainers. The following is by no means complete or definitive, but just " @@ -28,14 +28,14 @@ msgid "" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:12 +#: tools.dbk:14 msgid "" "Debian maintainer tools are meant to aid developers and free their time for " "critical tasks. As Larry Wall says, there's more than one way to do it." msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:16 +#: tools.dbk:18 msgid "" "Some people prefer to use high-level package maintenance tools and some do " "not. Debian is officially agnostic on this issue; any tool which gets the " @@ -46,36 +46,36 @@ msgid "" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:24 +#: tools.dbk:26 msgid "" "Most of the descriptions of these packages come from the actual package " "descriptions themselves. Further information can be found in the package " "documentation itself. You can also see more info with the command " -"<literal>apt-cache show <package-name></literal>." +"<command>apt-cache show <package-name></command>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:30 +#: tools.dbk:32 msgid "Core tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:32 +#: tools.dbk:34 msgid "The following tools are pretty much required for any maintainer." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:37 +#: tools.dbk:39 msgid "" "<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools " "(including <command>dpkg-source</command>) required to unpack, build, and " -"upload Debian source packages. These utilities contain the fundamental, " -"low-level functionality required to create and manipulate packages; as such, " +"upload Debian source packages. These utilities contain the fundamental, low-" +"level functionality required to create and manipulate packages; as such, " "they are essential for any Debian maintainer." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:48 +#: tools.dbk:50 msgid "" "<systemitem role=\"package\">debconf</systemitem> provides a consistent " "interface to configuring packages interactively. It is user interface " @@ -85,14 +85,14 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:54 +#: tools.dbk:56 msgid "" -"You can find documentation for this package in the <systemitem " -"role=\"package\">debconf-doc</systemitem> package." +"You can find documentation for this package in the <systemitem role=\"package" +"\">debconf-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:58 +#: tools.dbk:60 msgid "" "Many feel that this system should be used for all packages which require " "interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . " @@ -101,7 +101,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:68 +#: tools.dbk:70 msgid "" "<systemitem role=\"package\">fakeroot</systemitem> simulates root " "privileges. This enables you to build packages without being root (packages " @@ -111,12 +111,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:79 +#: tools.dbk:81 msgid "Package lint tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:81 +#: tools.dbk:83 msgid "" "According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a " "Unix C language processor which carries out more thorough checks on the code " @@ -126,7 +126,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:89 +#: tools.dbk:91 msgid "" "<systemitem role=\"package\">lintian</systemitem> dissects Debian packages " "and emits information about bugs and policy violations. It contains " @@ -135,33 +135,33 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:95 +#: tools.dbk:97 msgid "" -"You should periodically get the newest <systemitem " -"role=\"package\">lintian</systemitem> from `unstable' and check over all " -"your packages. Notice that the <literal>-i</literal> option provides " -"detailed explanations of what each error or warning means, what its basis in " -"Policy is, and commonly how you can fix the problem." +"You should periodically get the newest <systemitem role=\"package\">lintian</" +"systemitem> from `unstable' and check over all your packages. Notice that " +"the <literal>-i</literal> option provides detailed explanations of what each " +"error or warning means, what its basis in Policy is, and commonly how you " +"can fix the problem." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:102 +#: tools.dbk:104 msgid "" "Refer to <xref linkend=\"sanitycheck\"/> for more information on how and " "when to use Lintian." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:106 +#: tools.dbk:108 msgid "" "You can also see a summary of all problems reported by Lintian on your " -"packages at <ulink url=\"http://lintian.debian.org/\"></ulink>. These " -"reports contain the latest <command>lintian</command> output for the whole " -"development distribution (unstable)." +"packages at <ulink url=\"&url-lintian;\"></ulink>. These reports contain " +"the latest <command>lintian</command> output for the whole development " +"distribution (unstable)." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:116 +#: tools.dbk:118 msgid "" "<systemitem role=\"package\">linda</systemitem> is another package linter. " "It is similar to <systemitem role=\"package\">lintian</systemitem> but has a " @@ -169,74 +169,72 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:125 +#: tools.dbk:127 msgid "" -"<command>debdiff</command> (from the <systemitem " -"role=\"package\">devscripts</systemitem> package, <xref " -"linkend=\"devscripts\"/> ) compares file lists and control files of two " -"packages. It is a simple regression test, as it will help you notice if the " -"number of binary packages has changed since the last upload, or if something " -"has changed in the control file. Of course, some of the changes it reports " -"will be all right, but it can help you prevent various accidents." +"<command>debdiff</command> (from the <systemitem role=\"package" +"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) " +"compares file lists and control files of two packages. It is a simple " +"regression test, as it will help you notice if the number of binary packages " +"has changed since the last upload, or if something has changed in the " +"control file. Of course, some of the changes it reports will be all right, " +"but it can help you prevent various accidents." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:134 +#: tools.dbk:136 msgid "You can run it over a pair of binary packages:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:137 +#: tools.dbk:139 #, no-wrap -msgid "package_1-1_arch.deb package_2-1_arch.deb" +msgid "debdiff package_1-1_arch.deb package_2-1_arch.deb" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:140 +#: tools.dbk:142 msgid "Or even a pair of changes files:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:143 +#: tools.dbk:145 #, no-wrap -msgid "package_1-1_arch.changes package_2-1_arch.changes" +msgid "debdiff package_1-1_arch.changes package_2-1_arch.changes" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:146 +#: tools.dbk:148 msgid "" -"For more information please see <citerefentry> " -"<refentrytitle>debdiff</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry>." +"For more information please see <citerefentry> <refentrytitle>debdiff</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:155 +#: tools.dbk:157 msgid "Helpers for <filename>debian/rules</filename>" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:157 +#: tools.dbk:159 msgid "" -"Package building tools make the process of writing " -"<filename>debian/rules</filename> files easier. See <xref " -"linkend=\"helper-scripts\"/> for more information about why these might or " -"might not be desired." +"Package building tools make the process of writing <filename>debian/rules</" +"filename> files easier. See <xref linkend=\"helper-scripts\"/> for more " +"information about why these might or might not be desired." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:165 +#: tools.dbk:167 msgid "" "<systemitem role=\"package\">debhelper</systemitem> is a collection of " "programs which can be used in <filename>debian/rules</filename> to automate " -"common tasks related to building binary Debian packages. <systemitem " -"role=\"package\">debhelper</systemitem> includes programs to install various " +"common tasks related to building binary Debian packages. <systemitem role=" +"\"package\">debhelper</systemitem> includes programs to install various " "files into your package, compress files, fix file permissions, and integrate " "your package with the Debian menu system." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:173 +#: tools.dbk:175 msgid "" "Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> " "is broken into several small, simple commands which act in a consistent " @@ -245,81 +243,79 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:179 +#: tools.dbk:181 msgid "" -"There are a number of little <systemitem " -"role=\"package\">debhelper</systemitem> add-on packages, too transient to " -"document. You can see the list of most of them by doing <literal>apt-cache " -"search ^dh-</literal>." +"There are a number of little <systemitem role=\"package\">debhelper</" +"systemitem> add-on packages, too transient to document. You can see the " +"list of most of them by doing <literal>apt-cache search ^dh-</literal>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:188 +#: tools.dbk:190 msgid "" "<systemitem role=\"package\">debmake</systemitem>, a precursor to " -"<systemitem role=\"package\">debhelper</systemitem>, is a more " -"coarse-grained <filename>debian/rules</filename> assistant. It includes two " -"main programs: <command>deb-make</command>, which can be used to help a " +"<systemitem role=\"package\">debhelper</systemitem>, is a more coarse-" +"grained <filename>debian/rules</filename> assistant. It includes two main " +"programs: <command>deb-make</command>, which can be used to help a " "maintainer convert a regular (non-Debian) source archive into a Debian " "source package; and <command>debstd</command>, which incorporates in one big " -"shot the same sort of automated functions that one finds in <systemitem " -"role=\"package\">debhelper</systemitem>." +"shot the same sort of automated functions that one finds in <systemitem role=" +"\"package\">debhelper</systemitem>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:198 +#: tools.dbk:200 msgid "" "The consensus is that <systemitem role=\"package\">debmake</systemitem> is " -"now deprecated in favor of <systemitem " -"role=\"package\">debhelper</systemitem>. It is a bug to use <systemitem " -"role=\"package\">debmake</systemitem> in new packages. New packages using " -"<systemitem role=\"package\">debmake</systemitem> will be rejected from the " -"archive." +"now deprecated in favor of <systemitem role=\"package\">debhelper</" +"systemitem>. It is a bug to use <systemitem role=\"package\">debmake</" +"systemitem> in new packages. New packages using <systemitem role=\"package" +"\">debmake</systemitem> will be rejected from the archive." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:209 +#: tools.dbk:211 msgid "" "The <systemitem role=\"package\">dh-make</systemitem> package contains " "<command>dh_make</command>, a program that creates a skeleton of files " "necessary to build a Debian package out of a source tree. As the name " -"suggests, <command>dh_make</command> is a rewrite of <systemitem " -"role=\"package\">debmake</systemitem> and its template files use dh_* " -"programs from <systemitem role=\"package\">debhelper</systemitem>." +"suggests, <command>dh_make</command> is a rewrite of <systemitem role=" +"\"package\">debmake</systemitem> and its template files use dh_* programs " +"from <systemitem role=\"package\">debhelper</systemitem>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:217 +#: tools.dbk:219 msgid "" "While the rules files generated by <command>dh_make</command> are in general " "a sufficient basis for a working package, they are still just the " "groundwork: the burden still lies on the maintainer to finely tune the " -"generated files and make the package entirely functional and " -"Policy-compliant." +"generated files and make the package entirely functional and Policy-" +"compliant." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:227 +#: tools.dbk:229 msgid "" "<systemitem role=\"package\">yada</systemitem> is another packaging helper " "tool. It uses a <filename>debian/packages</filename> file to auto-generate " "<filename>debian/rules</filename> and other necessary files in the " -"<filename>debian/</filename> subdirectory. The " -"<filename>debian/packages</filename> file contains instruction to build " -"packages and there is no need to create any <filename>Makefile</filename> " -"files. There is possibility to use macro engine similar to the one used in " -"SPECS files from RPM source packages." +"<filename>debian/</filename> subdirectory. The <filename>debian/packages</" +"filename> file contains instruction to build packages and there is no need " +"to create any <filename>Makefile</filename> files. There is possibility to " +"use macro engine similar to the one used in SPECS files from RPM source " +"packages." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:237 +#: tools.dbk:239 msgid "" -"For more informations see <literal><ulink " -"url=\"http://yada.alioth.debian.org/\">YADA site</ulink></literal>." +"For more informations see <literal><ulink url=\"http://yada.alioth.debian." +"org/\">YADA site</ulink></literal>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:245 +#: tools.dbk:247 msgid "" "<systemitem role=\"package\">equivs</systemitem> is another package for " "making packages. It is often suggested for local use if you need to make a " @@ -329,12 +325,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:256 +#: tools.dbk:258 msgid "Package builders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:258 +#: tools.dbk:260 msgid "" "The following packages help with the package building process, general " "driving <command>dpkg-buildpackage</command> as well as handling supporting " @@ -342,7 +338,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:264 +#: tools.dbk:266 msgid "" "<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the " "capability to inject or import Debian source packages into a CVS repository, " @@ -351,7 +347,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:270 +#: tools.dbk:272 msgid "" "These utilities provide an infrastructure to facilitate the use of CVS by " "Debian maintainers. This allows one to keep separate CVS branches of a " @@ -361,7 +357,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:281 +#: tools.dbk:283 msgid "" "The <systemitem role=\"package\">debootstrap</systemitem> package and script " "allows you to bootstrap a Debian base system into any part of your " @@ -370,7 +366,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:287 +#: tools.dbk:289 msgid "" "Having a system like this can be useful in many ways. For instance, you can " "<command>chroot</command> into it if you want to test your build " @@ -379,7 +375,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:297 +#: tools.dbk:299 msgid "" "<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted " "system, and builds a package inside the chroot. It is very useful to check " @@ -389,7 +385,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:303 +#: tools.dbk:305 msgid "" "A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, " "which goes even further by doing the build within a User Mode Linux " @@ -397,31 +393,31 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:312 +#: tools.dbk:314 msgid "" "<systemitem role=\"package\">sbuild</systemitem> is another automated " -"builder. It can use chrooted environments as well. It can be used " -"stand-alone, or as part of a networked, distributed build environment. As " -"the latter, it is part of the system used by porters to build binary " -"packages for all the available architectures. See <xref " -"linkend=\"buildd\"/> for more information, and <ulink " -"url=\"http://buildd.debian.org/\"></ulink> to see the system in action." +"builder. It can use chrooted environments as well. It can be used stand-" +"alone, or as part of a networked, distributed build environment. As the " +"latter, it is part of the system used by porters to build binary packages " +"for all the available architectures. See <xref linkend=\"buildd\"/> for " +"more information, and <ulink url=\"&url-buildd;\"></ulink> to see the system " +"in action." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:324 +#: tools.dbk:326 msgid "Package uploaders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:326 +#: tools.dbk:328 msgid "" "The following packages help automate or simplify the process of uploading " "packages into the official archive." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:332 +#: tools.dbk:334 msgid "" "<systemitem role=\"package\">dupload</systemitem> is a package and a script " "to automatically upload Debian packages to the Debian archive, to log the " @@ -430,18 +426,18 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:342 +#: tools.dbk:344 msgid "" "The <systemitem role=\"package\">dput</systemitem> package and script does " "much the same thing as <systemitem role=\"package\">dupload</systemitem>, " -"but in a different way. It has some features over <systemitem " -"role=\"package\">dupload</systemitem>, such as the ability to check the " -"GnuPG signature and checksums before uploading, and the possibility of " -"running <command>dinstall</command> in dry-run mode after the upload." +"but in a different way. It has some features over <systemitem role=\"package" +"\">dupload</systemitem>, such as the ability to check the GnuPG signature " +"and checksums before uploading, and the possibility of running " +"<command>dinstall</command> in dry-run mode after the upload." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:354 +#: tools.dbk:356 msgid "" "The <systemitem role=\"package\">dcut</systemitem> script (part of the " "package <xref linkend=\"dput\"/> ) helps in removing files from the ftp " @@ -449,12 +445,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:362 +#: tools.dbk:364 msgid "Maintenance automation" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:364 +#: tools.dbk:366 msgid "" "The following tools help automate different maintenance tasks, from adding " "changelog entries or signature lines and looking up bugs in Emacs to making " @@ -462,24 +458,23 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:371 +#: tools.dbk:373 msgid "" "<systemitem role=\"package\">devscripts</systemitem> is a package containing " "wrappers and tools which are very helpful for maintaining your Debian " "packages. Example scripts include <command>debchange</command> and " -"<command>dch</command>, which manipulate your " -"<filename>debian/changelog</filename> file from the command-line, and " -"<command>debuild</command>, which is a wrapper around " -"<command>dpkg-buildpackage</command>. The <command>bts</command> utility is " -"also very helpful to update the state of bug reports on the command line. " -"<command>uscan</command> can be used to watch for new upstream versions of " -"your packages. <command>debrsign</command> can be used to remotely sign a " -"package prior to upload, which is nice when the machine you build the " -"package on is different from where your GPG keys are." +"<command>dch</command>, which manipulate your <filename>debian/changelog</" +"filename> file from the command-line, and <command>debuild</command>, which " +"is a wrapper around <command>dpkg-buildpackage</command>. The <command>bts</" +"command> utility is also very helpful to update the state of bug reports on " +"the command line. <command>uscan</command> can be used to watch for new " +"upstream versions of your packages. <command>debrsign</command> can be used " +"to remotely sign a package prior to upload, which is nice when the machine " +"you build the package on is different from where your GPG keys are." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:385 +#: tools.dbk:387 msgid "" "See the <citerefentry> <refentrytitle>devscripts</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of " @@ -487,18 +482,17 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:394 +#: tools.dbk:396 msgid "" "<systemitem role=\"package\">autotools-dev</systemitem> contains best " -"practices for people who maintain packages which use " -"<command>autoconf</command> and/or <command>automake</command>. Also " -"contains canonical <filename>config.sub</filename> and " -"<filename>config.guess</filename> files which are known to work on all " -"Debian ports." +"practices for people who maintain packages which use <command>autoconf</" +"command> and/or <command>automake</command>. Also contains canonical " +"<filename>config.sub</filename> and <filename>config.guess</filename> files " +"which are known to work on all Debian ports." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:405 +#: tools.dbk:407 msgid "" "<command>dpkg-repack</command> creates Debian package file out of a package " "that has already been installed. If any changes have been made to the " @@ -507,7 +501,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:411 +#: tools.dbk:413 msgid "" "This utility can make it easy to copy packages from one computer to another, " "or to recreate packages which are installed on your system but no longer " @@ -516,7 +510,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:420 +#: tools.dbk:422 msgid "" "<command>alien</command> converts binary packages between various packaging " "formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, " @@ -524,7 +518,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:429 +#: tools.dbk:431 msgid "" "<command>debsums</command> checks installed packages against their MD5 " "sums. Note that not all packages have MD5 sums, since they aren't required " @@ -532,7 +526,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:437 +#: tools.dbk:439 msgid "" "<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp " "package which provides assistance when editing some of the files in the " @@ -542,16 +536,16 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:448 +#: tools.dbk:450 msgid "" -"<command>dpkg-depcheck</command> (from the <systemitem " -"role=\"package\">devscripts</systemitem> package, <xref " -"linkend=\"devscripts\"/> ) runs a command under <command>strace</command> " -"to determine all the packages that were used by the said command." +"<command>dpkg-depcheck</command> (from the <systemitem role=\"package" +"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) runs a " +"command under <command>strace</command> to determine all the packages that " +"were used by the said command." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:454 +#: tools.dbk:456 msgid "" "For Debian packages, this is useful when you have to compose a " "<literal>Build-Depends</literal> line for your new package: running the " @@ -560,70 +554,68 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:460 +#: tools.dbk:462 #, no-wrap -msgid "-depcheck -b debian/rules build" +msgid "dpkg-depcheck -b debian/rules build" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:463 +#: tools.dbk:465 msgid "" "<command>dpkg-depcheck</command> can also be used to check for run-time " "dependencies, especially if your package uses exec(2) to run other programs." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:467 +#: tools.dbk:469 msgid "" -"For more information please see <citerefentry> " -"<refentrytitle>dpkg-depcheck</refentrytitle> <manvolnum>1</manvolnum> " -"</citerefentry>." +"For more information please see <citerefentry> <refentrytitle>dpkg-depcheck</" +"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:476 +#: tools.dbk:478 msgid "Porting tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:478 +#: tools.dbk:480 msgid "The following tools are helpful for porters and for cross-compilation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:483 +#: tools.dbk:485 msgid "" "<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the " "differences from one architecture to another. For instance, it could tell " -"you which packages need to be ported for architecture " -"<replaceable>Y</replaceable>, based on architecture " -"<replaceable>X</replaceable>." +"you which packages need to be ported for architecture <replaceable>Y</" +"replaceable>, based on architecture <replaceable>X</replaceable>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:493 +#: tools.dbk:495 msgid "" "<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for " "installing libraries and headers for cross-compiling in a way similar to " "<systemitem role=\"package\">dpkg</systemitem>. Furthermore, the " -"functionality of <command>dpkg-buildpackage</command> and " -"<command>dpkg-shlibdeps</command> is enhanced to support cross-compiling." +"functionality of <command>dpkg-buildpackage</command> and <command>dpkg-" +"shlibdeps</command> is enhanced to support cross-compiling." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:504 +#: tools.dbk:506 msgid "Documentation and information" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:506 +#: tools.dbk:508 msgid "" "The following packages provide information for maintainers or help with " "building documentation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:512 +#: tools.dbk:514 msgid "" "<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the " "DebianDoc SGML DTD, which is commonly used for Debian documentation. This " @@ -632,21 +624,21 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:518 +#: tools.dbk:520 msgid "" -"Documentation for the DTD can be found in the <systemitem " -"role=\"package\">debiandoc-sgml-doc</systemitem> package." +"Documentation for the DTD can be found in the <systemitem role=\"package" +"\">debiandoc-sgml-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:526 +#: tools.dbk:544 msgid "" "Contains the public GPG and PGP keys of Debian developers. See <xref " "linkend=\"key-maint\"/> and the package documentation for more information." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:534 +#: tools.dbk:552 msgid "" "<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for " "viewing Debian binary packages. This lets you examine a package without " diff --git a/po4a/po/best-pkging-practices.pot b/po4a/po/best-pkging-practices.pot index afae0ad..d65c41d 100644 --- a/po4a/po/best-pkging-practices.pot +++ b/po4a/po/best-pkging-practices.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,24 +15,24 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: best-pkging-practices.dbk:5 +#: best-pkging-practices.dbk:7 msgid "Best Packaging Practices" msgstr "" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:7 +#: best-pkging-practices.dbk:9 msgid "" "Debian's quality is largely due to the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>, " -"which defines explicit baseline requirements which all Debian packages must " -"fulfill. Yet there is also a shared history of experience which goes beyond " -"the Debian Policy, an accumulation of years of experience in packaging. " -"Many very talented people have created great tools, tools which help you, " -"the Debian maintainer, create and maintain excellent packages." +"url=\"&url-debian-policy;\">Debian Policy</ulink>, which defines explicit " +"baseline requirements which all Debian packages must fulfill. Yet there is " +"also a shared history of experience which goes beyond the Debian Policy, an " +"accumulation of years of experience in packaging. Many very talented people " +"have created great tools, tools which help you, the Debian maintainer, " +"create and maintain excellent packages." msgstr "" # type: Content of: <chapter><para> -#: best-pkging-practices.dbk:16 +#: best-pkging-practices.dbk:18 msgid "" "This chapter provides some best practices for Debian developers. All " "recommendations are merely that, and are not requirements or policy. These " @@ -41,12 +41,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:22 +#: best-pkging-practices.dbk:24 msgid "Best practices for <filename>debian/rules</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:24 +#: best-pkging-practices.dbk:26 msgid "" "The following recommendations apply to the <filename>debian/rules</filename> " "file. Since <filename>debian/rules</filename> controls the build process " @@ -55,12 +55,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:30 +#: best-pkging-practices.dbk:32 msgid "Helper scripts" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:32 +#: best-pkging-practices.dbk:34 msgid "" "The rationale for using helper scripts in <filename>debian/rules</filename> " "is that they let maintainers use and share common logic among many " @@ -75,7 +75,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:43 +#: best-pkging-practices.dbk:45 msgid "" "Helper scripts take care of these issues. Assuming you comply with the " "conventions expected by the helper script, the helper takes care of all the " @@ -85,7 +85,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:50 +#: best-pkging-practices.dbk:52 msgid "" "<xref linkend=\"tools\"/> contains a couple of different helpers. The most " "common and best (in our opinion) helper system is <systemitem " @@ -103,7 +103,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:64 +#: best-pkging-practices.dbk:66 msgid "" "You can get started with <systemitem role=\"package\">debhelper</systemitem> " "by reading <citerefentry> <refentrytitle>debhelper</refentrytitle> " @@ -119,22 +119,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:77 +#: 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=\"http://arch.debian.org/arch/private/srivasta/\"></ulink>." +"<ulink url=\"&url-rules-files;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:86 +#: best-pkging-practices.dbk:88 msgid "Separating your patches into multiple files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:88 +#: best-pkging-practices.dbk:90 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 " @@ -146,7 +146,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:97 +#: best-pkging-practices.dbk:99 msgid "" "Unfortunately, the packaging system as such currently doesn't provide for " "separating the patches into several files. Nevertheless, there are ways to " @@ -159,7 +159,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:107 +#: best-pkging-practices.dbk:109 msgid "" "<command>dbs</command> is one of the more popular approaches to this. It " "does all of the above, and provides a facility for creating new and updating " @@ -169,7 +169,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:114 +#: best-pkging-practices.dbk:116 msgid "" "<command>dpatch</command> also provides these facilities, but it's intended " "to be even easier to use. See the package <systemitem " @@ -178,12 +178,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:122 +#: best-pkging-practices.dbk:124 msgid "Multiple binary packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:124 +#: best-pkging-practices.dbk:126 msgid "" "A single source package will often build several binary packages, either to " "provide several flavors of the same software (e.g., the <systemitem " @@ -193,7 +193,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:131 +#: best-pkging-practices.dbk:133 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 " @@ -205,7 +205,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:140 +#: best-pkging-practices.dbk:142 msgid "" "The first case is a bit more difficult since it involves multiple recompiles " "of the same software but with different configuration options. The " @@ -215,21 +215,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:150 +#: best-pkging-practices.dbk:154 msgid "Best practices for <filename>debian/control</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:152 +#: best-pkging-practices.dbk:156 msgid "" "The following practices are relevant to the " "<filename>debian/control</filename> file. They supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-binary.html#s-descriptions\">Policy " -"on package descriptions</ulink>." +"url=\"&url-debian-policy;ch-binary.html#s-descriptions\">Policy on package " +"descriptions</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:158 +#: best-pkging-practices.dbk:162 msgid "" "The description of the package, as defined by the corresponding field in the " "<filename>control</filename> file, contains both the package synopsis and " @@ -241,12 +241,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:167 +#: best-pkging-practices.dbk:171 msgid "General guidelines for package descriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:169 +#: best-pkging-practices.dbk:173 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, " @@ -256,7 +256,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:176 +#: best-pkging-practices.dbk:180 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 " @@ -265,7 +265,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:182 +#: best-pkging-practices.dbk:186 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 — " @@ -275,7 +275,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:189 +#: best-pkging-practices.dbk:193 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 " @@ -283,7 +283,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:194 +#: best-pkging-practices.dbk:198 msgid "" "References to the names of any other software packages, protocol names, " "standards, or specifications should use their canonical forms, if one " @@ -293,27 +293,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:201 +#: best-pkging-practices.dbk:205 msgid "" "If you are having problems writing your description, you may wish to send it " -"along to <email>debian-l10n-english@lists.debian.org</email> and request " -"feedback." +"along to &email-debian-l10n-english; and request feedback." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:208 +#: best-pkging-practices.dbk:211 msgid "The package synopsis, or short description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:210 +#: best-pkging-practices.dbk:213 msgid "" "The synopsis line (the short description) should be concise. It must not " "repeat the package's name (this is policy)." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:214 +#: best-pkging-practices.dbk:217 msgid "" "It's a good idea to think of the synopsis as an appositive clause, not a " "full sentence. An appositive clause is defined in WordNet as a grammatical " @@ -326,14 +325,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:223 +#: best-pkging-practices.dbk:226 msgid "" "It might help to imagine that the synopsis is combined with the package name " "in the following way:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:227 +#: best-pkging-practices.dbk:230 #, no-wrap msgid "" "<replaceable>package-name</replaceable> is a " @@ -341,12 +340,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:230 +#: best-pkging-practices.dbk:233 msgid "Alternatively, it might make sense to think of it as" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:233 +#: best-pkging-practices.dbk:236 #, no-wrap msgid "" "<replaceable>package-name</replaceable> is " @@ -354,12 +353,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:236 +#: best-pkging-practices.dbk:239 msgid "or, if the package name itself is a plural (such as developers-tools)" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:239 +#: best-pkging-practices.dbk:242 #, no-wrap msgid "" "<replaceable>package-name</replaceable> are " @@ -367,7 +366,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:242 +#: best-pkging-practices.dbk:245 msgid "" "This way of forming a sentence from the package name and synopsis should be " "considered as a heuristic and not a strict rule. There are some cases where " @@ -375,12 +374,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:249 +#: best-pkging-practices.dbk:252 msgid "The long description" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:251 +#: best-pkging-practices.dbk:254 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 " @@ -389,12 +388,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:257 +#: best-pkging-practices.dbk:260 msgid "The long description should consist of full and complete sentences." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:260 +#: best-pkging-practices.dbk:263 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 " @@ -403,7 +402,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:266 +#: best-pkging-practices.dbk:269 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 " @@ -414,7 +413,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:274 +#: best-pkging-practices.dbk:277 msgid "" "Be careful to avoid spelling and grammar mistakes. Ensure that you " "spell-check it. Both <command>ispell</command> and " @@ -423,33 +422,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:279 +#: best-pkging-practices.dbk:282 #, no-wrap -msgid "-d american -g debian/control" +msgid "ispell -d american -g debian/control" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:282 +#: best-pkging-practices.dbk:285 #, no-wrap -msgid "-d en -D -c debian/control" +msgid "aspell -d en -D -c debian/control" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:285 +#: best-pkging-practices.dbk:288 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:290 +#: best-pkging-practices.dbk:293 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:296 +#: best-pkging-practices.dbk:299 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 " @@ -457,14 +456,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:303 +#: best-pkging-practices.dbk:306 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:309 +#: best-pkging-practices.dbk:312 msgid "" "If the package is experimental, or there are other reasons it should not be " "used, if there are other packages that should be used instead, it should be " @@ -472,7 +471,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:316 +#: best-pkging-practices.dbk:319 msgid "" "How is this package different from the competition? Is it a better " "implementation? more features? different features? Why should I choose this " @@ -480,12 +479,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:325 +#: best-pkging-practices.dbk:332 msgid "Upstream home page" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:327 +#: best-pkging-practices.dbk:334 msgid "" "We recommend that you add the URL for the package's home page to the package " "description in <filename>debian/control</filename>. This information should " @@ -493,7 +492,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:332 +#: best-pkging-practices.dbk:339 #, no-wrap msgid "" ".\n" @@ -501,52 +500,52 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:336 +#: best-pkging-practices.dbk:343 msgid "" "Note the spaces prepending the line, which serves to break the lines " "correctly. To see an example of how this displays, see <ulink " -"url=\"http://packages.debian.org/unstable/web/wml\"></ulink>." +"url=\"&url-eg-desc-upstream-info;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:341 +#: best-pkging-practices.dbk:348 msgid "" "If there is no home page for the software, this should naturally be left " "out." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:344 +#: best-pkging-practices.dbk:351 msgid "" "Note that we expect this field will eventually be replaced by a proper " "<filename>debian/control</filename> field understood by " -"<command>dpkg</command> and <literal>packages.debian.org</literal>. If you " +"<command>dpkg</command> and <literal>&packages-host;</literal>. If you " "don't want to bother migrating the home page from the description to this " "field, you should probably wait until that is available. Please make sure " "that this line matches the regular expression <literal>/^ Homepage: [^ " -"]*$/</literal>, as this allows <filename>packages.debian.org</filename> to " -"parse it correctly." +"]*$/</literal>, as this allows <filename>&packages-host;</filename> to parse " +"it correctly." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:355 +#: best-pkging-practices.dbk:362 msgid "Version Control System location" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:357 +#: best-pkging-practices.dbk:364 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:361 +#: best-pkging-practices.dbk:368 msgid "XS-Vcs-Browser" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:363 +#: best-pkging-practices.dbk:370 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 " @@ -554,7 +553,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:368 +#: best-pkging-practices.dbk:375 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 " @@ -562,12 +561,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:375 +#: best-pkging-practices.dbk:382 msgid "XS-Vcs-*" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:377 +#: best-pkging-practices.dbk:384 msgid "" "Value of this field should be a string identifying unequivocally the " "location of the Version Control System repository used to maintain the given " @@ -582,7 +581,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:388 +#: best-pkging-practices.dbk:395 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 " @@ -596,7 +595,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:399 +#: best-pkging-practices.dbk:406 msgid "" "In the following example, an instance of the field for a Subversion " "repository of the <systemitem role=\"package\">vim</systemitem> package is " @@ -607,7 +606,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:407 +#: best-pkging-practices.dbk:414 #, no-wrap msgid "" "Source: vim\n" @@ -619,25 +618,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:421 +#: best-pkging-practices.dbk:428 msgid "Best practices for <filename>debian/changelog</filename>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:423 +#: best-pkging-practices.dbk:430 msgid "" "The following practices supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html#s-changelogs\">Policy " -"on changelog files</ulink>." +"url=\"&url-debian-policy;ch-docs.html#s-changelogs\">Policy on changelog " +"files</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:428 +#: best-pkging-practices.dbk:435 msgid "Writing useful changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:430 +#: best-pkging-practices.dbk:437 msgid "" "The changelog entry for a package revision documents changes in that " "revision, and only them. Concentrate on describing significant and " @@ -645,7 +644,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:435 +#: best-pkging-practices.dbk:442 msgid "" "Focus on <emphasis>what</emphasis> was changed — who, how and when are " "usually less important. Having said that, remember to politely attribute " @@ -654,7 +653,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:441 +#: best-pkging-practices.dbk:448 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 " @@ -664,7 +663,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:448 +#: best-pkging-practices.dbk:455 msgid "" "Use common English so that the majority of readers can comprehend it. Avoid " "abbreviations, tech-speak and jargon when explaining changes that close " @@ -673,7 +672,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:454 +#: best-pkging-practices.dbk:461 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 " @@ -682,7 +681,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:460 +#: best-pkging-practices.dbk:467 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 " @@ -690,12 +689,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:467 +#: best-pkging-practices.dbk:474 msgid "Common misconceptions about changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:469 +#: best-pkging-practices.dbk:476 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> " "document generic packaging issues (Hey, if you're looking for foo.conf, it's " @@ -706,7 +705,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:477 +#: best-pkging-practices.dbk:484 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 " @@ -714,7 +713,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:482 +#: best-pkging-practices.dbk:489 msgid "" "The changelog entries should <emphasis role=\"strong\">not</emphasis> be " "used for random discussion with bug reporters (I don't see segfaults when " @@ -728,7 +727,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:493 +#: best-pkging-practices.dbk:500 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 " @@ -737,73 +736,73 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:501 +#: best-pkging-practices.dbk:508 msgid "Common errors in changelog entries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:503 +#: best-pkging-practices.dbk:510 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:507 +#: best-pkging-practices.dbk:514 #, no-wrap msgid "* Fixed all outstanding bugs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:510 +#: best-pkging-practices.dbk:517 msgid "This doesn't tell readers anything too useful, obviously." msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:513 +#: best-pkging-practices.dbk:520 #, no-wrap msgid "* Applied patch from Jane Random." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:516 +#: best-pkging-practices.dbk:523 msgid "What was the patch about?" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:519 +#: best-pkging-practices.dbk:526 #, no-wrap msgid "* Late night install target overhaul." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:522 +#: best-pkging-practices.dbk:529 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:526 +#: best-pkging-practices.dbk:533 #, no-wrap msgid "* Fix vsync FU w/ ancient CRTs." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:529 +#: best-pkging-practices.dbk:536 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:533 +#: best-pkging-practices.dbk:540 #, no-wrap msgid "* This is not a bug, closes: #nnnnnn." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:536 +#: best-pkging-practices.dbk:543 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 " @@ -811,13 +810,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:541 +#: best-pkging-practices.dbk:548 #, no-wrap msgid "* Has been fixed for ages, but I forgot to close; closes: #54321." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:544 +#: best-pkging-practices.dbk:551 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 " @@ -828,25 +827,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:551 +#: best-pkging-practices.dbk:558 #, no-wrap msgid "* Closes: #12345, #12346, #15432" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:554 +#: best-pkging-practices.dbk:561 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:560 +#: best-pkging-practices.dbk:567 msgid "Supplementing changelogs with NEWS.Debian files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:562 +#: best-pkging-practices.dbk:569 msgid "" "Important news about changes in a package can also be put in NEWS.Debian " "files. The news will be displayed by tools like apt-listchanges, before all " @@ -858,7 +857,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:571 +#: best-pkging-practices.dbk:578 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 " @@ -869,10 +868,10 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:579 +#: best-pkging-practices.dbk:586 #, no-wrap msgid "" -"(3.0pl1-74) unstable; urgency=low\n" +"cron (3.0pl1-74) unstable; urgency=low\n" "\n" " The checksecurity script is no longer included with the cron package:\n" " it now has its own package, checksecurity. If you liked the\n" @@ -884,7 +883,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:589 +#: best-pkging-practices.dbk:596 msgid "" "The NEWS.Debian file is installed as " "/usr/share/doc/<package>/NEWS.Debian.gz. It is compressed, and always " @@ -893,7 +892,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:595 +#: best-pkging-practices.dbk:602 msgid "" "Unlike changelog files, you need not update NEWS.Debian files with every " "release. Only update them if you have something particularly newsworthy " @@ -902,24 +901,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:605 +#: best-pkging-practices.dbk:623 msgid "Best practices for maintainer scripts" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:607 +#: best-pkging-practices.dbk:625 msgid "" "Maintainer scripts include the files <filename>debian/postinst</filename>, " "<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and " "<filename>debian/postrm</filename>. These scripts take care of any package " "installation or deinstallation setup which isn't handled merely by the " "creation or removal of files and directories. The following instructions " -"supplement the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy</ulink>." +"supplement the <ulink url=\"&url-debian-policy;\">Debian Policy</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:615 +#: best-pkging-practices.dbk:633 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 " @@ -927,14 +925,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:620 +#: best-pkging-practices.dbk:638 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:624 +#: best-pkging-practices.dbk:642 msgid "" "All prompting or interactive configuration should be kept to a minimum. " "When it is necessary, you should use the <systemitem " @@ -944,7 +942,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:631 +#: best-pkging-practices.dbk:649 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 " @@ -954,7 +952,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:638 +#: best-pkging-practices.dbk:656 msgid "" "If you change your maintainer scripts, be sure to test package removal, " "double installation, and purging. Be sure that a purged package is " @@ -963,45 +961,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:644 +#: best-pkging-practices.dbk:662 msgid "" "If you need to check for the existence of a command, you should use " "something like" msgstr "" -# type: Content of: <chapter><section><screen> -#: best-pkging-practices.dbk:648 +# type: Content of: <chapter><section><programlisting> +#: best-pkging-practices.dbk:665 #, no-wrap -msgid "[ -x /usr/sbin/install-docs ]; then ..." +msgid "if [ -x /usr/sbin/install-docs ]; then ..." msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:651 +#: best-pkging-practices.dbk:667 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><screen> -#: best-pkging-practices.dbk:655 -#, no-wrap -msgid "" -"() {\n" -" OLDIFS=$IFS\n" -" IFS=:\n" -" for p in $PATH; do\n" -" if [ -x $p/$* ]; then\n" -" IFS=$OLDIFS\n" -" return 0\n" -" fi\n" -" done\n" -" IFS=$OLDIFS\n" -" return 1\n" -"}" -msgstr "" - # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:669 +#: best-pkging-practices.dbk:672 msgid "" "You can use this function to search <literal>$PATH</literal> for a command " "name, passed as an argument. It returns true (zero) if the command was " @@ -1011,7 +991,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:676 +#: best-pkging-practices.dbk:679 msgid "" "While <command>which</command> is an acceptable alternative, since it is " "from the required <systemitem role=\"package\">debianutils</systemitem> " @@ -1022,14 +1002,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:686 +#: best-pkging-practices.dbk:689 msgid "" "Configuration management with <systemitem " "role=\"package\">debconf</systemitem>" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:688 +#: best-pkging-practices.dbk:691 msgid "" "<systemitem role=\"package\">Debconf</systemitem> is a configuration " "management system which can be used by all the various packaging scripts " @@ -1040,7 +1020,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:696 +#: best-pkging-practices.dbk:699 msgid "" "Debconf is a great tool but it is often poorly used. Many common mistakes " "are listed in the <citerefentry> " @@ -1050,7 +1030,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:703 +#: best-pkging-practices.dbk:706 msgid "" "These guidelines include some writing style and typography recommendations, " "general considerations about debconf usage as well as more specific " @@ -1059,12 +1039,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:709 +#: best-pkging-practices.dbk:712 msgid "Do not abuse debconf" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:711 +#: best-pkging-practices.dbk:714 msgid "" "Since debconf appeared in Debian, it has been widely abused and several " "criticisms received by the Debian distribution come from debconf abuse with " @@ -1073,7 +1053,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:717 +#: best-pkging-practices.dbk:720 msgid "" "Keep usage notes to what they belong: the NEWS.Debian, or README.Debian " "file. Only use notes for important notes which may directly affect the " @@ -1082,7 +1062,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:723 +#: best-pkging-practices.dbk:726 msgid "" "Carefully choose the questions priorities in maintainer scripts. See " "<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " @@ -1091,38 +1071,38 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:731 +#: best-pkging-practices.dbk:734 msgid "General recommendations for authors and translators" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:733 +#: best-pkging-practices.dbk:736 msgid "Write correct English" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:735 +#: best-pkging-practices.dbk:738 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:739 +#: best-pkging-practices.dbk:742 msgid "" -"Please use (and abuse) <email>debian-l10n-english@lists.debian.org</email> " -"mailing list. Have your templates proofread." +"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:743 +#: best-pkging-practices.dbk:746 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:747 +#: best-pkging-practices.dbk:750 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 " @@ -1131,12 +1111,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:755 +#: best-pkging-practices.dbk:758 msgid "Be kind to translators" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:757 +#: best-pkging-practices.dbk:760 msgid "" "Debconf templates may be translated. Debconf, along with its sister package " "<command>po-debconf</command> offers a simple framework for getting " @@ -1144,7 +1124,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:762 +#: best-pkging-practices.dbk:765 msgid "" "Please use gettext-based templates. Install <systemitem " "role=\"package\">po-debconf</systemitem> on your development system and read " @@ -1152,7 +1132,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:767 +#: best-pkging-practices.dbk:770 msgid "" "Avoid changing templates too often. Changing templates text induces more " "work to translators which will get their translation fuzzied. If you plan " @@ -1164,7 +1144,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:776 +#: best-pkging-practices.dbk:779 msgid "" "The use of the <command>podebconf-report-po</command> from the po-debconf " "package is highly recommended to warn translators which have incomplete " @@ -1172,30 +1152,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:781 +#: best-pkging-practices.dbk:784 msgid "" "If in doubt, you may also contact the translation team for a given language " -"(debian-l10n-xxxxx@lists.debian.org), or the " -"<email>debian-i18n@lists.debian.org</email> mailing list." +"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:786 +#: best-pkging-practices.dbk:789 msgid "" -"Calls for translations posted to <email>debian-i18n@lists.debian.org</email> " -"with the <filename>debian/po/templates.pot</filename> file attached or " -"referenced in a URL are encouraged. Be sure to mentions in these calls for " -"new translations which languages you have existing translations for, in " -"order to avoid duplicate work." +"Calls for translations posted to &email-debian-i18n; with the " +"<filename>debian/po/templates.pot</filename> file attached or referenced in " +"a URL are encouraged. Be sure to mentions in these calls for new " +"translations which languages you have existing translations for, in order to " +"avoid duplicate work." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:795 +#: best-pkging-practices.dbk:798 msgid "Unfuzzy complete translations when correcting typos and spelling" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:797 +#: best-pkging-practices.dbk:800 msgid "" "When the text of a debconf template is corrected and you are <emphasis " "role=\"strong\">sure</emphasis> that the change does <emphasis " @@ -1204,37 +1183,37 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:803 +#: best-pkging-practices.dbk:806 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:807 +#: best-pkging-practices.dbk:810 msgid "" "To <emphasis role=\"strong\">unfuzzy</emphasis> translations, you can " "proceed the following way:" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:813 +#: best-pkging-practices.dbk:816 msgid "" "Put all incomplete PO files out of the way. You can check the completeness " "by using (needs the <systemitem role=\"package\">gettext</systemitem> " "package installed):" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> -#: best-pkging-practices.dbk:818 +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> +#: best-pkging-practices.dbk:820 #, no-wrap msgid "" -"i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" +"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" "--statistics $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:824 +#: best-pkging-practices.dbk:825 msgid "" "move all files which report either fuzzy strings to a temporary place. " "Files which report no fuzzy strings (only translated and untranslated) will " @@ -1242,7 +1221,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:831 +#: best-pkging-practices.dbk:832 msgid "" "now <emphasis role=\"strong\">and now only</emphasis>, modify the template " "for the typos and check again that translation are not impacted (typos, " @@ -1250,42 +1229,42 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:838 +#: best-pkging-practices.dbk:839 msgid "" "run <command>debconf-updatepo</command>. This will fuzzy all strings you " "modified in translations. You can see this by running the above again" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:844 +#: best-pkging-practices.dbk:845 msgid "use the following command:" msgstr "" -# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen> +# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> #: best-pkging-practices.dbk:847 #, no-wrap -msgid "i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" +msgid "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:852 +#: best-pkging-practices.dbk:851 msgid "" "move back to debian/po the files which showed fuzzy strings in the first " "step" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:857 +#: best-pkging-practices.dbk:856 msgid "run <command>debconf-updatepo</command> again" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:864 +#: best-pkging-practices.dbk:863 msgid "Do not make assumptions about interfaces" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:866 +#: best-pkging-practices.dbk:865 msgid "" "Templates text should not make reference to widgets belonging to some " "debconf interfaces. Sentences like If you answer Yes... have no meaning " @@ -1294,7 +1273,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:871 +#: best-pkging-practices.dbk:870 msgid "" "String templates should also avoid mentioning the default values in their " "description. First, because this is redundant with the values seen by the " @@ -1303,19 +1282,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:877 +#: best-pkging-practices.dbk:876 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:883 +#: best-pkging-practices.dbk:882 msgid "Do not use first person" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:885 +#: best-pkging-practices.dbk:884 msgid "" "You should avoid the use of first person (I will do this... or We " "recommend...). The computer is not a person and the Debconf templates do " @@ -1327,24 +1306,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:895 +#: best-pkging-practices.dbk:894 msgid "Be gender neutral" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:897 +#: best-pkging-practices.dbk:896 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:905 +#: best-pkging-practices.dbk:904 msgid "Templates fields definition" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:907 +#: best-pkging-practices.dbk:906 msgid "" "This part gives some information which is mostly taken from the " "<citerefentry> <refentrytitle>debconf-devel</refentrytitle> " @@ -1352,27 +1331,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:912 +#: best-pkging-practices.dbk:911 msgid "Type" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:914 +#: best-pkging-practices.dbk:913 msgid "string:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:916 +#: best-pkging-practices.dbk:915 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:921 +#: best-pkging-practices.dbk:920 msgid "password:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:923 +#: best-pkging-practices.dbk:922 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 " @@ -1380,24 +1359,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:930 +#: best-pkging-practices.dbk:929 msgid "boolean:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:932 +#: best-pkging-practices.dbk:931 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:938 +#: best-pkging-practices.dbk:937 msgid "select:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:940 +#: best-pkging-practices.dbk:939 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 " @@ -1405,24 +1384,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:947 +#: best-pkging-practices.dbk:946 msgid "multiselect:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:949 +#: best-pkging-practices.dbk:948 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:955 +#: best-pkging-practices.dbk:954 msgid "note:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:957 +#: best-pkging-practices.dbk:956 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 " @@ -1432,22 +1411,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:966 +#: best-pkging-practices.dbk:965 msgid "text:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:968 +#: best-pkging-practices.dbk:967 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:973 +#: best-pkging-practices.dbk:972 msgid "error:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:975 +#: best-pkging-practices.dbk:974 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 " @@ -1455,26 +1434,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:980 +#: best-pkging-practices.dbk:979 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:988 +#: best-pkging-practices.dbk:987 msgid "Description: short and extended description" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:990 +#: best-pkging-practices.dbk:989 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:994 +#: best-pkging-practices.dbk:993 msgid "" "The short description should be kept short (50 characters or so) so that it " "may be accomodated by most debconf interfaces. Keeping it short also helps " @@ -1483,7 +1462,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1000 +#: best-pkging-practices.dbk:999 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 " @@ -1492,14 +1471,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1006 +#: best-pkging-practices.dbk:1005 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:1010 +#: best-pkging-practices.dbk:1009 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 " @@ -1509,7 +1488,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1017 +#: best-pkging-practices.dbk:1016 msgid "" "The extended description should use complete sentences. Paragraphs should " "be kept short for improved readability. Do not mix two ideas in the same " @@ -1517,7 +1496,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1022 +#: best-pkging-practices.dbk:1021 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 " @@ -1526,26 +1505,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1028 +#: best-pkging-practices.dbk:1027 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:1032 +#: best-pkging-practices.dbk:1031 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:1038 +#: best-pkging-practices.dbk:1037 msgid "Choices" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1040 +#: best-pkging-practices.dbk:1039 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 " @@ -1553,12 +1532,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1047 +#: best-pkging-practices.dbk:1046 msgid "Default" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1049 +#: best-pkging-practices.dbk:1048 msgid "" "This field is optional. It contains the default answer for string, select " "and multiselect templates. For multiselect templates, it may contain a " @@ -1566,41 +1545,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1058 +#: best-pkging-practices.dbk:1057 msgid "Templates fields specific style guide" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1060 +#: best-pkging-practices.dbk:1059 msgid "Type field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1062 +#: best-pkging-practices.dbk:1061 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:1068 +#: best-pkging-practices.dbk:1067 msgid "Description field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1070 +#: best-pkging-practices.dbk:1069 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:1074 +#: best-pkging-practices.dbk:1073 msgid "String/password templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1078 +#: best-pkging-practices.dbk:1077 msgid "" "The short description is a prompt and <emphasis " "role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP " @@ -1609,7 +1588,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1085 +#: best-pkging-practices.dbk:1084 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 " @@ -1618,12 +1597,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1095 +#: best-pkging-practices.dbk:1094 msgid "Boolean templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1099 +#: best-pkging-practices.dbk:1098 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 " @@ -1632,19 +1611,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1107 +#: best-pkging-practices.dbk:1106 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:1115 +#: best-pkging-practices.dbk:1114 msgid "Select/Multiselect" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1119 +#: best-pkging-practices.dbk:1118 msgid "" "The short description is a prompt and <emphasis " "role=\"strong\">not</emphasis> a title. Do <emphasis " @@ -1653,7 +1632,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1127 +#: best-pkging-practices.dbk:1126 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 " @@ -1662,24 +1641,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1137 +#: best-pkging-practices.dbk:1136 msgid "Notes" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1141 +#: best-pkging-practices.dbk:1140 msgid "The short description should be considered to be a *title*." msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1146 +#: best-pkging-practices.dbk:1145 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:1152 +#: best-pkging-practices.dbk:1151 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: " @@ -1691,12 +1670,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1167 +#: best-pkging-practices.dbk:1166 msgid "Choices field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1169 +#: best-pkging-practices.dbk:1168 msgid "" "If the Choices are likely to change often, please consider using the " "__Choices trick. This will split each individual choice into a single " @@ -1704,12 +1683,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1176 best-pkging-practices.dbk:1214 +#: best-pkging-practices.dbk:1175 best-pkging-practices.dbk:1213 msgid "Default field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1178 +#: best-pkging-practices.dbk:1177 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 " @@ -1717,7 +1696,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1183 +#: best-pkging-practices.dbk:1182 msgid "" "This special field allow translators to put the most appropriate choice " "according to their own language. It will become the default choice when " @@ -1726,15 +1705,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1189 +#: best-pkging-practices.dbk:1188 msgid "Example, taken from the geneweb package templates:" msgstr "" # type: Content of: <chapter><section><section><section><screen> -#: best-pkging-practices.dbk:1192 +#: best-pkging-practices.dbk:1191 #, no-wrap msgid "" -": geneweb/lang\n" +"Template: geneweb/lang\n" "Type: select\n" "__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech " "(cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), " @@ -1750,7 +1729,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1203 +#: best-pkging-practices.dbk:1202 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 " @@ -1758,21 +1737,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1208 +#: best-pkging-practices.dbk:1207 msgid "" "The comments are needed as the DefaultChoice 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:1216 +#: best-pkging-practices.dbk:1215 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:1220 +#: best-pkging-practices.dbk:1219 msgid "" "If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, " "see 2.2), consider making this field translatable, if you think it may be " @@ -1780,7 +1759,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1225 +#: best-pkging-practices.dbk:1224 msgid "" "If the default value may vary depending on language/country (for instance " "the default value for a language choice), consider using the special " @@ -1790,17 +1769,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1237 +#: best-pkging-practices.dbk:1236 msgid "Internationalization" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1239 +#: best-pkging-practices.dbk:1238 msgid "Handling debconf translations" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1241 +#: best-pkging-practices.dbk:1240 msgid "" "Like porters, translators have a difficult task. They work on many packages " "and must collaborate with many different maintainers. Moreover, most of the " @@ -1809,7 +1788,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1247 +#: best-pkging-practices.dbk:1246 msgid "" "The goal of <systemitem role=\"package\">debconf</systemitem> was to make " "packages configuration easier for maintainers and for users. Originally, " @@ -1823,7 +1802,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1257 +#: best-pkging-practices.dbk:1256 msgid "" "Using <systemitem role=\"package\">po-debconf</systemitem>, the translation " "is stored in <filename>po</filename> files (drawing from " @@ -1840,12 +1819,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1273 +#: best-pkging-practices.dbk:1272 msgid "Internationalized documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1275 +#: best-pkging-practices.dbk:1274 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 " @@ -1853,7 +1832,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1280 +#: best-pkging-practices.dbk:1279 msgid "" "If you maintain documentation of any size, its easier for translators if " "they have access to a source control system. That lets translators see the " @@ -1861,18 +1840,16 @@ msgid "" "they can see what needs to be retranslated. It is recommended that the " "translated documentation maintain a note about what source control revision " "the translation is based on. An interesting system is provided by <ulink " -"url=\"http://cvs.debian.org/boot-floppies/documentation/doc-check?rev=HEAD\\|[amp " -"]\\|content-type=text/vnd.viewcvs-markup\">doc-check</ulink> in the " -"<systemitem role=\"package\">boot-floppies</systemitem> package, which shows " -"an overview of the translation status for any given language, using " -"structured comments for the current revision of the file to be translated " -"and, for a translated file, the revision of the original file the " -"translation is based on. You might wish to adapt and provide that in your " -"CVS area." +"url=\"&url-i18n-doc-check;\">doc-check</ulink> in the <systemitem " +"role=\"package\">boot-floppies</systemitem> package, which shows an overview " +"of the translation status for any given language, using structured comments " +"for the current revision of the file to be translated and, for a translated " +"file, the revision of the original file the translation is based on. You " +"might wish to adapt and provide that in your CVS area." msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1295 +#: best-pkging-practices.dbk:1293 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 " @@ -1881,36 +1858,35 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1305 +#: best-pkging-practices.dbk:1303 msgid "Common packaging situations" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1307 +#: best-pkging-practices.dbk:1314 msgid "Packages using <command>autoconf</command>/<command>automake</command>" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1309 +#: best-pkging-practices.dbk:1316 msgid "" "Keeping <command>autoconf</command>'s <filename>config.sub</filename> and " "<filename>config.guess</filename> files up to date is critical for porters, " "especially on more volatile architectures. Some very good packaging " "practices for any package using <command>autoconf</command> and/or " -"<command>automake</command> have been synthesized in " -"<filename>/usr/share/doc/autotools-dev/README.Debian.gz</filename> from the " -"<systemitem role=\"package\">autotools-dev</systemitem> package. You're " -"strongly encouraged to read this file and to follow the given " +"<command>automake</command> have been synthesized in &file-bpp-autotools; " +"from the <systemitem role=\"package\">autotools-dev</systemitem> package. " +"You're strongly encouraged to read this file and to follow the given " "recommendations." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1321 +#: best-pkging-practices.dbk:1328 msgid "Libraries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1323 +#: best-pkging-practices.dbk:1330 msgid "" "Libraries are always difficult to package for various reasons. The policy " "imposes many constraints to ease their maintenance and to make sure upgrades " @@ -1919,28 +1895,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1329 +#: best-pkging-practices.dbk:1336 msgid "" "Good practices for library packaging have been grouped in <ulink " -"url=\"http://www.netfort.gr.jp/~dancer/column/libpkg-guide/\">the library " -"packaging guide</ulink>." +"url=\"&url-libpkg-guide;\">the library packaging guide</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1336 +#: best-pkging-practices.dbk:1343 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1338 +#: best-pkging-practices.dbk:1345 msgid "" -"Be sure to follow the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-docs.html\">Policy on " -"documentation</ulink>." +"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:1343 +#: best-pkging-practices.dbk:1350 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 " @@ -1948,7 +1922,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1348 +#: best-pkging-practices.dbk:1355 msgid "" "Policy specifies that documentation should be shipped in HTML format. We " "also recommend shipping documentation in PDF and plain text format if " @@ -1958,7 +1932,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1355 +#: best-pkging-practices.dbk:1362 msgid "" "Major shipped manuals should register themselves with <systemitem " "role=\"package\">doc-base</systemitem> on installation. See the <systemitem " @@ -1967,22 +1941,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1363 +#: best-pkging-practices.dbk:1370 msgid "Specific types of packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1365 +#: best-pkging-practices.dbk:1372 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:1371 +#: best-pkging-practices.dbk:1378 msgid "" -"Perl related packages have a <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/perl-policy/\">Perl " +"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl " "policy</ulink>, some examples of packages following that policy are " "<systemitem role=\"package\">libdbd-pg-perl</systemitem> (binary perl " "module) or <systemitem role=\"package\">libmldbm-perl</systemitem> (arch " @@ -1990,40 +1963,37 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1380 +#: best-pkging-practices.dbk:1387 msgid "" -"Python related packages have their python policy; see " -"<filename>/usr/share/doc/python/python-policy.txt.gz</filename> in the " -"<systemitem role=\"package\">python</systemitem> package." +"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:1387 +#: best-pkging-practices.dbk:1394 msgid "" -"Emacs related packages have the <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/debian-emacs-policy\">emacs " +"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:1394 +#: best-pkging-practices.dbk:1401 msgid "" -"Java related packages have their <ulink " -"url=\"http://www.debian.org/doc/packaging-manuals/java-policy/\">java " +"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:1401 +#: best-pkging-practices.dbk:1408 msgid "" -"Ocaml related packages have their own policy, found in " -"<filename>/usr/share/doc/ocaml/ocaml_packaging_policy.gz</filename> from the " -"<systemitem role=\"package\">ocaml</systemitem> package. A good example is " -"the <systemitem role=\"package\">camlzip</systemitem> source package." +"Ocaml related packages have their own policy, found in &file-ocaml-policy; " +"from the <systemitem role=\"package\">ocaml</systemitem> package. A good " +"example is the <systemitem role=\"package\">camlzip</systemitem> source " +"package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1409 +#: best-pkging-practices.dbk:1416 msgid "" "Packages providing XML or SGML DTDs should conform to the recommendations " "found in the <systemitem role=\"package\">sgml-base-doc</systemitem> " @@ -2031,20 +2001,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1415 +#: best-pkging-practices.dbk:1422 msgid "" "Lisp packages should register themselves with <systemitem " "role=\"package\">common-lisp-controller</systemitem>, about which see " -"<filename>/usr/share/doc/common-lisp-controller/README.packaging</filename>." +"&file-lisp-controller;." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1424 +#: best-pkging-practices.dbk:1452 msgid "Architecture-independent data" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1426 +#: best-pkging-practices.dbk:1454 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, " @@ -2054,7 +2024,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1433 +#: best-pkging-practices.dbk:1461 msgid "" "However, if the size of the data is considerable, consider splitting it out " "into a separate, architecture-independent package (_all.deb). By doing " @@ -2068,30 +2038,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1445 +#: best-pkging-practices.dbk:1473 msgid "Needing a certain locale during build" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1447 +#: best-pkging-practices.dbk:1475 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:1451 +#: best-pkging-practices.dbk:1479 msgid "" -"If you set LOCPATH to the equivalent of /usr/lib/locale, and LC_ALL to the " +"If you set <varname>LOCPATH</varname> to the equivalent of " +"<filename>/usr/lib/locale</filename>, and <varname>LC_ALL</varname> to the " "name of the locale you generate, you should get what you want without being " "root. Something like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1456 +#: best-pkging-practices.dbk:1484 #, no-wrap msgid "" -"=debian/tmpdir/usr/lib/locale\n" +"LOCALE_PATH=debian/tmpdir/usr/lib/locale\n" "LOCALE_NAME=en_IN\n" "LOCALE_CHARSET=UTF-8\n" "\n" @@ -2104,12 +2075,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1469 +#: best-pkging-practices.dbk:1497 msgid "Make transition packages deborphan compliant" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1471 +#: best-pkging-practices.dbk:1499 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 " @@ -2119,7 +2090,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1478 +#: best-pkging-practices.dbk:1506 msgid "" "For example, with --guess-dummy, deborphan tries to search all transitional " "packages which were needed for upgrade but which can now safely be removed. " @@ -2128,53 +2099,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1484 +#: best-pkging-practices.dbk:1512 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><screen> -#: best-pkging-practices.dbk:1488 -#, no-wrap -msgid "-cache search .|grep dummy" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1491 -msgid "or" -msgstr "" - -# type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1494 -#, no-wrap -msgid "-cache search .|grep transitional" -msgstr "" - -# type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1497 -msgid "." +"to your short description. If you are looking for examples, just run: " +"<command>apt-cache search .|grep dummy</command> or <command>apt-cache " +"search .|grep transitional</command>." msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1502 +#: best-pkging-practices.dbk:1520 msgid "Best practices for <filename>orig.tar.gz</filename> files" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1504 +#: best-pkging-practices.dbk:1522 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:1508 +#: best-pkging-practices.dbk:1526 msgid "Pristine source" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1510 +#: best-pkging-practices.dbk:1528 msgid "" "The defining characteristic of a pristine source tarball is that the " ".orig.tar.gz file is byte-for-byte identical to a tarball officially " @@ -2182,7 +2133,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1512 +#: best-pkging-practices.dbk:1530 msgid "" "We cannot prevent upstream authors from changing the tarball they distribute " "without also incrementing the version number, so there can be no guarantee " @@ -2197,7 +2148,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1522 +#: best-pkging-practices.dbk:1540 msgid "" "</footnote> This makes it possible to use checksums to easily verify that " "all changes between Debian's version and upstream's are contained in the " @@ -2207,7 +2158,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1530 +#: best-pkging-practices.dbk:1548 msgid "" "There is no universally accepted guidelines that upstream authors follow " "regarding to the directory structure inside their tarball, but " @@ -2217,18 +2168,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1538 +#: best-pkging-practices.dbk:1556 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:1541 +#: best-pkging-practices.dbk:1559 #, no-wrap -msgid "path/to/<packagename>_<upstream-version>.orig.tar.gz | tar xf -" +msgid "" +"zcat path/to/<packagename>_<upstream-version>.orig.tar.gz | tar " +"xf -" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1546 +#: best-pkging-practices.dbk:1564 msgid "" "If, after this, the temporary directory contains nothing but one directory " "and no other files, <command>dpkg-source</command> renames that directory to " @@ -2238,7 +2191,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1555 +#: best-pkging-practices.dbk:1573 msgid "" "Otherwise, the upstream tarball must have been packaged without a common " "top-level directory (shame on the upstream author!). In this case, " @@ -2248,12 +2201,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1566 +#: best-pkging-practices.dbk:1584 msgid "Repackaged upstream source" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1568 +#: best-pkging-practices.dbk:1586 msgid "" "You <emphasis role=\"strong\">should</emphasis> upload packages with a " "pristine source tarball if possible, but there are various reasons why it " @@ -2263,7 +2216,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1575 +#: best-pkging-practices.dbk:1593 msgid "" "In these cases the developer must construct a suitable .orig.tar.gz file " "himself. We refer to such a tarball as a repackaged upstream source. Note " @@ -2275,7 +2228,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1584 +#: best-pkging-practices.dbk:1602 msgid "" "There may be cases where it is desirable to repackage the source even though " "upstream distributes a <literal>.tar.gz</literal> that could in principle be " @@ -2287,12 +2240,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1593 +#: best-pkging-practices.dbk:1611 msgid "A repackaged .orig.tar.gz" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1598 +#: best-pkging-practices.dbk:1616 msgid "" "<emphasis role=\"strong\">must</emphasis> contain detailed information how " "the repackaged source was obtained, and how this can be reproduced in the " @@ -2300,20 +2253,21 @@ msgid "" "<literal>get-orig-source</literal> target in your " "<filename>debian/rules</filename> file that repeats the process, as " "described in the Policy Manual, <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules\">Main " -"building script: debian/rules</ulink>." +"url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building " +"script: debian/rules</ulink>." msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote> -#: best-pkging-practices.dbk:1610 +#: best-pkging-practices.dbk:1628 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 " "you. <footnote>" msgstr "" +#. or similarly named # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para> -#: best-pkging-practices.dbk:1612 +#: best-pkging-practices.dbk:1630 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 " @@ -2325,7 +2279,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1623 +#: best-pkging-practices.dbk:1642 msgid "" "<emphasis role=\"strong\">should</emphasis>, except where impossible for " "legal reasons, preserve the entire building and portablility infrastructure " @@ -2337,7 +2291,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1632 +#: best-pkging-practices.dbk:1651 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 " @@ -2346,7 +2300,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1639 +#: best-pkging-practices.dbk:1658 msgid "" "<emphasis role=\"strong\">should</emphasis> use " "<literal><packagename>-<upstream-version>.orig</literal> as the " @@ -2355,14 +2309,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1647 +#: best-pkging-practices.dbk:1666 msgid "" "<emphasis role=\"strong\">should</emphasis> be gzipped with maximal " "compression." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1652 +#: best-pkging-practices.dbk:1671 msgid "" "The canonical way to meet the latter two points is to let " "<literal>dpkg-source -b</literal> construct the repackaged tarball from an " @@ -2370,12 +2324,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1658 +#: best-pkging-practices.dbk:1677 msgid "Changing binary files in <literal>diff.gz</literal>" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1660 +#: best-pkging-practices.dbk:1679 msgid "" "Sometimes it is necessary to change binary files contained in the original " "tarball, or to add binary files that are not in it. If this is done by " @@ -2388,7 +2342,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1667 +#: best-pkging-practices.dbk:1686 msgid "" "The file should have a name that makes it clear which binary file it " "encodes. Usually, some postfix indicating the encoding should be appended " @@ -2398,25 +2352,15 @@ msgid "" "<literal>pack</literal> function. The code could look like" msgstr "" -# type: Content of: <chapter><section><section><section><para><footnote><screen> -#: best-pkging-practices.dbk:1673 -#, no-wrap -msgid "" -"-file: perl -ne 'print(pack u, $$_);'\n" -"$(file) > $(file).uuencoded uudecode-file: perl -ne 'print(unpack u, " -"$$_);'\n" -"$(file).uuencoded > $(file)" -msgstr "" - # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1675 +#: best-pkging-practices.dbk:1694 msgid "" -"</footnote>. The file would then be decoded and copied to its place during " -"the build process. Thus the change will be visible quite easy." +"&example-uu; </footnote>. The file would then be decoded and copied to its " +"place during the build process. Thus the change will be visible quite easy." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1680 +#: best-pkging-practices.dbk:1700 msgid "" "Some packages use <command>dbs</command> to manage patches to their upstream " "source, and always create a new <literal>orig.tar.gz</literal> file that " @@ -2428,12 +2372,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1693 +#: best-pkging-practices.dbk:1713 msgid "Best practices for debug packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1695 +#: best-pkging-practices.dbk:1715 msgid "" "A debug package is a package with a name ending in -dbg, that contains " "additional information that gdb can use. Since Debian binaries are stripped " @@ -2444,7 +2388,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1703 +#: best-pkging-practices.dbk:1723 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 " @@ -2457,7 +2401,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1713 +#: best-pkging-practices.dbk:1733 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 " @@ -2472,7 +2416,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1725 +#: best-pkging-practices.dbk:1745 msgid "" "The debugging symbols can be extracted from an object file using objcopy " "--only-keep-debug. Then the object file can be stripped, and objcopy " @@ -2482,7 +2426,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1732 +#: best-pkging-practices.dbk:1752 msgid "" "The dh_strip command in debhelper supports creating debug packages, and can " "take care of using objcopy to separate out the debugging symbols for you. " @@ -2492,7 +2436,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1739 +#: best-pkging-practices.dbk:1759 msgid "" "Note that the Debian package should depend on the package that it provides " "debugging symbols for, and this dependency should be versioned. For " @@ -2500,7 +2444,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1743 +#: best-pkging-practices.dbk:1763 #, no-wrap -msgid ": libfoo-dbg (= ${binary:Version})" +msgid "Depends: libfoo-dbg (= ${binary:Version})" msgstr "" diff --git a/po4a/po/beyond-pkging.pot b/po4a/po/beyond-pkging.pot index 586c3ca..7b45734 100644 --- a/po4a/po/beyond-pkging.pot +++ b/po4a/po/beyond-pkging.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,12 +15,12 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: beyond-pkging.dbk:5 +#: beyond-pkging.dbk:7 msgid "Beyond Packaging" msgstr "" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:7 +#: beyond-pkging.dbk:9 msgid "" "Debian is about a lot more than just packaging software and maintaining " "those packages. This chapter contains information about ways, often really " @@ -29,7 +29,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: beyond-pkging.dbk:12 +#: beyond-pkging.dbk:14 msgid "" "As a volunteer organization, Debian relies on the discretion of its members " "in choosing what they want to work on and in choosing the most critical " @@ -37,12 +37,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:17 +#: beyond-pkging.dbk:19 msgid "Bug reporting" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:19 +#: beyond-pkging.dbk:21 msgid "" "We encourage you to file bugs as you find them in Debian packages. In fact, " "Debian developers are often the first line testers. Finding and reporting " @@ -50,15 +50,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:24 +#: beyond-pkging.dbk:26 msgid "" -"Read the <ulink url=\"http://www.debian.org/Bugs/Reporting\">instructions " -"for reporting bugs</ulink> in the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>." +"Read the <ulink url=\"&url-bts-report;\">instructions for reporting " +"bugs</ulink> in the Debian <ulink url=\"&url-bts;\">bug tracking " +"system</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:29 +#: beyond-pkging.dbk:31 msgid "" "Try to submit the bug from a normal user account at which you are likely to " "receive mail, so that people can reach you if they need further information " @@ -66,7 +66,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:34 +#: beyond-pkging.dbk:36 msgid "" "You can use a tool like <citerefentry> " "<refentrytitle>reportbug</refentrytitle> <manvolnum>1</manvolnum> " @@ -75,11 +75,11 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:39 +#: beyond-pkging.dbk:41 msgid "" "Make sure the bug is not already filed against a package. Each package has " "a bug list easily reachable at " -"<literal>http://bugs.debian.org/<replaceable>packagename</replaceable></literal> " +"<literal>http://&bugs-host;/<replaceable>packagename</replaceable></literal> " "Utilities like <citerefentry> <refentrytitle>querybts</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> can also provide you with this " "information (and <command>reportbug</command> will usually invoke " @@ -87,7 +87,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:48 +#: beyond-pkging.dbk:50 msgid "" "Try to direct your bugs to the proper location. When for example your bug " "is about a package which overwrites files from another package, check the " @@ -96,7 +96,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:54 +#: beyond-pkging.dbk:56 msgid "" "For extra credit, you can go through other packages, merging bugs which are " "reported more than once, or tagging bugs `fixed' when they have already been " @@ -106,22 +106,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:61 +#: beyond-pkging.dbk:63 msgid "" "From time to time you may want to check what has been going on with the bug " "reports that you submitted. Take this opportunity to close those that you " "can't reproduce anymore. To find out all the bugs you submitted, you just " "have to visit " -"<literal>http://bugs.debian.org/from:<replaceable><your-email-addr></replaceable></literal>." +"<literal>http://&bugs-host;/from:<replaceable><your-email-addr></replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:68 +#: beyond-pkging.dbk:70 msgid "Reporting lots of bugs at once (mass bug filing)" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:70 +#: beyond-pkging.dbk:72 msgid "" "Reporting a great number of bugs for the same problem on a great number of " "different packages — i.e., more than 10 — is a deprecated practice. Take " @@ -132,46 +132,45 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:77 +#: beyond-pkging.dbk:79 msgid "" "If you report more than 10 bugs on the same topic at once, it is recommended " -"that you send a message to <email>debian-devel@lists.debian.org</email> " -"describing your intention before submitting the report, and mentioning the " -"fact in the subject of your mail. This will allow other developers to " -"verify that the bug is a real problem. In addition, it will help prevent a " -"situation in which several maintainers start filing the same bug report " -"simultaneously." +"that you send a message to &email-debian-devel; describing your intention " +"before submitting the report, and mentioning the fact in the subject of your " +"mail. This will allow other developers to verify that the bug is a real " +"problem. In addition, it will help prevent a situation in which several " +"maintainers start filing the same bug report simultaneously." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:85 +#: beyond-pkging.dbk:87 msgid "" "Please use the programms <command>dd-list</command> and if appropriate " "<command>whodepends</command> (from the package devscripts) to generate a " "list of all affected packages, and include the output in your mail to " -"<email>debian-devel@lists.debian.org</email>." +"&email-debian-devel;." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:91 +#: beyond-pkging.dbk:93 msgid "" "Note that when sending lots of bugs on the same subject, you should send the " -"bug report to <email>maintonly@bugs.debian.org</email> so that the bug " -"report is not forwarded to the bug distribution mailing list." +"bug report to <email>maintonly@&bugs-host;</email> so that the bug report is " +"not forwarded to the bug distribution mailing list." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:100 +#: beyond-pkging.dbk:102 msgid "Quality Assurance effort" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:102 +#: beyond-pkging.dbk:104 msgid "Daily work" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:104 +#: beyond-pkging.dbk:106 msgid "" "Even though there is a dedicated group of people for Quality Assurance, QA " "duties are not reserved solely for them. You can participate in this effort " @@ -180,30 +179,29 @@ msgid "" "possible, then you should consider orphaning some of your packages (see " "<xref linkend=\"orphaning\"/> ). Alternatively, you may ask the help of " "other people in order to catch up with the backlog of bugs that you have " -"(you can ask for help on <email>debian-qa@lists.debian.org</email> or " -"<email>debian-devel@lists.debian.org</email>). At the same time, you can " -"look for co-maintainers (see <xref linkend=\"collaborative-maint\"/> )." +"(you can ask for help on &email-debian-qa; or &email-debian-devel;). At the " +"same time, you can look for co-maintainers (see <xref " +"linkend=\"collaborative-maint\"/> )." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:118 +#: beyond-pkging.dbk:120 msgid "Bug squashing parties" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:120 +#: beyond-pkging.dbk:122 msgid "" "From time to time the QA group organizes bug squashing parties to get rid of " "as many problems as possible. They are announced on " -"<email>debian-devel-announce@lists.debian.org</email> and the announcement " -"explains which area will be the focus of the party: usually they focus on " -"release critical bugs but it may happen that they decide to help finish a " -"major upgrade (like a new perl version which requires recompilation of all " -"the binary modules)." +"&email-debian-devel-announce; and the announcement explains which area will " +"be the focus of the party: usually they focus on release critical bugs but " +"it may happen that they decide to help finish a major upgrade (like a new " +"perl version which requires recompilation of all the binary modules)." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:129 +#: beyond-pkging.dbk:131 msgid "" "The rules for non-maintainer uploads differ during the parties because the " "announcement of the party is considered prior notice for NMU. If you have " @@ -216,7 +214,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:138 +#: beyond-pkging.dbk:140 msgid "" "People participating in the party have special rules for NMU, they can NMU " "without prior notice if they upload their NMU to DELAYED/3-day at least. " @@ -227,19 +225,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:145 +#: beyond-pkging.dbk:147 msgid "" "If you don't feel confident about doing an NMU, just send a patch to the " "BTS. It's far better than a broken NMU." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:153 +#: beyond-pkging.dbk:155 msgid "Contacting other maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:155 +#: beyond-pkging.dbk:157 msgid "" "During your lifetime within Debian, you will have to contact other " "maintainers for various reasons. You may want to discuss a new way of " @@ -248,32 +246,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:161 +#: beyond-pkging.dbk:163 msgid "" "Looking up the email address of the maintainer for the package can be " "distracting. Fortunately, there is a simple email alias, " -"<literal><package>@packages.debian.org</literal>, which provides a way " -"to email the maintainer, whatever their individual email address (or " -"addresses) may be. Replace <literal><package></literal> with the " -"name of a source or a binary package." +"<literal><package>@&packages-host;</literal>, which provides a way to " +"email the maintainer, whatever their individual email address (or addresses) " +"may be. Replace <literal><package></literal> with the name of a " +"source or a binary package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:169 +#: beyond-pkging.dbk:171 msgid "" "You may also be interested in contacting the persons who are subscribed to a " "given source package via <xref linkend=\"pkg-tracking-system\"/> . You can " -"do so by using the <literal><package>@packages.qa.debian.org</literal> " -"email address." +"do so by using the <literal><package>@&pts-host;</literal> email " +"address." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:177 +#: beyond-pkging.dbk:180 msgid "Dealing with inactive and/or unreachable maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:179 +#: beyond-pkging.dbk:182 msgid "" "If you notice that a package is lacking maintenance, you should make sure " "that the maintainer is active and will continue to work on their packages. " @@ -283,32 +281,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:186 +#: beyond-pkging.dbk:189 msgid "" "There is a simple system (the MIA database) in which information about " "maintainers who are deemed Missing In Action is recorded. When a member of " "the QA group contacts an inactive maintainer or finds more information about " "one, this is recorded in the MIA database. This system is available in " "/org/qa.debian.org/mia on the host qa.debian.org, and can be queried with a " -"tool known as <command>mia-query</command>. Use" -msgstr "" - -# type: Content of: <chapter><section><screen> -#: beyond-pkging.dbk:194 -#, no-wrap -msgid "-query --help" -msgstr "" - -# type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:197 -msgid "" -"to see how to query the database. If you find that no information has been " -"recorded about an inactive maintainer yet, or that you can add more " -"information, you should generally proceed as follows." +"tool known as <command>mia-query</command>. Use <command>mia-query " +"--help</command> to see how to query the database. If you find that no " +"information has been recorded about an inactive maintainer yet, or that you " +"can add more information, you should generally proceed as follows." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:202 +#: beyond-pkging.dbk:200 msgid "" "The first step is to politely contact the maintainer, and wait a reasonable " "time for a response. It is quite hard to define reasonable time, but it is " @@ -317,7 +304,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:208 +#: beyond-pkging.dbk:206 msgid "" "If the maintainer doesn't reply within four weeks (a month), one can assume " "that a response will probably not happen. If that happens, you should " @@ -326,17 +313,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:216 +#: beyond-pkging.dbk:214 msgid "" "The echelon information available through the <ulink " -"url=\"https://db.debian.org/\">developers' LDAP database</ulink>, which " -"indicates when the developer last posted to a Debian mailing list. (This " -"includes uploads via debian-*-changes lists.) Also, remember to check " -"whether the maintainer is marked as on vacation in the database." +"url=\"&url-debian-db;\">developers' LDAP database</ulink>, which indicates " +"when the developer last posted to a Debian mailing list. (This includes " +"uploads via debian-*-changes lists.) Also, remember to check whether the " +"maintainer is marked as on vacation in the database." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:225 +#: beyond-pkging.dbk:223 msgid "" "The number of packages this maintainer is responsible for, and the condition " "of those packages. In particular, are there any RC bugs that have been open " @@ -346,7 +333,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: beyond-pkging.dbk:234 +#: beyond-pkging.dbk:232 msgid "" "Is there any activity of the maintainer outside of Debian? For example, they " "might have posted something recently to non-Debian mailing lists or news " @@ -354,7 +341,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:241 +#: beyond-pkging.dbk:239 msgid "" "A bit of a problem are packages which were sponsored — the maintainer is not " "an official Debian developer. The echelon information is not available for " @@ -365,28 +352,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:249 +#: beyond-pkging.dbk:247 msgid "" -"It is also allowed to post a query to " -"<email>debian-devel@lists.debian.org</email>, asking if anyone is aware of " -"the whereabouts of the missing maintainer. Please Cc: the person in " -"question." +"It is also allowed to post a query to &email-debian-devel;, asking if anyone " +"is aware of the whereabouts of the missing maintainer. Please Cc: the " +"person in question." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:254 +#: beyond-pkging.dbk:252 msgid "" -"Once you have gathered all of this, you can contact " -"<email>mia@qa.debian.org</email>. People on this alias will use the " -"information you provide in order to decide how to proceed. For example, " -"they might orphan one or all of the packages of the maintainer. If a " -"package has been NMUed, they might prefer to contact the NMUer before " -"orphaning the package — perhaps the person who has done the NMU is " -"interested in the package." +"Once you have gathered all of this, you can contact &email-mia;. People on " +"this alias will use the information you provide in order to decide how to " +"proceed. For example, they might orphan one or all of the packages of the " +"maintainer. If a package has been NMUed, they might prefer to contact the " +"NMUer before orphaning the package — perhaps the person who has done the NMU " +"is interested in the package." msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:262 +#: beyond-pkging.dbk:260 msgid "" "One last word: please remember to be polite. We are all volunteers and " "cannot dedicate all of our time to Debian. Also, you are not aware of the " @@ -397,7 +382,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:270 +#: beyond-pkging.dbk:268 msgid "" "On the other hand, although we are volunteers, we do have a responsibility. " "So you can stress the importance of the greater good — if a maintainer does " @@ -406,21 +391,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:276 +#: beyond-pkging.dbk:274 msgid "" "If you are interested in working in the MIA team, please have a look at the " "README file in /org/qa.debian.org/mia on qa.debian.org where the technical " -"details and the MIA procedures are documented and contact " -"<email>mia@qa.debian.org</email>." +"details and the MIA procedures are documented and contact &email-mia;." msgstr "" # type: Content of: <chapter><section><title> -#: beyond-pkging.dbk:284 +#: beyond-pkging.dbk:282 msgid "Interacting with prospective Debian developers" msgstr "" # type: Content of: <chapter><section><para> -#: beyond-pkging.dbk:286 +#: beyond-pkging.dbk:284 msgid "" "Debian's success depends on its ability to attract and retain new and " "talented volunteers. If you are an experienced developer, we recommend that " @@ -429,12 +413,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:292 +#: beyond-pkging.dbk:290 msgid "Sponsoring packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:294 +#: beyond-pkging.dbk:292 msgid "" "Sponsoring a package means uploading a package for a maintainer who is not " "able to do it on their own, a new maintainer applicant. Sponsoring a " @@ -442,7 +426,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:299 +#: beyond-pkging.dbk:303 msgid "" "New maintainers usually have certain difficulties creating Debian packages — " "this is quite understandable. That is why the sponsor is there, to check " @@ -452,7 +436,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:306 +#: beyond-pkging.dbk:310 msgid "" "Sponsoring merely by signing the upload or just recompiling is <emphasis " "role=\"strong\">definitely not recommended</emphasis>. You need to build " @@ -463,7 +447,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:313 +#: beyond-pkging.dbk:317 msgid "" "If you are an application manager for a prospective developer, you can also " "be their sponsor. That way you can also verify how the applicant is " @@ -471,12 +455,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:320 +#: beyond-pkging.dbk:324 msgid "Managing sponsored packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:322 +#: beyond-pkging.dbk:326 msgid "" "By uploading a sponsored package to Debian, you are certifying that the " "package meets minimum Debian standards. That implies that you must build " @@ -484,7 +468,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:327 +#: beyond-pkging.dbk:331 msgid "" "You cannot simply upload a binary <filename>.deb</filename> from the " "sponsoree. In theory, you should only ask for the diff file and the " @@ -496,7 +480,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:336 +#: beyond-pkging.dbk:340 msgid "" "Do not be afraid to write the sponsoree back and point out changes that need " "to be made. It often takes several rounds of back-and-forth email before " @@ -504,18 +488,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:341 +#: beyond-pkging.dbk:345 msgid "Once the package meets Debian standards, build and sign it with" msgstr "" # type: Content of: <chapter><section><section><screen> -#: beyond-pkging.dbk:344 +#: beyond-pkging.dbk:348 #, no-wrap -msgid "-buildpackage -k<replaceable>KEY-ID</replaceable>" +msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:347 +#: beyond-pkging.dbk:351 msgid "" "before uploading it to the incoming directory. Of course, you can also use " "any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique " @@ -523,7 +507,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:352 +#: beyond-pkging.dbk:356 msgid "" "The Maintainer field of the <filename>control</filename> file and the " "<filename>changelog</filename> should list the person who did the packaging, " @@ -532,41 +516,39 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:358 +#: beyond-pkging.dbk:362 msgid "" "If you prefer to leave a more evident trace of your sponsorship job, you can " "add a line stating it in the most recent changelog entry." msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:362 +#: beyond-pkging.dbk:366 msgid "" "You are encouraged to keep tabs on the package you sponsor using <xref " "linkend=\"pkg-tracking-system\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:368 +#: beyond-pkging.dbk:372 msgid "Advocating new developers" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:370 +#: beyond-pkging.dbk:374 msgid "" -"See the page about <ulink " -"url=\"http://www.debian.org/devel/join/nm-advocate\">advocating a " +"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a " "prospective developer</ulink> at the Debian web site." msgstr "" # type: Content of: <chapter><section><section><title> -#: beyond-pkging.dbk:377 +#: beyond-pkging.dbk:381 msgid "Handling new maintainer applications" msgstr "" # type: Content of: <chapter><section><section><para> -#: beyond-pkging.dbk:379 +#: beyond-pkging.dbk:383 msgid "" -"Please see <ulink " -"url=\"http://www.debian.org/devel/join/nm-amchecklist\">Checklist for " +"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for " "Application Managers</ulink> at the Debian web site." msgstr "" diff --git a/po4a/po/developer-duties.pot b/po4a/po/developer-duties.pot index 487ca81..74dcb07 100644 --- a/po4a/po/developer-duties.pot +++ b/po4a/po/developer-duties.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,50 +15,50 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: developer-duties.dbk:5 +#: developer-duties.dbk:7 msgid "Debian Developer's Duties" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:7 +#: developer-duties.dbk:9 msgid "Maintaining your Debian information" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:9 +#: developer-duties.dbk:11 msgid "" "There's a LDAP database containing information about Debian developers at " -"<ulink url=\"https://db.debian.org/\"></ulink>. You should enter your " -"information there and update it as it changes. Most notably, make sure that " -"the address where your debian.org email gets forwarded to is always up to " -"date, as well as the address where you get your debian-private subscription " -"if you choose to subscribe there." +"<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information " +"there and update it as it changes. Most notably, make sure that the address " +"where your debian.org email gets forwarded to is always up to date, as well " +"as the address where you get your debian-private subscription if you choose " +"to subscribe there." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:17 +#: developer-duties.dbk:19 msgid "" "For more information about the database, please see <xref " "linkend=\"devel-db\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:23 +#: developer-duties.dbk:25 msgid "Maintaining your public key" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:25 +#: developer-duties.dbk:27 msgid "" "Be very careful with your private keys. Do not place them on any public " "servers or multiuser machines, such as the Debian servers (see <xref " "linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. " "Read the documentation that comes with your software; read the <ulink " -"url=\"http://www.cam.ac.uk.pgp.net/pgpnet/pgp-faq/\">PGP FAQ</ulink>." +"url=\"&url-pgp-faq;\">PGP FAQ</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:32 +#: developer-duties.dbk:34 msgid "" "You need to ensure not only that your key is secure against being stolen, " "but also that it is secure against being lost. Generate and make a copy " @@ -67,33 +67,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:38 +#: developer-duties.dbk:40 msgid "" "If you add signatures to your public key, or add user identities, you can " "update the Debian key ring by sending your key to the key server at " -"<literal>keyring.debian.org</literal>." +"<literal>&keyserver-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:43 +#: developer-duties.dbk:45 msgid "" "If you need to add a completely new key or remove an old key, you need to " "get the new key signed by another developer. If the old key is compromised " "or invalid, you also have to add the revocation certificate. If there is no " "real reason for a new key, the Keyring Maintainers might reject the new " "key. Details can be found at <ulink " -"url=\"http://keyring.debian.org/replacing_keys.html\"></ulink>." +"url=\"http://&keyserver-host;/replacing_keys.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:51 +#: developer-duties.dbk:53 msgid "" "The same key extraction routines discussed in <xref " "linkend=\"registering\"/> apply." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:55 +#: developer-duties.dbk:57 msgid "" "You can find a more in-depth discussion of Debian key maintenance in the " "documentation of the <systemitem " @@ -101,56 +101,54 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:62 +#: developer-duties.dbk:64 msgid "Voting" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:64 +#: developer-duties.dbk:66 msgid "" "Even though Debian isn't really a democracy, we use a democratic process to " "elect our leaders and to approve general resolutions. These procedures are " -"defined by the <ulink " -"url=\"http://www.debian.org/devel/constitution\">Debian " +"defined by the <ulink url=\"&url-constitution;\">Debian " "Constitution</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:70 +#: developer-duties.dbk:72 msgid "" "Other than the yearly leader election, votes are not routinely held, and " "they are not undertaken lightly. Each proposal is first discussed on the " -"<email>debian-vote@lists.debian.org</email> mailing list and it requires " -"several endorsements before the project secretary starts the voting " -"procedure." +"&email-debian-vote; mailing list and it requires several endorsements before " +"the project secretary starts the voting procedure." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:76 +#: developer-duties.dbk:78 msgid "" "You don't have to track the pre-vote discussions, as the secretary will " -"issue several calls for votes on " -"<email>debian-devel-announce@lists.debian.org</email> (and all developers " -"are expected to be subscribed to that list). Democracy doesn't work well if " -"people don't take part in the vote, which is why we encourage all developers " -"to vote. Voting is conducted via GPG-signed/encrypted email messages." +"issue several calls for votes on &email-debian-devel-announce; (and all " +"developers are expected to be subscribed to that list). Democracy doesn't " +"work well if people don't take part in the vote, which is why we encourage " +"all developers to vote. Voting is conducted via GPG-signed/encrypted email " +"messages." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:84 +#: developer-duties.dbk:86 msgid "" "The list of all proposals (past and current) is available on the <ulink " -"url=\"http://www.debian.org/vote/\">Debian Voting Information</ulink> page, " -"along with information on how to make, second and vote on proposals." +"url=\"&url-vote;\">Debian Voting Information</ulink> page, along with " +"information on how to make, second and vote on proposals." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:91 +#: developer-duties.dbk:93 msgid "Going on vacation gracefully" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:93 +#: developer-duties.dbk:95 msgid "" "It is common for developers to have periods of absence, whether those are " "planned vacations or simply being buried in other work. The important thing " @@ -160,7 +158,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:100 +#: developer-duties.dbk:102 msgid "" "Usually this means that other developers are allowed to NMU (see <xref " "linkend=\"nmu\"/> ) your package if a big problem (release critical bug, " @@ -170,30 +168,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote> -#: developer-duties.dbk:107 +#: developer-duties.dbk:109 msgid "" "In order to inform the other developers, there are two things that you " -"should do. First send a mail to " -"<email>debian-private@lists.debian.org</email> with [VAC] prepended to the " -"subject of your message<footnote>" +"should do. First send a mail to <email>debian-private@&lists-host;</email> " +"with [VAC] prepended to the subject of your message<footnote>" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: developer-duties.dbk:109 +#: developer-duties.dbk:111 msgid "" "This is so that the message can be easily filtered by people who don't want " "to read vacation notices." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:111 +#: developer-duties.dbk:113 msgid "" "</footnote> and state the period of time when you will be on vacation. You " "can also give some special instructions on what to do if a problem occurs." msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:116 +#: developer-duties.dbk:118 msgid "" "The other thing to do is to mark yourself as on vacation in the <link " "linkend=\"devel-db\">Debian developers' LDAP database</link> (this " @@ -202,22 +199,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:122 +#: developer-duties.dbk:124 msgid "" "Ideally, you should sign up at the <ulink " -"url=\"http://nm.debian.org/gpg.php\">GPG coordination site</ulink> when " -"booking a holiday and check if anyone there is looking for signing. This is " +"url=\"&url-newmaint-db;gpg.php\">GPG coordination site</ulink> when booking " +"a holiday and check if anyone there is looking for signing. This is " "especially important when people go to exotic places where we don't have any " "developers yet but where there are people who are interested in applying." msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:131 +#: developer-duties.dbk:133 msgid "Coordination with upstream developers" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:133 +#: developer-duties.dbk:135 msgid "" "A big part of your job as Debian maintainer will be to stay in contact with " "the upstream developers. Debian users will sometimes report bugs that are " @@ -227,7 +224,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:140 +#: developer-duties.dbk:142 msgid "" "While it's not your job to fix non-Debian specific bugs, you may freely do " "so if you're able. When you make such fixes, be sure to pass them on to the " @@ -237,7 +234,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:147 +#: developer-duties.dbk:149 msgid "" "If you need to modify the upstream sources in order to build a policy " "compliant package, then you should propose a nice fix to the upstream " @@ -247,12 +244,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:156 +#: developer-duties.dbk:158 msgid "Managing release-critical bugs" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:158 +#: developer-duties.dbk:160 msgid "" "Generally you should deal with bug reports on your packages as described in " "<xref linkend=\"bug-handling\"/> . However, there's a special category of " @@ -266,14 +263,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:169 +#: developer-duties.dbk:171 msgid "" -"Developers who are part of the <ulink url=\"http://qa.debian.org/\">Quality " +"Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality " "Assurance</ulink> group are following all such bugs, and trying to help " "whenever possible. If, for any reason, you aren't able fix an RC bug in a " "package of yours within 2 weeks, you should either ask for help by sending a " "mail to the Quality Assurance (QA) group " -"<email>debian-qa@lists.debian.org</email>, or explain your difficulties and " +"<email>debian-qa@&lists-host;</email>, or explain your difficulties and " "present a plan to fix them by sending a mail to the bug report. Otherwise, " "people from the QA group may want to do a Non-Maintainer Upload (see <xref " "linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long " @@ -282,31 +279,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: developer-duties.dbk:184 +#: developer-duties.dbk:186 msgid "Retiring" msgstr "" # type: Content of: <chapter><section><para> -#: developer-duties.dbk:186 +#: developer-duties.dbk:188 msgid "" "If you choose to leave the Debian project, you should make sure you do the " "following steps:" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:192 +#: developer-duties.dbk:194 msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:197 +#: developer-duties.dbk:199 msgid "" "Send an gpg-signed email about why you are leaving the project to " -"<email>debian-private@lists.debian.org</email>." +"<email>debian-private@&lists-host;</email>." msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: developer-duties.dbk:203 +#: developer-duties.dbk:205 msgid "" "Notify the Debian key ring maintainers that you are leaving by opening a " "ticket in Debian RT by sending a mail to keyring@rt.debian.org with the " diff --git a/po4a/po/index.pot b/po4a/po/index.pot index b328a2e..825cd5d 100644 --- a/po4a/po/index.pot +++ b/po4a/po/index.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,42 +15,42 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Attribute 'lang' of: <book> -#: index.dbk:4 +#: index.dbk:6 msgid "en" msgstr "" # type: Content of: <book><title> -#: index.dbk:6 +#: index.dbk:8 msgid "Debian Developer's Reference" msgstr "" # type: Content of: <book><bookinfo><releaseinfo> -#: index.dbk:27 +#: index.dbk:29 msgid "ver. 3.3.9, 16 June, 2007" msgstr "" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:34 +#: index.dbk:36 msgid "Andreas Barth" msgstr "" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:43 +#: index.dbk:45 msgid "Adam Di Carlo" msgstr "" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:48 +#: index.dbk:50 msgid "Raphaël Hertzog" msgstr "" # type: Content of: <book><bookinfo><copyright><holder> -#: index.dbk:53 +#: index.dbk:55 msgid "Christian Schwarz" msgstr "" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:57 +#: index.dbk:59 msgid "" "This manual is free software; you may redistribute it and/or modify it under " "the terms of the GNU General Public License as published by the Free " @@ -59,7 +59,7 @@ msgid "" msgstr "" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:62 +#: index.dbk:64 msgid "" "This is distributed in the hope that it will be useful, but " "<emphasis>without any warranty</emphasis>; without even the implied warranty " @@ -68,18 +68,19 @@ msgid "" msgstr "" # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:68 +#: index.dbk:70 msgid "" -"A copy of the GNU General Public License is available as " -"<filename>/usr/share/common-licenses/GPL</filename> in the Debian GNU/Linux " -"distribution or on the World Wide Web at <ulink " -"url=\"http://www.gnu.org/copyleft/gpl.html\">the GNU web site</ulink>. You " -"can also obtain it by writing to the Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA." +"A copy of the GNU General Public License is available as &file-GPL; in the " +"&debian-formal; distribution or on the World Wide Web at <ulink " +"url=\"&url-gpl;\">the GNU web site</ulink>. You can also obtain it by " +"writing to the &fsf-addr;." msgstr "" +#. TODO: Maybe better: "This document has originally been written +# +#. in English. Translations into different languages are available." # type: Content of: <book><bookinfo><legalnotice><para> -#: index.dbk:76 +#: index.dbk:77 msgid "" "If you want to print this reference, you should use the <ulink " "url=\"developers-reference.pdf\">pdf version</ulink>. This page is also " diff --git a/po4a/po/l10n.pot b/po4a/po/l10n.pot index d09b196..8ca3d75 100644 --- a/po4a/po/l10n.pot +++ b/po4a/po/l10n.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,14 +15,14 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: l10n.dbk:5 +#: l10n.dbk:7 msgid "" "Internationalizing, translating, being internationalized and being " "translated" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:7 +#: l10n.dbk:9 msgid "" "Debian supports an ever-increasing number of natural languages. Even if you " "are a native English speaker and do not speak any other language, it is part " @@ -33,10 +33,10 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:15 +#: l10n.dbk:17 msgid "" "According to <ulink " -"url=\"http://www.debian.org/doc/manuals/intro-i18n/\">Introduction to " +"url=\"http://&www-debian-org;/doc/manuals/intro-i18n/\">Introduction to " "i18n</ulink> from Tomohiro KUBOTA, I18N (internationalization) means " "modification of a software or related technologies so that a software can " "potentially handle multiple languages, customs, and so on in the world. " @@ -45,7 +45,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:24 +#: l10n.dbk:26 msgid "" "l10n and i18n are interconnected, but the difficulties related to each of " "them are very different. It's not really difficult to allow a program to " @@ -56,7 +56,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: l10n.dbk:32 +#: l10n.dbk:34 msgid "" "Setting aside the i18n problems, where no general guideline can be given, " "there is actually no central infrastructure for l10n within Debian which " @@ -65,12 +65,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:38 +#: l10n.dbk:40 msgid "How translations are handled within Debian" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:40 +#: l10n.dbk:42 msgid "" "Handling translation of the texts contained in a package is still a manual " "task, and the process depends on the kind of text you want to see " @@ -78,7 +78,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:44 +#: l10n.dbk:46 msgid "" "For program messages, the gettext infrastructure is used most of the time. " "Most of the time, the translation is handled upstream within projects like " @@ -87,14 +87,14 @@ msgid "" "url=\"http://developer.gnome.org/projects/gtp/\">Gnome translation " "Project</ulink> or the <ulink url=\"http://i18n.kde.org/\">KDE one</ulink>. " "The only centralized resource within Debian is the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " +"url=\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink>, where you can find some statistics about the translation " "files found in the actual packages, but no real infrastructure to ease the " "translation process." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:57 +#: l10n.dbk:59 msgid "" "An effort to translate the package descriptions started long ago, even if " "very little support is offered by the tools to actually use them (i.e., only " @@ -104,18 +104,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:64 +#: l10n.dbk:66 msgid "" "For debconf templates, maintainers should use the po-debconf package to ease " "the work of translators, who could use the DDTP to do their work (but the " "French and Brazilian teams don't). Some statistics can be found both on the " "DDTP site (about what is actually translated), and on the <ulink " -"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation " +"url=\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink> site (about what is integrated in the packages)." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:72 +#: l10n.dbk:74 msgid "" "For web pages, each l10n team has access to the relevant CVS, and the " "statistics are available from the Central Debian translation statistics " @@ -123,7 +123,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:76 +#: l10n.dbk:78 msgid "" "For general documentation about Debian, the process is more or less the same " "as for the web pages (the translators have access to the CVS), but there are " @@ -131,34 +131,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:81 +#: l10n.dbk:83 msgid "" "For package-specific documentation (man pages, info documents, other " "formats), almost everything remains to be done." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:85 +#: l10n.dbk:87 msgid "" "Most notably, the KDE project handles translation of its documentation in " "the same way as its program messages." msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:89 +#: l10n.dbk:91 msgid "" "There is an effort to handle Debian-specific man pages within a <ulink " -"url=\"http://cvs.debian.org/manpages/?cvsroot=debian-doc\">specific CVS " +"url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS " "repository</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:96 +#: l10n.dbk:98 msgid "I18N & L10N FAQ for maintainers" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:98 +#: l10n.dbk:100 msgid "" "This is a list of problems that maintainers may face concerning i18n and " "l10n. While reading this, keep in mind that there is no real consensus on " @@ -168,12 +168,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:105 +#: l10n.dbk:107 msgid "How to get a given text translated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:107 +#: l10n.dbk:109 msgid "" "To translate package descriptions or debconf templates, you have nothing to " "do; the DDTP infrastructure will dispatch the material to translate to " @@ -181,7 +181,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:112 +#: l10n.dbk:114 msgid "" "For all other material (gettext files, man pages, or other documentation), " "the best solution is to put your text somewhere on the Internet, and ask on " @@ -192,12 +192,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:122 +#: l10n.dbk:124 msgid "How to get a given translation reviewed" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:124 +#: l10n.dbk:126 msgid "" "From time to time, individuals translate some texts in your package and will " "ask you for inclusion of the translation in the package. This can become " @@ -208,12 +208,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:134 +#: l10n.dbk:136 msgid "How to get a given translation updated" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:136 +#: l10n.dbk:138 msgid "" "If you have some translations of a given text lying around, each time you " "update the original, you should ask the previous translator to update the " @@ -222,7 +222,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:142 +#: l10n.dbk:144 msgid "" "If the translator is unresponsive, you may ask for help on the corresponding " "l10n mailing list. If everything fails, don't forget to put a warning in " @@ -231,7 +231,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:148 +#: l10n.dbk:150 msgid "" "Avoid removing a translation completely because it is outdated. Old " "documentation is often better than no documentation at all for non-English " @@ -239,12 +239,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:155 +#: l10n.dbk:157 msgid "How to handle a bug report concerning a translation" msgstr "" +#. TODO: add the i18n tag to the bug? # type: Content of: <chapter><section><section><para> -#: l10n.dbk:157 +#: l10n.dbk:159 msgid "" "The best solution may be to mark the bug as forwarded to upstream, and " "forward it to both the previous translator and his/her team (using the " @@ -252,12 +253,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:166 +#: l10n.dbk:169 msgid "I18N & L10N FAQ for translators" msgstr "" # type: Content of: <chapter><section><para> -#: l10n.dbk:168 +#: l10n.dbk:171 msgid "" "While reading this, please keep in mind that there is no general procedure " "within Debian concerning these points, and that in any case, you should " @@ -265,12 +266,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:173 +#: l10n.dbk:176 msgid "How to help the translation effort" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:175 +#: l10n.dbk:178 msgid "" "Choose what you want to translate, make sure that nobody is already working " "on it (using your debian-l10n-XXX mailing list), translate it, get it " @@ -279,12 +280,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: l10n.dbk:183 +#: l10n.dbk:186 msgid "How to provide a translation for inclusion in a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:185 +#: l10n.dbk:188 msgid "" "Make sure your translation is correct (asking for review on your l10n " "mailing list) before providing it for inclusion. It will save time for " @@ -293,7 +294,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: l10n.dbk:191 +#: l10n.dbk:194 msgid "" "The best solution is to file a regular bug containing the translation " "against the package. Make sure to use the 'PATCH' tag, and to not use a " @@ -302,12 +303,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: l10n.dbk:201 +#: l10n.dbk:204 msgid "Best current practice concerning l10n" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:205 +#: l10n.dbk:208 msgid "" "As a maintainer, never edit the translations in any way (even to reformat " "the layout) without asking on the corresponding l10n mailing list. You risk " @@ -316,7 +317,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:213 +#: l10n.dbk:216 msgid "" "As a translator, if you find an error in the original text, make sure to " "report it. Translators are often the most attentive readers of a given " @@ -324,7 +325,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:220 +#: l10n.dbk:223 msgid "" "In any case, remember that the major issue with l10n is that it requires " "several people to cooperate, and that it is very easy to start a flamewar " @@ -335,7 +336,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: l10n.dbk:230 +#: l10n.dbk:233 msgid "" "In any case, cooperation can only be achieved with <emphasis " "role=\"strong\">mutual respect</emphasis>." diff --git a/po4a/po/new-maintainer.pot b/po4a/po/new-maintainer.pot index a48fcef..61b7df9 100644 --- a/po4a/po/new-maintainer.pot +++ b/po4a/po/new-maintainer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,42 +15,40 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: new-maintainer.dbk:5 +#: new-maintainer.dbk:7 msgid "Applying to Become a Maintainer" msgstr "" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:7 +#: new-maintainer.dbk:9 msgid "Getting started" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:9 +#: new-maintainer.dbk:11 msgid "" "So, you've read all the documentation, you've gone through the <ulink " -"url=\"http://www.debian.org/doc/maint-guide/\">Debian New Maintainers' " -"Guide</ulink>, understand what everything in the <systemitem " +"url=\"&url-newmaint-guide;\">Debian New Maintainers' Guide</ulink>, " +"understand what everything in the <systemitem " "role=\"package\">hello</systemitem> example package is for, and you're about " "to Debianize your favorite piece of software. How do you actually become a " "Debian developer so that your work can be incorporated into the Project?" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:17 +#: new-maintainer.dbk:19 msgid "" -"Firstly, subscribe to <email>debian-devel@lists.debian.org</email> if you " -"haven't already. Send the word <literal>subscribe</literal> in the " -"<emphasis>Subject</emphasis> of an email to " -"<email>debian-devel-REQUEST@lists.debian.org</email>. In case of problems, " -"contact the list administrator at " -"<email>listmaster@lists.debian.org</email>. More information on available " -"mailing lists can be found in <xref linkend=\"mailing-lists\"/> . " -"<email>debian-devel-announce@lists.debian.org</email> is another list which " -"is mandatory for anyone who wishes to follow Debian's development." +"Firstly, subscribe to &email-debian-devel; if you haven't already. Send the " +"word <literal>subscribe</literal> in the <emphasis>Subject</emphasis> of an " +"email to &email-debian-devel-req;. In case of problems, contact the list " +"administrator at &email-listmaster;. More information on available mailing " +"lists can be found in <xref linkend=\"mailing-lists\"/> . " +"&email-debian-devel-announce; is another list which is mandatory for anyone " +"who wishes to follow Debian's development." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:28 +#: new-maintainer.dbk:29 msgid "" "You should subscribe and lurk (that is, read without posting) for a bit " "before doing any coding, and you should post about your intentions to work " @@ -58,35 +56,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:33 +#: new-maintainer.dbk:34 msgid "" -"Another good list to subscribe to is " -"<email>debian-mentors@lists.debian.org</email>. See <xref " +"Another good list to subscribe to is &email-debian-mentors;. See <xref " "linkend=\"mentors\"/> for details. The IRC channel " "<literal>#debian</literal> can also be helpful; see <xref " "linkend=\"irc-channels\"/> ." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:39 +#: new-maintainer.dbk:40 msgid "" -"When you know how you want to contribute to Debian GNU/Linux, you should get " +"When you know how you want to contribute to &debian-formal;, you should get " "in contact with existing Debian maintainers who are working on similar " "tasks. That way, you can learn from experienced developers. For example, " "if you are interested in packaging existing software for Debian, you should " "try to get a sponsor. A sponsor will work together with you on your package " "and upload it to the Debian archive once they are happy with the packaging " "work you have done. You can find a sponsor by mailing the " -"<email>debian-mentors@lists.debian.org</email> mailing list, describing your " -"package and yourself and asking for a sponsor (see <xref " -"linkend=\"sponsoring\"/> and <ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"for more information on sponsoring). On the other hand, if you are " -"interested in porting Debian to alternative architectures or kernels you can " -"subscribe to port specific mailing lists and ask there how to get started. " -"Finally, if you are interested in documentation or Quality Assurance (QA) " -"work you can join maintainers already working on these tasks and submit " -"patches and improvements." +"&email-debian-mentors; mailing list, describing your package and yourself " +"and asking for a sponsor (see <xref linkend=\"sponsoring\"/> and <ulink " +"url=\"&url-mentors;\"></ulink> for more information on sponsoring). On the " +"other hand, if you are interested in porting Debian to alternative " +"architectures or kernels you can subscribe to port specific mailing lists " +"and ask there how to get started. Finally, if you are interested in " +"documentation or Quality Assurance (QA) work you can join maintainers " +"already working on these tasks and submit patches and improvements." msgstr "" # type: Content of: <chapter><section><para> @@ -94,7 +89,7 @@ msgstr "" msgid "" "One pitfall could be a too-generic local part in your mailadress: Terms like " "mail, admin, root, master should be avoided, please see <ulink " -"url=\"http://www.debian.org/MailingLists/\"></ulink> for details." +"url=\"&url-debian-lists;\"></ulink> for details." msgstr "" # type: Content of: <chapter><section><title> @@ -105,10 +100,10 @@ msgstr "" # type: Content of: <chapter><section><para> #: new-maintainer.dbk:66 msgid "" -"The mailing list <email>debian-mentors@lists.debian.org</email> has been set " -"up for novice maintainers who seek help with initial packaging and other " -"developer-related issues. Every new developer is invited to subscribe to " -"that list (see <xref linkend=\"mailing-lists\"/> for details)." +"The mailing list &email-debian-mentors; has been set up for novice " +"maintainers who seek help with initial packaging and other developer-related " +"issues. Every new developer is invited to subscribe to that list (see <xref " +"linkend=\"mailing-lists\"/> for details)." msgstr "" # type: Content of: <chapter><section><para> @@ -118,6 +113,13 @@ msgid "" "to that list and an experienced developer will volunteer to help." msgstr "" +#. FIXME - out of order +# +#. Those who are seeking a +# +#. sponsor can request one at <ulink url="http://www.internatif.org/bortzmeyer/debian/sponsor/"></ulink>. +# +# # type: Content of: <chapter><section><para> #: new-maintainer.dbk:76 msgid "" @@ -126,53 +128,50 @@ msgid "" "able find a sponsor to upload your package for you. Sponsors are people who " "are official Debian Developers, and who are willing to criticize and upload " "your packages for you. Please read the unofficial debian-mentors FAQ at " -"<ulink " -"url=\"http://people.debian.org/~mpalmer/debian-mentors_FAQ.html\"></ulink> " -"first." +"<ulink url=\"&url-mentors;\"></ulink> first." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:84 +#: new-maintainer.dbk:89 msgid "" "If you wish to be a mentor and/or sponsor, more information is available in " "<xref linkend=\"newmaint\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: new-maintainer.dbk:90 +#: new-maintainer.dbk:95 msgid "Registering as a Debian developer" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:92 +#: new-maintainer.dbk:97 msgid "" -"Before you decide to register with Debian GNU/Linux, you will need to read " -"all the information available at the <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink>. It describes in detail the preparations you have to do " -"before you can register to become a Debian developer. For example, before " -"you apply, you have to read the <ulink " -"url=\"http://www.debian.org/social_contract\">Debian Social " -"Contract</ulink>. Registering as a developer means that you agree with and " -"pledge to uphold the Debian Social Contract; it is very important that " -"maintainers are in accord with the essential ideas behind Debian GNU/Linux. " -"Reading the <ulink url=\"http://www.gnu.org/gnu/manifesto.html\">GNU " -"Manifesto</ulink> would also be a good idea." +"Before you decide to register with &debian-formal;, you will need to read " +"all the information available at the <ulink url=\"&url-newmaint;\">New " +"Maintainer's Corner</ulink>. It describes in detail the preparations you " +"have to do before you can register to become a Debian developer. For " +"example, before you apply, you have to read the <ulink " +"url=\"&url-social-contract;\">Debian Social Contract</ulink>. Registering " +"as a developer means that you agree with and pledge to uphold the Debian " +"Social Contract; it is very important that maintainers are in accord with " +"the essential ideas behind &debian-formal;. Reading the <ulink " +"url=\"&url-gnu-manifesto;\">GNU Manifesto</ulink> would also be a good idea." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:105 +#: new-maintainer.dbk:111 msgid "" "The process of registering as a developer is a process of verifying your " "identity and intentions, and checking your technical skills. As the number " -"of people working on Debian GNU/Linux has grown to over 900 and our systems " -"are used in several very important places, we have to be careful about being " -"compromised. Therefore, we need to verify new maintainers before we can " -"give them accounts on our servers and let them upload packages." +"of people working on &debian-formal; has grown to over " +"&number-of-maintainers; and our systems are used in several very important " +"places, we have to be careful about being compromised. Therefore, we need " +"to verify new maintainers before we can give them accounts on our servers " +"and let them upload packages." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:113 +#: new-maintainer.dbk:120 msgid "" "Before you actually register you should have shown that you can do competent " "work and will be a good contributor. You show this by submitting patches " @@ -184,23 +183,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:122 +#: new-maintainer.dbk:129 msgid "" "Registration requires that you are familiar with Debian's philosophy and " "technical documentation. Furthermore, you need a GnuPG key which has been " "signed by an existing Debian maintainer. If your GnuPG key is not signed " "yet, you should try to meet a Debian Developer in person to get your key " -"signed. There's a <ulink url=\"http://nm.debian.org/gpg.php\">GnuPG Key " -"Signing Coordination page</ulink> which should help you find a Debian " -"Developer close to you. (If there is no Debian Developer close to you, " -"alternative ways to pass the ID check may be permitted as an absolute " -"exception on a case-by-case-basis. See the <ulink " -"url=\"http://www.debian.org/devel/join/nm-step2\">identification " +"signed. There's a <ulink url=\"&url-gpg-coord;\">GnuPG Key Signing " +"Coordination page</ulink> which should help you find a Debian Developer " +"close to you. (If there is no Debian Developer close to you, alternative " +"ways to pass the ID check may be permitted as an absolute exception on a " +"case-by-case-basis. See the <ulink url=\"&url-newmaint-id;\">identification " "page</ulink> for more information.)" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:135 +#: new-maintainer.dbk:142 msgid "" "If you do not have an OpenPGP key yet, generate one. Every developer needs " "an OpenPGP key in order to sign and verify package uploads. You should read " @@ -212,17 +210,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:143 +#: new-maintainer.dbk:150 msgid "" "Debian uses the <command>GNU Privacy Guard</command> (package <systemitem " "role=\"package\">gnupg</systemitem> version 1 or better) as its baseline " "standard. You can use some other implementation of OpenPGP as well. Note " -"that OpenPGP is an open standard based on <ulink " -"url=\"http://www.rfc-editor.org/rfc/rfc2440.txt\">RFC 2440</ulink>." +"that OpenPGP is an open standard based on <ulink url=\"&url-rfc2440;\">RFC " +"2440</ulink>." msgstr "" # type: Content of: <chapter><section><para><footnote> -#: new-maintainer.dbk:150 +#: new-maintainer.dbk:157 msgid "" "You need a version 4 key for use in Debian Development. Your key length " "must be at least 1024 bits; there is no reason to use a smaller key, and " @@ -230,7 +228,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:152 +#: new-maintainer.dbk:159 msgid "" "Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC " "2440. Version 4 is the key type that has always been created when using " @@ -239,7 +237,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:156 +#: new-maintainer.dbk:163 msgid "" "Version 4 (primary) keys can either use the RSA or the DSA algorithms, so " "this has nothing to do with GnuPG's question about which kind of key do you " @@ -248,7 +246,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:160 +#: new-maintainer.dbk:167 msgid "" "The easiest way to tell whether an existing key is a v4 key or a v3 (or v2) " "key is to look at the fingerprint: Fingerprints of version 4 keys are the " @@ -261,14 +259,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:167 +#: new-maintainer.dbk:174 msgid "" "Another possibility is to pipe the key into <command>pgpdump</command>, " "which will say something like Public Key Packet - Ver 4." msgstr "" # type: Content of: <chapter><section><para><footnote><para> -#: new-maintainer.dbk:169 +#: new-maintainer.dbk:176 msgid "" "Also note that your key must be self-signed (i.e. it has to sign all its " "own user IDs; this prevents user ID tampering). All modern OpenPGP software " @@ -277,18 +275,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:175 +#: new-maintainer.dbk:182 msgid "" -"If your public key isn't on a public key server such as " -"<literal>subkeys.pgp.net</literal>, please read the documentation available " -"at <ulink url=\"http://www.debian.org/devel/join/nm-step2\">NM Step 2: " -"Identification</ulink>. That document contains instructions on how to put " -"your key on the public key servers. The New Maintainer Group will put your " -"public key on the servers if it isn't already there." +"If your public key isn't on a public key server such as &pgp-keyserv;, " +"please read the documentation available at <ulink " +"url=\"&url-newmaint-id;\">NM Step 2: Identification</ulink>. That document " +"contains instructions on how to put your key on the public key servers. The " +"New Maintainer Group will put your public key on the servers if it isn't " +"already there." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:183 +#: new-maintainer.dbk:190 msgid "" "Some countries restrict the use of cryptographic software by their " "citizens. This need not impede one's activities as a Debian package " @@ -299,7 +297,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:191 +#: new-maintainer.dbk:198 msgid "" "To apply as a new maintainer, you need an existing Debian Developer to " "support your application (an <emphasis>advocate</emphasis>). After you have " @@ -310,24 +308,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:198 +#: new-maintainer.dbk:205 msgid "" "When you have found an advocate, have your GnuPG key signed and have already " "contributed to Debian for a while, you're ready to apply. You can simply " -"register on our <ulink url=\"http://nm.debian.org/newnm.php\">application " +"register on our <ulink url=\"&url-newmaint-apply;\">application " "page</ulink>. After you have signed up, your advocate has to confirm your " "application. When your advocate has completed this step you will be " "assigned an Application Manager who will go with you through the necessary " "steps of the New Maintainer process. You can always check your status on " -"the <ulink url=\"http://nm.debian.org/\">applications status board</ulink>." +"the <ulink url=\"&url-newmaint-db;\">applications status board</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: new-maintainer.dbk:208 +#: new-maintainer.dbk:215 msgid "" -"For more details, please consult <ulink " -"url=\"http://www.debian.org/devel/join/newmaint\">New Maintainer's " -"Corner</ulink> at the Debian web site. Make sure that you are familiar with " -"the necessary steps of the New Maintainer process before actually applying. " -"If you are well prepared, you can save a lot of time later on." +"For more details, please consult <ulink url=\"&url-newmaint;\">New " +"Maintainer's Corner</ulink> at the Debian web site. Make sure that you are " +"familiar with the necessary steps of the New Maintainer process before " +"actually applying. If you are well prepared, you can save a lot of time " +"later on." msgstr "" diff --git a/po4a/po/pkgs.pot b/po4a/po/pkgs.pot index 994e65d..c18a1ca 100644 --- a/po4a/po/pkgs.pot +++ b/po4a/po/pkgs.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,36 +15,35 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: pkgs.dbk:5 +#: pkgs.dbk:7 msgid "Managing Packages" msgstr "" # type: Content of: <chapter><para> -#: pkgs.dbk:7 +#: pkgs.dbk:9 msgid "" "This chapter contains information related to creating, uploading, " "maintaining, and porting packages." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:11 +#: pkgs.dbk:13 msgid "New packages" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:13 +#: pkgs.dbk:15 msgid "" "If you want to create a new package for the Debian distribution, you should " -"first check the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " +"first check the <ulink url=\"&url-wnpp;\">Work-Needing and Prospective " "Packages (WNPP)</ulink> list. Checking the WNPP list ensures that no one is " "already working on packaging that software, and that effort is not " -"duplicated. Read the <ulink url=\"http://www.debian.org/devel/wnpp/\">WNPP " -"web pages</ulink> for more information." +"duplicated. Read the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink> for " +"more information." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:21 +#: pkgs.dbk:23 msgid "" "Assuming no one else is already working on your prospective package, you " "must then submit a bug report (<xref linkend=\"submit-bug\"/> ) against the " @@ -55,21 +54,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:29 +#: pkgs.dbk:31 msgid "" "You should set the subject of the bug to ``ITP: " "<replaceable>foo</replaceable> -- <replaceable>short " "description</replaceable>'', substituting the name of the new package for " "<replaceable>foo</replaceable>. The severity of the bug report must be set " "to <emphasis>wishlist</emphasis>. If you feel it's necessary, send a copy " -"to <email>debian-devel@lists.debian.org</email> by putting the address in " -"the <literal>X-Debbugs-CC:</literal> header of the message (no, don't use " +"to &email-debian-devel; by putting the address in the " +"<literal>X-Debbugs-CC:</literal> header of the message (no, don't use " "<literal>CC:</literal>, because that way the message's subject won't " "indicate the bug number)." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:39 +#: pkgs.dbk:41 msgid "" "Please include a <literal>Closes: " "bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the " @@ -79,7 +78,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:45 +#: pkgs.dbk:47 msgid "" "When closing security bugs include CVE numbers as well as the Closes: " "#nnnnn. This is useful for the security team to track vulnerabilities. If " @@ -90,14 +89,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:53 +#: pkgs.dbk:55 msgid "" "There are a number of reasons why we ask maintainers to announce their " "intentions:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:59 +#: pkgs.dbk:61 msgid "" "It helps the (potentially new) maintainer to tap into the experience of " "people on the list, and lets them know if anyone else is working on it " @@ -105,14 +104,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:65 +#: pkgs.dbk:67 msgid "" "It lets other people thinking about working on the package know that there " "already is a volunteer, so efforts may be shared." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:71 +#: pkgs.dbk:73 msgid "" "It lets the rest of the maintainers know more about the package than the one " "line description and the usual changelog entry ``Initial release'' that gets " @@ -120,34 +119,33 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:78 +#: pkgs.dbk:80 msgid "" "It is helpful to the people who live off unstable (and form our first line " "of testers). We should encourage these people." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:84 +#: pkgs.dbk:86 msgid "" "The announcements give maintainers and other interested parties a better " "feel of what is going on, and what is new, in the project." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:90 +#: pkgs.dbk:92 msgid "" -"Please see <ulink " -"url=\"http://ftp-master.debian.org/REJECT-FAQ.html\"></ulink> for common " -"rejection reasons for a new package." +"Please see <ulink url=\"http://&ftp-master-host;/REJECT-FAQ.html\"></ulink> " +"for common rejection reasons for a new package." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:96 +#: pkgs.dbk:98 msgid "Recording changes in the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:98 +#: pkgs.dbk:100 msgid "" "Changes that you make to the package need to be recorded in the " "<filename>debian/changelog</filename>. These changes should provide a " @@ -161,7 +159,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:109 +#: pkgs.dbk:111 msgid "" "The <filename>debian/changelog</filename> file conforms to a certain " "structure, with a number of different fields. One field of note, the " @@ -172,7 +170,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:117 +#: pkgs.dbk:119 msgid "" "Changelog entries can be used to automatically close Debian bugs when the " "package is installed into the archive. See <xref " @@ -180,20 +178,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:121 +#: pkgs.dbk:123 msgid "" "It is conventional that the changelog entry of a package that contains a new " "upstream version of the software looks like this:" msgstr "" # type: Content of: <chapter><section><screen> -#: pkgs.dbk:125 +#: pkgs.dbk:127 #, no-wrap msgid "* new upstream version" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:128 +#: pkgs.dbk:130 msgid "" "There are tools to help you create entries and finalize the " "<filename>changelog</filename> for release — see <xref " @@ -201,17 +199,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:133 +#: pkgs.dbk:135 msgid "See also <xref linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:138 +#: pkgs.dbk:140 msgid "Testing the package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:140 +#: pkgs.dbk:142 msgid "" "Before you upload your package, you should do basic testing on it. At a " "minimum, you should try the following activities (you'll need to have an " @@ -219,7 +217,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:147 +#: pkgs.dbk:149 msgid "" "Install the package and make sure the software works, or upgrade the package " "from an older version to your new version if a Debian package for it already " @@ -227,7 +225,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:154 +#: pkgs.dbk:156 msgid "" "Run <command>lintian</command> over the package. You can run " "<command>lintian</command> as follows: <literal>lintian -v " @@ -240,40 +238,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:163 +#: pkgs.dbk:165 msgid "" "Normally, a package should <emphasis>not</emphasis> be uploaded if it causes " "lintian to emit errors (they will start with <literal>E</literal>)." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:167 +#: pkgs.dbk:169 msgid "" "For more information on <command>lintian</command>, see <xref " "linkend=\"lintian\"/> ." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:173 +#: pkgs.dbk:175 msgid "" "Optionally run <xref linkend=\"debdiff\"/> to analyze changes from an older " "version, if one exists." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:179 +#: pkgs.dbk:181 msgid "" "Downgrade the package to the previous version (if one exists) — this tests " "the <filename>postrm</filename> and <filename>prerm</filename> scripts." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:185 +#: pkgs.dbk:187 msgid "Remove the package, then reinstall it." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:190 +#: pkgs.dbk:192 msgid "" "Copy the source package in a different directory and try unpacking it and " "rebuilding it. This tests if the package relies on existing files outside " @@ -282,31 +280,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:200 +#: pkgs.dbk:202 msgid "Layout of the source package" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:202 +#: pkgs.dbk:204 msgid "There are two types of Debian source packages:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:207 +#: pkgs.dbk:209 msgid "" "the so-called <emphasis>native</emphasis> packages, where there is no " "distinction between the original sources and the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:213 +#: pkgs.dbk:215 msgid "" "the (more common) packages where there's an original source tarball file " "accompanied by another file that contains the patches applied for Debian" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:219 +#: pkgs.dbk:221 msgid "" "For the native packages, the source package includes a Debian source control " "file (<literal>.dsc</literal>) and the source tarball " @@ -317,7 +315,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:227 +#: pkgs.dbk:229 msgid "" "Whether a package is native or not is determined when it is built by " "<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle> " @@ -326,7 +324,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:233 +#: pkgs.dbk:235 msgid "" "The first time a version is uploaded which corresponds to a particular " "upstream version, the original source tar file should be uploaded and " @@ -336,7 +334,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:240 +#: pkgs.dbk:242 msgid "" "By default, <command>dpkg-genchanges</command> and " "<command>dpkg-buildpackage</command> will include the original source tar " @@ -347,7 +345,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:248 +#: pkgs.dbk:250 msgid "" "If no original source is included in the upload, the original source " "tar-file used by <command>dpkg-source</command> when constructing the " @@ -357,7 +355,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:255 +#: pkgs.dbk:257 msgid "" "Please notice that, in non-native packages, permissions on files that are " "not present in the .orig.tar.gz will not be preserved, as diff does not " @@ -365,12 +363,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:262 +#: pkgs.dbk:264 msgid "Picking a distribution" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:264 +#: pkgs.dbk:266 msgid "" "Each upload needs to specify which distribution the package is intended " "for. The package build process extracts this information from the first " @@ -380,7 +378,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:270 +#: pkgs.dbk:272 msgid "" "There are several possible values for this field: `stable', `unstable', " "`testing-proposed-updates' and `experimental'. Normally, packages are " @@ -388,7 +386,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:275 +#: pkgs.dbk:277 msgid "" "Actually, there are two other possible distributions: `stable-security' and " "`testing-security', but read <xref linkend=\"bug-security\"/> for more " @@ -396,19 +394,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:280 +#: pkgs.dbk:282 msgid "" "It is not possible to upload a package into several distributions at the " "same time." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:284 +#: pkgs.dbk:286 msgid "Special case: uploads to the <emphasis>stable</emphasis> distribution" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:286 +#: pkgs.dbk:288 msgid "" "Uploading to <emphasis>stable</emphasis> means that the package will " "transfered to the <emphasis>p-u-new</emphasis>-queue for review by the " @@ -419,7 +417,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:294 +#: pkgs.dbk:296 msgid "" "Extra care should be taken when uploading to <emphasis>stable</emphasis>. " "Basically, a package should only be uploaded to stable if one of the " @@ -427,22 +425,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:301 +#: pkgs.dbk:303 msgid "a truly critical functionality problem" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:306 +#: pkgs.dbk:308 msgid "the package becomes uninstallable" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:311 +#: pkgs.dbk:313 msgid "a released architecture lacks the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:316 +#: pkgs.dbk:318 msgid "" "In the past, uploads to <emphasis>stable</emphasis> were used to address " "security problems as well. However, this practice is deprecated, as uploads " @@ -453,14 +451,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:324 +#: pkgs.dbk:326 msgid "" "Changing anything else in the package that isn't important is discouraged, " "because even trivial fixes can cause bugs later on." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:328 +#: pkgs.dbk:330 msgid "" "Packages uploaded to <emphasis>stable</emphasis> need to be compiled on " "systems running <emphasis>stable</emphasis>, so that their dependencies are " @@ -474,19 +472,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:338 +#: pkgs.dbk:340 msgid "" -"The Release Team (which can be reached at " -"<email>debian-release@lists.debian.org</email>) will regularly evaluate the " -"uploads To <emphasis>stable-proposed-updates</emphasis> and decide if your " -"package can be included in <emphasis>stable</emphasis>. Please be clear " -"(and verbose, if necessary) in your changelog entries for uploads to " +"The Release Team (which can be reached at &email-debian-release;) will " +"regularly evaluate the uploads To " +"<emphasis>stable-proposed-updates</emphasis> and decide if your package can " +"be included in <emphasis>stable</emphasis>. Please be clear (and verbose, " +"if necessary) in your changelog entries for uploads to " "<emphasis>stable</emphasis>, because otherwise the package won't be " "considered for inclusion." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:347 +#: pkgs.dbk:349 msgid "" "It's best practice to speak with the stable release manager " "<emphasis>before</emphasis> uploading to " @@ -495,42 +493,42 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:355 +#: pkgs.dbk:357 msgid "" "Special case: uploads to " "<emphasis>testing/testing-proposed-updates</emphasis>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:357 +#: pkgs.dbk:359 msgid "" "Please see the information in the <link linkend=\"t-p-u\">testing " "section</link> for details." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:365 +#: pkgs.dbk:367 msgid "Uploading a package" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:367 +#: pkgs.dbk:369 msgid "Uploading to <literal>ftp-master</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:369 +#: pkgs.dbk:371 msgid "" "To upload a package, you should upload the files (including the signed " "changes and dsc-file) with anonymous ftp to " -"<literal>ftp-master.debian.org</literal> in the directory <ulink " -"url=\"ftp://ftp-master.debian.org/pub/UploadQueue/\">/pub/UploadQueue/</ulink>. " -"To get the files processed there, they need to be signed with a key in the " +"<literal>&ftp-master-host;</literal> in the directory <ulink " +"url=\"ftp://&ftp-master-host;&upload-queue;\">&upload-queue;</ulink>. To " +"get the files processed there, they need to be signed with a key in the " "debian keyring." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:377 +#: pkgs.dbk:379 msgid "" "Please note that you should transfer the changes file last. Otherwise, your " "upload may be rejected because the archive maintenance software will parse " @@ -538,7 +536,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:382 +#: pkgs.dbk:384 msgid "" "You may also find the Debian packages <xref linkend=\"dupload\"/> or <xref " "linkend=\"dput\"/> useful when uploading packages. These handy programs " @@ -546,31 +544,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:387 +#: pkgs.dbk:389 msgid "" "For removing packages, please see the README file in that ftp directory, and " "the Debian package <xref linkend=\"dcut\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:393 +#: pkgs.dbk:395 msgid "Uploading to <literal>non-US</literal>" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:395 +#: pkgs.dbk:397 msgid "" "<emphasis>Note:</emphasis> non-us was discontinued with the release of " "sarge." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:400 +#: pkgs.dbk:402 msgid "Delayed uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:402 +#: pkgs.dbk:404 msgid "" "Delayed uploads are done for the moment via the delayed queue at gluck. The " "upload-directory is " @@ -579,12 +577,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:407 +#: pkgs.dbk:409 msgid "With a fairly recent dput, this section" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:410 +#: pkgs.dbk:412 #, no-wrap msgid "" "[tfheen_delayed]\n" @@ -594,12 +592,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:416 +#: pkgs.dbk:418 msgid "in ~/.dput.cf should work fine for uploading to the DELAYED queue." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:419 +#: pkgs.dbk:421 msgid "" "<emphasis>Note:</emphasis> Since this upload queue goes to " "<literal>ftp-master</literal>, the prescription found in <xref " @@ -607,12 +605,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:426 +#: pkgs.dbk:428 msgid "Security uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:428 +#: pkgs.dbk:430 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " @@ -623,26 +621,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:438 +#: pkgs.dbk:440 msgid "Other upload queues" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:440 +#: pkgs.dbk:442 msgid "" "The scp queues on ftp-master, and security are mostly unusable due to the " "login restrictions on those hosts." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:444 +#: pkgs.dbk:446 msgid "" "The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are " "currently down. Work is underway to resurrect them." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:448 +#: pkgs.dbk:450 msgid "" "The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and " "ftp.chiark.greenend.org.uk are down permanently, and will not be " @@ -651,7 +649,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:454 +#: pkgs.dbk:456 msgid "" "For the time being, the anonymous ftp queue on auric.debian.org (the former " "ftp-master) works, but it is deprecated and will be removed at some point in " @@ -659,12 +657,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:461 +#: pkgs.dbk:463 msgid "Notification that a new package has been installed" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:463 +#: pkgs.dbk:465 msgid "" "The Debian archive maintainers are responsible for handling package " "uploads. For the most part, uploads are automatically handled on a daily " @@ -677,7 +675,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:472 +#: pkgs.dbk:474 msgid "" "In any case, you will receive an email notification indicating that the " "package has been added to the archive, which also indicates which bugs will " @@ -686,7 +684,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:478 +#: pkgs.dbk:480 msgid "" "The installation notification also includes information on what section the " "package was inserted into. If there is a disparity, you will receive a " @@ -694,19 +692,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:483 +#: pkgs.dbk:485 msgid "" "Note that if you upload via queues, the queue daemon software will also send " "you a notification by email." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:491 +#: pkgs.dbk:493 msgid "Specifying the package section, subsection and priority" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:493 +#: pkgs.dbk:495 msgid "" "The <filename>debian/control</filename> file's <literal>Section</literal> " "and <literal>Priority</literal> fields do not actually specify where the " @@ -717,7 +715,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:501 +#: pkgs.dbk:503 msgid "" "The archive maintainers keep track of the canonical sections and priorities " "for packages in the <emphasis>override file</emphasis>. If there is a " @@ -730,99 +728,95 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:511 +#: pkgs.dbk:513 msgid "" "To alter the actual section that a package is put in, you need to first make " "sure that the <filename>debian/control</filename> file in your package is " -"accurate. Next, send an email <email>override-change@debian.org</email> or " -"submit a bug against <systemitem " -"role=\"package\">ftp.debian.org</systemitem> requesting that the section or " -"priority for your package be changed from the old section or priority to the " -"new one. Be sure to explain your reasoning." +"accurate. Next, send an email &email-override; or submit a bug against " +"<systemitem role=\"package\">ftp.debian.org</systemitem> requesting that the " +"section or priority for your package be changed from the old section or " +"priority to the new one. Be sure to explain your reasoning." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:519 +#: pkgs.dbk:521 msgid "" "For more information about <emphasis>override files</emphasis>, see " "<citerefentry> <refentrytitle>dpkg-scanpackages</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> and <ulink " -"url=\"http://www.debian.org/Bugs/Developer#maintincorrect\"></ulink>." +"url=\"&url-bts-devel;#maintincorrect\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:525 +#: pkgs.dbk:527 msgid "" "Note that the <literal>Section</literal> field describes both the section as " "well as the subsection, which are described in <xref " "linkend=\"archive-sections\"/> . If the section is main, it should be " "omitted. The list of allowable subsections can be found in <ulink " -"url=\"http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections\"></ulink>." +"url=\"&url-debian-policy;ch-archive.html#s-subsections\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:534 +#: pkgs.dbk:536 msgid "Handling bugs" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:536 +#: pkgs.dbk:538 msgid "" "Every developer has to be able to work with the Debian <ulink " -"url=\"http://www.debian.org/Bugs/\">bug tracking system</ulink>. This " -"includes knowing how to file bug reports properly (see <xref " -"linkend=\"submit-bug\"/> ), how to update them and reorder them, and how to " -"process and close them." +"url=\"&url-bts;\">bug tracking system</ulink>. This includes knowing how to " +"file bug reports properly (see <xref linkend=\"submit-bug\"/> ), how to " +"update them and reorder them, and how to process and close them." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:542 +#: pkgs.dbk:544 msgid "" "The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for " -"developers</ulink>. This includes closing bugs, sending followup messages, " -"assigning severities and tags, marking bugs as forwarded, and other issues." +"url=\"&url-bts-devel;\">BTS documentation for developers</ulink>. This " +"includes closing bugs, sending followup messages, assigning severities and " +"tags, marking bugs as forwarded, and other issues." msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:548 +#: pkgs.dbk:550 msgid "" "Operations such as reassigning bugs to other packages, merging separate bug " "reports about the same issue, or reopening bugs when they are prematurely " "closed, are handled using the so-called control mail server. All of the " "commands available on this server are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " -"documentation</ulink>." +"url=\"&url-bts-control;\">BTS control server documentation</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:556 +#: pkgs.dbk:558 msgid "Monitoring bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:558 +#: pkgs.dbk:560 msgid "" "If you want to be a good maintainer, you should periodically check the " -"<ulink url=\"http://www.debian.org/Bugs/\">Debian bug tracking system " -"(BTS)</ulink> for your packages. The BTS contains all the open bugs against " -"your packages. You can check them by browsing this page: " -"<literal>http://bugs.debian.org/<replaceable>yourlogin</replaceable>@debian.org</literal>." +"<ulink url=\"&url-bts;\">Debian bug tracking system (BTS)</ulink> for your " +"packages. The BTS contains all the open bugs against your packages. You " +"can check them by browsing this page: " +"<literal>http://&bugs-host;/<replaceable>yourlogin</replaceable>@debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:565 +#: pkgs.dbk:567 msgid "" "Maintainers interact with the BTS via email addresses at " -"<literal>bugs.debian.org</literal>. Documentation on available commands can " -"be found at <ulink url=\"http://www.debian.org/Bugs/\"></ulink>, or, if you " -"have installed the <systemitem role=\"package\">doc-debian</systemitem> " -"package, you can look at the local files " -"<filename>/usr/share/doc/debian/bug-*</filename>." +"<literal>&bugs-host;</literal>. Documentation on available commands can be " +"found at <ulink url=\"&url-bts;\"></ulink>, or, if you have installed the " +"<systemitem role=\"package\">doc-debian</systemitem> package, you can look " +"at the local files &file-bts-docs;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:572 +#: pkgs.dbk:574 msgid "" "Some find it useful to get periodic reports on open bugs. You can add a " "cron job such as the following if you want to get a weekly email outlining " @@ -830,86 +824,84 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:577 +#: pkgs.dbk:579 #, no-wrap msgid "" "# ask for weekly reports of bugs in my packages\n" -"0 17 * * fri echo index maint <replaceable>address</replaceable> | mail " -"request@bugs.debian.org" +"&cron-bug-report;" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:581 +#: pkgs.dbk:583 msgid "" "Replace <replaceable>address</replaceable> with your official Debian " "maintainer address." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:587 +#: pkgs.dbk:589 msgid "Responding to bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:589 +#: pkgs.dbk:591 msgid "" "When responding to bugs, make sure that any discussion you have about bugs " "is sent both to the original submitter of the bug, and to the bug itself " -"(e.g., <email>123@bugs.debian.org</email>). If you're writing a new mail " -"and you don't remember the submitter email address, you can use the " -"<email>123-submitter@bugs.debian.org</email> email to contact the submitter " +"(e.g., <email>123@&bugs-host;</email>). If you're writing a new mail and " +"you don't remember the submitter email address, you can use the " +"<email>123-submitter@&bugs-host;</email> email to contact the submitter " "<emphasis>and</emphasis> to record your mail within the bug log (that means " "you don't need to send a copy of the mail to " -"<email>123@bugs.debian.org</email>)." +"<email>123@&bugs-host;</email>)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:598 +#: pkgs.dbk:600 msgid "" "If you get a bug which mentions FTBFS, this means Fails to build from " "source. Porters frequently use this acronym." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:602 +#: pkgs.dbk:604 msgid "" "Once you've dealt with a bug report (e.g. fixed it), mark it as " "<emphasis>done</emphasis> (close it) by sending an explanation message to " -"<email>123-done@bugs.debian.org</email>. If you're fixing a bug by changing " -"and uploading the package, you can automate bug closing as described in " -"<xref linkend=\"upload-bugfix\"/> ." +"<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing and " +"uploading the package, you can automate bug closing as described in <xref " +"linkend=\"upload-bugfix\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:609 +#: pkgs.dbk:611 msgid "" "You should <emphasis>never</emphasis> close bugs via the bug server " -"<literal>close</literal> command sent to " -"<email>control@bugs.debian.org</email>. If you do so, the original " -"submitter will not receive any information about why the bug was closed." +"<literal>close</literal> command sent to &email-bts-control;. If you do so, " +"the original submitter will not receive any information about why the bug " +"was closed." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:617 +#: pkgs.dbk:619 msgid "Bug housekeeping" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:619 +#: pkgs.dbk:621 msgid "" "As a package maintainer, you will often find bugs in other packages or have " "bugs reported against your packages which are actually bugs in other " "packages. The bug tracking system's features are described in the <ulink " -"url=\"http://www.debian.org/Bugs/Developer\">BTS documentation for Debian " -"developers</ulink>. Operations such as reassigning, merging, and tagging " -"bug reports are described in the <ulink " -"url=\"http://www.debian.org/Bugs/server-control\">BTS control server " +"url=\"&url-bts-devel;\">BTS documentation for Debian developers</ulink>. " +"Operations such as reassigning, merging, and tagging bug reports are " +"described in the <ulink url=\"&url-bts-control;\">BTS control server " "documentation</ulink>. This section contains some guidelines for managing " "your own bugs, based on the collective Debian developer experience." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:630 +#: pkgs.dbk:632 msgid "" "Filing bugs for problems that you find in other packages is one of the civic " "obligations of maintainership, see <xref linkend=\"submit-bug\"/> for " @@ -918,12 +910,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:635 +#: pkgs.dbk:637 msgid "Here's a list of steps that you may follow to handle a bug report:" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:640 +#: pkgs.dbk:642 msgid "" "Decide whether the report corresponds to a real bug or not. Sometimes users " "are just calling a program in the wrong way because they haven't read the " @@ -936,7 +928,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:650 +#: pkgs.dbk:652 msgid "" "If the bug submitter disagrees with your decision to close the bug, they may " "reopen it until you find an agreement on how to handle it. If you don't " @@ -946,24 +938,23 @@ msgid "" "decision of the technical committee by reassigning the bug to <systemitem " "role=\"package\">tech-ctte</systemitem> (you may use the clone command of " "the BTS if you wish to keep it reported against your package). Before doing " -"so, please read the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">recommended procedure</ulink>." +"so, please read the <ulink url=\"&url-tech-ctte;\">recommended " +"procedure</ulink>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:664 +#: pkgs.dbk:666 msgid "" "If the bug is real but it's caused by another package, just reassign the bug " "to the right package. If you don't know which package it should be " "reassigned to, you should ask for help on <link " -"linkend=\"irc-channels\">IRC</link> or on " -"<email>debian-devel@lists.debian.org</email>. Please make sure that the " -"maintainer(s) of the package the bug is reassigned to know why you " -"reassigned it." +"linkend=\"irc-channels\">IRC</link> or on &email-debian-devel;. Please make " +"sure that the maintainer(s) of the package the bug is reassigned to know why " +"you reassigned it." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:672 +#: pkgs.dbk:674 msgid "" "Sometimes you also have to adjust the severity of the bug so that it matches " "our definition of the severity. That's because people tend to inflate the " @@ -973,7 +964,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:680 +#: pkgs.dbk:682 msgid "" "If the bug is real but the same problem has already been reported by someone " "else, then the two relevant bug reports should be merged into one using the " @@ -985,7 +976,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:691 +#: pkgs.dbk:693 msgid "" "The bug submitter may have forgotten to provide some information, in which " "case you have to ask them for the required information. You may use the " @@ -997,22 +988,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:702 +#: pkgs.dbk:704 msgid "" "If the bug is related to the packaging, you just fix it. If you are not " "able to fix it yourself, then tag the bug as <literal>help</literal>. You " -"can also ask for help on <email>debian-devel@lists.debian.org</email> or " -"<email>debian-qa@lists.debian.org</email>. If it's an upstream problem, you " -"have to forward it to the upstream author. Forwarding a bug is not enough, " -"you have to check at each release if the bug has been fixed or not. If it " -"has, you just close it, otherwise you have to remind the author about it. " -"If you have the required skills you can prepare a patch that fixes the bug " -"and send it to the author at the same time. Make sure to send the patch to " -"the BTS and to tag the bug as <literal>patch</literal>." +"can also ask for help on &email-debian-devel; or &email-debian-qa;. If it's " +"an upstream problem, you have to forward it to the upstream author. " +"Forwarding a bug is not enough, you have to check at each release if the bug " +"has been fixed or not. If it has, you just close it, otherwise you have to " +"remind the author about it. If you have the required skills you can prepare " +"a patch that fixes the bug and send it to the author at the same time. Make " +"sure to send the patch to the BTS and to tag the bug as " +"<literal>patch</literal>." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:716 +#: pkgs.dbk:718 msgid "" "If you have fixed a bug in your local copy, or if a fix has been committed " "to the CVS repository, you may tag the bug as <literal>pending</literal> to " @@ -1023,7 +1014,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:726 +#: pkgs.dbk:728 msgid "" "Once a corrected package is available in the <emphasis>unstable</emphasis> " "distribution, you can close the bug. This can be done automatically, read " @@ -1031,12 +1022,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:735 +#: pkgs.dbk:737 msgid "When bugs are closed by new uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:737 +#: pkgs.dbk:739 msgid "" "As bugs and problems are fixed in your packages, it is your responsibility " "as the package maintainer to close these bugs. However, you should not " @@ -1047,7 +1038,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:745 +#: pkgs.dbk:747 msgid "" "However, it's possible to avoid having to manually close bugs after the " "upload — just list the fixed bugs in your " @@ -1056,10 +1047,10 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:751 +#: pkgs.dbk:753 #, no-wrap msgid "" -"-cannon (3.1415) unstable; urgency=low\n" +"acme-cannon (3.1415) unstable; urgency=low\n" "\n" " * Frobbed with options (closes: Bug#98339)\n" " * Added safety to prevent operator dismemberment, closes: bug#98765,\n" @@ -1068,20 +1059,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:759 +#: pkgs.dbk:761 msgid "" "Technically speaking, the following Perl regular expression describes how " "bug closing changelogs are identified:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:763 +#: pkgs.dbk:765 #, no-wrap msgid "/closes:\\s*(?:bug)?\\#\\s*\\d+(?:,\\s*(?:bug)?\\#\\s*\\d+)*/ig" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:766 +#: pkgs.dbk:768 msgid "" "We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal> " "syntax, as it is the most concise entry and the easiest to integrate with " @@ -1093,7 +1084,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:775 +#: pkgs.dbk:777 msgid "" "Historically, uploads identified as <link linkend=\"nmu\">Non-maintainer " "upload (NMU)</link> were tagged <literal>fixed</literal> instead of being " @@ -1102,48 +1093,46 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:781 +#: pkgs.dbk:783 msgid "" "If you happen to mistype a bug number or forget a bug in the changelog " "entries, don't hesitate to undo any damage the error caused. To reopen " "wrongly closed bugs, send a <literal>reopen " "<replaceable>XXX</replaceable></literal> command to the bug tracking " -"system's control address, <email>control@bugs.debian.org</email>. To close " -"any remaining bugs that were fixed by your upload, email the " -"<filename>.changes</filename> file to " -"<email>XXX-done@bugs.debian.org</email>, where " -"<replaceable>XXX</replaceable> is the bug number, and put Version: YYY and " -"an empty line as the first two lines of the body of the email, where " -"<replaceable>YYY</replaceable> is the first version where the bug has been " -"fixed." +"system's control address, &email-bts-control;. To close any remaining bugs " +"that were fixed by your upload, email the <filename>.changes</filename> file " +"to <email>XXX-done@&bugs-host;</email>, where <replaceable>XXX</replaceable> " +"is the bug number, and put Version: YYY and an empty line as the first two " +"lines of the body of the email, where <replaceable>YYY</replaceable> is the " +"first version where the bug has been fixed." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:793 +#: pkgs.dbk:795 msgid "" "Bear in mind that it is not obligatory to close bugs using the changelog as " "described above. If you simply want to close bugs that don't have anything " "to do with an upload you made, do it by emailing an explanation to " -"<email>XXX-done@bugs.debian.org</email>. Do <emphasis " +"<email>XXX-done@&bugs-host;</email>. Do <emphasis " "role=\"strong\">not</emphasis> close bugs in the changelog entry of a " "version if the changes in that version of the package don't have any bearing " "on the bug." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:801 +#: pkgs.dbk:803 msgid "" "For general information on how to write your changelog entries, see <xref " "linkend=\"bpp-debian-changelog\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:807 +#: pkgs.dbk:809 msgid "Handling security-related bugs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:809 +#: pkgs.dbk:811 msgid "" "Due to their sensitive nature, security-related bugs must be handled " "carefully. The Debian Security Team exists to coordinate this activity, " @@ -1153,18 +1142,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:816 +#: pkgs.dbk:820 msgid "" "When you become aware of a security-related bug in a Debian package, whether " "or not you are the maintainer, collect pertinent information about the " -"problem, and promptly contact the security team at " -"<email>team@security.debian.org</email> as soon as possible. <emphasis " -"role=\"strong\">DO NOT UPLOAD</emphasis> any packages for stable; the " -"security team will do that. Useful information includes, for example:" +"problem, and promptly contact the security team at &email-security-team; as " +"soon as possible. <emphasis role=\"strong\">DO NOT UPLOAD</emphasis> any " +"packages for stable; the security team will do that. Useful information " +"includes, for example:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:826 +#: pkgs.dbk:830 msgid "" "Which versions of the package are known to be affected by the bug. Check " "each version that is present in a supported Debian release, as well as " @@ -1172,12 +1161,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:833 +#: pkgs.dbk:837 msgid "The nature of the fix, if any is available (patches are especially helpful)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:838 +#: pkgs.dbk:842 msgid "" "Any fixed packages that you have prepared yourself (send only the " "<literal>.diff.gz</literal> and <literal>.dsc</literal> files and read <xref " @@ -1185,26 +1174,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:845 +#: pkgs.dbk:849 msgid "" "Any assistance you can provide to help with testing (exploits, regression " "testing, etc.)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:851 +#: pkgs.dbk:855 msgid "" "Any information needed for the advisory (see <xref " "linkend=\"bug-security-advisories\"/> )" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:857 +#: pkgs.dbk:861 msgid "Confidentiality" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:859 +#: pkgs.dbk:863 msgid "" "Unlike most other activities within Debian, information about security " "issues must sometimes be kept private for a time. This allows software " @@ -1215,27 +1204,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:866 +#: pkgs.dbk:870 msgid "There are several ways developers can learn of a security problem:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:871 +#: pkgs.dbk:875 msgid "they notice it on a public forum (mailing list, web site, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:876 +#: pkgs.dbk:880 msgid "someone files a bug report" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:881 +#: pkgs.dbk:885 msgid "someone informs them via private email" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:886 +#: pkgs.dbk:890 msgid "" "In the first two cases, the information is public and it is important to " "have a fix as soon as possible. In the last case, however, it might not be " @@ -1244,14 +1233,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:894 +#: pkgs.dbk:898 msgid "" "If the security exposure is minor, there is sometimes no need to keep the " "problem a secret and a fix should be made and released." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:900 +#: pkgs.dbk:904 msgid "" "If the problem is severe, it is preferable to share the information with " "other vendors and coordinate a release. The security team keeps in contact " @@ -1259,7 +1248,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:907 +#: pkgs.dbk:911 msgid "" "In all cases if the person who reports the problem asks that it not be " "disclosed, such requests should be honored, with the obvious exception of " @@ -1269,7 +1258,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:914 +#: pkgs.dbk:918 msgid "" "Please note that if secrecy is needed you may not upload a fix to unstable " "(or anywhere else, such as a public CVS repository). It is not sufficient " @@ -1278,7 +1267,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:920 +#: pkgs.dbk:924 msgid "" "There are two reasons for releasing information even though secrecy is " "requested: the problem has been known for a while, or the problem or exploit " @@ -1286,78 +1275,78 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:927 +#: pkgs.dbk:931 msgid "Security Advisories" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:929 +#: pkgs.dbk:933 msgid "" "Security advisories are only issued for the current, released stable " "distribution, and <emphasis>not</emphasis> for testing or unstable. When " -"released, advisories are sent to the " -"<email>debian-security-announce@lists.debian.org</email> mailing list and " -"posted on <ulink url=\"http://www.debian.org/security/\">the security web " -"page</ulink>. Security advisories are written and posted by the security " -"team. However they certainly do not mind if a maintainer can supply some of " -"the information for them, or write part of the text. Information that " -"should be in an advisory includes:" +"released, advisories are sent to the &email-debian-security-announce; " +"mailing list and posted on <ulink " +"url=\"&url-debian-security-advisories;\">the security web page</ulink>. " +"Security advisories are written and posted by the security team. However " +"they certainly do not mind if a maintainer can supply some of the " +"information for them, or write part of the text. Information that should be " +"in an advisory includes:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:942 +#: pkgs.dbk:946 msgid "A description of the problem and its scope, including:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:947 +#: pkgs.dbk:951 msgid "The type of problem (privilege escalation, denial of service, etc.)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:952 +#: pkgs.dbk:956 msgid "What privileges may be gained, and by whom (if any)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:957 +#: pkgs.dbk:961 msgid "How it can be exploited" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:962 +#: pkgs.dbk:966 msgid "Whether it is remotely or locally exploitable" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><itemizedlist><listitem><para> -#: pkgs.dbk:967 +#: pkgs.dbk:971 msgid "How the problem was fixed" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:972 +#: pkgs.dbk:976 msgid "This information allows users to assess the threat to their systems." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:977 +#: pkgs.dbk:981 msgid "Version numbers of affected packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:982 +#: pkgs.dbk:986 msgid "Version numbers of fixed packages" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:987 +#: pkgs.dbk:991 msgid "" "Information on where to obtain the updated packages (usually from the Debian " "security archive)" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:993 +#: pkgs.dbk:997 msgid "" "References to upstream advisories, <ulink " "url=\"http://cve.mitre.org\">CVE</ulink> identifiers, and any other " @@ -1365,12 +1354,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1002 +#: pkgs.dbk:1006 msgid "Preparing packages to address security issues" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1004 +#: pkgs.dbk:1008 msgid "" "One way that you can assist the security team in their duties is to provide " "them with fixed packages suitable for a security advisory for the stable " @@ -1378,7 +1367,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1009 +#: pkgs.dbk:1013 msgid "" "When an update is made to the stable release, care must be taken to avoid " "changing system behavior or introducing new bugs. In order to do this, make " @@ -1389,7 +1378,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1017 +#: pkgs.dbk:1021 msgid "" "This means that moving to a new upstream version is not a good solution. " "Instead, the relevant changes should be back-ported to the version present " @@ -1399,7 +1388,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1023 +#: pkgs.dbk:1027 msgid "" "In some cases, it is not possible to back-port a security fix, for example " "when large amounts of source code need to be modified or rewritten. If this " @@ -1409,7 +1398,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1030 +#: pkgs.dbk:1034 msgid "" "Related to this is another important guideline: always test your changes. " "If you have an exploit available, try it and see if it indeed succeeds on " @@ -1419,7 +1408,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1037 +#: pkgs.dbk:1041 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> include any changes in your " "package which are not directly related to fixing the vulnerability. These " @@ -1432,7 +1421,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1047 +#: pkgs.dbk:1051 msgid "" "Review and test your changes as much as possible. Check the differences " "from the previous version repeatedly (<command>interdiff</command> from the " @@ -1443,12 +1432,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1055 +#: pkgs.dbk:1059 msgid "Be sure to verify the following items:" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1060 +#: pkgs.dbk:1064 msgid "" "Target the right distribution in your " "<filename>debian/changelog</filename>. For stable this is " @@ -1460,12 +1449,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1070 +#: pkgs.dbk:1074 msgid "The upload should have urgency=high." msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1075 +#: pkgs.dbk:1079 msgid "" "Make descriptive, meaningful changelog entries. Others will rely on them to " "determine whether a particular bug was fixed. Always include an external " @@ -1478,7 +1467,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1087 +#: pkgs.dbk:1091 msgid "" "Make sure the version number is proper. It must be greater than the current " "package, but less than package versions in later distributions. If in " @@ -1491,7 +1480,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1099 +#: pkgs.dbk:1103 msgid "" "Do not make source-only uploads if your package has any binary-all packages " "(do not use the <literal>-S</literal> option to " @@ -1501,7 +1490,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1108 +#: pkgs.dbk:1112 msgid "" "Unless the upstream source has been uploaded to security.debian.org before " "(by a previous security update), build the upload with full upstream source " @@ -1511,7 +1500,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1117 +#: pkgs.dbk:1121 msgid "" "Be sure to use the exact same <filename>*.orig.tar.gz</filename> as used in " "the normal archive, otherwise it is not possible to move the security fix " @@ -1519,7 +1508,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1124 +#: pkgs.dbk:1128 msgid "" "Build the package on a clean system which only has packages installed from " "the distribution you are building for. If you do not have such a system " @@ -1529,12 +1518,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1135 +#: pkgs.dbk:1139 msgid "Uploading the fixed package" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1137 +#: pkgs.dbk:1141 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload a package to the security " "upload queue (oldstable-security, stable-security, etc.) without prior " @@ -1544,7 +1533,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1144 +#: pkgs.dbk:1148 msgid "" "Do <emphasis role=\"strong\">NOT</emphasis> upload your fix to " "proposed-updates without coordinating with the security team. Packages from " @@ -1556,7 +1545,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1153 +#: pkgs.dbk:1157 msgid "" "Once you have created and tested the new package and it has been approved by " "the security team, it needs to be uploaded so that it can be installed in " @@ -1566,7 +1555,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1159 +#: pkgs.dbk:1163 msgid "" "Once an upload to the security queue has been accepted, the package will " "automatically be rebuilt for all architectures and stored for verification " @@ -1574,7 +1563,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1164 +#: pkgs.dbk:1168 msgid "" "Uploads which are waiting for acceptance or verification are only accessible " "by the security team. This is necessary since there might be fixes for " @@ -1582,7 +1571,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1169 +#: pkgs.dbk:1173 msgid "" "If a member of the security team accepts a package, it will be installed on " "security.debian.org as well as proposed for the proper " @@ -1590,12 +1579,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1180 +#: pkgs.dbk:1184 msgid "Moving, removing, renaming, adopting, and orphaning packages" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1182 +#: pkgs.dbk:1186 msgid "" "Some archive manipulation operations are not automated in the Debian upload " "process. These procedures should be manually followed by maintainers. This " @@ -1603,12 +1592,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1187 +#: pkgs.dbk:1191 msgid "Moving packages" msgstr "" # type: Content of: <chapter><section><section><para><footnote> -#: pkgs.dbk:1189 +#: pkgs.dbk:1193 msgid "" "Sometimes a package will change its section. For instance, a package from " "the `non-free' section might be GPL'd in a later version, in which case the " @@ -1616,20 +1605,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para><footnote><para> -#: pkgs.dbk:1191 +#: pkgs.dbk:1195 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for guidelines on what section a package belongs in." +"See the <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"guidelines on what section a package belongs in." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1196 +#: pkgs.dbk:1200 msgid "" "If you need to change the section for one of your packages, change the " "package control information to place the package in the desired section, and " -"re-upload the package (see the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). You must ensure that you include the " +"re-upload the package (see the <ulink url=\"&url-debian-policy;\">Debian " +"Policy Manual</ulink> for details). You must ensure that you include the " "<filename>.orig.tar.gz</filename> in your upload (even if you are not " "uploading a new upstream version), or it will not appear in the new section " "together with the rest of the package. If your new section is valid, it " @@ -1638,7 +1626,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1208 +#: pkgs.dbk:1212 msgid "" "If, on the other hand, you need to change the " "<emphasis>subsection</emphasis> of one of your packages (e.g., ``devel'', " @@ -1649,12 +1637,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1217 +#: pkgs.dbk:1221 msgid "Removing packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1219 +#: pkgs.dbk:1223 msgid "" "If for some reason you want to completely remove a package (say, if it is an " "old compatibility library which is no longer required), you need to file a " @@ -1670,7 +1658,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1232 +#: pkgs.dbk:1236 msgid "" "There is one exception when an explicit removal request is not necessary: If " "a (source or binary) package is an orphan, it will be removed " @@ -1682,7 +1670,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1241 +#: pkgs.dbk:1245 msgid "" "In your removal request, you have to detail the reasons justifying the " "request. This is to avoid unwanted removals and to keep a trace of why a " @@ -1691,7 +1679,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1247 +#: pkgs.dbk:1251 msgid "" "Usually you only ask for the removal of a package maintained by yourself. " "If you want to remove another package, you have to get the approval of its " @@ -1699,31 +1687,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1252 +#: pkgs.dbk:1256 msgid "" "Further information relating to these and other package removal related " "topics may be found at <ulink " "url=\"http://wiki.debian.org/ftpmaster_Removals\"></ulink> and <ulink " -"url=\"http://qa.debian.org/howto-remove.html\"></ulink>." +"url=\"&url-debian-qa;howto-remove.html\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1257 +#: pkgs.dbk:1261 msgid "" "If in doubt concerning whether a package is disposable, email " -"<email>debian-devel@lists.debian.org</email> asking for opinions. Also of " -"interest is the <command>apt-cache</command> program from the <systemitem " +"&email-debian-devel; asking for opinions. Also of interest is the " +"<command>apt-cache</command> program from the <systemitem " "role=\"package\">apt</systemitem> package. When invoked as " "<literal>apt-cache showpkg <replaceable>package</replaceable></literal>, the " "program will show details for <replaceable>package</replaceable>, including " "reverse depends. Other useful programs include <literal>apt-cache " "rdepends</literal>, <command>apt-rdepends</command> and " "<command>grep-dctrl</command>. Removal of orphaned packages is discussed on " -"<email>debian-qa@lists.debian.org</email>." +"&email-debian-qa;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1268 +#: pkgs.dbk:1272 msgid "" "Once the package has been removed, the package's bugs should be handled. " "They should either be reassigned to another package in the case where the " @@ -1733,12 +1721,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1275 +#: pkgs.dbk:1279 msgid "Removing packages from <filename>Incoming</filename>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1277 +#: pkgs.dbk:1281 msgid "" "In the past, it was possible to remove packages from " "<filename>incoming</filename>. However, with the introduction of the new " @@ -1752,26 +1740,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1292 +#: pkgs.dbk:1296 msgid "Replacing or renaming packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1294 +#: pkgs.dbk:1298 msgid "" "When you make a mistake naming your package, you should follow a two-step " "process to rename it. First, set your <filename>debian/control</filename> " "file to replace and conflict with the obsolete name of the package (see the " -"<ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> for details). Once you've uploaded the package and the " -"package has moved into the archive, file a bug against " -"<literal>ftp.debian.org</literal> asking to remove the package with the " -"obsolete name. Do not forget to properly reassign the package's bugs at the " -"same time." +"<ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> for " +"details). Once you've uploaded the package and the package has moved into " +"the archive, file a bug against <literal>ftp.debian.org</literal> asking to " +"remove the package with the obsolete name. Do not forget to properly " +"reassign the package's bugs at the same time." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1304 +#: pkgs.dbk:1308 msgid "" "At other times, you may make a mistake in constructing your package and wish " "to replace it. The only way to do this is to increase the version number " @@ -1786,30 +1773,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1318 +#: pkgs.dbk:1322 msgid "Orphaning a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1320 +#: pkgs.dbk:1324 msgid "" "If you can no longer maintain a package, you need to inform others, and see " "that the package is marked as orphaned. You should set the package " -"maintainer to <literal>Debian QA Group " -"<packages@qa.debian.org></literal> and submit a bug report against the " -"pseudo package <systemitem role=\"package\">wnpp</systemitem>. The bug " -"report should be titled <literal>O: <replaceable>package</replaceable> -- " -"<replaceable>short description</replaceable></literal> indicating that the " -"package is now orphaned. The severity of the bug should be set to " +"maintainer to <literal>Debian QA Group &orphan-address;</literal> and submit " +"a bug report against the pseudo package <systemitem " +"role=\"package\">wnpp</systemitem>. The bug report should be titled " +"<literal>O: <replaceable>package</replaceable> -- <replaceable>short " +"description</replaceable></literal> indicating that the package is now " +"orphaned. The severity of the bug should be set to " "<emphasis>normal</emphasis>; if the package has a priority of standard or " "higher, it should be set to important. If you feel it's necessary, send a " -"copy to <email>debian-devel@lists.debian.org</email> by putting the address " -"in the X-Debbugs-CC: header of the message (no, don't use CC:, because that " -"way the message's subject won't indicate the bug number)." +"copy to &email-debian-devel; by putting the address in the X-Debbugs-CC: " +"header of the message (no, don't use CC:, because that way the message's " +"subject won't indicate the bug number)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1335 +#: pkgs.dbk:1339 msgid "" "If you just intend to give the package away, but you can keep maintainership " "for the moment, then you should instead submit a bug against <systemitem " @@ -1820,29 +1807,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1343 -msgid "" -"More information is on the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">WNPP web pages</ulink>." +#: pkgs.dbk:1347 +msgid "More information is on the <ulink url=\"&url-wnpp;\">WNPP web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1349 +#: pkgs.dbk:1353 msgid "Adopting a package" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1351 +#: pkgs.dbk:1355 msgid "" "A list of packages in need of a new maintainer is available in the <ulink " -"url=\"http://www.debian.org/devel/wnpp/\">Work-Needing and Prospective " -"Packages list (WNPP)</ulink>. If you wish to take over maintenance of any " -"of the packages listed in the WNPP, please take a look at the aforementioned " -"page for information and procedures." +"url=\"&url-wnpp;\">Work-Needing and Prospective Packages list " +"(WNPP)</ulink>. If you wish to take over maintenance of any of the packages " +"listed in the WNPP, please take a look at the aforementioned page for " +"information and procedures." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1358 +#: pkgs.dbk:1362 msgid "" "It is not OK to simply take over a package that you feel is neglected — that " "would be package hijacking. You can, of course, contact the current " @@ -1852,7 +1837,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1364 +#: pkgs.dbk:1368 msgid "" "Generally, you may not take over the package without the assent of the " "current maintainer. Even if they ignore you, that is still not grounds to " @@ -1860,12 +1845,12 @@ msgid "" "the developers' mailing list. If the discussion doesn't end with a positive " "conclusion, and the issue is of a technical nature, consider bringing it to " "the attention of the technical committee (see the <ulink " -"url=\"http://www.debian.org/devel/tech-ctte\">technical committee web " -"page</ulink> for more information)." +"url=\"&url-tech-ctte;\">technical committee web page</ulink> for more " +"information)." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1374 +#: pkgs.dbk:1378 msgid "" "If you take over an old package, you probably want to be listed as the " "package's official maintainer in the bug system. This will happen " @@ -1878,12 +1863,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1388 +#: pkgs.dbk:1392 msgid "Porting and being ported" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1390 +#: pkgs.dbk:1394 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 " @@ -1892,23 +1877,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1396 +#: pkgs.dbk:1400 msgid "" "Porting is the act of building Debian packages for architectures that are " "different from the original architecture of the package maintainer's binary " "package. It is a unique and essential activity. In fact, porters do most " "of the actual compiling of Debian packages. For instance, for a single " "<emphasis>i386</emphasis> binary package, there must be a recompile for each " -"architecture, which amounts to 12 more builds." +"architecture, which amounts to &number-of-arches; more builds." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1404 +#: pkgs.dbk:1408 msgid "Being kind to porters" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1406 +#: pkgs.dbk:1410 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 " @@ -1919,7 +1904,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1414 +#: pkgs.dbk:1418 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 " @@ -1929,7 +1914,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1421 +#: pkgs.dbk:1425 msgid "" "By far, most of the problems encountered by porters are caused by " "<emphasis>packaging bugs</emphasis> in the source packages. Here is a " @@ -1937,7 +1922,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1428 +#: pkgs.dbk:1432 msgid "" "Make sure that your <literal>Build-Depends</literal> and " "<literal>Build-Depends-Indep</literal> settings in " @@ -1955,31 +1940,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1442 +#: pkgs.dbk:1446 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:1446 +#: pkgs.dbk:1450 msgid "" -"See the <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian " -"Policy Manual</ulink> for instructions on setting build dependencies." +"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:1452 +#: pkgs.dbk:1456 msgid "" "Don't set architecture to a value other than ``all'' or ``any'' unless you " "really mean it. In too many cases, maintainers don't follow the " -"instructions in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " +"instructions in the <ulink url=\"&url-debian-policy;\">Debian Policy " "Manual</ulink>. Setting your architecture to ``i386'' is usually incorrect." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1460 +#: pkgs.dbk:1464 msgid "" "Make sure your source package is correct. Do <literal>dpkg-source -x " "<replaceable>package</replaceable>.dsc</literal> to make sure your source " @@ -1988,7 +1972,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1468 +#: pkgs.dbk:1472 msgid "" "Make sure you don't ship your source package with the " "<filename>debian/files</filename> or <filename>debian/substvars</filename> " @@ -1997,7 +1981,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1476 +#: pkgs.dbk:1480 msgid "" "Make sure you don't rely on locally installed or hacked configurations or " "programs. For instance, you should never be calling programs in " @@ -2007,14 +1991,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1485 +#: pkgs.dbk:1489 msgid "" "Don't depend on the package you're building being installed already (a " "sub-case of the above issue)." msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1491 +#: pkgs.dbk:1495 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 " @@ -2023,7 +2007,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><orderedlist><listitem><para> -#: pkgs.dbk:1499 +#: pkgs.dbk:1503 msgid "" "Make sure your debian/rules contains separate ``binary-arch'' and " "``binary-indep'' targets, as the Debian Policy Manual requires. Make sure " @@ -2033,12 +2017,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1510 +#: pkgs.dbk:1514 msgid "Guidelines for porter uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1512 +#: pkgs.dbk:1516 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 " @@ -2049,7 +2033,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1520 +#: pkgs.dbk:1524 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 " @@ -2057,7 +2041,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1525 +#: pkgs.dbk:1529 msgid "" "The way to invoke <command>dpkg-buildpackage</command> is as " "<literal>dpkg-buildpackage -B " @@ -2069,7 +2053,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1533 +#: pkgs.dbk:1537 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 " @@ -2079,12 +2063,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1540 +#: pkgs.dbk:1544 msgid "Recompilation or binary-only NMU" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1542 +#: pkgs.dbk:1546 msgid "" "Sometimes the initial porter upload is problematic because the environment " "in which the package was built was not good enough (outdated or obsolete " @@ -2096,7 +2080,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1551 +#: pkgs.dbk:1555 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 " @@ -2105,7 +2089,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1557 +#: pkgs.dbk:1561 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 " @@ -2113,7 +2097,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1562 +#: pkgs.dbk:1566 msgid "" "Such recompilations require special ``magic'' version numbering, so that the " "archive maintenance tools recognize that, even though there is a new Debian " @@ -2123,7 +2107,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: pkgs.dbk:1569 +#: pkgs.dbk:1573 msgid "" "The ``magic'' for a recompilation-only NMU is triggered by using a suffix " "appended to the package version number, following the form b<number>. " @@ -2134,7 +2118,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: pkgs.dbk:1574 +#: pkgs.dbk:1578 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 " @@ -2144,7 +2128,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1582 +#: pkgs.dbk:1586 msgid "" "Similar to initial porter uploads, the correct way of invoking " "<command>dpkg-buildpackage</command> is <literal>dpkg-buildpackage " @@ -2152,12 +2136,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1589 +#: pkgs.dbk:1593 msgid "When to do a source NMU if you are a porter" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1591 +#: pkgs.dbk:1595 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 " @@ -2170,7 +2154,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1600 +#: pkgs.dbk:1604 msgid "" "If you are a porter doing an NMU for `unstable', the above guidelines for " "porting should be followed, with two variations. Firstly, the acceptable " @@ -2184,7 +2168,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1611 +#: pkgs.dbk:1615 msgid "" "Secondly, porters doing source NMUs should make sure that the bug they " "submit to the BTS should be of severity `serious' or greater. This ensures " @@ -2195,7 +2179,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1619 +#: pkgs.dbk:1623 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 " @@ -2206,7 +2190,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1627 +#: pkgs.dbk:1631 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 " @@ -2215,12 +2199,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1637 +#: pkgs.dbk:1641 msgid "Porting infrastructure and automation" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1639 +#: pkgs.dbk:1643 msgid "" "There is infrastructure and several tools to help automate package porting. " "This section contains a brief overview of this automation and porting to " @@ -2229,40 +2213,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1644 +#: pkgs.dbk:1648 msgid "Mailing lists and web pages" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1646 +#: pkgs.dbk:1650 msgid "" "Web pages containing the status of each port can be found at <ulink " -"url=\"http://www.debian.org/ports/\"></ulink>." +"url=\"&url-debian-ports;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1650 +#: pkgs.dbk:1654 msgid "" "Each port of Debian has a mailing list. The list of porting mailing lists " -"can be found at <ulink url=\"http://lists.debian.org/ports.html\"></ulink>. " -"These lists are used to coordinate porters, and to connect the users of a " -"given port with the porters." +"can be found at <ulink url=\"&url-debian-port-lists;\"></ulink>. These " +"lists are used to coordinate porters, and to connect the users of a given " +"port with the porters." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:1658 +#: pkgs.dbk:1662 msgid "Porter tools" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1660 +#: pkgs.dbk:1664 msgid "" "Descriptions of several porting tools can be found in <xref " "linkend=\"tools-porting\"/> ." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1668 +#: pkgs.dbk:1672 msgid "" "The <systemitem role=\"package\">buildd</systemitem> system is used as a " "distributed, client-server build distribution system. It is usually used in " @@ -2274,7 +2258,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1677 +#: pkgs.dbk:1681 msgid "" "<systemitem role=\"package\">buildd</systemitem> is not yet available as a " "package; however, most porting efforts are either using it currently or " @@ -2288,18 +2272,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1687 +#: pkgs.dbk:1691 msgid "" "Some of the data produced by <systemitem " "role=\"package\">buildd</systemitem> which is generally useful to porters is " -"available on the web at <ulink url=\"http://buildd.debian.org/\"></ulink>. " -"This data includes nightly updated information from " -"<command>andrea</command> (source dependencies) and <systemitem " -"role=\"package\">quinn-diff</systemitem> (packages needing recompilation)." +"available on the web at <ulink url=\"&url-buildd;\"></ulink>. This data " +"includes nightly updated information from <command>andrea</command> (source " +"dependencies) and <systemitem role=\"package\">quinn-diff</systemitem> " +"(packages needing recompilation)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1695 +#: pkgs.dbk:1699 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 " @@ -2309,19 +2293,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:1702 +#: pkgs.dbk:1706 msgid "" "The buildds admins of each arch can be contacted at the mail address " "$arch@buildd.debian.org." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1710 +#: pkgs.dbk:1714 msgid "When your package is <emphasis>not</emphasis> portable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1712 +#: pkgs.dbk:1716 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 " @@ -2331,14 +2315,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1719 +#: pkgs.dbk:1723 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:1725 +#: pkgs.dbk:1729 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 " @@ -2350,7 +2334,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1733 +#: pkgs.dbk:1737 msgid "" "Additionally, if you believe the list of supported architectures is pretty " "constant, you should change 'any' to a list of supported architectures in " @@ -2359,18 +2343,18 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1741 +#: pkgs.dbk:1745 msgid "" "In order to prevent autobuilders from needlessly trying to build your " "package, it must be included in <filename>packages-arch-specific</filename>, " "a list used by the <command>wanna-build</command> script. The current " "version is available as <ulink " -"url=\"http://cvs.debian.org/srcdep/Packages-arch-specific?cvsroot=dak\"></ulink>; " +"url=\"&url-cvsweb;srcdep/Packages-arch-specific?cvsroot=dak\"></ulink>; " "please see the top of the file for whom to contact for changes." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1751 +#: pkgs.dbk:1755 msgid "" "Please note that it is insufficient to only add your package to " "Packages-arch-specific without making it fail to build on unsupported " @@ -2382,12 +2366,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:1764 +#: pkgs.dbk:1768 msgid "Non-Maintainer Uploads (NMUs)" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1766 +#: pkgs.dbk:1770 msgid "" "Under certain circumstances it is necessary for someone other than the " "official package maintainer to make a release of a package. This is called " @@ -2395,7 +2379,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1771 +#: pkgs.dbk:1775 msgid "" "This section handles only source NMUs, i.e. NMUs which upload a new version " "of the package. For binary-only NMUs by porters or QA members, please see " @@ -2405,7 +2389,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1778 +#: pkgs.dbk:1782 msgid "" "The main reason why NMUs are done is when a developer needs to fix another " "developer's package in order to address serious problems or crippling bugs " @@ -2414,7 +2398,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1783 +#: pkgs.dbk:1787 msgid "" "First and foremost, it is critical that NMU patches to source should be as " "non-disruptive as possible. Do not do housekeeping tasks, do not change the " @@ -2426,7 +2410,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:1792 +#: pkgs.dbk:1796 msgid "" "And please remember the Hippocratic Oath: Above all, do no harm. It is " "better to leave a package with an open grave bug than applying a " @@ -2434,12 +2418,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1797 +#: pkgs.dbk:1801 msgid "How to do a NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1799 +#: pkgs.dbk:1803 msgid "" "NMUs which fix important, serious or higher severity bugs are encouraged and " "accepted. You should endeavor to reach the current maintainer of the " @@ -2448,7 +2432,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1805 +#: pkgs.dbk:1809 msgid "" "NMUs should be made to assist a package's maintainer in resolving bugs. " "Maintainers should be thankful for that help, and NMUers should respect the " @@ -2457,14 +2441,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1811 +#: pkgs.dbk:1815 msgid "" "A NMU should follow all conventions, written down in this section. For an " "upload to testing or unstable, this order of steps is recommended:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1817 +#: pkgs.dbk:1821 msgid "" "Make sure that the package's bugs that the NMU is meant to address are all " "filed in the Debian Bug Tracking System (BTS). If they are not, submit them " @@ -2472,7 +2456,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1824 +#: pkgs.dbk:1828 msgid "" "Wait a few days for the response from the maintainer. If you don't get any " "response, you may want to help them by sending the patch that fixes the " @@ -2480,7 +2464,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1831 +#: pkgs.dbk:1835 msgid "" "Wait a few more days. If you still haven't got an answer from the " "maintainer, send them a mail announcing your intent to NMU the package. " @@ -2491,7 +2475,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1841 +#: pkgs.dbk:1845 msgid "" "Upload your package to incoming in <filename>DELAYED/7-day</filename> (cf. " "<xref linkend=\"delayed-incoming\"/> ), send the final patch to the " @@ -2500,7 +2484,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:1849 +#: pkgs.dbk:1853 msgid "" "Follow what happens, you're responsible for any bug that you introduced with " "your NMU. You should probably use <xref linkend=\"pkg-tracking-system\"/> " @@ -2508,7 +2492,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1856 +#: pkgs.dbk:1860 msgid "" "At times, the release manager or an organized group of developers can " "announce a certain period of time in which the NMU rules are relaxed. This " @@ -2520,7 +2504,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1865 +#: pkgs.dbk:1869 msgid "" "For the testing distribution, the rules may be changed by the release " "managers. Please take additional care, and acknowledge that the usual way " @@ -2528,7 +2512,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1870 +#: pkgs.dbk:1874 msgid "" "For the stable distribution, please take extra care. Of course, the release " "managers may also change the rules here. Please verify before you upload " @@ -2537,7 +2521,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1876 +#: pkgs.dbk:1880 msgid "" "When a security bug is detected, the security team may do an NMU, using " "their own rules. Please refer to <xref linkend=\"bug-security\"/> for more " @@ -2545,14 +2529,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1881 +#: pkgs.dbk:1885 msgid "" "For the differences for Porters NMUs, please see <xref " "linkend=\"source-nmu-when-porter\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1885 +#: pkgs.dbk:1889 msgid "" "Of course, it is always possible to agree on special rules with a maintainer " "(like the maintainer asking please upload this fix directly for me, and no " @@ -2560,12 +2544,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1892 +#: pkgs.dbk:1896 msgid "NMU version numbering" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1894 +#: pkgs.dbk:1898 msgid "" "Whenever you have made a change to a package, no matter how trivial, the " "version number needs to change. This enables our packing system to " @@ -2573,7 +2557,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1898 +#: pkgs.dbk:1902 msgid "" "If you are doing a non-maintainer upload (NMU), you should add a new minor " "version number to the <replaceable>debian-revision</replaceable> part of the " @@ -2587,7 +2571,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1909 +#: pkgs.dbk:1913 msgid "" "The Debian revision minor number is needed to avoid stealing one of the " "package maintainer's version numbers, which might disrupt their work. It " @@ -2596,7 +2580,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1915 +#: pkgs.dbk:1919 msgid "" "If there is no <replaceable>debian-revision</replaceable> component in the " "version number then one should be created, starting at `0.1' (but in case of " @@ -2609,7 +2593,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1925 +#: pkgs.dbk:1929 msgid "" "If you upload a package to testing or stable, sometimes, you need to fork " "the version number tree. For this, version numbers like 1.1-3sarge0.1 could " @@ -2617,12 +2601,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1932 +#: pkgs.dbk:1936 msgid "Source NMUs must have a new changelog entry" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1934 +#: pkgs.dbk:1938 msgid "" "Anyone who is doing a source NMU must create a changelog entry, describing " "which bugs are fixed by the NMU, and generally why the NMU was required and " @@ -2631,23 +2615,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1940 +#: pkgs.dbk:1944 msgid "By convention, source NMU changelog entries start with the line" msgstr "" # type: Content of: <chapter><section><section><screen> -#: pkgs.dbk:1943 +#: pkgs.dbk:1947 #, no-wrap msgid "* Non-maintainer upload" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1948 +#: pkgs.dbk:1952 msgid "Source NMUs and the Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1950 +#: pkgs.dbk:1954 msgid "" "Maintainers other than the official package maintainer should make as few " "changes to the package as possible, and they should always send a patch as a " @@ -2656,7 +2640,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1956 +#: pkgs.dbk:1960 msgid "" "What if you are simply recompiling the package? If you just need to " "recompile it for a single architecture, then you may do a binary-only NMU as " @@ -2667,7 +2651,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1963 +#: pkgs.dbk:1967 msgid "" "Bugs fixed by source NMUs used to be tagged fixed instead of closed, but " "since version tracking is in place, such bugs are now also closed with the " @@ -2675,7 +2659,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1968 +#: pkgs.dbk:1972 msgid "" "Also, after doing an NMU, you have to send the information to the existing " "bugs that are fixed by your NMU, including the unified diff. Historically, " @@ -2690,7 +2674,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1979 +#: pkgs.dbk:1983 msgid "" "In addition, the normal maintainer should <emphasis>always</emphasis> retain " "the entry in the changelog file documenting the non-maintainer upload -- and " @@ -2699,12 +2683,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:1987 +#: pkgs.dbk:1991 msgid "Building source NMUs" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1989 +#: pkgs.dbk:1993 msgid "" "Source NMU packages are built normally. Pick a distribution using the same " "rules as found in <xref linkend=\"distribution\"/> , follow the other " @@ -2712,7 +2696,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:1994 +#: pkgs.dbk:1998 msgid "" "Make sure you do <emphasis>not</emphasis> change the value of the maintainer " "in the <filename>debian/control</filename> file. Your name as given in the " @@ -2721,12 +2705,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2002 +#: pkgs.dbk:2006 msgid "Acknowledging an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2004 +#: pkgs.dbk:2008 msgid "" "If one of your packages has been NMU'ed, you have to incorporate the changes " "in your copy of the sources. This is easy, you just have to apply the patch " @@ -2740,7 +2724,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2015 +#: pkgs.dbk:2019 msgid "" "In any case, you should not be upset by the NMU. An NMU is not a personal " "attack against the maintainer. It is a proof that someone cares enough " @@ -2751,28 +2735,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2025 +#: pkgs.dbk:2029 msgid "NMU vs QA uploads" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2027 +#: pkgs.dbk:2031 msgid "" "Unless you know the maintainer is still active, it is wise to check the " "package to see if it has been orphaned. The current list of orphaned " "packages which haven't had their maintainer set correctly is available at " -"<ulink url=\"http://qa.debian.org/orphaned.html\"></ulink>. If you perform " -"an NMU on an improperly orphaned package, please set the maintainer to " -"``Debian QA Group <packages@qa.debian.org>''." +"<ulink url=\"&url-debian-qa-orphaned;\"></ulink>. If you perform an NMU on " +"an improperly orphaned package, please set the maintainer to <literal>Debian " +"QA Group <packages@qa.debian.org></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2037 +#: pkgs.dbk:2041 msgid "Who can do an NMU" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2039 +#: pkgs.dbk:2043 msgid "" "Only official, registered Debian Developers can do binary or source NMUs. A " "Debian Developer is someone who has their key in the Debian key ring. " @@ -2783,12 +2767,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2049 +#: pkgs.dbk:2053 msgid "Terminology" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2051 +#: pkgs.dbk:2055 msgid "" "There are two new terms used throughout this section: ``binary-only NMU'' " "and ``source NMU''. These terms are used with specific technical meaning " @@ -2799,7 +2783,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2059 +#: pkgs.dbk:2063 msgid "" "A source NMU is an upload of a package by a developer who is not the " "official maintainer, for the purposes of fixing a bug in the package. " @@ -2811,7 +2795,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2068 +#: pkgs.dbk:2072 msgid "" "A binary-only NMU is a recompilation and upload of a binary package for a " "given architecture. As such, it is usually part of a porting effort. A " @@ -2824,7 +2808,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2078 +#: pkgs.dbk:2082 msgid "" "Both classes of NMUs, source and binary-only, can be lumped under the term " "``NMU''. However, this often leads to confusion, since most people think " @@ -2833,12 +2817,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2088 +#: pkgs.dbk:2092 msgid "Collaborative maintenance" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2090 +#: pkgs.dbk:2094 msgid "" "Collaborative maintenance is a term describing the sharing of Debian package " "maintenance duties by several people. This collaboration is almost always a " @@ -2849,7 +2833,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2098 +#: pkgs.dbk:2102 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 " @@ -2859,14 +2843,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2104 +#: pkgs.dbk:2108 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:2110 +#: pkgs.dbk:2114 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 " @@ -2876,7 +2860,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2118 +#: pkgs.dbk:2122 msgid "" "Add the co-maintainer's correct maintainer name and address to the " "<literal>Uploaders</literal> field in the global part of the " @@ -2884,20 +2868,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><screen> -#: pkgs.dbk:2123 +#: pkgs.dbk:2127 #, no-wrap -msgid ": John Buzz <jbuzz@debian.org>, Adam Rex <arex@debian.org>" +msgid "" +"Uploaders: John Buzz <jbuzz@debian.org>, Adam Rex " +"<arex@debian.org>" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: pkgs.dbk:2128 +#: pkgs.dbk:2132 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:2134 +#: pkgs.dbk:2138 msgid "" "Another form of collaborative maintenance is team maintenance, which is " "recommended if you maintain several packages with the same group of " @@ -2907,7 +2893,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2143 +#: pkgs.dbk:2147 msgid "" "Put the team member mainly responsible for the package in the Maintainer " "field. In the Uploaders, put the mailing list address, and the team members " @@ -2915,7 +2901,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><orderedlist><listitem><para> -#: pkgs.dbk:2150 +#: pkgs.dbk:2154 msgid "" "Put the mailing list address in the Maintainer field. In the Uploaders " "field, put the team members who care for the package. In this case, you " @@ -2924,7 +2910,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: pkgs.dbk:2158 +#: pkgs.dbk:2162 msgid "" "In any case, it is a bad idea to automatically put all team members in the " "Uploaders field. It clutters the Developer's Package Overview listing (see " @@ -2933,24 +2919,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: pkgs.dbk:2166 +#: pkgs.dbk:2170 msgid "The testing distribution" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2168 +#: pkgs.dbk:2172 msgid "Basics" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2170 +#: pkgs.dbk:2174 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2174 +#: pkgs.dbk:2178 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 " @@ -2960,12 +2946,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2183 +#: pkgs.dbk:2187 msgid "Updates from unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2185 +#: pkgs.dbk:2189 msgid "" "The scripts that update the <emphasis>testing</emphasis> distribution are " "run each day after the installation of the updated packages; these scripts " @@ -2976,14 +2962,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2193 +#: pkgs.dbk:2197 msgid "" "The inclusion of a package from <emphasis>unstable</emphasis> is conditional " "on the following:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2199 +#: pkgs.dbk:2203 msgid "" "The package must have been available in <emphasis>unstable</emphasis> for 2, " "5 or 10 days, depending on the urgency (high, medium or low). Please note " @@ -2994,14 +2980,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2208 +#: pkgs.dbk:2212 msgid "" "It must have the same number or fewer release-critical bugs than the version " "currently available in <emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2214 +#: pkgs.dbk:2218 msgid "" "It must be available on all architectures on which it has previously been " "built in unstable. <xref linkend=\"madison\"/> may be of interest to check " @@ -3009,14 +2995,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2221 +#: pkgs.dbk:2225 msgid "" "It must not break any dependency of a package which is already available in " "<emphasis>testing</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2227 +#: pkgs.dbk:2231 msgid "" "The packages on which it depends must either be available in " "<emphasis>testing</emphasis> or they must be accepted into " @@ -3025,32 +3011,30 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2235 +#: pkgs.dbk:2239 msgid "" "To find out whether a package is progressing into testing or not, see the " -"testing script output on the <ulink " -"url=\"http://www.debian.org/devel/testing\">web page of the testing " -"distribution</ulink>, or use the program <command>grep-excuses</command> " -"which is in the <systemitem role=\"package\">devscripts</systemitem> " -"package. This utility can easily be used in a <citerefentry> " -"<refentrytitle>crontab</refentrytitle> <manvolnum>5</manvolnum> " -"</citerefentry> to keep yourself informed of the progression of your " -"packages into <emphasis>testing</emphasis>." +"testing script output on the <ulink url=\"&url-testing-maint;\">web page of " +"the testing distribution</ulink>, or use the program " +"<command>grep-excuses</command> which is in the <systemitem " +"role=\"package\">devscripts</systemitem> package. This utility can easily " +"be used in a <citerefentry> <refentrytitle>crontab</refentrytitle> " +"<manvolnum>5</manvolnum> </citerefentry> to keep yourself informed of the " +"progression of your packages into <emphasis>testing</emphasis>." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2246 +#: pkgs.dbk:2250 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 " "own by looking for what would break with the inclusion of the package. The " -"<ulink url=\"http://www.debian.org/devel/testing\">testing web page</ulink> " -"gives some more information about the usual problems which may be causing " -"such troubles." +"<ulink url=\"&url-testing-maint;\">testing web page</ulink> gives some more " +"information about the usual problems which may be causing such troubles." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2253 +#: pkgs.dbk:2257 msgid "" "Sometimes, some packages never enter <emphasis>testing</emphasis> because " "the set of inter-relationship is too complicated and cannot be sorted out by " @@ -3058,7 +3042,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2258 +#: pkgs.dbk:2262 msgid "" "Some further dependency analysis is shown on <ulink " "url=\"http://bjorn.haxx.se/debian/\"></ulink> — but be warned, this page " @@ -3066,12 +3050,13 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2263 +#: pkgs.dbk:2267 msgid "out-of-date" msgstr "" +#. FIXME: better rename this file than document rampant professionalism? # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2265 +#: pkgs.dbk:2270 msgid "" "For the testing migration script, outdated means: There are different " "versions in unstable for the release architectures (except for the " @@ -3081,47 +3066,47 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2272 +#: pkgs.dbk:2277 msgid "Consider this example:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2279 pkgs.dbk:2310 +#: pkgs.dbk:2284 pkgs.dbk:2315 msgid "alpha" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2280 pkgs.dbk:2311 +#: pkgs.dbk:2285 pkgs.dbk:2316 msgid "arm" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2285 pkgs.dbk:2317 pkgs.dbk:2377 +#: pkgs.dbk:2290 pkgs.dbk:2322 pkgs.dbk:2382 msgid "testing" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2286 pkgs.dbk:2291 pkgs.dbk:2318 pkgs.dbk:2319 pkgs.dbk:2326 +#: pkgs.dbk:2291 pkgs.dbk:2296 pkgs.dbk:2323 pkgs.dbk:2324 pkgs.dbk:2331 msgid "1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2287 pkgs.dbk:2320 pkgs.dbk:2325 +#: pkgs.dbk:2292 pkgs.dbk:2325 pkgs.dbk:2330 msgid "-" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2290 pkgs.dbk:2323 pkgs.dbk:2378 +#: pkgs.dbk:2295 pkgs.dbk:2328 pkgs.dbk:2383 msgid "unstable" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2292 pkgs.dbk:2324 +#: pkgs.dbk:2297 pkgs.dbk:2329 msgid "2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2298 +#: pkgs.dbk:2303 msgid "" "The package is out of date on alpha in unstable, and will not go to " "testing. And removing foo from testing would not help at all, the package " @@ -3129,17 +3114,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2303 +#: pkgs.dbk:2308 msgid "However, if ftp-master removes a package in unstable (here on arm):" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><thead><row><entry> -#: pkgs.dbk:2312 +#: pkgs.dbk:2317 msgid "hurd-i386" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2332 +#: pkgs.dbk:2337 msgid "" "In this case, the package is up to date on all release architectures in " "unstable (and the extra hurd-i386 doesn't matter, as it's not a release " @@ -3147,7 +3132,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2337 +#: pkgs.dbk:2342 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 " @@ -3155,12 +3140,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2344 +#: pkgs.dbk:2349 msgid "Removals from testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2346 +#: pkgs.dbk:2351 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 " @@ -3170,26 +3155,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2353 +#: pkgs.dbk:2358 msgid "" "Of course, there is another reason to remove a package from testing: It's " "just too buggy (and having a single RC-bug is enough to be in this state)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2357 +#: pkgs.dbk:2362 msgid "" "Furthermore, if a package has been removed from unstable, and no package in " "testing depends on it any more, then it will automatically be removed." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2363 +#: pkgs.dbk:2368 msgid "circular dependencies" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2365 +#: pkgs.dbk:2370 msgid "" "A situation which is not handled very well by britney is if package " "<emphasis>a</emphasis> depends on the new version of package " @@ -3197,63 +3182,62 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2370 +#: pkgs.dbk:2375 msgid "An example of this is:" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2383 +#: pkgs.dbk:2388 msgid "a" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2384 +#: pkgs.dbk:2389 msgid "1; depends: b=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2385 +#: pkgs.dbk:2390 msgid "2; depends: b=2" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2388 +#: pkgs.dbk:2393 msgid "b" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2389 +#: pkgs.dbk:2394 msgid "1; depends: a=1" msgstr "" # type: Content of: <chapter><section><section><section><informaltable><tgroup><tbody><row><entry> -#: pkgs.dbk:2390 +#: pkgs.dbk:2395 msgid "2; depends: a=2" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2396 +#: pkgs.dbk:2401 msgid "" "Neither package <emphasis>a</emphasis> nor package <emphasis>b</emphasis> is " "considered for update." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2400 +#: pkgs.dbk:2405 msgid "" "Currently, this requires some manual hinting from the release team. Please " -"contact them by sending mail to " -"<email>debian-release@lists.debian.org</email> if this happens to one of " -"your packages." +"contact them by sending mail to &email-debian-release; if this happens to " +"one of your packages." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2407 +#: pkgs.dbk:2412 msgid "influence of package in testing" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2409 +#: pkgs.dbk:2414 msgid "" "Generally, there is nothing that the status of a package in testing means " "for transition of the next version from unstable to testing, with two " @@ -3267,7 +3251,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2419 +#: pkgs.dbk:2424 msgid "" "In summary this means: The only influence that a package being in testing " "has on a new version of the same package is that the new version might go in " @@ -3275,17 +3259,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2426 +#: pkgs.dbk:2431 msgid "details" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2428 +#: pkgs.dbk:2433 msgid "If you are interested in details, this is how britney works:" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2431 +#: pkgs.dbk:2436 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 " @@ -3298,7 +3282,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2440 +#: pkgs.dbk:2445 msgid "" "Now, the more complex part happens: Britney tries to update testing with the " "valid candidates; first, each package alone, and then larger and even larger " @@ -3309,29 +3293,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2448 +#: pkgs.dbk:2453 msgid "" "If you want to see more details, you can look it up on " -"merkel:/org/ftp.debian.org/testing/update_out/ (or there in " +"merkel:/org/&ftp-debian-org;/testing/update_out/ (or there in " "~aba/testing/update_out to see a setup with a smaller packages file). Via " "web, it's at <ulink " -"url=\"http://ftp-master.debian.org/testing/update_out_code/\"></ulink>" +"url=\"http://&ftp-master-host;/testing/update_out_code/\"></ulink>" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2455 +#: pkgs.dbk:2460 msgid "" "The hints are available via <ulink " -"url=\"http://ftp-master.debian.org/testing/hints/\"></ulink>." +"url=\"http://&ftp-master-host;/testing/hints/\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2463 +#: pkgs.dbk:2468 msgid "Direct updates to testing" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2465 +#: pkgs.dbk:2470 msgid "" "The testing distribution is fed with packages from unstable according to the " "rules explained above. However, in some cases, it is necessary to upload " @@ -3340,17 +3324,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2471 +#: pkgs.dbk:2476 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 " "have a good reason to upload there. In order to know what a good reason is " "in the release managers' eyes, you should read the instructions that they " -"regularly give on <email>debian-devel-announce@lists.debian.org</email>." +"regularly give on &email-debian-devel-announce;." msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2478 +#: pkgs.dbk:2483 msgid "" "You should not upload to <emphasis>testing-proposed-updates</emphasis> when " "you can update your packages through <emphasis>unstable</emphasis>. If you " @@ -3362,7 +3346,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2487 +#: pkgs.dbk:2492 msgid "" "Version numbers are usually selected by adding the codename of the testing " "distribution and a running number, like 1.2sarge1 for the first upload " @@ -3370,12 +3354,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: pkgs.dbk:2492 +#: pkgs.dbk:2497 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:2497 +#: pkgs.dbk:2502 msgid "" "Make sure that your package really needs to go through " "<emphasis>testing-proposed-updates</emphasis>, and can't go through " @@ -3383,31 +3367,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2503 +#: pkgs.dbk:2508 msgid "Make sure that you included only the minimal amount of changes;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2508 +#: pkgs.dbk:2513 msgid "Make sure that you included an appropriate explanation in the changelog;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2513 +#: pkgs.dbk:2518 msgid "" "Make sure that you've written <emphasis>testing</emphasis> or " "<emphasis>testing-proposed-updates</emphasis> into your target distribution;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2519 +#: pkgs.dbk:2524 msgid "" "Make sure that you've built and tested your package in " "<emphasis>testing</emphasis>, not in <emphasis>unstable</emphasis>;" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2525 +#: pkgs.dbk:2530 msgid "" "Make sure that your version number is higher than the version in " "<emphasis>testing</emphasis> and " @@ -3416,32 +3400,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: pkgs.dbk:2532 +#: pkgs.dbk:2537 msgid "" "After uploading and successful build on all platforms, contact the release " -"team at <email>debian-release@lists.debian.org</email> and ask them to " -"approve your upload." +"team at &email-debian-release; and ask them to approve your upload." msgstr "" # type: Content of: <chapter><section><section><title> -#: pkgs.dbk:2541 +#: pkgs.dbk:2545 msgid "Frequently asked questions" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2543 +#: pkgs.dbk:2547 msgid "What are release-critical bugs, and how do they get counted?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2545 +#: pkgs.dbk:2549 msgid "" "All bugs of some higher severities are by default considered " "release-critical; currently, these are critical, grave, and serious bugs." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2549 +#: pkgs.dbk:2553 msgid "" "Such bugs are presumed to have an impact on the chances that the package " "will be released with the stable release of Debian: in general, if a package " @@ -3450,7 +3433,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2555 +#: pkgs.dbk:2559 msgid "" "The unstable bug count are all release-critical bugs without either any " "release-tag (such as potato, woody) or with release-tag sid; also, only if " @@ -3460,19 +3443,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2562 +#: pkgs.dbk:2566 msgid "" "This will change post-sarge, as soon as we have versions in the bug tracking " "system." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: pkgs.dbk:2568 +#: pkgs.dbk:2572 msgid "How could installing a package into testing possibly break other packages?" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2570 +#: pkgs.dbk:2574 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 " @@ -3482,7 +3465,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2577 +#: pkgs.dbk:2581 msgid "" "However, the old version may have provided a binary package with an old " "soname of a library, such as libacme-foo0. Removing the old acmefoo will " @@ -3490,7 +3473,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2582 +#: pkgs.dbk:2586 msgid "" "Evidently, this mainly affects packages which provide changing sets of " "binary packages in different versions (in turn, mainly libraries). However, " @@ -3499,7 +3482,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2588 +#: pkgs.dbk:2592 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 " @@ -3512,7 +3495,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: pkgs.dbk:2598 +#: pkgs.dbk:2602 msgid "" "If you are having problems with complicated groups of packages like this, " "contact debian-devel or debian-release for help." diff --git a/po4a/po/resources.pot b/po4a/po/resources.pot index 856c359..ecc2c54 100644 --- a/po4a/po/resources.pot +++ b/po4a/po/resources.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,12 +15,12 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: resources.dbk:5 +#: resources.dbk:7 msgid "Resources for Debian Developers" msgstr "" # type: Content of: <chapter><para> -#: resources.dbk:7 +#: resources.dbk:9 msgid "" "In this chapter you will find a very brief road map of the Debian mailing " "lists, the Debian machines which may be available to you as a developer, and " @@ -29,31 +29,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:12 +#: resources.dbk:14 msgid "Mailing lists" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:14 +#: resources.dbk:16 msgid "" "Much of the conversation between Debian developers (and users) is managed " "through a wide array of mailing lists we host at <literal><ulink " -"url=\"http://lists.debian.org/\">lists.debian.org</ulink></literal>. To " -"find out more on how to subscribe or unsubscribe, how to post and how not to " -"post, where to find old posts and how to search them, how to contact the " -"list maintainers and see various other information about the mailing lists, " -"please read <ulink url=\"http://www.debian.org/MailingLists/\"></ulink>. " -"This section will only cover aspects of mailing lists that are of particular " -"interest to developers." +"url=\"http://&lists-host;/\">&lists-host;</ulink></literal>. To find out " +"more on how to subscribe or unsubscribe, how to post and how not to post, " +"where to find old posts and how to search them, how to contact the list " +"maintainers and see various other information about the mailing lists, " +"please read <ulink url=\"&url-debian-lists;\"></ulink>. This section will " +"only cover aspects of mailing lists that are of particular interest to " +"developers." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:24 +#: resources.dbk:27 msgid "Basic rules for use" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:26 +#: resources.dbk:29 msgid "" "When replying to messages on the mailing list, please do not send a carbon " "copy (<literal>CC</literal>) to the original poster unless they explicitly " @@ -62,7 +62,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:32 +#: resources.dbk:35 msgid "" "Cross-posting (sending the same message to multiple lists) is discouraged. " "As ever on the net, please trim down the quoting of articles you're replying " @@ -71,95 +71,90 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:37 +#: resources.dbk:40 msgid "" -"Please read the <ulink " -"url=\"http://www.debian.org/MailingLists/#codeofconduct\">code of " +"Please read the <ulink url=\"&url-debian-lists;#codeofconduct\">code of " "conduct</ulink> for more information." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:44 +#: resources.dbk:47 msgid "Core development mailing lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:46 +#: resources.dbk:49 msgid "The core Debian mailing lists that developers should use are:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:51 +#: resources.dbk:54 msgid "" -"<email>debian-devel-announce@lists.debian.org</email>, used to announce " -"important things to developers. All developers are expected to be " -"subscribed to this list." +"&email-debian-devel-announce;, used to announce important things to " +"developers. All developers are expected to be subscribed to this list." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:58 +#: resources.dbk:61 msgid "" -"<email>debian-devel@lists.debian.org</email>, used to discuss various " -"development related technical issues." +"&email-debian-devel;, used to discuss various development related technical " +"issues." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:64 -msgid "" -"<email>debian-policy@lists.debian.org</email>, where the Debian Policy is " -"discussed and voted on." +#: resources.dbk:67 +msgid "&email-debian-policy;, where the Debian Policy is discussed and voted on." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:70 +#: resources.dbk:73 msgid "" -"<email>debian-project@lists.debian.org</email>, used to discuss various " -"non-technical issues related to the project." +"&email-debian-project;, used to discuss various non-technical issues related " +"to the project." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:76 +#: resources.dbk:79 msgid "" "There are other mailing lists available for a variety of special topics; see " -"<ulink url=\"http://lists.debian.org/\"></ulink> for a list." +"<ulink url=\"http://&lists-host;/\"></ulink> for a list." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:82 +#: resources.dbk:85 msgid "Special lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:84 +#: resources.dbk:87 msgid "" -"<email>debian-private@lists.debian.org</email> is a special mailing list for " -"private discussions amongst Debian developers. It is meant to be used for " -"posts which for whatever reason should not be published publicly. As such, " -"it is a low volume list, and users are urged not to use " -"<email>debian-private@lists.debian.org</email> unless it is really " -"necessary. Moreover, do <emphasis>not</emphasis> forward email from that " -"list to anyone. Archives of this list are not available on the web for " -"obvious reasons, but you can see them using your shell account on " -"<literal>lists.debian.org</literal> and looking in the " -"<filename>~debian/archive/debian-private</filename> directory." +"&email-debian-private; is a special mailing list for private discussions " +"amongst Debian developers. It is meant to be used for posts which for " +"whatever reason should not be published publicly. As such, it is a low " +"volume list, and users are urged not to use &email-debian-private; unless it " +"is really necessary. Moreover, do <emphasis>not</emphasis> forward email " +"from that list to anyone. Archives of this list are not available on the " +"web for obvious reasons, but you can see them using your shell account on " +"<literal>&lists-host;</literal> and looking in the " +"<filename>&file-debian-private-archive;</filename> directory." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:96 +#: resources.dbk:99 msgid "" -"<email>debian-email@lists.debian.org</email> is a special mailing list used " -"as a grab-bag for Debian related correspondence such as contacting upstream " -"authors about licenses, bugs, etc. or discussing the project with others " -"where it might be useful to have the discussion archived somewhere." +"&email-debian-email; is a special mailing list used as a grab-bag for Debian " +"related correspondence such as contacting upstream authors about licenses, " +"bugs, etc. or discussing the project with others where it might be useful " +"to have the discussion archived somewhere." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:104 +#: resources.dbk:107 msgid "Requesting new development-related lists" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:106 +#: resources.dbk:109 msgid "" "Before requesting a mailing list that relates to the development of a " "package (or a small group of related packages), please consider if using an " @@ -170,31 +165,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:114 +#: resources.dbk:117 msgid "" -"If you decide that a regular mailing list on lists.debian.org is really what " -"you want, go ahead and fill in a request, following <ulink " -"url=\"http://www.debian.org/MailingLists/HOWTO_start_list\">the " -"HOWTO</ulink>." +"If you decide that a regular mailing list on &lists-host; is really what you " +"want, go ahead and fill in a request, following <ulink " +"url=\"&url-debian-lists-new;\">the HOWTO</ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:123 +#: resources.dbk:126 msgid "IRC channels" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:125 +#: resources.dbk:128 msgid "" "Several IRC channels are dedicated to Debian's development. They are mainly " -"hosted on the <ulink url=\"http://www.oftc.net/oftc/\">Open and free " -"technology community (OFTC)</ulink> network. The " -"<literal>irc.debian.org</literal> DNS entry is an alias to " -"<literal>irc.oftc.net</literal>." +"hosted on the <ulink url=\"&url-oftc;\">Open and free technology community " +"(OFTC)</ulink> network. The <literal>irc.debian.org</literal> DNS entry is " +"an alias to <literal>irc.oftc.net</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:131 +#: resources.dbk:134 msgid "" "The main channel for Debian in general is <emphasis>#debian</emphasis>. " "This is a large, general-purpose channel where users can find recent news in " @@ -205,7 +198,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:139 +#: resources.dbk:142 msgid "" "The main channel for Debian development is " "<emphasis>#debian-devel</emphasis>. It is a very active channel since " @@ -217,20 +210,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:147 +#: resources.dbk:150 msgid "" "Since <emphasis>#debian-devel</emphasis> is an open channel, you should not " -"speak there of issues that are discussed in " -"<email>debian-private@lists.debian.org</email>. There's another channel for " -"this purpose, it's called <emphasis>#debian-private</emphasis> and it's " -"protected by a key. This key is available in the archives of debian-private " -"in <filename>master.debian.org:~debian/archive/debian-private/</filename>, " -"just <command>zgrep</command> for <emphasis>#debian-private</emphasis> in " -"all the files." +"speak there of issues that are discussed in &email-debian-private;. There's " +"another channel for this purpose, it's called " +"<emphasis>#debian-private</emphasis> and it's protected by a key. This key " +"is available in the archives of debian-private in " +"<filename>master.debian.org:&file-debian-private-archive;</filename>, just " +"<command>zgrep</command> for <emphasis>#debian-private</emphasis> in all the " +"files." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:157 +#: resources.dbk:160 msgid "" "There are other additional channels dedicated to specific subjects. " "<emphasis>#debian-bugs</emphasis> is used for coordinating bug squashing " @@ -245,7 +238,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:169 +#: resources.dbk:172 msgid "" "Some non-English developers' channels exist as well, for example " "<emphasis>#debian-devel-fr</emphasis> for French speaking people interested " @@ -253,16 +246,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:174 +#: resources.dbk:177 msgid "" "Channels dedicated to Debian also exist on other IRC networks, notably on " -"the <ulink url=\"http://www.freenode.net/\">freenode</ulink> IRC network, " -"which was pointed at by the <literal>irc.debian.org</literal> alias until " -"4th June 2006." +"the <ulink url=\"&url-openprojects;\">freenode</ulink> IRC network, which " +"was pointed at by the <literal>irc.debian.org</literal> alias until 4th June " +"2006." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:179 +#: resources.dbk:183 msgid "" "To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a " "signed mail where you tell what your nick is. Put cloak somewhere in the " @@ -274,27 +267,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:190 +#: resources.dbk:194 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:192 +#: resources.dbk:196 msgid "" "This document contains a lot of information which is useful to Debian " "developers, but it cannot contain everything. Most of the other interesting " -"documents are linked from <ulink url=\"http://www.debian.org/devel/\">The " -"Developers' Corner</ulink>. Take the time to browse all the links, you will " -"learn many more things." +"documents are linked from <ulink url=\"&url-devel-docs;\">The Developers' " +"Corner</ulink>. Take the time to browse all the links, you will learn many " +"more things." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:201 +#: resources.dbk:205 msgid "Debian machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:203 +#: resources.dbk:207 msgid "" "Debian has several computers working as servers, most of which serve " "critical functions in the Debian project. Most of the machines are used for " @@ -303,16 +296,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:208 +#: resources.dbk:212 msgid "" "Most of the machines are available for individual developers to use, as long " "as the developers follow the rules set forth in the <ulink " -"url=\"http://www.debian.org/devel/dmup\">Debian Machine Usage " -"Policies</ulink>." +"url=\"&url-dmup;\">Debian Machine Usage Policies</ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:213 +#: resources.dbk:217 msgid "" "Generally speaking, you can use these machines for Debian-related purposes " "as you see fit. Please be kind to system administrators, and do not use up " @@ -322,7 +314,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:220 +#: resources.dbk:224 msgid "" "Please take care to protect your Debian passwords and SSH keys installed on " "Debian machines. Avoid login or upload methods which send passwords over " @@ -330,32 +322,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:225 +#: resources.dbk:229 msgid "" "Please do not put any material that doesn't relate to Debian on the Debian " "servers, unless you have prior permission." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:229 +#: resources.dbk:233 msgid "" "The current list of Debian machines is available at <ulink " -"url=\"http://db.debian.org/machines.cgi\"></ulink>. That web page contains " -"machine names, contact information, information about who can log in, SSH " -"keys etc." +"url=\"&url-devel-machines;\"></ulink>. That web page contains machine " +"names, contact information, information about who can log in, SSH keys etc." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:235 +#: resources.dbk:239 msgid "" "If you have a problem with the operation of a Debian server, and you think " "that the system operators need to be notified of this problem, the Debian " "system administrator team is reachable at " -"<email>debian-admin@lists.debian.org</email>." +"<email>debian-admin@&lists-host;</email>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:241 +#: resources.dbk:245 msgid "" "If you have a problem with a certain service, not related to the system " "administration (such as packages to be removed from the archive, suggestions " @@ -365,110 +356,109 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:248 +#: resources.dbk:252 msgid "" "Some of the core servers are restricted, but the information from there is " "mirrored to another server." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:252 +#: resources.dbk:256 msgid "The bugs server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:254 +#: resources.dbk:258 msgid "" -"<literal>bugs.debian.org</literal> is the canonical location for the Bug " +"<literal>&bugs-host;</literal> is the canonical location for the Bug " "Tracking System (BTS)." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:258 resources.dbk:276 +#: resources.dbk:262 resources.dbk:280 msgid "It is restricted; a mirror is available on <literal>merkel</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:261 +#: resources.dbk:265 msgid "" "If you plan on doing some statistical analysis or processing of Debian bugs, " "this would be the place to do it. Please describe your plans on " -"<email>debian-devel@lists.debian.org</email> before implementing anything, " -"however, to reduce unnecessary duplication of effort or wasted processing " -"time." +"&email-debian-devel; before implementing anything, however, to reduce " +"unnecessary duplication of effort or wasted processing time." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:269 +#: resources.dbk:273 msgid "The ftp-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:271 +#: resources.dbk:275 msgid "" -"The <literal>ftp-master.debian.org</literal> server holds the canonical copy " -"of the Debian archive (excluding the non-US packages). Generally, package " +"The <literal>&ftp-master-host;</literal> server holds the canonical copy of " +"the Debian archive (excluding the non-US packages). Generally, package " "uploads go to this server; see <xref linkend=\"upload\"/> ." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:279 +#: resources.dbk:283 msgid "" "Problems with the Debian FTP archive generally need to be reported as bugs " -"against the <systemitem role=\"package\">ftp.debian.org</systemitem> " -"pseudo-package or an email to <email>ftpmaster@debian.org</email>, but also " -"see the procedures in <xref linkend=\"archive-manip\"/> ." +"against the <systemitem role=\"package\">&ftp-debian-org;</systemitem> " +"pseudo-package or an email to &email-ftpmaster;, but also see the procedures " +"in <xref linkend=\"archive-manip\"/> ." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:287 +#: resources.dbk:291 msgid "The non-US server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:289 +#: resources.dbk:293 msgid "" -"The non-US server <literal>non-us.debian.org</literal> was discontinued with " -"the release of sarge. The pseudo-package <systemitem " +"The non-US server <literal>&non-us-host;</literal> was discontinued with the " +"release of sarge. The pseudo-package <systemitem " "role=\"package\">nonus.debian.org</systemitem> still exists for now." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:296 +#: resources.dbk:300 msgid "The www-master server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:298 +#: resources.dbk:302 msgid "" "The main web server is <literal>www-master.debian.org</literal>. It holds " "the official web pages, the face of Debian for most newbies." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:302 +#: resources.dbk:306 msgid "" "If you find a problem with the Debian web server, you should generally " "submit a bug against the pseudo-package, <systemitem " "role=\"package\">www.debian.org</systemitem>. Remember to check whether or " "not someone else has already reported the problem to the <ulink " -"url=\"http://bugs.debian.org/www.debian.org\">Bug Tracking System</ulink>." +"url=\"http://&bugs-host;/&www-debian-org;\">Bug Tracking System</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:311 +#: resources.dbk:315 msgid "The people web server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:313 +#: resources.dbk:317 msgid "" "<literal>people.debian.org</literal> is the server used for developers' own " "web pages about anything related to Debian." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:317 +#: resources.dbk:321 msgid "" "If you have some Debian-specific information which you want to serve on the " "web, you can do this by putting material in the " @@ -478,14 +468,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:324 +#: resources.dbk:328 msgid "" "You should only use this particular location because it will be backed up, " "whereas on other hosts it won't." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:328 +#: resources.dbk:332 msgid "" "Usually the only reason to use a different host is when you need to publish " "materials subject to the U.S. export restrictions, in which case you can " @@ -493,24 +483,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:333 -msgid "" -"Send mail to <email>debian-devel@lists.debian.org</email> if you have any " -"questions." +#: resources.dbk:337 +msgid "Send mail to &email-debian-devel; if you have any questions." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:339 +#: resources.dbk:342 msgid "The CVS server" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:341 +#: resources.dbk:345 msgid "Our CVS server is located on <literal>cvs.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:344 +#: resources.dbk:348 msgid "" "If you need to use a publicly accessible CVS server, for instance, to help " "coordinate work on a package between many different developers, you can " @@ -518,204 +506,138 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:349 +#: resources.dbk:353 msgid "" "Generally, <literal>cvs.debian.org</literal> offers a combination of local " "CVS access, anonymous client-server read-only access, and full client-server " "access through <command>ssh</command>. Also, the CVS area can be accessed " -"read-only via the Web at <ulink url=\"http://cvs.debian.org/\"></ulink>." +"read-only via the Web at <ulink url=\"&url-cvsweb;\"></ulink>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:355 +#: resources.dbk:359 msgid "" -"To request a CVS area, send a request via email to " -"<email>debian-admin@debian.org</email>. Include the name of the requested " -"CVS area, the Debian account that should own the CVS root area, and why you " -"need it." +"To request a CVS area, send a request via email to &email-debian-admin;. " +"Include the name of the requested CVS area, the Debian account that should " +"own the CVS root area, and why you need it." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:363 +#: resources.dbk:367 msgid "chroots to different distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:365 +#: resources.dbk:369 msgid "" "On some machines, there are chroots to different distributions available. " "You can use them like this:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:369 +#: resources.dbk:373 #, no-wrap msgid "" -"% dchroot unstable\n" +"vore$ dchroot unstable\n" "Executing shell in chroot: /org/vore.debian.org/chroots/user/unstable" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:373 +#: resources.dbk:377 msgid "" "In all chroots, the normal user home directories are available. You can " "find out which chroots are available via " -"<literal>http://db.debian.org/machines.cgi</literal>." +"<literal>&url-devel-machines;</literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:382 +#: resources.dbk:386 msgid "The Developers Database" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:384 +#: resources.dbk:388 msgid "" -"The Developers Database, at <ulink url=\"https://db.debian.org/\"></ulink>, " -"is an LDAP directory for managing Debian developer attributes. You can use " -"this resource to search the list of Debian developers. Part of this " -"information is also available through the finger service on Debian servers, " -"try <command>finger yourlogin@db.debian.org</command> to see what it " -"reports." +"The Developers Database, at <ulink url=\"&url-debian-db;\"></ulink>, is an " +"LDAP directory for managing Debian developer attributes. You can use this " +"resource to search the list of Debian developers. Part of this information " +"is also available through the finger service on Debian servers, try " +"<command>finger yourlogin@db.debian.org</command> to see what it reports." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:391 +#: resources.dbk:396 msgid "" -"Developers can <ulink url=\"https://db.debian.org/login.html\">log into the " +"Developers can <ulink url=\"&url-debian-db-login;\">log into the " "database</ulink> to change various information about themselves, such as:" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:397 +#: resources.dbk:402 msgid "forwarding address for your debian.org email" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:402 +#: resources.dbk:407 msgid "subscription to debian-private" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:407 +#: resources.dbk:412 msgid "whether you are on vacation" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:412 +#: resources.dbk:417 msgid "" "personal information such as your address, country, the latitude and " "longitude of the place where you live for use in <ulink " -"url=\"http://www.debian.org/devel/developers.loc\">the world map of Debian " -"developers</ulink>, phone and fax numbers, IRC nickname and web page" +"url=\"&url-worldmap;\">the world map of Debian developers</ulink>, phone and " +"fax numbers, IRC nickname and web page" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> -#: resources.dbk:420 +#: resources.dbk:425 msgid "password and preferred shell on Debian Project machines" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:425 +#: resources.dbk:430 msgid "" "Most of the information is not accessible to the public, naturally. For " "more information please read the online documentation that you can find at " -"<ulink url=\"http://db.debian.org/doc-general.html\"></ulink>." +"<ulink url=\"&url-debian-db-doc;\"></ulink>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:430 +#: resources.dbk:435 msgid "" "Developers can also submit their SSH keys to be used for authorization on " "the official Debian machines, and even add new *.debian.net DNS entries. " "Those features are documented at <ulink " -"url=\"http://db.debian.org/doc-mail.html\"></ulink>." +"url=\"&url-debian-db-mail-gw;\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:438 +#: resources.dbk:443 msgid "The Debian archive" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:440 +#: resources.dbk:445 msgid "" -"The Debian GNU/Linux distribution consists of a lot of packages " -"(<filename>.deb</filename>'s, currently around 9000) and a few additional " -"files (such as documentation and installation disk images)." +"The &debian-formal; distribution consists of a lot of packages " +"(<filename>.deb</filename>'s, currently around &number-of-pkgs;) and a few " +"additional files (such as documentation and installation disk images)." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:445 +#: resources.dbk:451 msgid "Here is an example directory tree of a complete Debian archive:" msgstr "" -# type: Content of: <chapter><section><screen> -#: resources.dbk:448 -#, no-wrap -msgid "" -"/stable/main/\n" -"dists/stable/main/binary-i386/\n" -"dists/stable/main/binary-m68k/\n" -"dists/stable/main/binary-alpha/\n" -" ...\n" -"dists/stable/main/source/\n" -" ...\n" -"dists/stable/main/disks-i386/\n" -"dists/stable/main/disks-m68k/\n" -"dists/stable/main/disks-alpha/\n" -" ...\n" -"\n" -"dists/stable/contrib/\n" -"dists/stable/contrib/binary-i386/\n" -"dists/stable/contrib/binary-m68k/\n" -"dists/stable/contrib/binary-alpha/\n" -" ...\n" -"dists/stable/contrib/source/\n" -"\n" -"dists/stable/non-free/\n" -"dists/stable/non-free/binary-i386/\n" -"dists/stable/non-free/binary-m68k/\n" -"dists/stable/non-free/binary-alpha/\n" -" ...\n" -"dists/stable/non-free/source/\n" -"\n" -"dists/testing/\n" -"dists/testing/main/\n" -" ...\n" -"dists/testing/contrib/\n" -" ...\n" -"dists/testing/non-free/\n" -" ...\n" -"\n" -"dists/unstable\n" -"dists/unstable/main/\n" -" ...\n" -"dists/unstable/contrib/\n" -" ...\n" -"dists/unstable/non-free/\n" -" ...\n" -"\n" -"pool/\n" -"pool/main/a/\n" -"pool/main/a/apt/\n" -" ...\n" -"pool/main/b/\n" -"pool/main/b/bash/\n" -" ...\n" -"pool/main/liba/\n" -"pool/main/liba/libalias-perl/\n" -" ...\n" -"pool/main/m/\n" -"pool/main/m/mailx/\n" -" ...\n" -"pool/non-free/n/\n" -"pool/non-free/n/netscape/\n" -" ..." -msgstr "" - # type: Content of: <chapter><section><para> -#: resources.dbk:508 +#: resources.dbk:455 msgid "" "As you can see, the top-level directory contains two directories, " "<filename>dists/</filename> and <filename>pool/</filename>. The latter is a " @@ -733,7 +655,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:522 +#: resources.dbk:469 msgid "" "<filename>dists/stable</filename> contains three directories, namely " "<filename>main</filename>, <filename>contrib</filename>, and " @@ -741,7 +663,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:527 +#: resources.dbk:474 msgid "" "In each of the areas, there is a directory for the source packages " "(<filename>source</filename>) and a directory for each supported " @@ -750,7 +672,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:532 +#: resources.dbk:479 msgid "" "The <filename>main</filename> area contains additional directories which " "hold the disk images and some essential pieces of documentation required for " @@ -759,35 +681,34 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:538 +#: resources.dbk:485 msgid "Sections" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:540 +#: resources.dbk:487 msgid "" "The <emphasis>main</emphasis> section of the Debian archive is what makes up " -"the <emphasis role=\"strong\">official Debian GNU/Linux " +"the <emphasis role=\"strong\">official &debian-formal; " "distribution</emphasis>. The <emphasis>main</emphasis> section is official " "because it fully complies with all our guidelines. The other two sections " "do not, to different degrees; as such, they are <emphasis " -"role=\"strong\">not</emphasis> officially part of Debian GNU/Linux." +"role=\"strong\">not</emphasis> officially part of &debian-formal;." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:548 +#: resources.dbk:495 msgid "" "Every package in the main section must fully comply with the <ulink " -"url=\"http://www.debian.org/social_contract#guidelines\">Debian Free " -"Software Guidelines</ulink> (DFSG) and with all other policy requirements as " -"described in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>. The DFSG is our definition of “free software.” Check out " -"the Debian Policy Manual for details." +"url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> (DFSG) and with " +"all other policy requirements as described in the <ulink " +"url=\"&url-debian-policy;\">Debian Policy Manual</ulink>. The DFSG is our " +"definition of “free software.” Check out the Debian Policy Manual for " +"details." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:556 +#: resources.dbk:503 msgid "" "Packages in the <emphasis>contrib</emphasis> section have to comply with the " "DFSG, but may fail other requirements. For instance, they may depend on " @@ -795,7 +716,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:561 +#: resources.dbk:508 msgid "" "Packages which do not conform to the DFSG are placed in the " "<emphasis>non-free</emphasis> section. These packages are not considered as " @@ -805,15 +726,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:568 +#: resources.dbk:515 msgid "" -"The <ulink url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink> contains a more exact definition of the three sections. The " -"above discussion is just an introduction." +"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> contains " +"a more exact definition of the three sections. The above discussion is just " +"an introduction." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:573 +#: resources.dbk:520 msgid "" "The separation of the three sections at the top-level of the archive is " "important for all people who want to distribute Debian, either via FTP " @@ -824,7 +745,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:581 +#: resources.dbk:528 msgid "" "On the other hand, a CD-ROM vendor could easily check the individual package " "licenses of the packages in <emphasis>non-free</emphasis> and include as " @@ -833,7 +754,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:587 +#: resources.dbk:534 msgid "" "Note that the term section is also used to refer to categories which " "simplify the organization and browsing of available packages, e.g. " @@ -845,12 +766,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:597 +#: resources.dbk:544 msgid "Architectures" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:599 +#: resources.dbk:546 msgid "" "In the first days, the Linux kernel was only available for Intel i386 (or " "greater) platforms, and so was Debian. But as Linux became more and more " @@ -858,7 +779,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:604 +#: resources.dbk:551 msgid "" "The Linux 2.0 kernel supports Intel x86, DEC Alpha, SPARC, Motorola 680x0 " "(like Atari, Amiga and Macintoshes), MIPS, and PowerPC. The Linux 2.2 " @@ -875,9 +796,9 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:618 +#: resources.dbk:565 msgid "" -"Debian GNU/Linux 1.3 is only available as <emphasis>i386</emphasis>. Debian " +"&debian-formal; 1.3 is only available as <emphasis>i386</emphasis>. Debian " "2.0 shipped for <emphasis>i386</emphasis> and <emphasis>m68k</emphasis> " "architectures. Debian 2.1 ships for the <emphasis>i386</emphasis>, " "<emphasis>m68k</emphasis>, <emphasis>alpha</emphasis>, and " @@ -890,27 +811,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:629 +#: resources.dbk:576 msgid "" "Information for developers and users about the specific ports are available " -"at the <ulink url=\"http://www.debian.org/ports/\">Debian Ports web " -"pages</ulink>." +"at the <ulink url=\"&url-debian-ports;\">Debian Ports web pages</ulink>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:635 +#: resources.dbk:582 msgid "Packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:637 +#: resources.dbk:584 msgid "" "There are two types of Debian packages, namely <emphasis>source</emphasis> " "and <emphasis>binary</emphasis> packages." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:641 +#: resources.dbk:588 msgid "" "Source packages consist of either two or three files: a " "<filename>.dsc</filename> file, and either a <filename>.tar.gz</filename> " @@ -919,7 +839,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:647 +#: resources.dbk:594 msgid "" "If a package is developed specially for Debian and is not distributed " "outside of Debian, there is just one <filename>.tar.gz</filename> file which " @@ -932,7 +852,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:657 +#: resources.dbk:604 msgid "" "The <filename>.dsc</filename> file lists all the files in the source package " "together with checksums (<command>md5sums</command>) and some additional " @@ -940,12 +860,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:664 +#: resources.dbk:611 msgid "Distributions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:666 +#: resources.dbk:613 msgid "" "The directory system described in the previous chapter is itself contained " "within <emphasis>distribution directories</emphasis>. Each distribution is " @@ -954,7 +874,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:672 +#: resources.dbk:619 msgid "" "To summarize, the Debian archive has a root directory within an FTP server. " "For instance, at the mirror site, <literal>ftp.us.debian.org</literal>, the " @@ -964,7 +884,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:679 +#: resources.dbk:626 msgid "" "A distribution comprises Debian source and binary packages, and the " "respective <filename>Sources</filename> and <filename>Packages</filename> " @@ -975,12 +895,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:687 +#: resources.dbk:634 msgid "Stable, testing, and unstable" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:689 +#: resources.dbk:636 msgid "" "There are always distributions called <emphasis>stable</emphasis> (residing " "in <filename>dists/stable</filename>), <emphasis>testing</emphasis> " @@ -991,7 +911,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:696 +#: resources.dbk:643 msgid "" "Active development is done in the <emphasis>unstable</emphasis> distribution " "(that's why this distribution is sometimes called the <emphasis>development " @@ -1003,7 +923,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:705 +#: resources.dbk:652 msgid "" "The <link linkend=\"testing\">testing</link> distribution is generated " "automatically by taking packages from unstable if they satisfy certain " @@ -1013,7 +933,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:712 +#: resources.dbk:659 msgid "" "After a period of development, once the release manager deems fit, the " "<emphasis>testing</emphasis> distribution is frozen, meaning that the " @@ -1030,11 +950,11 @@ msgid "" "<emphasis>testing</emphasis>, and the previous <emphasis>stable</emphasis> " "is renamed to <emphasis>oldstable</emphasis> and stays there until it is " "finally archived. On archiving, the contents are moved to " -"<literal>archive.debian.org</literal>)." +"<literal>&archive-host;</literal>)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:729 +#: resources.dbk:676 msgid "" "This development cycle is based on the assumption that the " "<emphasis>unstable</emphasis> distribution becomes " @@ -1054,7 +974,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:746 +#: resources.dbk:693 msgid "" "Note that development under <emphasis>unstable</emphasis> continues during " "the freeze period, since the <emphasis>unstable</emphasis> distribution " @@ -1062,31 +982,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:753 +#: resources.dbk:700 msgid "More information about the testing distribution" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:755 +#: resources.dbk:702 msgid "" "Packages are usually installed into the `testing' distribution after they " "have undergone some degree of testing in unstable." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:759 +#: resources.dbk:706 msgid "" "For more details, please see the <link linkend=\"testing\">information about " "the testing distribution</link>." msgstr "" # type: Content of: <chapter><section><section><section><title> -#: resources.dbk:765 +#: resources.dbk:712 msgid "Experimental" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:767 +#: resources.dbk:714 msgid "" "The <emphasis>experimental</emphasis> distribution is a special " "distribution. It is not a full distribution in the same sense as `stable' " @@ -1101,25 +1021,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:778 +#: resources.dbk:725 msgid "" "These are the <citerefentry> <refentrytitle>sources.list</refentrytitle> " "<manvolnum>5</manvolnum> </citerefentry> lines for " "<emphasis>experimental</emphasis>:" msgstr "" -# type: Content of: <chapter><section><section><section><screen> -#: resources.dbk:783 +# type: Content of: <chapter><section><section><section><programlisting> +#: resources.dbk:730 #, no-wrap msgid "" -"http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental " +"deb http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ experimental " "main\n" "deb-src http://ftp.<replaceable>xy</replaceable>.debian.org/debian/ " "experimental main" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:787 +#: resources.dbk:734 msgid "" "If there is a chance that the software could do grave damage to a system, it " "is likely to be better to put it into <emphasis>experimental</emphasis>. " @@ -1128,7 +1048,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:793 +#: resources.dbk:740 msgid "" "Whenever there is a new upstream version of a package that introduces new " "features but breaks a lot of old ones, it should either not be uploaded, or " @@ -1141,7 +1061,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:803 +#: resources.dbk:750 msgid "" "Some experimental software can still go into <emphasis>unstable</emphasis>, " "with a few warnings in the description, but that isn't recommended because " @@ -1154,21 +1074,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:813 +#: resources.dbk:760 msgid "" "New software which isn't likely to damage your system can go directly into " "<emphasis>unstable</emphasis>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:817 +#: resources.dbk:764 msgid "" "An alternative to <emphasis>experimental</emphasis> is to use your personal " "web space on <literal>people.debian.org</literal>." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: resources.dbk:821 +#: resources.dbk:768 msgid "" "When uploading to unstable a package which had bugs fixed in experimental, " "please consider using the option <literal>-v</literal> to " @@ -1176,12 +1096,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:830 +#: resources.dbk:777 msgid "Release code names" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:832 +#: resources.dbk:779 msgid "" "Every released Debian distribution has a <emphasis>code name</emphasis>: " "Debian 1.1 is called `buzz'; Debian 1.2, `rex'; Debian 1.3, `bo'; Debian " @@ -1197,7 +1117,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:844 +#: resources.dbk:791 msgid "" "Since Debian has an open development model (i.e., everyone can participate " "and follow the development) even the `unstable' and `testing' distributions " @@ -1209,7 +1129,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:853 +#: resources.dbk:800 msgid "" "On the other hand, if we called the distribution directories " "<emphasis>Debian-x.y</emphasis> from the beginning, people would think that " @@ -1220,7 +1140,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:861 +#: resources.dbk:808 msgid "" "Thus, the names of the distribution directories in the archive are " "determined by their code names and not their release status (e.g., " @@ -1233,12 +1153,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:875 +#: resources.dbk:822 msgid "Debian mirrors" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:877 +#: resources.dbk:824 msgid "" "The various download archives and the web site have several mirrors " "available in order to relieve our canonical servers from heavy load. In " @@ -1252,17 +1172,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:888 +#: resources.dbk:835 msgid "" "All the information on Debian mirrors, including a list of the available " "public FTP/HTTP servers, can be found at <ulink " -"url=\"http://www.debian.org/mirror/\"></ulink>. This useful page also " -"includes information and tools which can be helpful if you are interested in " -"setting up your own mirror, either for internal or public access." +"url=\"&url-debian-mirrors;\"></ulink>. This useful page also includes " +"information and tools which can be helpful if you are interested in setting " +"up your own mirror, either for internal or public access." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:895 +#: resources.dbk:842 msgid "" "Note that mirrors are generally run by third-parties who are interested in " "helping Debian. As such, developers generally do not have accounts on these " @@ -1270,20 +1190,20 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:902 +#: resources.dbk:849 msgid "The Incoming system" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:904 +#: resources.dbk:851 msgid "" "The Incoming system is responsible for collecting updated packages and " "installing them in the Debian archive. It consists of a set of directories " -"and scripts that are installed on <literal>ftp-master.debian.org</literal>." +"and scripts that are installed on <literal>&ftp-master-host;</literal>." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:909 +#: resources.dbk:856 msgid "" "Packages are uploaded by all the maintainers into a directory called " "<filename>UploadQueue</filename>. This directory is scanned every few " @@ -1307,56 +1227,55 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:928 +#: resources.dbk:875 msgid "" "Once the package is accepted, the system sends a confirmation mail to the " "maintainer and closes all the bugs marked as fixed by the upload, and the " "auto-builders may start recompiling it. The package is now publicly " -"accessible at <ulink url=\"http://incoming.debian.org/\"></ulink> until it " -"is really installed in the Debian archive. This happens only once a day " -"(and is also called the `dinstall run' for historical reasons); the package " -"is then removed from incoming and installed in the pool along with all the " -"other packages. Once all the other updates (generating new " +"accessible at <ulink url=\"&url-incoming;\"></ulink> until it is really " +"installed in the Debian archive. This happens only once a day (and is also " +"called the `dinstall run' for historical reasons); the package is then " +"removed from incoming and installed in the pool along with all the other " +"packages. Once all the other updates (generating new " "<filename>Packages</filename> and <filename>Sources</filename> index files " "for example) have been made, a special script is called to ask all the " "primary mirrors to update themselves." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:940 +#: resources.dbk:887 msgid "" "The archive maintenance software will also send the OpenPGP/GnuPG signed " "<filename>.changes</filename> file that you uploaded to the appropriate " "mailing lists. If a package is released with the " "<literal>Distribution:</literal> set to `stable', the announcement is sent " -"to <email>debian-changes@lists.debian.org</email>. If a package is released " -"with <literal>Distribution:</literal> set to `unstable' or `experimental', " -"the announcement will be posted to " -"<email>debian-devel-changes@lists.debian.org</email> instead." +"to &email-debian-changes;. If a package is released with " +"<literal>Distribution:</literal> set to `unstable' or `experimental', the " +"announcement will be posted to &email-debian-devel-changes; instead." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:950 +#: resources.dbk:897 msgid "" "Though ftp-master is restricted, a copy of the installation is available to " -"all developers on <literal>merkel.debian.org</literal>." +"all developers on <literal>&ftp-master-mirror;</literal>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:956 +#: resources.dbk:960 msgid "Package information" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:958 +#: resources.dbk:962 msgid "On the web" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:960 +#: resources.dbk:964 msgid "" "Each package has several dedicated web pages. " -"<literal>http://packages.debian.org/<replaceable>package-name</replaceable></literal> " +"<literal>http://&packages-host;/<replaceable>package-name</replaceable></literal> " "displays each version of the package available in the various " "distributions. Each version links to a page which provides information, " "including the package description, the dependencies, and package download " @@ -1364,31 +1283,31 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:967 +#: resources.dbk:971 msgid "" "The bug tracking system tracks bugs for each package. You can view the bugs " "of a given package at the URL " -"<literal>http://bugs.debian.org/<replaceable>package-name</replaceable></literal>." +"<literal>http://&bugs-host;/<replaceable>package-name</replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:974 +#: resources.dbk:978 msgid "The <command>madison</command> utility" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:976 +#: resources.dbk:980 msgid "" "<command>madison</command> is a command-line utility that is available on " -"<literal>ftp-master.debian.org</literal>, and on the mirror on " -"<literal>merkel.debian.org</literal>. It uses a single argument " +"<literal>&ftp-master-host;</literal>, and on the mirror on " +"<literal>&ftp-master-mirror;</literal>. It uses a single argument " "corresponding to a package name. In result it displays which version of the " "package is available for each architecture and distribution combination. An " "example will explain it better." msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:984 +#: resources.dbk:988 #, no-wrap msgid "" "$ madison libdbd-mysql-perl\n" @@ -1402,7 +1321,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:991 +#: resources.dbk:995 msgid "" "In this example, you can see that the version in " "<emphasis>unstable</emphasis> differs from the version in " @@ -1412,12 +1331,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1001 +#: resources.dbk:1005 msgid "The Package Tracking System" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1003 +#: resources.dbk:1007 msgid "" "The Package Tracking System (PTS) is an email-based tool to track the " "activity of a source package. This really means that you can get the same " @@ -1426,67 +1345,67 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1008 +#: resources.dbk:1012 msgid "" "Each email sent through the PTS is classified under one of the keywords " "listed below. This will let you select the mails that you want to receive." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1012 +#: resources.dbk:1016 msgid "By default you will get:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1019 +#: resources.dbk:1023 msgid "All the bug reports and following discussions." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1027 +#: resources.dbk:1031 msgid "" -"The email notifications from <email>control@bugs.debian.org</email> about " -"bug report status changes." +"The email notifications from <email>control@&bugs-host;</email> about bug " +"report status changes." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1036 +#: resources.dbk:1040 msgid "" "The email notification from <command>katie</command> when an uploaded source " "package is accepted." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1045 +#: resources.dbk:1049 msgid "" "Other warning and error emails from <command>katie</command> (such as an " "override disparity for the section and/or the priority field)." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1054 +#: resources.dbk:1058 msgid "" "Any non-automatic email sent to the PTS by people who wanted to contact the " "subscribers of the package. This can be done by sending mail to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " -"In order to prevent spam, all messages sent to these addresses must contain " -"the <literal>X-PTS-Approved</literal> header with a non-empty value." +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. In " +"order to prevent spam, all messages sent to these addresses must contain the " +"<literal>X-PTS-Approved</literal> header with a non-empty value." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1066 +#: resources.dbk:1070 msgid "" "Regular summary emails about the package's status. Currently, only " "progression in <emphasis>testing</emphasis> is sent." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1073 +#: resources.dbk:1077 msgid "You can also decide to receive additional information:" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1080 +#: resources.dbk:1084 msgid "" "The email notification from <command>katie</command> when an uploaded binary " "package is accepted. In other words, whenever a build daemon or a porter " @@ -1495,40 +1414,40 @@ msgid "" msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1091 +#: resources.dbk:1095 msgid "" "CVS commit notifications, if the package has a CVS repository and the " "maintainer has set up forwarding commit notifications to the PTS." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1100 +#: resources.dbk:1104 msgid "" "Translations of descriptions or debconf templates submitted to the Debian " "Description Translation Project." msgstr "" # type: Content of: <chapter><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1109 +#: resources.dbk:1113 msgid "" "Information about changes made to the package in derivative distributions " "(for example Ubuntu)." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1116 +#: resources.dbk:1120 msgid "The PTS email interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1118 +#: resources.dbk:1122 msgid "" "You can control your subscription(s) to the PTS by sending various commands " "to <email>pts@qa.debian.org</email>." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1126 +#: resources.dbk:1130 msgid "" "Subscribes <replaceable>email</replaceable> to communications related to the " "source package <replaceable>sourcepackage</replaceable>. Sender address is " @@ -1539,7 +1458,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1139 +#: resources.dbk:1143 msgid "" "Removes a previous subscription to the source package " "<replaceable>sourcepackage</replaceable> using the specified email address " @@ -1547,21 +1466,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1149 +#: resources.dbk:1153 msgid "" "Removes all subscriptions of the specified email address or the sender " "address if the second argument is left out." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1158 +#: resources.dbk:1162 msgid "" "Lists all subscriptions for the sender or the email address optionally " "specified." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1167 +#: resources.dbk:1171 msgid "" "Tells you the keywords that you are accepting. For an explanation of " "keywords, <link linkend=\"pkg-tracking-system\">see above</link>. Here's a " @@ -1569,78 +1488,76 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1174 +#: resources.dbk:1178 msgid "<literal>bts</literal>: mails coming from the Debian Bug Tracking System" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1179 -msgid "" -"<literal>bts-control</literal>: reply to mails sent to " -"<email>control@bugs.debian.org</email>" +#: resources.dbk:1183 +msgid "<literal>bts-control</literal>: reply to mails sent to &email-bts-control;" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1185 +#: resources.dbk:1189 msgid "" "<literal>summary</literal>: automatic summary mails about the state of a " "package" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1191 +#: resources.dbk:1195 msgid "<literal>cvs</literal>: notification of CVS commits" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1196 +#: resources.dbk:1200 msgid "<literal>ddtp</literal>: translations of descriptions and debconf templates" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1201 +#: resources.dbk:1205 msgid "" "<literal>derivatives</literal>: changes made on the package by derivative " "distributions" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1207 +#: resources.dbk:1211 msgid "" "<literal>upload-source</literal>: announce of a new source upload that has " "been accepted" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1213 +#: resources.dbk:1217 msgid "" "<literal>upload-binary</literal>: announce of a new binary-only upload " "(porting)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1219 +#: resources.dbk:1223 msgid "" "<literal>katie-other</literal>: other mails from ftpmasters (override " "disparity, etc.)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><itemizedlist><listitem><para> -#: resources.dbk:1225 +#: resources.dbk:1229 msgid "" "<literal>default</literal>: all the other mails (those which aren't " "automatic)" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1235 +#: resources.dbk:1239 msgid "" "Same as the previous item but for the given source package, since you may " "select a different set of keywords for each source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1244 +#: resources.dbk:1248 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the default set of " @@ -1648,7 +1565,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1254 +#: resources.dbk:1258 msgid "" "Accept (+) or refuse (-) mails classified under the given keyword(s). " "Define the list (=) of accepted keywords. This changes the set of accepted " @@ -1656,19 +1573,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1264 +#: resources.dbk:1268 msgid "" "Same as previous item but overrides the keywords list for the indicated " "source package." msgstr "" # type: Content of: <chapter><section><section><variablelist><varlistentry><listitem><para> -#: resources.dbk:1273 +#: resources.dbk:1277 msgid "Stops processing commands. All following lines are ignored by the bot." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1279 +#: resources.dbk:1283 msgid "" "The <command>pts-subscribe</command> command-line utility (from the " "<systemitem role=\"package\">devscripts</systemitem> package) can be handy " @@ -1677,15 +1594,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1287 +#: resources.dbk:1291 msgid "Filtering PTS mails" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1289 +#: resources.dbk:1293 msgid "" "Once you are subscribed to a package, you will get the mails sent to " -"<literal><replaceable>sourcepackage</replaceable>@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>@&pts-host;</literal>. " "Those mails have special headers appended to let you filter them in a " "special mailbox (e.g. with <command>procmail</command>). The added headers " "are <literal>X-Loop</literal>, <literal>X-PTS-Package</literal>, " @@ -1693,29 +1610,29 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1297 +#: resources.dbk:1301 msgid "" "Here is an example of added headers for a source upload notification on the " "<systemitem role=\"package\">dpkg</systemitem> package:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1301 +#: resources.dbk:1305 #, no-wrap msgid "" -"-Loop: dpkg@packages.qa.debian.org\n" +"X-Loop: dpkg@&pts-host;\n" "X-PTS-Package: dpkg\n" "X-PTS-Keyword: upload-source\n" "X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1309 +#: resources.dbk:1313 msgid "Forwarding CVS commits in the PTS" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1311 +#: resources.dbk:1315 msgid "" "If you use a publicly accessible CVS repository for maintaining your Debian " "package, you may want to forward the commit notification to the PTS so that " @@ -1724,43 +1641,43 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1317 +#: resources.dbk:1321 msgid "" "Once you set up the CVS repository to generate commit notifications, you " "just have to make sure it sends a copy of those mails to " -"<literal><replaceable>sourcepackage</replaceable>_cvs@packages.qa.debian.org</literal>. " +"<literal><replaceable>sourcepackage</replaceable>_cvs@&pts-host;</literal>. " "Only the people who accept the <emphasis>cvs</emphasis> keyword will receive " "these notifications." msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1326 +#: resources.dbk:1330 msgid "The PTS web interface" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1328 +#: resources.dbk:1332 msgid "" -"The PTS has a web interface at <ulink " -"url=\"http://packages.qa.debian.org/\"></ulink> that puts together a lot of " -"information about each source package. It features many useful links (BTS, " -"QA stats, contact information, DDTP translation status, buildd logs) and " -"gathers much more information from various places (30 latest changelog " -"entries, testing status, ...). It's a very useful tool if you want to know " -"what's going on with a specific source package. Furthermore there's a form " -"that allows easy subscription to the PTS via email." +"The PTS has a web interface at <ulink url=\"http://&pts-host;/\"></ulink> " +"that puts together a lot of information about each source package. It " +"features many useful links (BTS, QA stats, contact information, DDTP " +"translation status, buildd logs) and gathers much more information from " +"various places (30 latest changelog entries, testing status, ...). It's a " +"very useful tool if you want to know what's going on with a specific source " +"package. Furthermore there's a form that allows easy subscription to the " +"PTS via email." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1338 +#: resources.dbk:1342 msgid "" "You can jump directly to the web page concerning a specific source package " "with a URL like " -"<literal>http://packages.qa.debian.org/<replaceable>sourcepackage</replaceable></literal>." +"<literal>http://&pts-host;/<replaceable>sourcepackage</replaceable></literal>." msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1343 +#: resources.dbk:1347 msgid "" "This web interface has been designed like a portal for the development of " "packages: you can add custom content on your packages' pages. You can add " @@ -1769,81 +1686,81 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1349 +#: resources.dbk:1353 msgid "Static news items can be used to indicate:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1354 +#: resources.dbk:1358 msgid "" "the availability of a project hosted on <link " "linkend=\"alioth\">Alioth</link> for co-maintaining the package" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1360 +#: resources.dbk:1364 msgid "a link to the upstream web site" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1365 +#: resources.dbk:1369 msgid "a link to the upstream bug tracker" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1370 +#: resources.dbk:1374 msgid "the existence of an IRC channel dedicated to the software" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1375 +#: resources.dbk:1379 msgid "" "any other available resource that could be useful in the maintenance of the " "package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1381 +#: resources.dbk:1385 msgid "Usual news items may be used to announce that:" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1386 +#: resources.dbk:1390 msgid "beta packages are available for testing" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1391 +#: resources.dbk:1395 msgid "final packages are expected for next week" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1396 +#: resources.dbk:1400 msgid "the packaging is about to be redone from scratch" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1401 +#: resources.dbk:1405 msgid "backports are available" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1406 +#: resources.dbk:1410 msgid "the maintainer is on vacation (if they wish to publish this information)" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1411 +#: resources.dbk:1415 msgid "a NMU is being worked on" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: resources.dbk:1416 +#: resources.dbk:1420 msgid "something important will affect the package" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1421 +#: resources.dbk:1425 msgid "" "Both kinds of news are generated in a similar manner: you just have to send " "an email either to <email>pts-static-news@qa.debian.org</email> or to " @@ -1857,7 +1774,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1432 +#: resources.dbk:1436 msgid "" "Here are a few examples of valid mails used to generate news items in the " "PTS. The first one adds a link to the cvsweb interface of debian-cd in the " @@ -1865,19 +1782,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1437 +#: resources.dbk:1441 #, no-wrap msgid "" -": Raphael Hertzog <hertzog@debian.org>\n" +"From: Raphael Hertzog <hertzog@debian.org>\n" "To: pts-static-news@qa.debian.org\n" "Subject: Browse debian-cd CVS repository with cvsweb\n" "\n" "Package: debian-cd\n" -"Url: http://cvs.debian.org/debian-cd/" +"Url: &url-cvsweb;debian-cd/" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1445 +#: resources.dbk:1449 msgid "" "The second one is an announcement sent to a mailing list which is also sent " "to the PTS so that it is published on the PTS web page of the package. Note " @@ -1885,11 +1802,11 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: resources.dbk:1450 +#: resources.dbk:1454 #, no-wrap msgid "" ": Raphael Hertzog <hertzog@debian.org>\n" -"To: debian-gtk-gnome@lists.debian.org\n" +"To: debian-gtk-gnome@&lists-host;\n" "Bcc: pts-news@qa.debian.org\n" "Subject: Galeon 2.0 backported for woody\n" "X-PTS-Package: galeon\n" @@ -1903,7 +1820,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1463 +#: resources.dbk:1467 msgid "" "Think twice before adding a news item to the PTS because you won't be able " "to remove it later and you won't be able to edit it either. The only thing " @@ -1912,24 +1829,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1473 +#: resources.dbk:1477 msgid "Developer's packages overview" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1475 +#: resources.dbk:1479 msgid "" "A QA (quality assurance) web portal is available at <ulink " -"url=\"http://qa.debian.org/developer.php\"></ulink> which displays a table " -"listing all the packages of a single developer (including those where the " -"party is listed as a co-maintainer). The table gives a good summary about " -"the developer's packages: number of bugs by severity, list of available " -"versions in each distribution, testing status and much more including links " -"to any other useful information." +"url=\"&url-ddpo;\"></ulink> which displays a table listing all the packages " +"of a single developer (including those where the party is listed as a " +"co-maintainer). The table gives a good summary about the developer's " +"packages: number of bugs by severity, list of available versions in each " +"distribution, testing status and much more including links to any other " +"useful information." msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1484 +#: resources.dbk:1488 msgid "" "It is a good idea to look up your own data regularly so that you don't " "forget any open bugs, and so that you don't forget which packages are your " @@ -1937,12 +1854,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1491 +#: resources.dbk:1495 msgid "Debian *Forge: Alioth" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1493 +#: resources.dbk:1497 msgid "" "Alioth is a fairly new Debian service, based on a slightly modified version " "of the GForge software (which evolved from SourceForge). This software " @@ -1952,7 +1869,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1500 +#: resources.dbk:1504 msgid "" "It is intended to provide facilities to free software projects backed or led " "by Debian, facilitate contributions from external developers to projects " @@ -1961,7 +1878,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1506 +#: resources.dbk:1510 msgid "" "All Debian developers automatically have an account on Alioth. They can " "activate it by using the recover password facility. External developers can " @@ -1969,27 +1886,25 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: resources.dbk:1511 -msgid "" -"For more information please visit <ulink " -"url=\"http://alioth.debian.org/\"></ulink>." +#: resources.dbk:1515 +msgid "For more information please visit <ulink url=\"&url-alioth;\"></ulink>." msgstr "" # type: Content of: <chapter><section><title> -#: resources.dbk:1517 +#: resources.dbk:1521 msgid "Goodies for Developers" msgstr "" # type: Content of: <chapter><section><section><title> -#: resources.dbk:1519 +#: resources.dbk:1523 msgid "LWN Subscriptions" msgstr "" # type: Content of: <chapter><section><section><para> -#: resources.dbk:1521 +#: resources.dbk:1525 msgid "" "Since October of 2002, HP has sponsored a subscription to LWN for all " "interested Debian developers. Details on how to get access to this benefit " "are in <ulink " -"url=\"http://lists.debian.org/debian-devel-announce/2002/10/msg00018.html\"></ulink>." +"url=\"http://&lists-host;/debian-devel-announce/2002/10/msg00018.html\"></ulink>." msgstr "" diff --git a/po4a/po/scope.pot b/po4a/po/scope.pot index 2154e96..ac90ea1 100644 --- a/po4a/po/scope.pot +++ b/po4a/po/scope.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:12+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,19 +15,19 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <chapter><title> -#: scope.dbk:5 +#: scope.dbk:7 msgid "Scope of This Document" msgstr "" # type: Content of: <chapter><para> -#: scope.dbk:7 +#: scope.dbk:9 msgid "" "The purpose of this document is to provide an overview of the recommended " "procedures and the available resources for Debian developers." msgstr "" # type: Content of: <chapter><para> -#: scope.dbk:11 +#: scope.dbk:14 msgid "" "The procedures discussed within include how to become a maintainer (<xref " "linkend=\"new-maintainer\"/> ); how to create new packages (<xref " @@ -40,7 +40,7 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: scope.dbk:20 +#: scope.dbk:23 msgid "" "The resources discussed in this reference include the mailing lists (<xref " "linkend=\"mailing-lists\"/> ) and servers (<xref " @@ -52,18 +52,17 @@ msgid "" msgstr "" # type: Content of: <chapter><para> -#: scope.dbk:28 +#: scope.dbk:31 msgid "" "It should be clear that this reference does not discuss the technical " "details of Debian packages nor how to generate them. Nor does this " "reference detail the standards to which Debian software must comply. All of " "such information can be found in the <ulink " -"url=\"http://www.debian.org/doc/debian-policy/\">Debian Policy " -"Manual</ulink>." +"url=\"&url-debian-policy;\">Debian Policy Manual</ulink>." msgstr "" # type: Content of: <chapter><para> -#: scope.dbk:35 +#: scope.dbk:38 msgid "" "Furthermore, this document is <emphasis>not an expression of formal " "policy</emphasis>. It contains documentation for the Debian system and " diff --git a/po4a/po/tools.pot b/po4a/po/tools.pot index 7cca30a..f852050 100644 --- a/po4a/po/tools.pot +++ b/po4a/po/tools.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2007-06-26 16:13+0000\n" +"POT-Creation-Date: 2007-07-01 21:01+0000\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" @@ -15,12 +15,12 @@ msgstr "" "Content-Transfer-Encoding: ENCODING" # type: Content of: <appendix><title> -#: tools.dbk:5 +#: tools.dbk:7 msgid "Overview of Debian Maintainer Tools" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:7 +#: tools.dbk:9 msgid "" "This section contains a rough overview of the tools available to " "maintainers. The following is by no means complete or definitive, but just " @@ -28,14 +28,14 @@ msgid "" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:12 +#: tools.dbk:14 msgid "" "Debian maintainer tools are meant to aid developers and free their time for " "critical tasks. As Larry Wall says, there's more than one way to do it." msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:16 +#: tools.dbk:18 msgid "" "Some people prefer to use high-level package maintenance tools and some do " "not. Debian is officially agnostic on this issue; any tool which gets the " @@ -46,26 +46,26 @@ msgid "" msgstr "" # type: Content of: <appendix><para> -#: tools.dbk:24 +#: tools.dbk:26 msgid "" "Most of the descriptions of these packages come from the actual package " "descriptions themselves. Further information can be found in the package " "documentation itself. You can also see more info with the command " -"<literal>apt-cache show <package-name></literal>." +"<command>apt-cache show <package-name></command>." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:30 +#: tools.dbk:32 msgid "Core tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:32 +#: tools.dbk:34 msgid "The following tools are pretty much required for any maintainer." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:37 +#: tools.dbk:39 msgid "" "<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools " "(including <command>dpkg-source</command>) required to unpack, build, and " @@ -75,7 +75,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:48 +#: tools.dbk:50 msgid "" "<systemitem role=\"package\">debconf</systemitem> provides a consistent " "interface to configuring packages interactively. It is user interface " @@ -85,14 +85,14 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:54 +#: tools.dbk:56 msgid "" "You can find documentation for this package in the <systemitem " "role=\"package\">debconf-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:58 +#: tools.dbk:60 msgid "" "Many feel that this system should be used for all packages which require " "interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . " @@ -101,7 +101,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:68 +#: tools.dbk:70 msgid "" "<systemitem role=\"package\">fakeroot</systemitem> simulates root " "privileges. This enables you to build packages without being root (packages " @@ -111,12 +111,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:79 +#: tools.dbk:81 msgid "Package lint tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:81 +#: tools.dbk:83 msgid "" "According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a " "Unix C language processor which carries out more thorough checks on the code " @@ -126,7 +126,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:89 +#: tools.dbk:91 msgid "" "<systemitem role=\"package\">lintian</systemitem> dissects Debian packages " "and emits information about bugs and policy violations. It contains " @@ -135,7 +135,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:95 +#: tools.dbk:97 msgid "" "You should periodically get the newest <systemitem " "role=\"package\">lintian</systemitem> from `unstable' and check over all " @@ -145,23 +145,23 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:102 +#: tools.dbk:104 msgid "" "Refer to <xref linkend=\"sanitycheck\"/> for more information on how and " "when to use Lintian." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:106 +#: tools.dbk:108 msgid "" "You can also see a summary of all problems reported by Lintian on your " -"packages at <ulink url=\"http://lintian.debian.org/\"></ulink>. These " -"reports contain the latest <command>lintian</command> output for the whole " -"development distribution (unstable)." +"packages at <ulink url=\"&url-lintian;\"></ulink>. These reports contain " +"the latest <command>lintian</command> output for the whole development " +"distribution (unstable)." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:116 +#: tools.dbk:118 msgid "" "<systemitem role=\"package\">linda</systemitem> is another package linter. " "It is similar to <systemitem role=\"package\">lintian</systemitem> but has a " @@ -169,7 +169,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:125 +#: tools.dbk:127 msgid "" "<command>debdiff</command> (from the <systemitem " "role=\"package\">devscripts</systemitem> package, <xref " @@ -181,29 +181,29 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:134 +#: tools.dbk:136 msgid "You can run it over a pair of binary packages:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:137 +#: tools.dbk:139 #, no-wrap -msgid "package_1-1_arch.deb package_2-1_arch.deb" +msgid "debdiff package_1-1_arch.deb package_2-1_arch.deb" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:140 +#: tools.dbk:142 msgid "Or even a pair of changes files:" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:143 +#: tools.dbk:145 #, no-wrap -msgid "package_1-1_arch.changes package_2-1_arch.changes" +msgid "debdiff package_1-1_arch.changes package_2-1_arch.changes" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:146 +#: tools.dbk:148 msgid "" "For more information please see <citerefentry> " "<refentrytitle>debdiff</refentrytitle> <manvolnum>1</manvolnum> " @@ -211,12 +211,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:155 +#: tools.dbk:157 msgid "Helpers for <filename>debian/rules</filename>" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:157 +#: tools.dbk:159 msgid "" "Package building tools make the process of writing " "<filename>debian/rules</filename> files easier. See <xref " @@ -225,7 +225,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:165 +#: tools.dbk:167 msgid "" "<systemitem role=\"package\">debhelper</systemitem> is a collection of " "programs which can be used in <filename>debian/rules</filename> to automate " @@ -236,7 +236,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:173 +#: tools.dbk:175 msgid "" "Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> " "is broken into several small, simple commands which act in a consistent " @@ -245,7 +245,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:179 +#: tools.dbk:181 msgid "" "There are a number of little <systemitem " "role=\"package\">debhelper</systemitem> add-on packages, too transient to " @@ -254,7 +254,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:188 +#: tools.dbk:190 msgid "" "<systemitem role=\"package\">debmake</systemitem>, a precursor to " "<systemitem role=\"package\">debhelper</systemitem>, is a more " @@ -267,7 +267,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:198 +#: tools.dbk:200 msgid "" "The consensus is that <systemitem role=\"package\">debmake</systemitem> is " "now deprecated in favor of <systemitem " @@ -278,7 +278,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:209 +#: tools.dbk:211 msgid "" "The <systemitem role=\"package\">dh-make</systemitem> package contains " "<command>dh_make</command>, a program that creates a skeleton of files " @@ -289,7 +289,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:217 +#: tools.dbk:219 msgid "" "While the rules files generated by <command>dh_make</command> are in general " "a sufficient basis for a working package, they are still just the " @@ -299,7 +299,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:227 +#: tools.dbk:229 msgid "" "<systemitem role=\"package\">yada</systemitem> is another packaging helper " "tool. It uses a <filename>debian/packages</filename> file to auto-generate " @@ -312,14 +312,14 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:237 +#: tools.dbk:239 msgid "" "For more informations see <literal><ulink " "url=\"http://yada.alioth.debian.org/\">YADA site</ulink></literal>." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:245 +#: tools.dbk:247 msgid "" "<systemitem role=\"package\">equivs</systemitem> is another package for " "making packages. It is often suggested for local use if you need to make a " @@ -329,12 +329,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:256 +#: tools.dbk:258 msgid "Package builders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:258 +#: tools.dbk:260 msgid "" "The following packages help with the package building process, general " "driving <command>dpkg-buildpackage</command> as well as handling supporting " @@ -342,7 +342,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:264 +#: tools.dbk:266 msgid "" "<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the " "capability to inject or import Debian source packages into a CVS repository, " @@ -351,7 +351,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:270 +#: tools.dbk:272 msgid "" "These utilities provide an infrastructure to facilitate the use of CVS by " "Debian maintainers. This allows one to keep separate CVS branches of a " @@ -361,7 +361,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:281 +#: tools.dbk:283 msgid "" "The <systemitem role=\"package\">debootstrap</systemitem> package and script " "allows you to bootstrap a Debian base system into any part of your " @@ -370,7 +370,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:287 +#: tools.dbk:289 msgid "" "Having a system like this can be useful in many ways. For instance, you can " "<command>chroot</command> into it if you want to test your build " @@ -379,7 +379,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:297 +#: tools.dbk:299 msgid "" "<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted " "system, and builds a package inside the chroot. It is very useful to check " @@ -389,7 +389,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:303 +#: tools.dbk:305 msgid "" "A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, " "which goes even further by doing the build within a User Mode Linux " @@ -397,7 +397,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:312 +#: tools.dbk:314 msgid "" "<systemitem role=\"package\">sbuild</systemitem> is another automated " "builder. It can use chrooted environments as well. It can be used " @@ -405,23 +405,23 @@ msgid "" "the latter, it is part of the system used by porters to build binary " "packages for all the available architectures. See <xref " "linkend=\"buildd\"/> for more information, and <ulink " -"url=\"http://buildd.debian.org/\"></ulink> to see the system in action." +"url=\"&url-buildd;\"></ulink> to see the system in action." msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:324 +#: tools.dbk:326 msgid "Package uploaders" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:326 +#: tools.dbk:328 msgid "" "The following packages help automate or simplify the process of uploading " "packages into the official archive." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:332 +#: tools.dbk:334 msgid "" "<systemitem role=\"package\">dupload</systemitem> is a package and a script " "to automatically upload Debian packages to the Debian archive, to log the " @@ -430,7 +430,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:342 +#: tools.dbk:344 msgid "" "The <systemitem role=\"package\">dput</systemitem> package and script does " "much the same thing as <systemitem role=\"package\">dupload</systemitem>, " @@ -441,7 +441,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:354 +#: tools.dbk:356 msgid "" "The <systemitem role=\"package\">dcut</systemitem> script (part of the " "package <xref linkend=\"dput\"/> ) helps in removing files from the ftp " @@ -449,12 +449,12 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:362 +#: tools.dbk:364 msgid "Maintenance automation" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:364 +#: tools.dbk:366 msgid "" "The following tools help automate different maintenance tasks, from adding " "changelog entries or signature lines and looking up bugs in Emacs to making " @@ -462,7 +462,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:371 +#: tools.dbk:373 msgid "" "<systemitem role=\"package\">devscripts</systemitem> is a package containing " "wrappers and tools which are very helpful for maintaining your Debian " @@ -479,7 +479,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:385 +#: tools.dbk:387 msgid "" "See the <citerefentry> <refentrytitle>devscripts</refentrytitle> " "<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of " @@ -487,7 +487,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:394 +#: tools.dbk:396 msgid "" "<systemitem role=\"package\">autotools-dev</systemitem> contains best " "practices for people who maintain packages which use " @@ -498,7 +498,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:405 +#: tools.dbk:407 msgid "" "<command>dpkg-repack</command> creates Debian package file out of a package " "that has already been installed. If any changes have been made to the " @@ -507,7 +507,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:411 +#: tools.dbk:413 msgid "" "This utility can make it easy to copy packages from one computer to another, " "or to recreate packages which are installed on your system but no longer " @@ -516,7 +516,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:420 +#: tools.dbk:422 msgid "" "<command>alien</command> converts binary packages between various packaging " "formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, " @@ -524,7 +524,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:429 +#: tools.dbk:431 msgid "" "<command>debsums</command> checks installed packages against their MD5 " "sums. Note that not all packages have MD5 sums, since they aren't required " @@ -532,7 +532,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:437 +#: tools.dbk:439 msgid "" "<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp " "package which provides assistance when editing some of the files in the " @@ -542,7 +542,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:448 +#: tools.dbk:450 msgid "" "<command>dpkg-depcheck</command> (from the <systemitem " "role=\"package\">devscripts</systemitem> package, <xref " @@ -551,7 +551,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:454 +#: tools.dbk:456 msgid "" "For Debian packages, this is useful when you have to compose a " "<literal>Build-Depends</literal> line for your new package: running the " @@ -560,20 +560,20 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><screen> -#: tools.dbk:460 +#: tools.dbk:462 #, no-wrap -msgid "-depcheck -b debian/rules build" +msgid "dpkg-depcheck -b debian/rules build" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:463 +#: tools.dbk:465 msgid "" "<command>dpkg-depcheck</command> can also be used to check for run-time " "dependencies, especially if your package uses exec(2) to run other programs." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:467 +#: tools.dbk:469 msgid "" "For more information please see <citerefentry> " "<refentrytitle>dpkg-depcheck</refentrytitle> <manvolnum>1</manvolnum> " @@ -581,17 +581,17 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:476 +#: tools.dbk:478 msgid "Porting tools" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:478 +#: tools.dbk:480 msgid "The following tools are helpful for porters and for cross-compilation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:483 +#: tools.dbk:485 msgid "" "<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the " "differences from one architecture to another. For instance, it could tell " @@ -601,7 +601,7 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:493 +#: tools.dbk:495 msgid "" "<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for " "installing libraries and headers for cross-compiling in a way similar to " @@ -611,19 +611,19 @@ msgid "" msgstr "" # type: Content of: <appendix><section><title> -#: tools.dbk:504 +#: tools.dbk:506 msgid "Documentation and information" msgstr "" # type: Content of: <appendix><section><para> -#: tools.dbk:506 +#: tools.dbk:508 msgid "" "The following packages provide information for maintainers or help with " "building documentation." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:512 +#: tools.dbk:514 msgid "" "<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the " "DebianDoc SGML DTD, which is commonly used for Debian documentation. This " @@ -632,21 +632,21 @@ msgid "" msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:518 +#: tools.dbk:520 msgid "" "Documentation for the DTD can be found in the <systemitem " "role=\"package\">debiandoc-sgml-doc</systemitem> package." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:526 +#: tools.dbk:544 msgid "" "Contains the public GPG and PGP keys of Debian developers. See <xref " "linkend=\"key-maint\"/> and the package documentation for more information." msgstr "" # type: Content of: <appendix><section><section><para> -#: tools.dbk:534 +#: tools.dbk:552 msgid "" "<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for " "viewing Debian binary packages. This lets you examine a package without " diff --git a/tools.dbk b/tools.dbk index 1590c75..7f62648 100644 --- a/tools.dbk +++ b/tools.dbk @@ -521,6 +521,22 @@ Documentation for the DTD can be found in the <systemitem role="package">debiandoc-sgml-doc</systemitem> package. </para> </section> +<!-- TODO: Maybe better: +<section id="docbook-xml"> +<title><systemitem role="package">docbook-xml</systemitem> + +docbook-xml provides the +DocBook XML DTDs, which are commonly used for Debian documentation (as +is the older debiandoc SGML DTD). This manual, for instance, is written +in DocBook XML. The docbook-xsl package provides the XSL files +for building and styling the source to various output formats. You +will need an XSLT processor, such as xsltproc, and an FO processor, such as +fop, to generate documentation. + + +-->
<systemitem role="package">debian-keyring</systemitem>