Your message dated Mon, 27 Feb 2012 17:27:46 +0800
with message-id 
<CAN3veRdR1OFWW=h+vkhxkbotsujtkszbzgwc0uans4f1ojc...@mail.gmail.com>
and subject line Re: Aptitude: "why" gives invalid reasons (e.g. using packages 
that are not installed).
has caused the Debian Bug report #531030,
regarding Aptitude: "why" gives invalid reasons (e.g. using packages that are 
not installed).
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.)


-- 
531030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531030
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.11.11-1+b1
Severity: minor


Output from aptitude:

root@host:~# aptitude why libass1
i   sun-java6-plugin          Depends    firefox | firefox-2 |
iceweasel | mozilla-firefox | iceape-browser | mozilla-browser |
epiphany-gecko | epiphany-webkit | epiphany-browser | galeon |
midbrowser | xulrunner
p   galeon                    Recommends gnome-control-center
p   gnome-control-center      Recommends gnome-session
p   gnome-session             Recommends gnome-panel
p   gnome-panel               Recommends gnome-applets (>= 2.12.1-1)
p   gnome-applets             Depends    gstreamer0.10-alsa |
gstreamer0.10-audiosink | hurd
p   gstreamer0.10-plugins-bad Provides   gstreamer0.10-audiosink
p   gstreamer0.10-plugins-bad Depends    libass1

root@host:~# aptitude why bittorrent
i   bittorrent     Suggests bittorrent-gui
p   bittorrent-gui Depends  bittorrent (>= 3.4.2-1)


However: Purging the package, then reinstalling it and after wards
making it as "auto"-installed (or probably just marking the package as
autoinstalled right away) makes aptitude suggest removal of the
package (though this is quite expected). However this makes slightly
more difficult to reproduce. If it is any help; I discovered it by
using gtkorphan to find unused packages and then queried "aptitude why
<package>".

Also, it does not come with an invalid reason for every orphaned package.


~Niels

-- Package-specific info:
aptitude 0.4.11.11 compiled at Apr 17 2009 21:35:13
Compiler: g++ 4.3.3
Compiled against:
  apt version 4.6.0
  NCurses version 5.7
  libsigc++ version: 2.0.18
  Ept support enabled.

Current library versions:
  NCurses version: ncurses 5.7.20090404
  cwidget version: 0.5.12
  Apt version: 4.6.0
        linux-gate.so.1 =>  (0xb7f03000)
        libapt-pkg-libc6.9-6.so.4.7 =>
/usr/lib/libapt-pkg-libc6.9-6.so.4.7 (0xb7e2c000)
        libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7dee000)
        libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb7de7000)
        libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0xb7d23000)
        libept.so.0 => /usr/lib/libept.so.0 (0xb7ca8000)
        libxapian.so.15 => /usr/lib/libxapian.so.15 (0xb7b51000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7b3c000)
        libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7b23000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7a31000)
        libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7a0b000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb79df000)
        libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb787f000)
        libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb787b000)
        libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7876000)
        /lib/ld-linux.so.2 (0xb7f04000)
Terminal: screen
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:

aptitude linkage:

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6. 0.7.21            Advanced front-end for dpkg
ii  libc6                  2.9-12            GNU C Library: Shared
libraries
ii  libcwidget3            0.5.12-4          high-level terminal
interface libr
ii  libept0                0.5.26+b1         High-level library for
managing De
ii  libgcc1                1:4.4.0-5         GCC support library
ii  libncursesw5           5.7+20090404-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.4.0-5           The GNU Standard C++
Library v3
ii  libxapian15            1.0.12-2          Search engine library
ii  zlib1g                 1:1.2.3.3.dfsg-13 compression library - runtime

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do <none>     (no description available)
ii  libparse-debianchangelog-perl 1.1.1-2    parse Debian changelogs
and output

Versions of packages aptitude suggests:
ii  debtags                       1.7.9+b1   Enables support for
package tags
ii  tasksel                       2.78       Tool for selecting tasks
for insta

-- no debconf information




--- End Message ---
--- Begin Message ---
Hello


Thanks for reporting this issue with aptitude.


With regards to "orphaned" packages and the "why" command, the man
page says this:

  Explains the reason that a particular package should or cannot be
  installed on the system.

  This command searches for packages that require or conflict with the
  given package. It displays a sequence of dependencies leading to the
  target package, along with a note indicating the installed state of
  each package in the dependency chain:

  …

  By default aptitude outputs only the “most installed, strongest,
  tightest, shortest” dependency chain.…

You will note that the second paragraph does not mention any
restriction about only using installed packages, although the program
does try to use as many installed packages as possible in it's
response.

"aptitude why" is not a tool to locate orphaned packages.

I am closing this as it is not a bug, rather a feature which enables
investigation of dependency chains regardless of package installation
status.


Regards


--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Reply via email to