Your message dated Sun, 1 Jul 2012 08:04:37 +0800
with message-id
<can3vercdugqx7_fy9rhevcda_nqccr3a0gk0e_jncyyhjdh...@mail.gmail.com>
and subject line Re: Bug#599364: aptitude: combining ?narrow and ?archive does
not work as expected
has caused the Debian Bug report #599364,
regarding aptitude: combining ?narrow and ?archive does not work as expected
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.)
--
599364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599364
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.3-3.1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When I use a search expression like:
aptitude search '?narrow(?installed,?archive(unstable))'
I would expect to match only packages that have one version that is both
installed and in unstable.
(At least if I understood the documentation correctly)
Instead what I get is the same as:
aptitude search '?and(?installed,?archive(unstable))'
Strangely this bug does not exist for experimental or testing, i.e.:
aptitude search '?and(?installed,?archive(testing))'
did what I expected.
- -- Package-specific info:
aptitude 0.6.3 compiled at Aug 26 2010 20:10:19
Compiler: g++ 4.4.5 20100816 (prerelease)
Compiled against:
apt version 4.10.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.10.1
linux-gate.so.1 => (0xb785b000)
libapt-pkg.so.4.10 => /usr/lib/libapt-pkg.so.4.10 (0xb774a000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7704000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb76fd000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0xb763d000)
libept.so.1 => /usr/lib/libept.so.1 (0xb75ec000)
libxapian.so.22 => /usr/lib/sse2/libxapian.so.22 (0xb7411000)
libz.so.1 => /usr/lib/libz.so.1 (0xb73fd000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7372000)
libboost_iostreams.so.1.42.0 => /usr/lib/libboost_iostreams.so.1.42.0
(0xb7359000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7340000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb724b000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7225000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7207000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb70c0000)
libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb70bc000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb70b8000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb70b4000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb70a3000)
librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb7099000)
/lib/ld-linux.so.2 (0xb785c000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
- -- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg4.10] 0.8.5 Advanced front-end for dpkg
ii libboost-iostreams1.42. 1.42.0-4 Boost.Iostreams Library
ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib
ii libcwidget3 0.5.16-3 high-level terminal interface libr
ii libept1 1.0.3+b1 High-level library for managing De
ii libgcc1 1:4.4.4-8 GCC support library
ii libncursesw5 5.7+20100313-4 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.7.2-1 SQLite 3 shared library
ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3
ii libxapian22 1.2.3-2 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.38 maintenance tools for a Xapian ind
pn aptitude-doc-en | aptitude-do <none> (no description available)
pn libparse-debianchangelog-perl <none> (no description available)
ii sensible-utils 0.0.4 Utilities for sensible alternative
Versions of packages aptitude suggests:
pn debtags <none> (no description available)
ii tasksel 2.82 Tool for selecting tasks for insta
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkys8t8ACgkQ5/YQEZwskCAS9QCeNX5P7YJL/BpA0xGKq7hpq4Eb
jXgAoIfDwDZIljTE24jVybZmzsmsm9f8
=faO0
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Thanks for the quick response.
On 1 July 2012 04:58, Michael Maurer <[email protected]> wrote:
> In my naïveté I think I assumed then that "aptitude search
> '?narrow(?installed,?archive(unstable))'" would show packages that are
> installed from
> the unstable repositories.
> If I understand the documentation correctly now though (and feel free to
> correct me if I don't), aptitude does not really track from which
> repositories a given package comes from, it only tracks versions.
>
> That is installing version x.y.z of a given package from the
> testing repositories yields the same state, as far as aptitude
> is concerned, as installing version x.y.z of the same package
> from the unstable repositories.(assuming here that the version
> of our package is the same in testing and unstable)
Indeed. That is because x.y.z is (in theory) no different whether it
came from testing, unstable, or some third party archive.
Further, ?archive relates only to versions currently available in the
given archive, not whether a particular package has been installed
from there.
I will see what, if anything, should be done about the documentation.
One thing I do not want to do is add a bunch of verbose explanations
of the various nuanced implications, which really doesn't aide general
comprehension. To this end, I think the current documentation is ok:
Matches package versions which are available from an archive
that matches the regular expression ARCHIVE. For instance,
“?archive(testing)” matches any package available from the
testing archive.
Regards
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
