also sprach Travis Crump <pretzalz@techhouse.org> [2004.08.27.2213 +0200]: > If testing is pinned to 500 and foo has a 'current pin' of > 100[since foo's installed version is no longer in any archive it > just has the 'default' installed pin], new version>old version and > 500>100 so it gets upgraded. Whereas if testing is pinned to 99, > 99<100 and it sticks with the currently installed version. great, thanks. the tipp to use the 100 priority (which i should have figured out myself, but as i said, it was friday) gave it away. thus, with the following: stable: version 1.0-1, pin at 900 testing: version 2.0-1, pin at 600 unstable: version 3.0-1, pin at 99 and 2.0-1 installed, the following pins will be given out: 1.0-1: 900 2.0-1: 100/600 3.0-1: 99 when 3.0-1 hits testing, the local package will be updated because: 1.0-1: 900 2.0-1: 100 3.0-1: 600 the first candidate is 1.0-1, but since 900 < 1000 and 2.0-1 --> 1.0-1 would be a downgrade, it does not qualify. however, 600 > 100, thus 3.0-1 gets installed. if i had pinned testing at 99 and unstable at 98 instead, it would be: 1.0-1: 900 2.0-1: 100 3.0-1: 99 and since 100 > 99, the version would stay at 2.0-1. cool. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
Attachment:
signature.asc
Description: Digital signature