Your message dated Sun, 18 Jan 2009 17:36:15 -0800
with message-id <[email protected]>
and subject line Closing per submitter
has caused the Debian Bug report #503175,
regarding aptitude shows false update count
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
503175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503175
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.11.10-1lenny1
Severity: normal



-- Package-specific info:
aptitude 0.4.11.10 compiled at Oct  9 2008 09:10:42
Compiler: g++ 4.3.2
Compiled against:
  apt version 4.6.0
  NCurses version 5.6
  libsigc++ version: 2.0.18
  Ept support enabled.

Current library versions:
  NCurses version: ncurses 5.6.20080830
  cwidget version: 0.5.12
  Apt version: 4.6.0
        linux-vdso.so.1 =>  (0x00007fff0f9ff000)
        libapt-pkg-libc6.7-6.so.4.6 => /usr/lib/libapt-pkg-libc6.7-6.so.4.6 
(0x00007f4c074f5000)
        libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007f4c072aa000)
        libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007f4c070a5000)
        libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007f4c06dd2000)
        libept.so.0 => /usr/lib/libept.so.0 (0x00007f4c06b59000)
        libxapian.so.15 => /usr/lib/libxapian.so.15 (0x00007f4c067ef000)
        libz.so.1 => /usr/lib/libz.so.1 (0x00007f4c065d8000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007f4c063bc000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f4c060b0000)
        libm.so.6 => /lib/libm.so.6 (0x00007f4c05e2d000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f4c05c16000)
        libc.so.6 => /lib/libc.so.6 (0x00007f4c058c3000)
        libutil.so.1 => /lib/libutil.so.1 (0x00007f4c056c0000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007f4c054bc000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f4c077b5000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:

aptitude linkage:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'winehq'), (110, 'unstable'), (100, 
'stable'), (95, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6. 0.7.14+b1         Advanced front-end for dpkg
ii  libc6                  2.7-14            GNU C Library: Shared libraries
ii  libcwidget3            0.5.12-3          high-level terminal interface libr
ii  libept0                0.5.22            High-level library for managing De
ii  libgcc1                1:4.3.2-1         GCC support library
ii  libncursesw5           5.6+20080830-1    shared libraries for terminal hand
ii  libsigc++-2.0-0c2a     2.0.18-2          type-safe Signal Framework for C++
ii  libstdc++6             4.3.2-1           The GNU Standard C++ Library v3
ii  libxapian15            1.0.7-3           Search engine library
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptit 0.4.11.10-1lenny1 English manual for aptitude, a ter
ii  libparse-debianchangel 1.1.1-2           parse Debian changelogs and output

Versions of packages aptitude suggests:
pn  debtags                       <none>     (no description available)
ii  tasksel                       2.75       Tool for selecting tasks for insta

-- no debconf information

aptitude update gives the following:
Current status: 0 broken [+0], 0 updates [+0], 9416 new [+0]

aptitude install (or safe-upgrade) shows the following:
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

apt-show-versions gives the following culprit:
wine/etch downgradeable from 1.1.5-1 to 1.1.1~winehq0~debian~4.0-1

apt-show-versions -a wine
wine 1.1.5-1 install ok installed
wine 1.0.0-1~bpo40+1            etch-backports www.backports.org
No stable version
wine 1.0.0-1                    testing        debian.mirror.frontiernet.net
wine 1.0.0-1.1                  sid            debian.mirror.frontiernet.net
wine 1.1.1~winehq0~debian~4.0-1 etch           wine.budgetdedicated.com
wine 1.1.5-1                    experimental   debian.mirror.frontiernet.net
No testing version
No unstable version
wine/etch downgradeable from 1.1.5-1 to 1.1.1~winehq0~debian~4.0-1


Note that the wine package 1.1.1 is the one from winehq, using the winehq 
repos. Source list:
deb http://wine.budgetdedicated.com/apt/ etch main

That's also the one with 500 priority (same thing happened woth a 450 prority, 
but that shouldn't override an installed package (and in fact it doesn't 
actually try to install it, which is good). Downgrading the wine package to 
this version clears up all the problems. Reinstalling the experimental (most 
recent) version causes the erroneous count to appear again. Changing the 
priority to <100 also solves the problem. >=100 and the problem occurs. Since 
an installed package supposedly has a prioroty of 100 then having equal 
priorities shouldn't cause this problem (installed has a > version). Because 
installed has a > version then this shouldn't happen even with larger 
priorities (unless I'm misunderstanding something about how they're supposed to 
work).

Note that I suspect that this should really be filed against ether apt or dpkg 
since upgrade manager exhibits similiar symptoms. Systray icon shows as updates 
available. Bring up the app and it states "System up to date". But since I'm 
not sure exactly where to file it, and since I discovered it using aptitude 
(command line mode) I'm sending it here.

If you need any more info please ask.
-jcm



--- End Message ---
--- Begin Message ---
  The submitter tells me that this was due to an unusual configuration
on his machine.  It looks to me like aptitude's behavior is correct:
an update is available (the newer older version), and *-upgrade shows
that a package is not being upgraded for whatever reason.  I'm still
curious what "aptitude install wine" would have done, but I forgot
to ask before and he's fixed his system.  Anyway, we can close this. :-)

  There may be a bug in the apt documentation.

  Daniel


--- End Message ---

Reply via email to