|Newer page:||version 5||Last edited on Wednesday, March 19, 2003 6:48:50 am||by MishaGorodnitzky|
|Older page:||version 3||Last edited on Tuesday, June 4, 2002 12:30:36 am||by perry||Revert|
@@ -51,11 +51,13 @@
followed by an equals then by the string.
The data for these matches are taken from the ''Release'' files that APT downloads during an update. The available keys are:
@@ -192,11 +194,13 @@
A package pin looks like this:
-Pin: version .4.
+ Package: apt
+ Pin: version .4.
+ Pin-Priority: 1001
The first line specifies the package, the second gives the Pin specification and the last gives the priority of this pin. The first word of the pin specification may be version, release or origin, the remainder of the field is described in the Versioning section above.
A default pin is how the priorities of package files are
@@ -205,11 +209,12 @@
file. Only release or origin may be used in the Pin
specification since they match Packages files.
-Pin: release v=2.1*
+ Package: *
+ Pin: release v=2.1*
+ Pin-Priority: 998
If the Pin-Priority field is omitted then the priority defaults to 989 for both cases.
@@ -225,9 +230,9 @@
In practice this is often desired. A user may use a default
pin to make the stable distribution the default and then use
-the __--target-dist__ option with
+the __--target-dist__ option with apt-get(8) to
select newer versions from unstable. The packages that have
been upgraded to unstable will continue to follow the
versions that are available in unstable since the stable
versions now fall below the downgrade prevention
@@ -246,16 +251,16 @@
priority larger than 1000.
See the APT bug page
-/usr/share/doc/debian/bug-reporting.txt'' or the
+ /usr/share/doc/debian/bug-reporting.txt'' or the
APT was written by the APT team