Your message dated Wed, 16 Sep 2015 23:55:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#622715: aptitude does not give any idea which package
is responsible for a library removal
has caused the Debian Bug report #622715,
regarding aptitude does not give any idea which package is responsible for a
library removal
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.)
--
622715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622715
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.3-4
Severity: important
*** Please type your report below this line ***
I have seen this many a time and more so now when I am trying to
upgrade from stable to testing. What happens is many a time there is a
library which is being removed and there is no hint as to which
package is the one responsible for the library being removed.
Sometimes you do get hints when the package names are similar, but
many a times not. Also sometimes the package names may be similar but
they may be a part of a series of packages and its hard to figure out
which is the one responsible. I do not claim to know the answer but
one way perhaps could be
say if library 'stable' is being removed due to changes in package
'sid' it could show as
library 'stable being removed:'sid'
This would atleast indicate which package is the one responsible and
then one can download the changelog and see what changes have made
library 'stable' reduntant. Maybe fixed upstream, or merged within
package 'sid' or no longer needed whatever the reason, atleast I know
this is due to package 'sid' .
-- 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 => (0x00007fff3d9c0000)
libapt-pkg.so.4.10 => /usr/lib/libapt-pkg.so.4.10 (0x00007fbd0594c000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007fbd056f9000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007fbd054f3000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007fbd05227000)
libept.so.1 => /usr/lib/libept.so.1 (0x00007fbd04fcb000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007fbd04bac000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007fbd04995000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007fbd046fa000)
libboost_iostreams.so.1.42.0 => /usr/lib/libboost_iostreams.so.1.42.0
(0x00007fbd044de000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fbd042c2000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fbd03fb9000)
libm.so.6 => /lib/libm.so.6 (0x00007fbd03d36000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fbd03b20000)
libc.so.6 => /lib/libc.so.6 (0x00007fbd037be000)
libutil.so.1 => /lib/libutil.so.1 (0x00007fbd035ba000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fbd033b6000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007fbd031b1000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x00007fbd02fa1000)
librt.so.1 => /lib/librt.so.1 (0x00007fbd02d99000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbd05c8c000)
Terminal: xterm
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38.2+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg4.10] 0.8.13.2 Advanced front-end for dpkg
ii libboost-iostreams1.42. 1.42.0-4 Boost.Iostreams Library
ii libc6 2.11.2-13 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-2 GCC support library
ii libncursesw5 5.9-1 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.5-1 SQLite 3 shared library
ii libstdc++6 4.6.0-2 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.41 maintenance and search tools for a
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.89 Tool for selecting tasks for insta
-- no debconf information
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
--- End Message ---
--- Begin Message ---
tags 622715 + moreinfo
stop
2011-05-14 21:06 Daniel Burrows:
On Thu, Apr 14, 2011 at 11:40:22AM +0530, shirish शिरीष <[email protected]>
was heard to say:
*** Please type your report below this line ***
I have seen this many a time and more so now when I am trying to
upgrade from stable to testing. What happens is many a time there is a
library which is being removed and there is no hint as to which
package is the one responsible for the library being removed.
Sometimes you do get hints when the package names are similar, but
many a times not. Also sometimes the package names may be similar but
they may be a part of a series of packages and its hard to figure out
which is the one responsible. I do not claim to know the answer but
one way perhaps could be
say if library 'stable' is being removed due to changes in package
'sid' it could show as
library 'stable being removed:'sid'
This would atleast indicate which package is the one responsible and
then one can download the changelog and see what changes have made
library 'stable' reduntant. Maybe fixed upstream, or merged within
package 'sid' or no longer needed whatever the reason, atleast I know
this is due to package 'sid' .
Assuming you're working at the command-line, does it help if you pass
"-W"?
4 years old bug, asked for more info within the same day and none
provided, so closing now.
There are multiple reasons why packages might be removed in this way.
The most common one is probably because it's "automatically" installed
(pulled-in by a package that the user or the system does want
installed), the package name of the library changes (or is removed from
Debian altogether), and it's removed upon upgrades.
If it's removed for this reason, aptitude tells about this in both the
curses interface and in the command line.
If it is removed because of conflicts with other packages, aptitude also
has ways to see that in curses; in the command line with the option
suggested by Daniel Burrows, and others.
There is abundant documentation about all this.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
