Bug#375393: aptitude show package-name can list wrong version as installed.

2006-06-30 Thread Andrew Vaughan 
On Friday 30 June 2006 14:59, Daniel Burrows wrote:
   The basic problem here is that the State line just refers to the
 state of the package in general, not the version being displayed.  A

Hmm.  I don't feel that's a problem.  To me that's the expected behaviour.

 secondary problem is that we may have a wrong default here -- aptitude is
 defaulting to the candidate version (what would be installed by
 install), when you probably want it to default to the current version
 if one exists.

That was indeed my (naive?) expectation.  

Feel free to close this or tag won't fix if you feel that the current design 
is appropriate.

Otherwise, can I suggest the fix below?  

   Change Version: to 
  Installed Version: 1.1.0-1sarge1
   iff other versions are available, add
  Available Versions: 1.1.0-1, 1.2.0-1

Unfortunately this will break scripts parsing aptitude show package 
output.


Thanks for your work on Debian

Andrew V.







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#375393: aptitude show package-name can list wrong version as installed.

2006-06-29 Thread Daniel Burrows 
  The basic problem here is that the State line just refers to the state
of the package in general, not the version being displayed.  A secondary
problem is that we may have a wrong default here -- aptitude is defaulting
to the candidate version (what would be installed by install), when you
probably want it to default to the current version if one exists.

  Daniel


signature.asc
Description: Digital signature

Bug#375393: aptitude show package-name can list wrong version as installed.

2006-06-25 Thread Andrew Vaughan 
Package: aptitude
Version: 0.4.1-1.1
Severity: minor

After using dpkg --purge, dpkg -i to manually downgrade a package, 
aptitude show package-name | grep Version still shows the original 
version as installed.  This behaviour continues even after an interactive 
available package-list update, and setting the package on hold.

Indeed, even using to aptitude to purge the package, and then using dpkg -i to 
install the old version doesn't reset the version aptitude thinks is installed.
I'm too lazy to create a repository so that aptitude can install the old 
version.

Fooling round with this and Forbidden, I now have

$ aptitude show nvidia-settings
Package: nvidia-settings
State: installed [held]
Forbidden version: 1.0+20060516-1
Automatically installed: no
Version: 1.0+20060516-1

In interactive mode aptitude shows the correct version as installed 
(Version: 1.0+20051122-1).

Thanks for your work on Debian.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3.1 0.6.44.2   Advanced front-end for dpkg
ii  libc6 2.3.6-13   GNU C Library: Shared libraries
ii  libgcc1   1:4.1.1-1  GCC support library
ii  libncursesw5  5.5-2  Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a2.0.16-3   type-safe Signal Framework for C++
ii  libstdc++64.1.1-1The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc 0.4.1-1.1  English manual for aptitude, a ter

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]