Your message dated Sat, 12 Sep 2015 18:47:14 +0100
with message-id <[email protected]>
and subject line Re: aptitude: package tagging status?
has caused the Debian Bug report #320096,
regarding aptitude: package tagging status?
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.)
--
320096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320096
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.15.9-3
Severity: wishlist
Hello once more. I see you have a package listing escape code reserved
for tagged packages. I for one would absolutely love the ability to tag
packages and have those tags saved between aptitude uses. Do you still
plan to implement tagging?
Thanks, and I hope I'm not nagging,
Brian
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10portege
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.3-5-3 0.6.38 Advanced front-end for dpkg
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.0-11 GCC support library
ii libncurses5 5.4-8 Shared libraries for terminal hand
ii libsigc++-1.2-5c102 1.2.5-4 type-safe Signal Framework for C++
ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3
Versions of packages aptitude recommends:
ii aptitude-doc-en [aptitude-doc 0.2.15.9-3 English manual for aptitude, a ter
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.4.11
Hello Brian,
2005-07-26 23:43 Brian Kimball:
Package: aptitude
Version: 0.2.15.9-3
Severity: wishlist
Hello once more. I see you have a package listing escape code reserved
for tagged packages. I for one would absolutely love the ability to tag
packages and have those tags saved between aptitude uses. Do you still
plan to implement tagging?
This functionality is present since 0.4.11, released on 2008-03-15, copy
of the relevant parts of the change log below.
Therefore closing the bug, sorry that it was not handled in a more
timely manner.
* aptitude now supports attaching arbitrary strings to packages,
known as "user tags" (to distinguish them from debtags tags). The
following commands will manipulate user tags:
aptitude add-user-tag tag package...
aptitude remove-user-tag tag package...
Each of these commands will add user tags to or remove them from
one or more packages (possibly selected using search expressions).
In addition, all command-line actions that modify package state
now take the following optional arguments:
--add-user-tag TAG
--add-user-tag-to TAG PATTERN
--remove-user-tag TAG
--remove-user-tag-from TAG PATTERN
The variants that take a PATTERN will add tags to or remove tags
from any packages that match the given PATTERN. (e.g.:
"--add-user-tag-to installed-for-build-dep ?action(install)").
The variants that do not take a PATTERN will affect any package
that is being modified (this is equivalent to using the pattern
"?not(?action(keep))").
The ?user-tag(tag) matcher will select packages with a tag
matching the given regular expression. User tags also show up at
the end of package descriptions, next to the list of debtags tags
for a package.
--
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
