Your message dated Fri, 18 Sep 2015 20:07:51 +0100
with message-id <[email protected]>
and subject line Re: aptitude: Impossible update (I think that aptitude can't
find dependencys)
has caused the Debian Bug report #588665,
regarding Impossible update (I think that aptitude can't find dependencys)
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.)
--
588665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588665
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.1.5-3
Severity: important
When I run "aptitude update" and after "aptitude safe-upgrade" I get this line:
(I translate it by myself, so maybe something is not exactly what you will see
on your aptitude)
"Resolving dependencys...
Open: 26168; Close: 28933; Delayed: 22045; Conflict: 17"
I wait a lot of time, the numbers above changes but never go ahead, so is
impossible update my system.
This problem happening when I delayed to update my Debian (I don't use this
laptop all day, so sometimes I delay 10 days to update it, so I think that I
have a lot of packages to update and aptitude can't manager all this updates).
-- Package-specific info:
aptitude 0.6.1.5 compiled at Mar 12 2010 09:52:06
Compiler: g++ 4.4.3
Compiled against:
apt version 4.8.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.8.0
linux-gate.so.1 => (0xb7f6b000)
libapt-pkg-libc6.9-6.so.4.8 => /usr/lib/libapt-pkg-libc6.9-6.so.4.8
(0xb7e92000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0xb7e4c000)
liblog4cxx.so.10 => /usr/lib/liblog4cxx.so.10 (0xb7ca5000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb7c9f000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0xb7bdf000)
libept.so.0 => /usr/lib/libept.so.0 (0xb7b6c000)
libxapian.so.15 => /usr/lib/libxapian.so.15 (0xb7a1c000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7a07000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb7983000)
libboost_iostreams.so.1.40.0 => /usr/lib/libboost_iostreams.so.1.40.0
(0xb7978000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb795f000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb786a000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7843000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7825000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb76de000)
libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb76da000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb76d6000)
libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0xb76b5000)
libdb-4.8.so => /usr/lib/libdb-4.8.so (0xb754f000)
libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0xb7521000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb7510000)
librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb7507000)
/lib/ld-linux.so.2 (0xb7f6c000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb7502000)
libcrypt.so.1 => /lib/i686/cmov/libcrypt.so.1 (0xb74d0000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb74aa000)
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: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.9 0.7.25.3 Advanced front-end for dpkg
ii libboost-iostreams1.40. 1.40.0-6+b1 Boost.Iostreams Library
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libcwidget3 0.5.16-3 high-level terminal interface libr
ii libept0 0.5.30 High-level library for managing De
ii libgcc1 1:4.4.4-6 GCC support library
ii liblog4cxx10 0.10.0-1.1 A logging library for C++
ii libncursesw5 5.7+20100313-2 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.6.23.1-4 SQLite 3 shared library
ii libstdc++6 4.4.4-6 The GNU Standard C++ Library v3
ii libxapian15 1.0.20-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.81 Tool for selecting tasks for insta
-- no debconf information
--- End Message ---
--- Begin Message ---
2014-02-07 11:30 To [email protected]:
Control: tags -1 + moreinfo
Hi,
It is unclear if this is because of an infinite loop, or because for
example the machine starts using swap memory and things slow down
significantly after some point, or perhaps because it tries very hard
to work out how to upgrade without removing packages (which is the
mode of operation of "safe-upgrade").
Does this still happen in your system, and if yes with which versions
of aptitude?
Does it happen the same when you do "full-upgrade" (be warned that it
might be more disruptive changes than "safe-upgrade", as the name
implies)?
From the manual page:
safe-upgrade
[...]
It is sometimes necessary to remove one package in order to
upgrade another; this command is not able to upgrade packages in such
situations. Use the full-upgrade command to upgrade as many packages
as possible.
full-upgrade
Upgrades installed packages to their most recent version,
removing or installing packages as necessary. This command is less
conservative than safe-upgrade and thus more likely to perform
unwanted actions. However, it is capable of upgrading packages that
safe-upgrade cannot upgrade.
You can perhaps also try partial upgrades to alleviate the situation:
If no <package>s are listed on the command line, aptitude
will attempt to upgrade every package that can be upgraded. Otherwise,
aptitude will attempt to upgrade only the packages which it is
instructed to upgrade. The <package>s can be extended with suffixes in
the same manner as arguments to aptitude install, so you can also give
additional instructions to aptitude here; for instance, aptitude
safe-upgrade bash dash- will attempt to upgrade the bash package and
remove the dash package.
I am going to close this bug report, because it is 5 years old and has
been marked for 1.5 years as more info, with no more info provided
(understandably, after such long time), and mainly because with the
information provided there is not much that can be done about it to try
to track the problem.
There are other cases which look similar, like #632125 -- there the
problem it's worse because it implies at least waiting for 10h, while in
this case is unknown; and that bug report at least lists the
repositories configured in the system.
This report could be merged with the other, but I am not 100% sure if
it's the same issue, and even if it's the same issue the reporter is
unavailable to reply, and looking at a merged bug report which does not
provide more insight into the situation is a waste of time rather than a
help to fix the actual issue.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
