Output of `apt-cache policy` is still confusing people

Bug #1349509 reported by Ganton
6
This bug affects 1 person
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://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!

Revision history for this message
Julian Andres Klode (juliank) wrote :

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
Revision history for this message
dino99 (9d9) wrote :

Fixed in xenial

apt (1.1~exp13) experimental; urgency=medium

Changed in apt (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.