[Aptitude-devel] Bug#816781: Bug#816781: aptitude: Can not cancel pending upgrade actions

2017-05-29 Thread Cesare Leonardi

On 29/05/2017 11:31, Axel Beckert wrote:

Before you press the corresponding menu entry, but after already
having selected it, aptitude will show the following long description
in the status line:

  Cancel all pending actions from this session

So this menu entry only cancels actions which weren't scheduled in
previous sessions on purpose.


Thank you Axel for the detailed and clear explanation.
I admit i've never noted the string in the status bar...


So maybe we should be a little bit more verbose with the short
description in the menu or maybe even split "Cancel pending actions"
into two separate menu entries:

* Cancel pending actions of this session
* Cancel all pending actions

or similar.


It will be wonderful to have two entries, because "Cancel all pending 
actions" is quite self explanatory, will match the previous behaviour 
and users should not be surprised upgrading from Debian 8 to 9.


But isn't it too late for Stretch?

Anyway, I think that making a note at least in NEWS.Debian could be helpful.

Cesare.

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel


[Aptitude-devel] Bug#816781: Bug#816781: aptitude: Can not cancel pending upgrade actions

2017-05-29 Thread Axel Beckert
Hi,

Cesare Leonardi wrote:
> Steps to reproduce (always reproducible for me):
> - Open the TUI;
> - Press [u] to search for updates;
> - Review the upgradable package list and press [U] to mark them as
>   upgradable;
> - Decide to postpone the real upgrade and exit from aptitude;

This is relevant here.

> - Re-enter the TUI but for some reason you want aptitude forget all
>   pending actions by pressing the corresponding menu entry;
> - Observe that aptitude make some work but doesn't actually forget
>   nothing.

That's expected.

> Note that the same command works as expected if it's given during the
> same session, without exit.

Exactly.

Before you press the corresponding menu entry, but after already
having selected it, aptitude will show the following long description
in the status line:

  Cancel all pending actions from this session

So this menu entry only cancels actions which weren't scheduled in
previous sessions on purpose.

So maybe we should be a little bit more verbose with the short
description in the menu or maybe even split "Cancel pending actions"
into two separate menu entries:

* Cancel pending actions of this session
* Cancel all pending actions

or similar.

For now, what should do what you want is calling "aptitude keep-all"
on the commandline.

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

___
Aptitude-devel mailing list
Aptitude-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel


[Aptitude-devel] Bug#816781: aptitude: Can not cancel pending upgrade actions

2017-05-29 Thread Cesare Leonardi
Package: aptitude
Version: 0.8.7-1
Followup-For: Bug #816781

Since some times I'm hitting the following bug and today I've found the
time to report it to Debian. Even if it's a different use case, I think
it's closely related to this bug, so i'm posting here.

Steps to reproduce (always reproducible for me):
- Open the TUI;
- Press [u] to search for updates;
- Review the upgradable package list and press [U] to mark them as
  upgradable;
- Decide to postpone the real upgrade and exit from aptitude;
- Re-enter the TUI but for some reason you want aptitude forget all
  pending actions by pressing the corresponding menu entry;
- Observe that aptitude make some work but doesn't actually forget
  nothing.

Note that the same command works as expected if it's given during the
same session, without exit.

If I understand correctly, Manuel suggests to use the following
steps to obtain the same practical effect as cancel pending actions:
- With the cursor go on the "Upgradable Packages" tree root.
- Package -> Keep

Is that correct?
But in that case i haven't understood now what the "Cancel pending
actions" command is for.

Cesare.


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

aptitude version information:
aptitude 0.8.7
Compiler: g++ 6.3.0 20170406
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20161126
  cwidget version: 0.5.17
  Apt version: 5.0.1

aptitude linkage:
linux-vdso.so.1 (0x7ffc688a4000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f35fc6a2000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f35fc472000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f35fc248000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f35fc041000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f35fbd44000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f35fba3a000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f35fb822000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f35fb609000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f35fb405000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f35faff1000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f35fadd4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f35faa5)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f35fa74c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f35fa535000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f35fa197000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f35f9f93000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7f35f9d7c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f35f9b6)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f35f995)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f35f972a000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f35f9518000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f35f931)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f35f9109000)
/lib64/ld-linux-x86-64.so.2 (0x55db3ead2000)

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages aptitude depends on:
ii  aptitude-common0.8.7-1
ii  libapt-pkg5.0  1.4.4
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-iostreams1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-10
ii  libcwidget3v5  0.5.17-4+b1
ii  libgcc11:6.3.0-18
ii  libncursesw5   6.0+20161126-1
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libsqlite3-0   3.16.2-3
ii  libstdc++6 6.3.0-18
ii  libtinfo5  6.0+20161126-1
ii  libxapian301.4.3-2

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-12
ii  sensible-utils 0.0.9

Versions of packages aptitude suggests:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  debtags 
ii  tasksel 3.39

-- n