also sprach Carlos Sousa <csousa@tvtel.pt> [2002.12.03.1646 +0100]: > > Package: * > > Pin: release a=stable > > Pin-Priority: 999 > > > > Package: * > > Pin: release a=testing > > Pin-Priority: 333 > > Both stable and testing are pinned in the 100-999 bracket, so apt > is perhaps feeling free to download whichever package is the most recent > (the one in testing). ok. i raised stable to 1001, which did the trick. nevertheless, the above setup works perfectly fine with all my other machines. there, testing is at 666 and unstable at 333, so packages will stable if they are available there, testing if they aren't in stable, and unstable if they aren't in testing. > If you assign a value of 99 or below, then apt will ignore that > particular release unless asked for with the -t switch. That's how > I have unstable pinned in my system. i'll have to try that... > Warning: very limited understanding of the apt pinning mechanism here :) yup. AOL -- .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc
Attachment:
pgpqxWZuZu83e.pgp
Description: PGP signature