David Z Maze wrote:
> Thomas Gies <email@example.com> writes:
>> Why does dselect update packages from unstable even if I put
>> APT::Default-Release "testing";
>> in my apt.conf?
> Because dselect isn't terribly cognizant of APT; dselect was written
> first, and doesn't really understand why one would have multiple
> available versions of the same package, so it just picks the newest
> one ("unstable"). If you're looking for a CUI dpkg frontend that
> understands more of what APT is up to, you might look at aptitude.
Hm, it works with dselect if you have pinning similar to this:
fernst@live:~$ cat /etc/apt/preferences
X-comment: ============================ Track apt-build as primary
Pin: release a=apt-build
X-comment: ============================ Track testing as default
Pin: release a=testing
X-comment: ============================ Make unstable available
Pin: release a=unstable
But you will only have access to one version of a package when using
aptitude on the other hand offers access to all versions of a package.
- From: Thomas Gies <firstname.lastname@example.org>
- Re: dselect
- From: David Z Maze <email@example.com>