All settings involving pinning are of the first-come-first-serve level. Adding an exception for the default-release setting to have an effect on all packages from this release "maybe" is just complicating a feature in usage, documentation and code which is already very complicated – and what makes default-release be so special, why not for all of them… (which can't be done because behavior changes are a no-no in general).
Or in other words: You are arguing that default-release should not override pinnings of packages but that doesn't happen. It overrides the pinning of releases. If it wouldn't be doing that, what would be the point… The usecase for this is your very own usecase – or how do you overrule your preferences setting in case you occasionally don't want the PPA to take the lead? You can use globs and regexes in preferences btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565782 Title: APT doesn't respect pin-priority when using APT::Default-Release option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1565782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
