Bug#852967: release-notes: Document apt pinning changes

[Baptiste Jammet <baptiste@mailoo.org>]

Hi,

Dixit Julian Andres Klode, le 28/01/2017 :

>In apt 1.1, we introduced a new pinning engine. 
[...]

Is the attached snippet (from your words) clear enough? 
I dropped the examples as I think pin-players will understand easily
(I'm not one but I understood, so...).

Please comment if needed. Thanks

Baptiste

Index: en/issues.dbk
===================================================================
--- en/issues.dbk	(révision 11404)
+++ en/issues.dbk	(copie de travail)
@@ -369,6 +369,26 @@
         </listitem>
       </itemizedlist>
     </section>
+    <section id="new-apt-pinning">
+      <title>New APT pinning engine</title>
+      <para>
+        APT 1.1 introduced a new pinning engine that now matches the
+        description in the manual page.
+      </para>
+      <para>
+        The old engine assigned one pin priority per package,
+        the new assigns pin priorities per version. It then picks
+        the version with the highest pin that is not a downgrade or that has
+        a pin > 1000.
+      </para>
+      <para>
+        This changes the effect of some pins, especially negative ones.
+        Previously, pinning a version to -1 effectively prevented the
+        package from being installed (the package pin was -1),
+        it now only prevents the version of this package from being
+        installed.
+      </para>
+    </section>
     <section id="apt-new-requirements-to-mirrors">
       <title>New requirements for APT repository</title>
       <note>

Attachment: pgpf3qBrUqZf3.pgp
Description: OpenPGP digital signature