Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#5899 - post install messages should appear last
Attached to Project:
Pacman
Opened by héctor (hacosta) - Sunday, 26 November 2006, 18:27 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 08 December 2006, 23:06 GMT
Opened by héctor (hacosta) - Sunday, 26 November 2006, 18:27 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 08 December 2006, 23:06 GMT
|
Detailsi think pacman should output post install messages after all packages are done updating for example
pacman -Syu upgrading nvidia... done. upgrading X... done. upgrading Y... done. upgrading Z... done. ------------------------------- By using this package you accept the NVIDIA license, blah blah blah notice that i dont show this message until all packages are done. blah blah blah |
This task depends upon
Closed by Aaron Griffin (phrakture)
Friday, 26 January 2007, 16:38 GMT
Reason for closing: Fixed
Additional comments about closing: Install messages will remain in the order they are in, BUT are logged to pacman.log (in CVS)
Friday, 26 January 2007, 16:38 GMT
Reason for closing: Fixed
Additional comments about closing: Install messages will remain in the order they are in, BUT are logged to pacman.log (in CVS)
If you have a large number of Packages to update and you leave it unattended,
it is possible to miss the messages because they have gone off the screen.
A message at the end of updating suggesting that you read the file would be good.
Personally, I think it's important to show upgrade messages _as they happen_ and not after, as sometimes these messages include application output (i.e. scrollkeeper)
IMO yes.
> Personally, I think it's important to show upgrade messages _as they happen_ and not after
Agree. There's no need to show them after because they will be logged to pacman.log anyway.
Users just must learn this feature (but this will be the case with pacman2->pacman3 switch anyway).