[Aptitude-devel] Bug#820486: I follow aptitude's advice and end up with a broken (B) package

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Tue Apr 26 14:06:48 UTC 2016

Control: tags -1 - moreinfo
Control: close -1

2016-04-23 18:25 積丹尼 Dan Jacobson:
>retitle 820486 be sure CLI shows same amount of info as curses for broken packages
>MAFM> The curses interface says why the package is broken, I am not sure if
>MAFM> cmdline's "why" does the same, but without knowing the source of the
>MAFM> problem not much can be done.
>OK, maybe just be sure we command line users are at no disadvantage vs.
>curses users in terms of how much information is available in this case.

The command line users are not at disadvantage, even if why doesn't show
them (it probably does).  ?broken and similar search patterns can be
used for this.

I just don't have all possible ways to list them on the top of my head.
The users will have to do some work on their own.

Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>

More information about the Aptitude-devel mailing list