Dear Maintainer,

for binary rebuilds uploaded to the archive (binNMUs), apt-show-versions
claims that a newer version than in the archive is installed:

$ apt-show-versions | fgrep newer
dvi2ps 5.1j-1+b1 newer than version in archive
pong2 0.1.3-1+b1 newer than version in archive
rss-glx 0.9.1-5+b4 newer than version in archive
wpasupplicant 1.0-3+b2 newer than version in archive
$ apt-cache policy dvi2ps pong2 rss-glx wpasupplicant
dvi2ps:
  Installed: 5.1j-1+b1
  Candidate: 5.1j-1+b1
  Version table:
 *** 5.1j-1+b1 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
pong2:
  Installed: 0.1.3-1+b1
  Candidate: 0.1.3-1+b1
  Version table:
 *** 0.1.3-1+b1 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
rss-glx:
  Installed: 0.9.1-5+b4
  Candidate: 0.9.1-5+b4
  Version table:
 *** 0.9.1-5+b4 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
wpasupplicant:
  Installed: 1.0-3+b2
  Candidate: 1.0-3+b2
  Version table:
 *** 1.0-3+b2 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status

I'd expect that apt-show-versions would recognize those packages as
"uptodate".

Hi,

Axel Beckert wrote:

If you have testing and unstable in your sources list with according
pinning to prefer testing, another symptom of this issue is:

$ apt-show-versions | fgrep manually
bc/sid *manually* upgradeable from 1.06.95-2+b1 to 1.06.95-4
curves/wheezy *manually* upgradeable from 0.8.19 to 0.8.19+b2
dc/sid *manually* upgradeable from 1.06.95-2+b1 to 1.06.95-4
jpeginfo/wheezy *manually* upgradeable from 1.6.0-5 to 1.6.0-5+b1
$ apt-cache policy bc curves dc jpeginfo
bc:
  Installed: 1.06.95-2+b1
  Candidate: 1.06.95-2+b1
  Version table:
     1.06.95-4 0
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
 *** 1.06.95-2+b1 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        100 /var/lib/dpkg/status
curves:
  Installed: 0.8.19
  Candidate: 0.8.19
  Version table:
 *** 0.8.19 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
dc:
  Installed: 1.06.95-2+b1
  Candidate: 1.06.95-2+b1
  Version table:
     1.06.95-4 0
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
 *** 1.06.95-2+b1 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        100 /var/lib/dpkg/status
jpeginfo:
  Installed: 1.6.0-5
  Candidate: 1.6.0-5
  Version table:
 *** 1.6.0-5 0
        900 http://ftp.ch.debian.org/debian/ wheezy/main amd64 Packages
        800 http://ftp.ch.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status

(Not sure why curves and jpeginfo show up there at all since I don't
see any binNMU for them in the "apt-cache policy" output. This may be
a different issue. Feel free to clone the bug in that case.)

		Regards, Axel