On Jo, 20 iun 13, 20:13:06, Andrei POPESCU wrote: > On Ma, 18 iun 13, 18:00:37, Roland Hieber wrote: > > > But nevertheless, apt still assigns a prio of 500:
Actually it doesn't, 500 is the priority of the source, the package itself has 250 (the number behind the version). > > $ apt-cache policy libavdevice53 > > libavdevice53: > > Installed: 6:9.3-1 > > Candidate: 7:0.10.3-dmo1 > > Package pin: 7:0.10.3-dmo1 > > Version table: > > 7:0.10.3-dmo1 250 > > 500 > > http://debian-multimedia.informatik.uni-erlangen.de/debian-multimedia/ > > testing/main amd64 Packages > > *** 6:9.3-1 250 > > 100 /var/lib/dpkg/status > > 6:0.8.6-1 250 > > 500 http://debian.tu-bs.de/debian/ wheezy/main amd64 Packages > > > > > > However, if I change the pinning to Package: *, everything works as > > expected (for all packages of course, but I don't need that :P) > > > > Is this a PEBCAK, or is this a bug in apt? I think we didn't understand priorities correctly. Let's see again what the fine manual (apt_preferences(5)) says: How APT Interprets Priorities Priorities (P) assigned in the APT preferences file must be positive or negative integers. They are interpreted as follows (roughly speaking): [...] 500 <= P < 990 causes a version to be installed unless there is a version available belonging to the target release or the installed version is more recent As per above output you have 6:9.3-1 installed, which is more recent than 6:0.8.6-1. Because of this apt wants to jump directly to the higher version from dmo (apt will not downgrade unless the priority is higher than 1000). Does this make sense? Solution: uninstall 6:9.3-1 and apt will then prefer the Debian version. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc
Description: Digital signature
