Le 10/04/2011 09:35, Osamu Aoki a écrit : > Hi, Hi Osamu and every translator of the maint-guide, > If you find any issues with the English original, please let me know. After getting in touch with Osamu, I'm about to commit the attached changes to the maint-guide: mostly typo and stylish fix. Since most of these changes can be trivially unfuzzy, I'm about to take care of that in the process. If you already began to translate it, you can either commit it or send it to me right now so I can take care of the unfuzzy on your real file. You can also take care of it yourself, don't hesitate to tell me, in order to avoid double work. If you receive this message too late, and have a hard time with conflicted merge in Subversion, please send me your file, and I'll clean up my mess. Another note (from translator to translator): the conversion process took care of restoring most of the existing translation, but some of them were lost anyway. I managed to restore a few more string from the source of maint-guide 1.2.25 currently in the archive: e.g. some footnote were already translated in the PO file from the SGML source, so I was able to copy and paste the existing translation and manually take care of the tag (DocBook ones are different). Regards David P.-S.: rationale about the attached changes in the guide. -text in the older system (including the older Ubuntu system etc.), […] +text in an older system (including an older Ubuntu system etc.), […] Used to be “Lenny”, but the sentence seems about “any older version” rather than “the oldstable distribution”. -learn about Unix programming, too. +learn about UNIX programming, too. Forgot that one earlier (I can prepare the trivial unfuzzy if you wish). -waiting for good maintainers (see <xref linkend="choose"/> ). +waiting for good maintainers (see <xref linkend="choose"/>). Probably some broken legacy typography for text only output without hyperlink (I can prepare also the trivial unfuzzy if you wish). Other changes should be alike or selfexplainable, but I'll provide more input if needed.
Index: maint-guide.en.dbk
===================================================================
--- maint-guide.en.dbk (révision 8661)
+++ maint-guide.en.dbk (copie de travail)
@@ -78,7 +78,7 @@
release.
<footnote><para> The document assumes you are using the
<literal>&base-release;</literal> system or newer. If you need to follow this
-text in the older system (including the older Ubuntu system etc.), you must
+text in an older system (including an older Ubuntu system etc.), you must
install backported <systemitem role="package">dpkg</systemitem> and
<systemitem role="package">debhelper</systemitem> packages, at least.
</para> </footnote>
@@ -90,11 +90,11 @@
wondering how you can make your own packages and perhaps you think it is a very
difficult task. Well, if you are a real novice on Linux, it is hard, but if
you were rookie, you wouldn't be reading this doc now. :-) You do need to know
-a little about Unix programming but you certainly don't need to be a wizard.
+a little about UNIX programming but you certainly don't need to be a wizard.
<footnote><para>
You can learn basic operations of the Debian system from
<ulink url="&debref;">Debian Reference</ulink>. It contains some pointers to
-learn about Unix programming, too.
+learn about UNIX programming, too.
</para></footnote>
</para>
<para>
@@ -108,7 +108,7 @@
next releases of that and maybe other packages later on.
</para>
<para>
-If you need some help on packaging, please read <xref linkend="helpme"/> .
+If you need some help on packaging, please read <xref linkend="helpme"/>.
</para>
<para>
Newer versions of this document should always be available online at
@@ -120,7 +120,7 @@
</para>
<section id="socialdynamism"><title>Social dynamism of Debian</title>
<para>
-Here are my observation of the social dynamism of Debian. I hope this will prepare you for the interaction with Debian.
+Here are my observations of the social dynamism of Debian. I hope this will prepare you for the interaction with Debian.
</para>
<itemizedlist>
<listitem><para>We all are volunteers.</para>
@@ -151,7 +151,7 @@
<itemizedlist>
<listitem><para><ulink url="&logiciellibre;">Debian: 17 ans de logiciel libre, "do-ocracy" et démocratie</ulink> (Introductory slides in English PDF) </para> </listitem>
<listitem><para><ulink url="&debianorghelp;">How can you help Debian?</ulink> (official) </para> </listitem>
-<listitem><para><ulink url="&debianfaqhelp;">The Debian GNU/Linux FAQ, Chapter 13 - 'Contributing to the Debian Project' (semi-official) </ulink></para> </listitem>
+<listitem><para><ulink url="&debianfaqhelp;">The Debian GNU/Linux FAQ, Chapter 13 - 'Contributing to the Debian Project'</ulink> (semi-official) </para> </listitem>
<listitem><para><ulink url="&debianwikihelp;">Debian Wiki, HelpDebian</ulink> (supplemental) </para> </listitem>
<listitem><para><ulink url="&nm-do;">Debian New Maintainer site</ulink> (official) </para> </listitem>
<listitem><para><ulink url="&debianmentorfaq;">Debian Mentors FAQ</ulink> (supplemental) </para> </listitem>
@@ -171,7 +171,7 @@
Please note that you do not need to create any new package to become an
official Debian Developer. Contributing to the existing packages can provide a
path to become an official Debian Developer too. There are many packages
-waiting for good maintainers (see <xref linkend="choose"/> ).
+waiting for good maintainers (see <xref linkend="choose"/>).
</para>
</section>
<section id="needprogs"><title>Programs you need for development</title>
@@ -219,8 +219,8 @@
<listitem>
<para>
<systemitem role="package">perl</systemitem> - Perl is one of the most used
-interpreted scripting languages on today's Unix-like systems, often referred to
-as Unix's Swiss Army Chainsaw. (see <citerefentry>
+interpreted scripting languages on today's UNIX-like systems, often referred to
+as UNIX's Swiss Army Chainsaw. (see <citerefentry>
<refentrytitle>perl</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>)
</para>
</listitem>
@@ -570,7 +570,7 @@
</listitem>
<listitem>
<para>
-files in <filename>/usr/share/doc/<replaceable>package</replaceable></filename> for all pertinent packages.
+files in <filename>/usr/share/doc/<replaceable>package</replaceable></filename> for all pertinent packages
</para>
</listitem>
<listitem>
@@ -687,13 +687,13 @@
<para> <ulink url="&wnpp-do;">Work-Needing and Prospective Packages</ulink> </para>
</listitem>
<listitem>
-<para> <ulink url="&wnpp-bts;">Debian Bug report logs: Bugs in package wnpp in unstable</ulink> </para>
+<para> <ulink url="&wnpp-bts;">Debian Bug report logs: Bugs in pseudo-package <systemitem role="package">wnpp</systemitem> in <literal>unstable</literal></ulink> </para>
</listitem>
<listitem>
<para> <ulink url="&wnpp-dn;">Debian Packages that Need Lovin'</ulink> </para>
</listitem>
<listitem>
-<para> <ulink url="&wnpp-debtags;">Browse WNPP bugs based on debtags</ulink> </para>
+<para> <ulink url="&wnpp-debtags;">Browse <systemitem role="package">wnpp</systemitem> bugs based on debtags</ulink> </para>
</listitem>
</itemizedlist>
<para>
@@ -834,7 +834,7 @@
<para>
So the first thing to do is to find and download the original source code. I
presume that you already have the source file that you picked up at the
-author's homepage. Sources for free Unix programs usually come in
+author's homepage. Sources for free UNIX programs usually come in
<command>tar</command>+<command>gzip</command> format with extension
<filename>.tar.gz</filename>, or
<command>tar</command>+<command>bzip2</command> format with extension
@@ -893,7 +893,7 @@
<filename>*.html</filename>. You must find instructions on how to correctly
compile and install the program (most probably they'll assume you want to
install to <filename>/usr/local/bin</filename> directory; you won't be doing
-that, but more on that later in <xref linkend="destdir"/> ).
+that, but more on that later in <xref linkend="destdir"/>).
</para>
<para>
Simple programs come with a <filename>Makefile</filename> file in them and can
@@ -978,7 +978,7 @@
other files with <literal>autoreconf -i -f</literal> as the user may improve
the compatibility of the source.
<footnote><para>You can automate this by using
-<systemitem role="package">dh_autoreconf</systemitem> package.
+<systemitem role="package">dh-autoreconf</systemitem> package.
See <xref linkend="customrules"/>.</para></footnote>
</para>
<para>
@@ -1111,11 +1111,11 @@
</itemizedlist>
<para>
You should also notice that many template files are created in the source under
-the <filename>debian</filename> directory. These will be explained in <xref linkend="dreq"/> and <xref linkend="dother"/> . You should also understand
+the <filename>debian</filename> directory. These will be explained in <xref linkend="dreq"/> and <xref linkend="dother"/>. You should also understand
that the packaging is not automatic process. You need to modify the upstream
-source for Debian as <xref linkend="modify"/> . After all these, you need to
-build Debian packages under the proper method as <xref linkend="build"/> ,
-check them as <xref linkend="checkit"/> , and upload them as <xref linkend="upload"/> . I will explain all these steps.
+source for Debian as <xref linkend="modify"/>. After all these, you need to
+build Debian packages under the proper method as <xref linkend="build"/>,
+check them as <xref linkend="checkit"/>, and upload them as <xref linkend="upload"/>. I will explain all these steps.
</para>
<para>
Once again, as a new maintainer you are discouraged from creating complicated
@@ -1166,7 +1166,7 @@
<para>
Updating an existing package may get complicated since it may be using older
techniques. Please stick with fresh packaging cases for now to learn basics.
-I will come back to explain it later in <xref linkend="update"/> .
+I will come back to explain it later in <xref linkend="update"/>.
</para>
</section>
</chapter>
@@ -1486,7 +1486,7 @@
such as <filename>debian/patches/fix-gentoo-target.patch</filename>, be sure to
send them to the upstream maintainer so they can be included in the next
program revision and be useful to everyone else. Also remember to make your
-fixes not specific to Debian or Linux (or even Unix!) prior to sending them --
+fixes not specific to Debian or Linux (or even UNIX!) prior to sending them --
make them portable. This will make your fixes much easier to apply.
</para>
<para>
@@ -1590,7 +1590,7 @@
and many more.
<footnote> <para>See
<ulink url="&policy-subsections;">Debian Policy Manual, 2.4 'Sections'</ulink> and
-<ulink url="§ions-unstable;">List of sections in 'sid'</ulink>.</para>
+<ulink url="§ions-unstable;">List of sections in <literal>sid</literal></ulink>.</para>
</footnote>
</para>
<para>
@@ -1664,7 +1664,7 @@
For source packages which have some binary packages with <literal>Architecture:
any</literal>, they are rebuild by the autobuilder. Since this autobuilder
procedure runs <literal>debian/rules build</literal> in it while installing
-only packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="autobuilder"/> ), the <literal>Build-Depends</literal> field needs to
+only packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="autobuilder"/>), the <literal>Build-Depends</literal> field needs to
list practically all the required packages and the
<literal>Build-Depends-indep</literal> is rarely used.
</para>
@@ -1900,8 +1900,8 @@
</para>
<para>
<citerefentry> <refentrytitle>dh_perl</refentrytitle> <manvolnum>1</manvolnum>
-</citerefentry> calculates perl dependencies. It generates a list of a
-dependency on perl or perlapi for each binary package. Such list is used for
+</citerefentry> calculates Perl dependencies. It generates a list of a
+dependency on <literal>perl</literal> or <literal>perlapi</literal> for each binary package. Such list is used for
substituting <literal>${perl:Depends}</literal>.
</para>
<para>
@@ -1994,7 +1994,7 @@
and license information.
<ulink url="&policy-copyright;">Debian Policy Manual, 12.5 'Copyright information'</ulink>
dictates its content and
-<ulink url="&dep5;">DEP-5: Machine-parseable debian/copyright</ulink>
+<ulink url="&dep5;">DEP-5: Machine-parseable <filename>debian/copyright</filename></ulink>
provides guidelines for its format.
</para>
<para>
@@ -2126,7 +2126,7 @@
</para>
<para>
You can read more about updating the <filename>changelog</filename> file later
-in <xref linkend="update"/> .
+in <xref linkend="update"/>.
</para>
</section>
<section id="rules"><title><filename>rules</filename> file</title>
@@ -2175,7 +2175,7 @@
<literal>binary</literal> target: to create all binary packages (effectively
combination of <literal>binary-arch</literal> and
<literal>binary-indep</literal> targets). (required)<footnote><para> This
-target is used by <literal>dpkg-buildpackage</literal> as in <xref linkend="completebuild"/> . </para> </footnote>
+target is used by <literal>dpkg-buildpackage</literal> as in <xref linkend="completebuild"/>. </para> </footnote>
</para>
</listitem>
<listitem>
@@ -2183,7 +2183,7 @@
<literal>binary-arch</literal> target: to create arch-dependent
(<literal>Architecture: any</literal>) binary packages in the parent directory.
(required)<footnote><para> This target is used by <literal>dpkg-buildpackage
--B</literal> as in <xref linkend="autobuilder"/> . </para> </footnote>
+-B</literal> as in <xref linkend="autobuilder"/>. </para> </footnote>
</para>
</listitem>
<listitem>
@@ -2248,7 +2248,7 @@
<filename>/usr/bin/make</filename>.
</para>
<para>
-Line 10 can be uncommented to set <literal>DH_VERBOSE</literal> variable to 1.
+Line 11 can be uncommented to set <literal>DH_VERBOSE</literal> variable to 1.
Then, the <command>dh</command> command will output which
<command>dh_*</command> commands are executed by the <command>dh</command>
command. You can also add <literal>export DH_OPTIONS=-v</literal> line here.
@@ -2270,7 +2270,7 @@
scripts listed for each required explicit targets and frozen them to the state
when it was initially packaged. This new <command>dh</command> command is
simpler and frees us from this constrain. You still have full power to
-customize this with <literal>override_dh_*</literal> targets. See <xref linkend="customrules"/> . It is based only on the <systemitem role="package">debhelper</systemitem> package and does not obfuscate the
+customize this with <literal>override_dh_*</literal> targets. See <xref linkend="customrules"/>. It is based only on the <systemitem role="package">debhelper</systemitem> package and does not obfuscate the
package building process like the <systemitem role="package">cdbs</systemitem>
package. </para> </footnote> The <command>dh</command> command is a wrapper
script which runs appropriate sequences of <command>dh_*</command> programs
@@ -2847,13 +2847,13 @@
</listitem>
<listitem>
<para>
-modify the <filename>control</filename> file (see <xref linkend="control"/> ),
+modify the <filename>control</filename> file (see <xref linkend="control"/>),
if necessary.
</para>
</listitem>
<listitem>
<para>
-modify the <filename>rules</filename> file (see <xref linkend="rules"/> ), if
+modify the <filename>rules</filename> file (see <xref linkend="rules"/>), if
necessary.
</para>
</listitem>
@@ -2944,7 +2944,7 @@
</listitem>
</itemizedlist>
<para>
-For more information on the <emphasis>maintainer scripts</emphasis>, see <xref linkend="maintscripts"/> .
+For more information on the <emphasis>maintainer scripts</emphasis>, see <xref linkend="maintscripts"/>.
</para>
</section>
<section id="crond"><title><filename><replaceable>package</replaceable>.cron.*</filename> files</title>
@@ -3013,7 +3013,7 @@
</para>
<para>
Files listed in the <filename>install</filename> file doesn't need the
-directories created first. See <xref linkend="install"/> .
+directories created first. See <xref linkend="install"/>.
</para>
<para>
It is best to try to run the installation first and only use this if you
@@ -3056,7 +3056,7 @@
manual, in <ulink url="&doc-base;">Debian doc-base Manual</ulink>.
</para>
<para>
-For more details on installing additional documentation, look in <xref linkend="destdir"/> .
+For more details on installing additional documentation, look in <xref linkend="destdir"/>.
</para>
</section>
<section id="docs"><title><filename>docs</filename> file</title>
@@ -3127,16 +3127,16 @@
The <filename><replaceable>package</replaceable>.default</filename> file will
be installed into
<filename>/etc/default/<replaceable>package</replaceable></filename>. This
-file sets defaults that are sourced by the init script. Most times this
-default file is used to disable running a daemon, set some default flags or
-timeouts. If your init script has certain <emphasis>settable</emphasis>
-features you want to install these into the default file, not the init script.
+file sets defaults that are sourced by the <filename>.init</filename> script. Most times this
+<filename>.default</filename> file is used to disable running a daemon, set some default flags or
+timeouts. If your <filename>.init</filename> script has certain <emphasis>settable</emphasis>
+features you want to install these into the <filename>.default</filename> file, not the <filename>.init</filename> script.
</para>
<para>
-If your upstream program has an init file you can either use it or not. If you
-don't use their init.d script then create a new one in
+If your upstream program has an <filename>.init</filename> file you can either use it or not. If you
+don't use their <filename>init.d</filename> script then create a new one in
<filename>debian/<replaceable>package</replaceable>.init</filename>. However
-if the upstream init script looks fine and installs in the right place you
+if the upstream <filename>.init</filename> script looks fine and installs in the right place you
still need to setup the <filename>rc*</filename> symlinks. To do this you will
need to override <command>dh_installinit</command> in the
<filename>rules</filename> file with the following lines:
@@ -3255,10 +3255,10 @@
<row> <entry>1</entry> <entry>User command</entry> <entry>Executable commands or scripts</entry> </row>
<row> <entry>2</entry> <entry>System calls</entry> <entry>Functions provided by the kernel</entry> </row>
<row> <entry>3</entry> <entry>Library calls</entry> <entry>Functions within system libraries</entry> </row>
- <row> <entry>4</entry> <entry>Special files</entry> <entry>Usually found in /dev</entry> </row>
+ <row> <entry>4</entry> <entry>Special files</entry> <entry>Usually found in <filename>/dev</filename></entry> </row>
<row> <entry>5</entry> <entry>File formats</entry> <entry>E.g. <filename>/etc/passwd</filename>'s format</entry> </row>
<row> <entry>6</entry> <entry>Games</entry> <entry>Games or other frivolous programs</entry> </row>
- <row> <entry>7</entry> <entry>Macro packages</entry> <entry>Such as man macros</entry> </row>
+ <row> <entry>7</entry> <entry>Macro packages</entry> <entry>Such as <command>man</command> macros</entry> </row>
<row> <entry>8</entry> <entry>System administration</entry> <entry>Programs typically only run by root</entry> </row>
<row> <entry>9</entry> <entry>Kernel routines</entry> <entry>Non-standard calls and internals</entry> </row>
</tbody>
@@ -3623,7 +3623,7 @@
You can store such <command>dpkg-source</command> option argument in the
<filename>source/options</filename> file of the source package as the generic
solution to address this problem of the autogenerated files. The following
-will skip creating patch files for <filename>config.sub</filename>
+will skip creating patch files for <filename>config.sub</filename>,
<filename>config.guess</filename> and <filename>Makefile</filename>.
</para>
<screen>
@@ -3668,13 +3668,13 @@
by your sponsor. </para> </footnote>
</para>
<para>
-For <xref linkend="modify"/> , we created 3 patches in
+For <xref linkend="modify"/>, we created 3 patches in
<filename>debian/patches</filename>.
</para>
<para>
Since Debian patches are located in <filename>debian/patches</filename>, please
make sure to setup the <command>dquilt</command> command properly as described
-in <xref linkend="quiltrc"/> .
+in <xref linkend="quiltrc"/>.
</para>
<para>
When someone (including yourself) provides you with a patch
@@ -3715,12 +3715,12 @@
</listitem>
<listitem>
<para>
-packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/> ), and
+packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/>), and
</para>
</listitem>
<listitem>
<para>
-packages listed in the <literal>Build-Depends-indep</literal> field (see <xref linkend="control"/> ).
+packages listed in the <literal>Build-Depends-indep</literal> field (see <xref linkend="control"/>).
</para>
</listitem>
</itemizedlist>
@@ -3771,7 +3771,7 @@
The only input that will be required of you is your GPG secret pass phrase,
twice.
<footnote><para>
-This GPG key must be signed by the Debian developer to get connected to the web
+This GPG key must be signed by a Debian developer to get connected to the web
of trust and must be registerd to <ulink url="&keyring;">the Debian
keyring</ulink>. This enables your uploaded packages to be accepted to the
Debian archives. See
@@ -3891,7 +3891,7 @@
</listitem>
<listitem>
<para>
-packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/> ).
+packages listed in the <literal>Build-Depends</literal> field (see <xref linkend="control"/>).
</para>
</listitem>
</itemizedlist>
@@ -3939,7 +3939,7 @@
</para>
<para>
Although packages listed in the <literal>Build-Depends-indep</literal> field
-are required to be installed for the normal packaging by us (see <xref linkend="completebuild"/> ), they are not required to be installed for the
+are required to be installed for the normal packaging by us (see <xref linkend="completebuild"/>), they are not required to be installed for the
autobuilder system since it build only architecture dependent binary packages.
<footnote><para> Unlike under the <systemitem role="package">pbuilder</systemitem> package, the <command>chroot</command>
environment under the <systemitem role="package">sbuild</systemitem> package
@@ -3948,7 +3948,7 @@
packaging and autobuilder situation dictates whether you record such required
packages in the <literal>Build-Depends</literal> or
<literal>Build-Depends-indep</literal> fields of the
-<filename>debian/control</filename> file (see <xref linkend="control"/> ).
+<filename>debian/control</filename> file (see <xref linkend="control"/>).
</para>
</section>
<section id="option-sa"><title>Including <filename>orig.tar.gz</filename> for upload</title>
@@ -4263,7 +4263,7 @@
<filename>preinst</filename>, <filename>prerm</filename>,
<filename>postinst</filename>, and <filename>postrm</filename> files, are
non-trivial unless they are auto-generated by the <systemitem role="package">debhelper</systemitem> programs. So do not use them if you are
-a novice maintainer (see <xref linkend="maintscripts"/> ).
+a novice maintainer (see <xref linkend="maintscripts"/>).
</para>
<para>
If the package makes use of these non-trivial <emphasis>maintainer
@@ -4344,7 +4344,7 @@
for many common packaging errors. <footnote><para> You do not need to provide
the <command>lintian</command> option <literal>-i -I --show-overrides</literal>
if you customized <filename>/etc/devscripts.conf</filename> or
-<filename>~/.devscripts</filename> as described in <xref linkend="debuild"/> .
+<filename>~/.devscripts</filename> as described in <xref linkend="debuild"/>.
</para> </footnote>
</para>
<screen>
@@ -4388,7 +4388,7 @@
<para>
For warnings, tune the package to avoid them or verify that the warnings are
spurious. If spurious, set the <filename>lintian-overrides</filename> files as
-described in <xref linkend="lintian"/> .
+described in <xref linkend="lintian"/>.
</para>
<para>
Note that you can build the package with <command>dpkg-buildpackage</command>
@@ -4477,9 +4477,9 @@
</para></footnote>
you can upload the package to the Debian archive.
<footnote><para>
-There are publically accessible archives such as <ulink url="&mentors-dn;"/>
+There are publicly accessible archives such as <ulink url="&mentors-dn;"/>
which work almost the same way as Debian archive and provide upload area for
-the non-DD. You can set up an equivqlent archive by yourself using tools
+the non-DD. You can set up an equivalent archive by yourself using tools
listed at <ulink url="&deb-archive;"/>. So this section is useful for the
non-DD, too.
</para></footnote>
@@ -4672,7 +4672,7 @@
</listitem>
<listitem>
<para>
-Repeat what you did in <xref linkend="completebuild"/> , <xref linkend="checkit"/> , and <xref linkend="upload"/> . The difference is that
+Repeat what you did in <xref linkend="completebuild"/>, <xref linkend="checkit"/>, and <xref linkend="upload"/>. The difference is that
this time, the original source archive won't be included, as it hasn't been
changed and it already exists in the Debian archive.
</para>
@@ -4834,7 +4834,7 @@
... document changes made
</screen>
<para>
-If you set up a <filename>debian/watch</filename> file as described in <xref linkend="watch"/> , you can skip the <command>wget</command> command. You
+If you set up a <filename>debian/watch</filename> file as described in <xref linkend="watch"/>, you can skip the <command>wget</command> command. You
simply run <citerefentry> <refentrytitle>uscan</refentrytitle>
<manvolnum>1</manvolnum> </citerefentry> in the
<filename><replaceable>foo</replaceable>-<replaceable>oldversion</replaceable></filename>
@@ -4847,7 +4847,7 @@
uupdate</literal> at the end of the URL. </para> </footnote>
</para>
<para>
-You can release this updated source by repeating what you did in <xref linkend="completebuild"/> , <xref linkend="checkit"/> , and <xref linkend="upload"/> .
+You can release this updated source by repeating what you did in <xref linkend="completebuild"/>, <xref linkend="checkit"/>, and <xref linkend="upload"/>.
</para>
</section>
<section id="packagestyle"><title>Updating the packaging style</title>
@@ -4932,7 +4932,7 @@
</listitem>
</itemizedlist>
<para>
-You need to do other tasks described in <xref linkend="newupstream"/> , too.
+You need to do other tasks described in <xref linkend="newupstream"/>, too.
</para>
</section>
<section id="reminders"><title>Reminders for updating packages</title>
Attachment:
signature.asc
Description: OpenPGP digital signature