[Aptitude-devel] how to get verbosity in aptitude command-line mode via its configuration file.

shirish शिरीष shirishag75 at gmail.com
Tue Dec 10 07:34:41 GMT 2019

Reply at bottom :-

On 09/12/2019, Axel Beckert <abe at debian.org> wrote:
> Hi shirish,
> shirish शिरीष wrote:
>> While I'm asking the same question at
>> https://unix.stackexchange.com/questions/555993/verbosity-in-aptitude-command-line-mode
>> just for completeness asking the same here too -
> Thanks! I replied there: https://unix.stackexchange.com/a/556303
> TL;DR: I can't reproduce this. For me, there is a difference of one
> additional line—from Debian 8 Jessie up to Debian Sid.
> I though found a related bug while doing so, reported at
> https://bugs.debian.org/946458
> 		Regards, Axel
> --
>  ,''`.  |  Axel Beckert <abe at debian.org>, https://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

Dear Axel,

Thank you. The reason I broached the subject is that sometimes when
something is triggered after upgrading packages, at the very end at
times it takes a long time to know what is happening, I can see the
HDD sensor spinning which tells me some work is going on but no output
on the CLI to tell me what is happening. FWIW, I am subscribed to the
bug :)

          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

More information about the Aptitude-devel mailing list