Package: aptitude
Version: 0.4.4-1
Severity: normal

I had the following:

Press return to continue.

Uncaught exception: 
../../../src/generic/problemresolver/problemresolver.h:2216: 
generic_problem_resolver<PackageUniverse>::generic_problem_resolver(int, 
int, int, int, unsigned int, int, const PackageUniverse&) [with 
PackageUniverse = aptitude_universe]: Assertion 
"bd.broken_under(solution::root_node(initial_broken, universe, 
weights))" failed.
victoria:/home/amarsh04# aptitude -u
Uncaught exception: 
../../../src/generic/problemresolver/problemresolver.h:2216: 
generic_problem_resolver<PackageUniverse>::generic_problem_resolver(int, 
int, int, int, unsigned int, int, const PackageUniverse&) [with 
PackageUniverse = aptitude_universe]: Assertion 
"bd.broken_under(solution::root_node(initial_broken, universe, 
weights))" failed.
victoria:/home/amarsh04#

after doing an update. I had previously had a power failure while 
aptitude was running but sitting doing nothing, and had deleted 
/var/cache/apt/*.bin and re-run aptitude -u

Is there any other way to get aptitude into a consistent state that 
won't have uncaught exceptions?

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3. 0.6.46.3    Advanced front-end for dpkg
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1                      1:4.1.1-20  GCC support library
ii  libncursesw5                 5.5-5       Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a           2.0.17-2    type-safe Signal Framework for C++
ii  libstdc++6                   4.1.1-20    The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc 0.4.4-1    English manual for aptitude, a ter

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to