Matt Zimmerman wrote:
Package: *
Pin: release a=testing
Pin-Priority=600
Package: *
Pin: release a=sid
Pin-Priority=100
You want a=unstable here, not a=sid.
Hmm, i was curious about that, but since it worked for months with
a=sid i left it. Is it some {policy|rule|habit|...} to use unstable
instead of sid? And why does an "apt-cache policy" report sid instead
of unstable?
Anyway, this doesn't solve the problem of ignoring preferences:
[EMAIL PROTECTED]:~$ apt-cache policy apt
apt:
Installed: 0.5.14
Candidate: 0.5.14
Version Table:
*** 0.5.14 0
500 file: sarge/main Packages
500 http://ftp.de.debian.org sarge/main Packages
500 http://ftp.de.debian.org sid/main Packages
100 /var/lib/dpkg/status
W: No priority (or zero) specified for pin
W: No priority (or zero) specified for pin
Warnings about no/zero specified priorities, so apt seems to set default
500 instead of using configured 600/100 for sarge/sid. Worse, apt tries
to upgrade to newest seen package (i.e. sid's packages):
[EMAIL PROTECTED]:~$ apt-cache policy bash
bash:
Installed: 2.05b-8.1
Candidate: 2.05b-10
Version Table:
2.05b-10 0
500 http://ftp.de.debian.org sid/main Packages
*** 2.05b-8.1 0
500 file: sarge/main Packages
500 http://ftp.de.debian.org sarge/main Packages
100 /var/lib/dpkg/status
W: No priority (or zero) specified for pin
W: No priority (or zero) specified for pin
Only workaround so far is to disable sid packages in sources.list. Then
all upgrades seeme to run as expected.
Gerhard
