Bug#578514: apt: fails to upgrade a single package without explicit version specification

[Jens Seidel <jensseidel@users.sf.net>]

On Tue, Apr 20, 2010 at 04:48:13PM +0200, David Kalnischkies wrote:
> 2010/4/20 Jens Seidel <jensseidel@users.sf.net>:
> > The message "git-svn is already the newest version" is wrong as
> > 1:1.7.0.4-1 is installed but -2 exists:
> 
> Existence is not enough, it also need a decent pin value to be
> considered as candidate version.
> Could you show us the output of "apt-cache policy git-svn" ?

apt-cache policy git-svn
git-svn:
  Installed: 1:1.7.0-1
  Candidate: 1:1.7.0-1
  Version table:
     1:1.7.0.4-2 0
        800 http://ftp.de.debian.org unstable/main Packages
     1:1.7.0.4-1 0
        800 http://ftp.de.debian.org unstable/main Packages
 *** 1:1.7.0-1 0
        900 http://ftp.de.debian.org testing/main Packages
        100 /var/lib/dpkg/status
     1:1.5.6.5-3+lenny3 0
        500 http://security.debian.org lenny/updates/main Packages

My /etc/apt/preferences:
Package: *
Pin: release a=testing
Pin-Priority: 900

Package: *
Pin: release a=unstable
Pin-Priority: 800

Jens