Package: aptitude Version: 0.4.1-1.1 Severity: normal I love the new feature by which when a package is broken, aptitude offers a choice of ways to resolve the problem. But today I am upgrading a machine that hasn't been touched for months, and with 400 new packages, if I type 'U', aptitude runs like crazy until it has a process image of over 600MB, at which point it starts thrashing (I have 512MB RAM). It's probably hard to test this, but if there's a quadratic algorithm lurking somewhere, it might be the culprit.
Norman -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-6-3.1 0.6.44.2 Advanced front-end for dpkg ii libc6 2.3.6-13 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-4 GCC support library ii libncursesw5 5.5-2 Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.16-3 type-safe Signal Framework for C++ ii libstdc++6 4.1.0-4 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-do <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
