Bug#798240: aptitude: Sort resolver's solutions by number of removals

2015-09-07 Thread Michele Alessandrini 
Package: aptitude
Version: 0.6.11-1+b1
Severity: wishlist


When a serious conflict arises with an update, the resolver usually presents 
many solutions with a lot of removed packages,
then you have to browse a lot of solutions to usually find a more acceptable 
one, consisting of keeping
a few packages at the current version, and perhaps removing a few ones.
It would be more convenient if the first solutions presented were the ones with 
the minimum number of packages removed.


-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.11 compiled at Nov  8 2014 13:34:39
Compiler: g++ 4.9.1
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.4.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20150810
  cwidget version: 0.5.17
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x7ffec7deb000)
libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7fc59c3f5000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7fc59c1c5000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7fc59bf9a000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fc59bd94000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7fc59ba7e000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fc59b7b)
libboost_iostreams.so.1.55.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7fc59b598000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7fc59b181000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc59af63000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fc59ac57000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc59a956000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fc59a73f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc59a396000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fc59a193000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc599f8e000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fc599d73000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fc599b63000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fc59993f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fc599737000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fc599531000)
/lib64/ld-linux-x86-64.so.2 (0x56525f74b000)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.11-1
ii  libapt-pkg4.121.0.9.10
ii  libboost-iostreams1.55.0  1.55.0+dfsg-4
ii  libc6 2.19-19
ii  libcwidget3   0.5.17-2
ii  libgcc1   1:5.1.1-14
ii  libncursesw5  6.0+20150810-1
ii  libsigc++-2.0-0c2a2.4.1-1
ii  libsqlite3-0  3.8.11.1-1
ii  libstdc++65.1.1-14
ii  libtinfo5 6.0+20150810-1
ii  libxapian22   1.2.21-1

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-doc  
pn  libparse-debianchangelog-perl   
ii  sensible-utils  0.0.9

Versions of packages aptitude suggests:
pn  apt-xapian-index  
pn  debtags   
ii  tasksel   3.33

-- no debconf information

Bug#798240: [Aptitude-devel] Bug#798240: aptitude: Sort resolver's solutions by number of removals

2015-09-07 Thread Axel Beckert 
Hi,

Michele Alessandrini wrote:
> When a serious conflict arises with an update, the resolver usually
> presents many solutions with a lot of removed packages, then you
> have to browse a lot of solutions to usually find a more acceptable
> one, consisting of keeping a few packages at the current version,
> and perhaps removing a few ones. It would be more convenient if the
> first solutions presented were the ones with the minimum number of
> packages removed.

We suspect that this issue got introduced (or worsened) by some
Multiarch fixes. I currently can't find the according bug report, but
I'm very sure, there is one.

Try setting 'Aptitude::ProblemResolver::Remove-Level "maximum";' in
/etc/apt/apt.conf as a workaround.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE