Bug#818712: frontend: "pager" doesn't wait/scroll anymore
Adam Borowski writes: > On Thu, Mar 24, 2016 at 12:03:31AM +0100, Robert Luberda wrote: >> According to the apt-get man page the `-y' option causes it to run >> non-interactively, and apt-listchanges has recently started honouring >> this setting, as requested in bug #687443. That's why it forces the >> "text" frontend and disables confirmation. > > This sounds wrong to me: the option -y is "assume-yes" rather than > "noninteractive". Let me quote the man page: -y, --yes, --assume-yes Automatic yes to prompts; assume "yes" as answer to all prompts and run non-interactively. So it is both "assume-yes" and "non-interactive". However for truly non-interactive upgrades one needs to disable debconf prompts as well, so I guess the value of DEBIAN_FRONTEND environment variable could be checked as well, probably separately to the -y option. > > What about having a setting for apt-listchanges instead of piggybacking on a > mostly unrelated apt-get option? It is related, see https://bugs.debian.org/687443. However I can add an option like --ignore-apt-assume to disable this behaviour. Regards, robert
Bug#818712: frontend: "pager" doesn't wait/scroll anymore
On Thu, Mar 24, 2016 at 12:03:31AM +0100, Robert Luberda wrote: > Adam Borowski writes: > >> If not, what tool and with what options do you run to perform upgrades? > > > > apt-get -y dist-upgrade > > > According to the apt-get man page the `-y' option causes it to run > non-interactively, and apt-listchanges has recently started honouring > this setting, as requested in bug #687443. That's why it forces the > "text" frontend and disables confirmation. This sounds wrong to me: the option -y is "assume-yes" rather than "noninteractive". Thus, I believe that if someone wants apt-listchanges to somehow ignore explicitely set frontend, it should be a distinct option from commonly used -y. > Is this explanation OK to you, may I close the bug report? What about having a setting for apt-listchanges instead of piggybacking on a mostly unrelated apt-get option? As of 2.86, there's no way to assume-yes on apt while having apt-listchanges obey the frontend. -- A tit a day keeps the vet away.
Bug#818712: frontend: "pager" doesn't wait/scroll anymore
Adam Borowski writes: >> If not, what tool and with what options do you run to perform upgrades? > > apt-get -y dist-upgrade > According to the apt-get man page the `-y' option causes it to run non-interactively, and apt-listchanges has recently started honouring this setting, as requested in bug #687443. That's why it forces the "text" frontend and disables confirmation. Is this explanation OK to you, may I close the bug report? Regards, robert
Bug#818712: frontend: "pager" doesn't wait/scroll anymore
On Sun, Mar 20, 2016 at 12:54:15AM +0100, Robert Luberda wrote: > Adam Borowski writes: > > Since the last upload, apt-listchanges just blasts all new changelog entries > > to the terminal instead of feeding them to a pager. > > Do you use the -y or -q (or --assume-yes or --quiet) option of > apt-get/aptitude? > If not, what tool and with what options do you run to perform upgrades? apt-get -y dist-upgrade -- A tit a day keeps the vet away.
Bug#818712: frontend: "pager" doesn't wait/scroll anymore
Adam Borowski writes: Hi > Since the last upload, apt-listchanges just blasts all new changelog entries > to the terminal instead of feeding them to a pager. Do you use the -y or -q (or --assume-yes or --quiet) option of apt-get/aptitude? If not, what tool and with what options do you run to perform upgrades? Thanks, robert
Bug#818712: frontend: "pager" doesn't wait/scroll anymore
Package: apt-listchanges Version: 2.86 Severity: normal Hi! Since the last upload, apt-listchanges just blasts all new changelog entries to the terminal instead of feeding them to a pager. If none of newly upgraded packages uses debconf or something full-screen and the amount of changes is smaller than your scrollback length that output might still be present in the scrollback, but that doesn't allow reading them beforehand. I guess this is what "text" does which is a distinct option than "pager", and not what I configured. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.5-x32 (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages apt-listchanges depends on: ii apt1.2.7 ii debconf [debconf-2.0] 1.5.59 ii debianutils4.7 ii python-apt 1.1.0~beta2 pn python:any ii ucf3.0036 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii chromium [www-browser] 49.0.2623.87-1 ii elinks [www-browser] 0.12~pre6-11+b2 ii exim4-daemon-light [mail-transport-agent]4.86.2-2 ii firefox [www-browser]45.0.1-1 ii lxterminal [x-terminal-emulator] 0.2.0-1 pn python-glade2 ii python-gtk2 2.24.0-4 ii rxvt-unicode-256color [x-terminal-emulator] 9.21-1+b1 ii xfce4-terminal [x-terminal-emulator] 0.6.3-2 ii xterm [x-terminal-emulator] 324-1 -- debconf information: * apt-listchanges/save-seen: true * apt-listchanges/email-address: * apt-listchanges/which: both * apt-listchanges/confirm: false * apt-listchanges/frontend: pager
