Russ Allbery wrote:

> I think we should hopefully be close to a final wording now.

Indeed!  All I have left are copy-edits (patch below).

> +++ b/policy.sgml
[...]
> +                                        The unpacked files may be
> +           partly from the new version or partly missing, so the script
> +           cannot not

s/ not//

>                        rely on files included in the package.
[...]
> +           Called before unpackaging 

s/unpackaging/unpacking/

>                                       the new package as part of the
> +           error handling of <prgn>preinst</prgn> failures.
[...]
>         When one binary package declares that it breaks another,
>         <prgn>dpkg</prgn> will refuse to allow the package which
> -       declares <tt>Breaks</tt> be installed unless the broken
> +       declares <tt>Breaks</tt> be unpacked unless the broken

s/be/to be/

> @@ -5048,7 +5132,7 @@ Provides: mail-transport-agent
>  Conflicts: mail-transport-agent
>  Replaces: mail-transport-agent
>           </example>
> -         ensuring that only one MTA can be installed at any one
> +         ensuring that only one MTA can be unpacked at any one
>           time.  See <ref id="virtual"> for more information about this
>           example.
>       </sect1>

Aside: is this advice right?  Maybe we should be encouraging

 Provides: mail-transport-agent
 Breaks: mail-transport-agent
 Replaces: mail-transport-agent

instead.

The new text looks very good.  Thanks again.

-- 8< --
Subject: Three typos
---
diff --git i/policy.sgml w/policy.sgml
index 3c63507..406301e 100644
--- i/policy.sgml
+++ w/policy.sgml
@@ -3805,7 +3805,7 @@ Checksums-Sha256:
              unpacking the new package because the <tt>postrm
              upgrade</tt> action failed.  The unpacked files may be
              partly from the new version or partly missing, so the script
-             cannot not rely on files included in the package.  Package
+             cannot rely on files included in the package.  Package
              dependencies may not be available.  Pre-dependencies will be
              at least unpacked following the same rules as above, except
              they may be only "Half-Installed" if an upgrade of the
@@ -3927,7 +3927,7 @@ Checksums-Sha256:
            <tag><var>new-postrm</var> <tt>abort-upgrade</tt>
              <var>old-version</var></tag>
            <item>
-             Called before unpackaging the new package as part of the
+             Called before unpacking the new package as part of the
              error handling of <prgn>preinst</prgn> failures.  May assume
              the same state as <prgn>preinst</prgn> can assume.
            </item>
@@ -4776,7 +4776,7 @@ Build-Depends: foo [linux-any], bar [any-i386], baz 
[!linux-any]
        <p>
          When one binary package declares that it breaks another,
          <prgn>dpkg</prgn> will refuse to allow the package which
-         declares <tt>Breaks</tt> be unpacked unless the broken
+         declares <tt>Breaks</tt> to be unpacked unless the broken
          package is deconfigured first, and it will refuse to
          allow the broken package to be reconfigured.
        </p>
-- 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to