Output of `apt-cache policy` is still confusing people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Output of `apt-cache policy` is still confusing people. As it was stated by Julian Andres Klode (juliank) in <https:/
"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:/
mysql-
Installed: (none)
Candidate: 5.5.31-
Package pin: 5.5.31-
Version table:
500 http://
500 http://
1001 http://
500 http://
and that 1002 was shown for "5.5.31-
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:/
Anyway, thanks for all the good software!
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.