In addition, the following seems to be strange: The manpage says: > If the target release has been specified then APT uses the following > algorithm to set the priorities of the versions of a package. Assign: > > priority 1 > to the versions coming from archives which in their Release files > are marked as "NotAutomatic: yes" but not as "ButAutomaticUpgrades: > yes" like the debian experimental archive. > > priority 100 > to the version that is already installed (if any) and to the > versions coming from archives which in their Release files are > marked as "NotAutomatic: yes" and "ButAutomaticUpgrades: yes" like > the debian backports archive since squeeze-backports. > > priority 500 > to the versions that are not installed and do not belong to the > target release. > > priority 990 > to the versions that are not installed and belong to the target > release. No consider I've set: APT::Default-Release "stable"; and have added stable and testing in sources list. For package foo, the following versions are known: installed: 1.0 stable: 1.0 testing: 2.0 I'd conclude from the above that this means: 1.0 == 100 (and not 990, as THIS version IS installed) 2.0 == 500 (as THIS version is NOT installed) So the package should be upgraded, right? But it is not.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature