This has been fixed in the debian/experimental with a new algorithm for
pinning. I hope that this will be part of Ubuntu 16.04, but it's
probably too late and too risky to include in 15.10.
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1349509
Title:
Output of `apt-cache policy` is still confusing people
Status in apt package in Ubuntu:
Fix Committed
Bug description:
Output of `apt-cache policy` is still confusing people. As it was
stated by Julian Andres Klode (juliank) in
<https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364/comments/8>:
"The pin value displayed after the version does not actually
correspond to the version, but is the pin value of the candidate
version. This is confusing, yes, we might want to change this in a
future release".
For example, in
<https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364/comments/7>
it was written:
mysql-client-5.5:
Installed: (none)
Candidate: 5.5.31-0ubuntu0.12.04.1
Package pin: 5.5.31-0ubuntu0.12.04.1
Version table:
5.5.31-0ubuntu0.12.04.1 1002
500
http://srv11-msk.msk.mirantis.net/ubuntu-repo/mirror.yandex.ru/ubuntu/
precise-security/main amd64 Packages
500
http://srv11-msk.msk.mirantis.net/ubuntu-repo/mirror.yandex.ru/ubuntu/
precise-updates/main amd64 Packages
5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3 1002
1001
http://srv11-msk.msk.mirantis.net/ubuntu-repo/precise-fuel-folsom/
precise-2.1.0.1/main amd64 Packages
5.5.22-0ubuntu1 1002
500
http://srv11-msk.msk.mirantis.net/ubuntu-repo/mirror.yandex.ru/ubuntu/
precise/main amd64 Packages
and that 1002 was shown for "5.5.31-0ubuntu0.12.04.1",
"5.5.28-23.7ubuntu0.12.04.2+mirantis.wsrep3" and "5.5.22-0ubuntu1 1002"...
altough it was related only to "5.5.31-0ubuntu0.12.04.1" (the candidate
version).
One row should bring particular information about that row,
information that is common to all rows should appear in a separate
place.
I was misleaded, too, by the same kind of problem, and after searching
and searching... I found those explanations by Julian Andres Klode and
more confused users in
<https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364>.
Anyway, thanks for all the good software!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1349509/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
