Your message dated Tue, 29 Sep 2015 00:13:48 +0100
with message-id <[email protected]>
and subject line Re: Bug#579073: add an option that tells aptitude to never
_clear_ the A (automatically installed) flag
has caused the Debian Bug report #579073,
regarding add an option that tells aptitude to never _clear_ the A
(automatically installed) flag
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.)
--
579073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579073
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.2.1-2
Severity: wishlist
Hi.
It would be really nice to have a config option which tells
aptitude to never _clear_ the A flag of packages.
I mean even if there are no packages which depend/recommend/suggest/etc.
the respective package.
It may of course _set_ the flag.
The reason is that it's often handy to manually mark packages with
the A flag which are not depended/recommended/suggested/etc. but still
should have the A flag.
E.g. packages like m4-doc which are not depended/recommended/suggested/etc.
by m4 but I still like to have it at with most other packages, where
the main package suggests the doc package.
If I later decide to get rid of unneeded packages, I'll see m4-doc,
remember why I set the A flag, and decide to delete it (if I e.g. deleted
m4 in the meantime).
Thanks,
Chris.
-- Package-specific info:
aptitude 0.6.2.1 compiled at Apr 23 2010 14:34:56
Compiler: g++ 4.4.3
Compiled against:
apt version 4.8.0
NCurses version 5.7
libsigc++ version: 2.2.4.2
Ept support enabled.
Gtk+ support disabled.
Current library versions:
NCurses version: ncurses 5.7.20100313
cwidget version: 0.5.16
Apt version: 4.8.0
linux-vdso.so.1 => (0x00007fffc81b4000)
libapt-pkg-libc6.9-6.so.4.8 => /usr/lib/libapt-pkg-libc6.9-6.so.4.8
(0x00007fa6f1189000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007fa6f0f36000)
liblog4cxx.so.10 => /usr/lib/liblog4cxx.so.10 (0x00007fa6f0b48000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007fa6f0943000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007fa6f0677000)
libept.so.0 => /usr/lib/libept.so.0 (0x00007fa6f03ff000)
libxapian.so.15 => /usr/lib/libxapian.so.15 (0x00007fa6f00ac000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007fa6efe95000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007fa6efc04000)
libboost_iostreams.so.1.42.0 => /usr/lib/libboost_iostreams.so.1.42.0
(0x00007fa6ef9e9000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fa6ef7cd000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fa6ef4b8000)
libm.so.6 => /lib/libm.so.6 (0x00007fa6ef236000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fa6ef020000)
libc.so.6 => /lib/libc.so.6 (0x00007fa6eeccb000)
libutil.so.1 => /lib/libutil.so.1 (0x00007fa6eeac8000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fa6ee8c4000)
libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0x00007fa6ee6a0000)
libdb-4.8.so => /usr/lib/libdb-4.8.so (0x00007fa6ee326000)
libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0x00007fa6ee0ee000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x00007fa6ededd000)
librt.so.1 => /lib/librt.so.1 (0x00007fa6edcd5000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa6f146c000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007fa6edad0000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fa6ed899000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007fa6ed671000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.9 0.7.25.3 Advanced front-end for dpkg
ii libboost-iostreams1.42. 1.42.0-3 Boost.Iostreams Library
ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib
ii libcwidget3 0.5.16-3 high-level terminal interface libr
ii libept0 0.5.30 High-level library for managing De
ii libgcc1 1:4.4.3-9 GCC support library
ii liblog4cxx10 0.10.0-1.1 A logging library for C++
ii libncursesw5 5.7+20100313-2 shared libraries for terminal hand
ii libsigc++-2.0-0c2a 2.2.4.2-1 type-safe Signal Framework for C++
ii libsqlite3-0 3.6.23.1-1 SQLite 3 shared library
ii libstdc++6 4.4.3-9 The GNU Standard C++ Library v3
ii libxapian15 1.0.19-1 Search engine library
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages aptitude recommends:
ii apt-xapian-index 0.30 maintenance tools for a Xapian ind
ii aptitude-doc-en [aptitude-doc 0.6.2.1-2 English manual for aptitude, a ter
ii libparse-debianchangelog-perl 1.1.1-2 parse Debian changelogs and output
ii sensible-utils 0.0.4 Utilities for sensible alternative
Versions of packages aptitude suggests:
ii debtags 1.7.9+b2 Enables support for package tags
ii tasksel 2.81 Tool for selecting tasks for insta
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 579073 + wontfix
stop
Hi Christoph,
2010-06-30 22:37 Christoph Anton Mitterer:
On Tue, 2010-04-27 at 07:03 -0700, Daniel Burrows wrote:
I really don't understand what you're asking for. The "A flag" says
"remove this package when nothing uses it". You want to have packages
that aren't installed and that nothing depends on, but are still
automatically installed? (automatically installed for what?)
Well... *G* yes...
The thing is the following:
There are many packages, which I do not install for their own,... for
example m4-doc.... I just install it, if I install m4 itself, too.
Now unfortunately many of such packages are neither recommended nor
suggested by their "parents".
The same holds also true e.g. for many -dbg packages.
I'd "manually" install some libfoo-dev package,... and would like to
have the -dbg (and perhaps also -doc) package, too.
What I now do is:
- I deactivated the auto-removal feature
- Set the A flag on such packages manually
- From time to time,... go over all packages, that aptitude _would_
delete (because of the A flag/etc.) and delete only those which I really
want to get rid of.
Of course I could simply not mark such -doc, -dbg or similar packages
with "A",... but this would mean that I probably forget to delete them,
as I never look over them again.
Better explained? :)
I think that this is a good example where user-tags are useful.
You can mark your packages with tags such as "review-needed" and
"needed-by-${program}", then search for them on a
${program}-by-${program} basis or as a whole, and decide whether you can
remove them or not.
More info in man page, and search patterns.
The original request, repurposing automatically installed packages
feature (quite a central feature in aptitude) for this use-case, and
adding extra config options/funcionality to disable the central
functionality, is not a good idea. So marking as +wontfix and closing.
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
