Thanks for the reply David,
I can live with looking at apt-cache policy and seeing all the pinned packages.
But I still count on apt-cache policy to disambiguate between different 
candidate versions of a package, as it does whenmultiple repositories are in 
the sources.list.
In that case, if the candidate package was chosen due to a pin, the Pin: line 
would display that explicitly and if multiple pinsapply to the package, only 
the ones that resulted in that candidate would be displayed (for example if one 
Pin was by versionand the other by origin).
Alternatively, it would be just as useful if in listing the possible 
candidates, the pin information affecting each was added (if relevant),just as 
different repositories are listed. thanks,--jack shaio
 

      From: David Kalnischkies <da...@kalnischkies.de>
 To: js <jsh...@yahoo.com>; 807983-d...@bugs.debian.org 
 Sent: Wednesday, December 23, 2015 1:06 PM
 Subject: Re: Bug#807983: apt-cache policy no longer displays pinning info
   
On Mon, Dec 14, 2015 at 09:29:29PM -0500, js wrote:
> Restoring this behavior would make it much easier to see why a package
> is kept at a version that is not the latest.
> 
> [Perhaps this is related to the change in 1.1~exp9 to the pinning algorithm?]

The problem with this Pin: line was that you can have both multiple pins
effecting (different) versions of a package and a pin effecting multiple
versions. What to display in these cases?

Julian (and I) therefore decided to drop this line as it tends to be
more confusing than helpful.

Have a look at the end of the output of "apt-cache policy" for a list of
all package (versions) effected by pins. The output changed slightly
with 1.1, but the list itself exists also in earlier versions. Also, if
you look very closely at the package specific policy display you can see
now that the version you specified is pinned to 1001.

I hope that helps you getting over the "loss" as both is intend to be
the better replacement, but feel free to report back if that isn't
working for you. Marking the bug as closed in the meantime as I don't
see Pin: coming back as-was.


Best regards

David Kalnischkies

  

Reply via email to