Your message dated Mon, 28 Sep 2015 23:52:49 +0100
with message-id <[email protected]>
and subject line Re: Bug#683866: aptitude does not have an autoremove command
has caused the Debian Bug report #683866,
regarding aptitude does not have an autoremove command
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.)
--
683866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683866
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.8-1
Severity: wishlist
Dear Maintainer,
aptitude does not have the autoremove command that apt-get has. There
does not appear to be any way to uninstall automatically installed
packages from the command line with aptitude.
(I don't know if it is a goal to be able to do everything from the
command line with aptitude, or to mirror every function of apt-get. The
reason I would rather use aptitude than apt-get is that aptitude
maintains a simple log file that is handy to refer to.)
Andrew
-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.6.8 compiled at Jun 9 2012 10:02:58
Compiler: g++ 4.7.0
Compiled against:
apt version 4.12.0
NCurses version 5.9
libsigc++ version: 2.2.10
Ept support enabled.
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 5.9.20110404
cwidget version: 0.5.16
Apt version: 4.12.0
aptitude linkage:
linux-vdso.so.1 => (0x00007fffa89ff000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
(0x00007fdb8e1e6000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5
(0x00007fdb8dfb6000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007fdb8dd8c000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x00007fdb8db87000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007fdb8d887000)
libept.so.1.0.5.4.12 => /usr/lib/libept.so.1.0.5.4.12 (0x00007fdb8d5e6000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007fdb8d201000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fdb8cfea000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
(0x00007fdb8cd3e000)
libboost_iostreams.so.1.49.0 => /usr/lib/libboost_iostreams.so.1.49.0
(0x00007fdb8cb25000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fdb8c909000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007fdb8c601000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fdb8c37f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fdb8c169000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdb8bde1000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fdb8bbde000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdb8b9da000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007fdb8b7c9000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fdb8b5c4000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fdb8b3bb000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdb8eb70000)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 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 aptitude-common 0.6.8-1
ii libapt-pkg4.12 0.9.7.2
ii libboost-iostreams1.49.0 1.49.0-3.1
ii libc6 2.13-33
ii libcwidget3 0.5.16-3.4
ii libept1.4.12 1.0.9
ii libgcc1 1:4.7.1-2
ii libncursesw5 5.9-10
ii libsigc++-2.0-0c2a 2.2.10-0.2
ii libsqlite3-0 3.7.13-1
ii libstdc++6 4.7.1-2
ii libtinfo5 5.9-10
ii libxapian22 1.2.12-1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages aptitude recommends:
ii apt-xapian-index 0.45
pn aptitude-doc-en | aptitude-doc <none>
pn libparse-debianchangelog-perl <none>
ii sensible-utils 0.0.7
Versions of packages aptitude suggests:
pn debtags <none>
ii tasksel 3.11
-- no debconf information
--- End Message ---
--- Begin Message ---
tags -1 + wontfix
stop
Hi Andrew,
2012-08-05 04:32 Andrew Pimlott:
Excerpts from Andrew Pimlott's message of Sat Aug 04 20:06:36 -0700 2012:
Excerpts from Daniel Hartwig's message of Sat Aug 04 17:53:08 -0700 2012:
> > aptitude does not have the autoremove command that apt-get has. There
> > does not appear to be any way to uninstall automatically installed
> > packages from the command line with aptitude.
>
> Aptitude operates under the principal that you either wish for it to
> manage unused packages, or you do not. The default is the manage
> unused packages but this can be changed by setting
> Aptitude::Delete-Unused "0".
>
> When managing unused packages any action will cause their removal:
Thanks for the explanation. I have had Delete-Unused set to "true"
forever, so I guess I forgot that this is the default behavior.
Wait, I got confused: so Delete-Unused "true" (my setting) is the
default behavior. I definitely don't see automatically installed but
unused packages deleted on "any action". For example, right now, I have
an automatically installed but unused package. If I go into the UI and
press 'g', the unused package is about to be removed. But if run
"aptitude install" on some random package:
% sudo aptitude install -s unclutter
The following NEW packages will be installed:
unclutter
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded
It is not about to remove the unused package. So it's far from true
that "any action" will cause their removal. In my experience, typical
command line use practically never causes automatic removal.
All actions in UI/interactive mode end up in 'g', so the clean-up
happens without you doing anything, although sometimes it is not
immediate (in the same session that you remove the package).
In command line mode, I think that this does not happen when you
explicitly indicate a new package to install (unless there is some
relationship between the packages that you act on, their dependencies,
and the cruft); but it does it if you do "aptitude
install/remove/upgrade/purge" without arguments -- it runs pending
actions, including the removal of cruft. Maybe you never run
"install/remove/purge" without arguments, but the people who use the UI
(where autoremoval happens all the time), I guess that they end up
running "upgrade" without arguments at some point.
In addition, most of the time when you remove/purge/upgrade in the
command line a package explicitly (the actions that can leave cruft
behind), it also removes the unnedeed dependencies right away -- if it
is safe to do so. Sometimes it doesn't happen immediately (there are
many reports asking for this, since there are some hard cases/bugs,
hopefully they will be fixed at some point), but it happens in the next
runs.
In any case, the effect is that maybe the cruft stays in the system for
a little bit longer than strictly necessary, but the cruft packages are
never upgraded, downloaded or anything -- they are just waiting to be
removed.
So in short, the worst thing that happens typically with this cruft is
that they use some space for some extra while, but that's about it.
Still, your workaround for lack of autoremove holds, so I no longer have
a complaint!
Good.
Since you are happy about this and the "autoremove" feature is not
really needed in aptitude, I am going to close the bug report then.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
