For some reason I was under the impression, that APT::Default-Release
would be overridden by the more-specific pin. I.e. default-release would
apply only to those where nothing else does; a fall-back. Apparently I was
mistaken.
By the way, apt_preferences(5) does not seem to specify, which one is
preferred, Default-Release or the pin if both match a package. Perhaps it
should?
This is the behavior I, too, expected (and tripped up on it earlier this
week). From what I can tell, APT::Default-Release is a _blanket_ setting,
with pins providing finer-grained control. Given this fact, I would've
expected pins to take precedence, since they can provide more specific
control over a base policy offered by APT::Default-Release. So even if
currently APT::Default-Release takes precedence over pins, IMHO, it ought to
be the other way around.
Amit
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
