Your message dated Sun, 6 Dec 2015 22:32:31 +0000
with message-id <[email protected]>
and subject line Re: aptitude dependency display for PreDepends seems to
disregard pin choice
has caused the Debian Bug report #631525,
regarding aptitude dependency display for PreDepends seems to disregard pin
choice
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.)
--
631525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631525
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.3-4
Severity: normal
In testing 500/ unstable 50 mix systm, I saw the following for recent
libpam-modules:
--------------
i --\ libpam-modules 1.1.3-1 1.1.3-1
Description: Pluggable Authentication Modules for PAM
This package completes the set of modules for PAM. It includes the
pam_unix_*.so module as well as some specialty modules.
Homepage: http://pam.sourceforge.net/
Tags: devel::library, role::shared-lib, security::authentication,
use::configuring
Priority: required
Section: admin
Maintainer: Steve Langasek <[email protected]>
Compressed size: 340 k
Uncompressed size: 995 k
Source Package: pam
--\ PreDepends (6)
--- debconf (>= 0.5) | debconf-2.0
--- libc6 (>= 2.4)
--- libdb5.1
--- libpam-modules-bin (= 1.1.3-2) (UNSATISFIED)
--- libpam0g (>= 1.1.3-2) (UNSATISFIED)
--- libselinux1 (>= 2.0.85)
--\ Conflicts (3)
--- libpam-mkhomedir
--- libpam-motd
--- libpam-umask
--\ Replaces (2)
--- libpam-umask
--- libpam0g-util
--- Package names provided by libpam-modules (3)
--- Packages which depend on libpam-modules (33)
--\ Versions of libpam-modules (2)
i 1.1.3-1
p 1.1.3-2
---------------------------
Since 1.1.3-1 is pin choice, I expected not to see PreDepends for
libpam-modules-bin and libpam0g. After seeing (UNSATISFIED), I thought
system is broken. But reality is not so bad. It is just displaying
bogus PreDepend.
Until suggested version becomes 1.1.3-2 by manual intervention, these
1.1.3-2 dependency is best hidden.
FYI:
$ apt-cache policy libpam-modules
libpam-modules:
Installed: 1.1.3-1
Candidate: 1.1.3-1
Version table:
1.1.3-2 0
50 http://ftp2.jp.debian.org/debian/ sid/main amd64 Packages
*** 1.1.3-1 0
500 http://ftp2.jp.debian.org/debian/ wheezy/main amd64 Packages
100 /var/lib/dpkg/status
-- Package-specific info:
aptitude 0.6.3 compiled at Apr 2 2011 21:33:01
Compiler: g++ 4.5.2
Compiled against:
apt version 4.10.1
NCurses version 5.8
libsigc++ version: 2.2.4.2
Ept support enabled.
Gtk+ support disabled.
Current library versions:
NCurses version: ncurses 5.9.20110404
cwidget version: 0.5.16
Apt version: 4.10.1
linux-vdso.so.1 => (0x00007fff9edd5000)
libapt-pkg.so.4.10 => /usr/lib/libapt-pkg.so.4.10 (0x00007f4762156000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007f4761f03000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007f4761cfd000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007f4761a31000)
libept.so.1 => /usr/lib/libept.so.1 (0x00007f47617d5000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007f47613b6000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f476119f000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f4760f02000)
libboost_iostreams.so.1.42.0 => /usr/lib/libboost_iostreams.so.1.42.0
(0x00007f4760ce9000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f4760acd000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f47607c3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4760540000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f476032a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f475ffa7000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f475fda3000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f475fb9f000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f475f99a000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x00007f475f78a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f475f582000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4762491000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg4.10] 0.8.14.1 Advanced front-end for dpkg
ii libboost-iostreams1.42. 1.42.0-4+b1 Boost.Iostreams Library
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libcwidget3 0.5.16-3 high-level terminal interface libr
ii libept1 1.0.5 High-level library for managing De
ii libgcc1 1:4.6.0-10 GCC support library
ii libncursesw5 5.9-1 shared libraries for terminal hand
ii libsigc++-2.0-0c2a 2.2.9-1 type-safe Signal Framework for C++
ii libsqlite3-0 3.7.6.3-1 SQLite 3 shared library
ii libstdc++6 4.6.0-10 The GNU Standard C++ Library v3
ii libxapian22 1.2.5-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.43 maintenance and search tools for a
ii aptitude-doc-en [aptitude-doc 0.6.3-4 English manual for aptitude, a ter
ii libparse-debianchangelog-perl 1.2.0-1 parse Debian changelogs and output
ii sensible-utils 0.0.6 Utilities for sensible alternative
Versions of packages aptitude suggests:
ii debtags 1.7.11 Enables support for package tags
ii tasksel 2.89 Tool for selecting tasks for insta
-- no debconf information
--- End Message ---
--- Begin Message ---
2011-06-24 17:07 Osamu Aoki:
Package: aptitude
Version: 0.6.3-4
Severity: normal
In testing 500/ unstable 50 mix systm, I saw the following for recent
libpam-modules:
--------------
i --\ libpam-modules 1.1.3-1 1.1.3-1
Description: Pluggable Authentication Modules for PAM
This package completes the set of modules for PAM. It includes the
pam_unix_*.so module as well as some specialty modules.
Homepage: http://pam.sourceforge.net/
Tags: devel::library, role::shared-lib, security::authentication,
use::configuring
Priority: required
Section: admin
Maintainer: Steve Langasek <[email protected]>
Compressed size: 340 k
Uncompressed size: 995 k
Source Package: pam
--\ PreDepends (6)
--- debconf (>= 0.5) | debconf-2.0
--- libc6 (>= 2.4)
--- libdb5.1
--- libpam-modules-bin (= 1.1.3-2) (UNSATISFIED)
--- libpam0g (>= 1.1.3-2) (UNSATISFIED)
--- libselinux1 (>= 2.0.85)
--\ Conflicts (3)
--- libpam-mkhomedir
--- libpam-motd
--- libpam-umask
--\ Replaces (2)
--- libpam-umask
--- libpam0g-util
--- Package names provided by libpam-modules (3)
--- Packages which depend on libpam-modules (33)
--\ Versions of libpam-modules (2)
i 1.1.3-1
p 1.1.3-2
---------------------------
Since 1.1.3-1 is pin choice, I expected not to see PreDepends for
libpam-modules-bin and libpam0g. After seeing (UNSATISFIED), I thought
system is broken. But reality is not so bad. It is just displaying
bogus PreDepend.
Until suggested version becomes 1.1.3-2 by manual intervention, these
1.1.3-2 dependency is best hidden.
FYI:
$ apt-cache policy libpam-modules
libpam-modules:
Installed: 1.1.3-1
Candidate: 1.1.3-1
Version table:
1.1.3-2 0
50 http://ftp2.jp.debian.org/debian/ sid/main amd64 Packages
*** 1.1.3-1 0
500 http://ftp2.jp.debian.org/debian/ wheezy/main amd64 Packages
100 /var/lib/dpkg/status
2012-09-07 16:14 Daniel Hartwig:
Hello
Osamu Aoki <[email protected]> wrote:
In testing 500/ unstable 50 mix systm, I saw the following for recent
libpam-modules:
--------------
i --\ libpam-modules 1.1.3-1 1.1.3-1
^current candidate^
The header line is misleading and shows the current (installed) and
candidate version numbers regardless of which version the other details
are for. There is no indication which version you are actually looking
at. [1]
[1] http://bugs.debian.org/593248
--\ PreDepends (6)
--- libpam-modules-bin (= 1.1.3-2) (UNSATISFIED)
--- libpam0g (>= 1.1.3-2) (UNSATISFIED)
This is the only hint that the details here are for 1.1.3-2.
Since 1.1.3-1 is pin choice, I expected not to see PreDepends for
libpam-modules-bin and libpam0g. After seeing (UNSATISFIED), I thought
system is broken. But reality is not so bad. It is just displaying
bogus PreDepend.
Yes, this is normally what happens. When you select to view the details
of a package in aptitude you get the first version which is either:
- the candidate;
- marked for install; or
- currently installed.
In this case it looks like you are being shown some other version. Most
likely from pressing RET on a version item, such as one of:
--\ Versions of libpam-modules (2)
i 1.1.3-1
p 1.1.3-2
or in the main view, when the final grouping policy is “versions”:
i --\ libpam-modules 1.1.3-7 1.1.3-7.1
i 1.1.3-7 100
p 1.1.3-7.1 500
So, when this happened, do you recall how this screen was opened? Was
it by selecting a particular version?
If you select to view a similar package from the main screen (and not a
specific version of it) are you shown the details for the candidate
version?
Until suggested version becomes 1.1.3-2 by manual intervention, these
1.1.3-2 dependency is best hidden.
I think the current behaviour I mention above is ok. If a user asks to
view a specific version then they should be shown the details for that
version.
As explained in the follow-up e-mail, in principle this is likely the
correct information that should be shown.
After a few years with no follow-ups, it looks to me that this should be
closed -- please reopen if you still have concerns about this issue.
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
