Your message dated Wed, 9 Jan 2013 10:24:19 +0800
with message-id 
<can3vere_qj0bhx_bdowm-712-50xvvtwbgq1yzw9z3m5kzb...@mail.gmail.com>
and subject line Re: [Aptitude-devel] Bug#402454: aptitude: ~O definition and 
behaviour
has caused the Debian Bug report #697735,
regarding aptitude: ~O should not match any virtual package at least
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.)


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

Although documentation say:
|~Oorigin
|
|    Matches package versions whose origin matches the regular expression
|    origin. For instance, “!~Odebian” will find any unofficial packages
|    on your system (packages not from the Debian archive). 

it seems it matches all packages which can be found in the active
downloadeded package list.

Thus “!~Odebian” will also find virtual packages and obsolete packages which
is no longer found in the origins when used along aptitude search.

I would suggest following instead:
|~Oorigin
|
|    Matches non-virtual package versions whose origin can be traced to
|    the regular expression origin using active /etc/apt/sources.list.
|    “!~v!~Odebian” will find non-virtual package versions which can not
|    trace their origin to debian using active /etc/apt/sources.list on
|    your system (packages not from the active Debian archive).
|
-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3. 0.6.46.4    Advanced front-end for dpkg
ii  libc6                        2.3.6.ds1-9 GNU C Library: Shared libraries
ii  libgcc1                      1:4.1.1-20  GCC support library
ii  libncursesw5                 5.5-5       Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a           2.0.17-2    type-safe Signal Framework for C++
ii  libstdc++6                   4.1.1-20    The GNU Standard C++ Library v3

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

-- no debconf information

-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
        Osamu Aoki <[email protected]>  Yokohama Japan, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and http://people.debian.org/~osamu
 `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract



--- End Message ---
--- Begin Message ---
On 9 January 2013 09:43, Axel Beckert <[email protected]> wrote:
>> I would suggest following instead:
>> |~Oorigin
>> |
>> |    Matches non-virtual package versions whose origin can be traced to
>> |    the regular expression origin using active /etc/apt/sources.list.
>
> I'll take that as suggestions for a behaviour change. I clone the bug
> accordingly, because the "non-virtual" would be wrong if it should
> document the current state.

This is the current behaviour and implied by the current description:

> Matches package /versions/ whose origin matches the regular
> expression origin.

Virtual packages have no /version/ and never match an ?origin term.
They are not specially avoided and it would be misleading to
mention “matches non-virtual package …” explicitly in the definition.

Note that mentioning the specific implications of virtual vs. real
packages at every search term where they are relevant would make
the documentation terribly verbose.  It is best to rely on precise
text and the implication of terms such as “package versions”, though
I believe there may be room for a more general discussion of
virtual vs. real packages earlier in the text, to clarify these terms.

Regards

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

Reply via email to