2010/8/26 Paul Wise <p...@debian.org>:
> AFAIK to achieve that you need pinning priorities > 500 and < 1000.
A pin-value >= 100 is enough in this scenario.
> 500 would have maybe even the wrong effect, as repositories
which are not from the default-release - if set at all - get 500 per default
(expect if the Releasefile says Non-Automatic: yes, then it is pin 1).
So setting t-p-u too > 500 would give it always a preference in case no
default-release (which gets pin 990) is set.
Example:
Package: apt
Pin: release t-p-u
Pin-Priority: 600
apt:
Installed: 0.8.0
Candidate: 0.8.1
Version table:
0.9.0 0
500 http://ftp.de.debian.org/debian/ testing/main i386 Packages
0.8.1 0
600 http://ftp.de.debian.org/debian/ t-p-u/main i386 Packages
*** 0.8.0 0
100 /var/lib/dpkg/status
Note that the candidate is t-p-u apt 0.8.1 and not testing apt 0.9.0 …
In case APT::Default-Release (-t option) is set to "testing" the candidate
will be 0.9.0 as testing will have a pinning of 990 instead of 500…
but in this case 0.8.1 would be never a candidate as long as in testing
is still apt 0.8.0 as 990 > 600 and if you manually use 0.8.1 from t-p-u
apt will wait with an upgrade until this one or newer is in proper testing…
So, to let that actually work a user should not have a default-release…
Long story short:
If you want to get updates from an archive only if you pushed a version
previously from it: 100 => pin > 500.
Best regards
David Kalnischkies
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktinoy2_9zczxmktndqe3xve2jx5-gbziybjbc...@mail.gmail.com
