Thomas Hood wrote:
If a target release has been specified, then APT uses the following algorithm to set the priorities of the instances of a package. Assign: priority 100 to the instance of a package that is already installed (if any). priority 500 to the instances of a package that are not installed and do not belong to the target release. priority 990 to the instances of a package that are not installed and belong to the target release.
Is this right? Shouldn't it be something to the effect: priority 100 to the instance of a package that is already installed (if any). priority 500 to the instances of a package that are available in an archive but do not belong to the target release. priority 990 to the instances of a package that belong to the target release. For instance, taking a random package: pretzalz@Pretzalz:~$ apt-cache policy coreutils coreutils: Installed: 4.5.2-1 Candidate: 4.5.2-1 Version Table: 4.5.3-4 0 70 http://http.us.debian.org unstable/main Packages *** 4.5.2-1 0 700 http://http.us.debian.org testing/main Packages 100 /var/lib/dpkg/status 4.5.2-1 gets both the 100 for being installed and the 700 for belonging to the testing release. There are other places in the man page that use this language as well.