[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#338660: marked as done (developers-reference: Various typos, forgotten words, and slight rewordings)

Your message dated Sun, 09 Apr 2006 10:47:09 -0700
with message-id <E1FSe0D-00075e-6v@spohr.debian.org>
and subject line Bug#338660: fixed in developers-reference 3.3.7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: developers-reference
Version: 3.3.6
Severity: minor
Tags: patch

Hi,

upon reading the Developer's Reference I noticed a few typos and
forgotten words.  I append a patch, which fixes those.  It also contains
suggestions to improve the wording of few sentences.

uLI

--- /tmp/ediff7676ZEL	2005-11-11 20:26:39.344994822 +0100
+++ /tmp/developers-reference.sgml	2005-11-11 20:26:39.349994237 +0100
@@ -165,7 +165,7 @@
 sponsor can request one at <url id="&url-sponsors;">.
 -->
 Please read the
-inofficial debian-mentors FAQ at <url id="&url-mentors;"> first.
+unofficial debian-mentors FAQ at <url id="&url-mentors;"> first.
 	<p>
 If you wish to be a mentor and/or sponsor, more information is
 available in <ref id="newmaint">.
@@ -561,7 +561,7 @@
 all the files.
 	<p>
 There are other additional channels dedicated to specific subjects.
-<em>#debian-bugs</em> is used for coordinating bug squash parties.
+<em>#debian-bugs</em> is used for coordinating bug squashing parties.
 <em>#debian-boot</em> is used to coordinate the work on the debian-installer.
 <em>#debian-doc</em> is
 occasionally used to talk about documentation, like the document you are
@@ -2087,9 +2087,9 @@
 
       <sect1 id="upload-bugfix">When bugs are closed by new uploads
 	<p>
-As bugs and problems are fixed your packages, it is your
-responsibility as the package maintainer to close the bug.  However,
-you should not close the bug until the package which fixes the bug has
+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 close a bug until the package which fixes the bug has
 been accepted into the Debian archive.  Therefore, once you get
 notification that your updated package has been installed into the
 archive, you can and should close the bug in the BTS.
@@ -2849,7 +2849,7 @@
        <p>
 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 with a reasonable amount of time. An example is a package that
+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.
        <p>
@@ -2889,7 +2889,7 @@
 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 there removal by filing a bug against
+request their removal by filing a bug against
 <package>ftp.debian.org</package>
 
 
@@ -2921,9 +2921,10 @@
 However, aesthetic changes must <em>not</em> be made in a non-maintainer
 upload.
 	<p>
-And please remember the Hippocratic Oath: "Above all, do no harm."
-It is better if a package has an grave bug open, than if a not working
-patch was applied, and the bug is only hidden now but not resolved.
+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.
 
 
       <sect1 id="nmu-guidelines">How to do a NMU
@@ -2983,7 +2984,7 @@
 for a package to enter testing is through unstable.
 	<p>
 For the stable distribution, please take extra care. Of course, the release
-managers may also change the rules here. Please verify before upload that
+managers may also change the rules here. Please verify before you upload that
 all your changes are OK for inclusion into the next stable release by the
 release manager.
 	<p>
@@ -3540,7 +3541,7 @@
 	<sect1 id="helper-scripts">Helper scripts
 	<p>
 The rationale for using helper scripts in <file>debian/rules</file> is
-that lets maintainers use and share common logic among many packages.
+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 <file>/usr/lib/menu</file>, and add commands to the
 maintainer scripts to register and unregister the menu entries.  Since
@@ -4079,8 +4080,8 @@
 	<p>
 These guidelines include some writing style and typography
 recommendations, general considerations about debconf usage as well as
-more specific recommendations for some parts of the distribution (for
-instance, the installation system).
+more specific recommendations for some parts of the distribution (the
+installation system for instance).
 
 	<sect1>Do not abuse debconf
 	<p>
@@ -4283,7 +4284,7 @@
 
 	<sect2>Description: short and extended description
 	<p>
-Templates descriptions have two parts: short and extended. The short 
+Template descriptions have two parts: short and extended. The short 
 description is in the "Description:" line of the template.
 	<p>
 The short description should be kept short (50 characters or so) so
@@ -4566,7 +4567,7 @@
           <p>
 Policy specifies that documentation should be shipped in HTML format.
 We also recommend shipping documentation in PDF and plain text format if
-convenient and quality output is possible.  However, it is generally
+convenient and if output of reasonable quality is possible.  However, it is generally
 not appropriate to ship plain text versions of documentation whose source
 format is HTML.</p>
           <p>
@@ -4705,7 +4706,7 @@
 distributed by the upstream author.
 <footnote>
 We cannot prevent upstream authors from changing the tarball
-they distribute without also upping the version number, so
+they distribute without also incrementing the version number, so
 there can be no guarantee that a pristine tarball is identical
 to what upstream <em>currently</em> distributing at any point in
 time. All that can be expected is that it is identical to
@@ -5026,7 +5027,7 @@
       <p>
 You may also be interested in contacting the persons who are
 subscribed to a given source package via <ref id="pkg-tracking-system">.
-You can do so by using the <tt>&lt;package-name&gt;@&pts-host;</tt>
+You can do so by using the <tt>&lt;package&gt;@&pts-host;</tt>
 email address.
 <!-- FIXME: moo@packages.d.o is easily confused with moo@packages.qa.d.o -->
 
@@ -5349,7 +5350,7 @@
 avoid the chaos resulting in having several versions of the same document in
 bug reports.
 	    <p>
-The best solution is to fill a regular bug containing the translation against
+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 severity higher
 than 'wishlist', since the lack of translation never prevented a program from
 running.

--- End Message ---
--- Begin Message --- 
Source: developers-reference
Source-Version: 3.3.7

We believe that the bug you reported is fixed in the latest version of
developers-reference, which is due to be installed in the Debian FTP archive:

developers-reference-fr_3.3.7_all.deb
  to pool/main/d/developers-reference/developers-reference-fr_3.3.7_all.deb
developers-reference_3.3.7.dsc
  to pool/main/d/developers-reference/developers-reference_3.3.7.dsc
developers-reference_3.3.7.tar.gz
  to pool/main/d/developers-reference/developers-reference_3.3.7.tar.gz
developers-reference_3.3.7_all.deb
  to pool/main/d/developers-reference/developers-reference_3.3.7_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 338660@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Barth <aba@not.so.argh.org> (supplier of updated developers-reference package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 09 Apr 2006 11:31:52 -0600
Source: developers-reference
Binary: developers-reference-fr developers-reference
Architecture: source all
Version: 3.3.7
Distribution: unstable
Urgency: low
Maintainer: Debian Documentation Project <debian-doc@lists.debian.org>
Changed-By: Andreas Barth <aba@not.so.argh.org>
Description: 
 developers-reference - guidelines and information for Debian developers
 developers-reference-fr - guidelines and information for Debian developers, in French
Closes: 295483 297069 298016 299217 302000 305947 306120 306630 308103 309502 317411 320981 326857 327682 334820 336146 338660 339826 340024 341195 341197 341568 344303 347229 348160 349493 351255 351944 352749 353447
Changes: 
 developers-reference (3.3.7) unstable; urgency=low
 .
   * Andreas Barth:
     - adjust information about distributions with reality.
     - add note on alioth accounts. Thanks, Phillip Kern. Closes: #306630
     - correct manpage section of dpkg-scanpackages. Closes: #297069
     - fix RFC 2440 URL. Closes: #308103
     - add $arch@buildd information. Closes: #295483
     - link to keyring.d.o for key replacement. Thanks, Martin Michlmayr.
       Closes: #298016
     - add information about Packages-arch-specific. Thanks, Frank Küster.
       Closes: #302000
     - add hint about LWN subscription. Thanks, Martin Michlmayr.
       Closes: #299217
     - more about debconf-style translation. Thanks, Christian Perrier.
       Closes: #309502
     - non-us discontinued.
     - document nmu changes wrt version tracking. Thanks, Justin Pryzby.
       Closes: #341197
     - fix spelling issues. Thanks to various people.
       Closes: #336146, #326857, #338660
     - update menu policy helpers. Thanks, Florian Ernst. Closes: #340024
     - send mia-mail to mia@qa. Thanks, Adam D. Barratt. Closes: #341568
     - Joerg Jaspert is now freenode contact. Closes: #344303
     - give a clearer description of the gpg v4-key issues. Thanks,
       Martin Michlmayr and Peter Palfrader. Closes: #317411
     - more verbose about Homepage. Closes: #339826
     - add sarge and etch. Closes: #327682
     - document severity of RoM-request bugs. Closes: #305947
     - update FSF address. Closes: #334820
     - fix P-a-s link. Closes: #341195
     - reflect binNMU changes. Closes: #349493
     - new security upload queue. Closes: #352749
     - fix experimental's sources.list entry. Closes: #347229
     - remove deprecated "Closes:..." to ACK NMU bug fixes. Closes: #353447
     - when resigning, gpg-sign your mail. Closes: #348160
     - make pristine source and repackaged origtargz anchors work.
       Closes: #351255
     - same number of RC bugs is ok. Closes: #351944
     - dpkg-source doesn't keep permissions. Thanks, Enrico Zini.
       Closes: #306120
     - also mention aspell. Closes: #320981
 .
   * Frédéric Bothamy
     - French translation updated to version 3.3.7, proofread by Bernard Adrian
Files: 
 1fa3306d313ef71c320b29fc65de5a73 687 doc optional developers-reference_3.3.7.dsc
 a5ebba2123818aa47c897654ac1352c0 272598 doc optional developers-reference_3.3.7.tar.gz
 075ee8db80660b21d2d1b51ca29e79c4 589522 doc optional developers-reference_3.3.7_all.deb
 43eeb36aeb4ed2ff90bf3d2934867239 231352 doc optional developers-reference-fr_3.3.7_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFEOUZDmdOZoew2oYURAurBAKCxZGWku01W9/y4hgoovvanK/0S4ACdHkMA
U767wyMyp3Imd76flAehRNs=
=2Xb4
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: