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#1105 - pacman 2.8-1 No colored Messages
Attached to Project:
Pacman
Opened by Albert Steiner (alibaba) - Saturday, 10 July 2004, 19:48 GMT
Last edited by Simo Leone (neotuli) - Sunday, 15 October 2006, 17:21 GMT
Opened by Albert Steiner (alibaba) - Saturday, 10 July 2004, 19:48 GMT
Last edited by Simo Leone (neotuli) - Sunday, 15 October 2006, 17:21 GMT
|
Detailsif have in my package install scripts colored messages
and calls to the /etc/rc.d/package start stop after update to 2.8-1 never any color will be displayed and the output from stat_fail stat_done looks ::Stopping Package 9G [BUSY] 9G [DONE] the scripts runnig aoutside well, and if i downgrade to pacman 2.7.9-1 all color and stat_ will be correct displayed ? regards albert 
testpkg.tar.gz
(1.4 KiB)
|
This task depends upon
Closed by Aaron Griffin (phrakture)
Thursday, 01 February 2007, 01:55 GMT
Reason for closing: Fixed
Additional comments about closing: Works in CVS
Thursday, 01 February 2007, 01:55 GMT
Reason for closing: Fixed
Additional comments about closing: Works in CVS
The pacman package doesn't provide any scripts that are used by the rc.d scrpits.
i now that the pacman not provide the rc.d srcipts,
but i look at var/run/daemons and if the package is running then
i call /etc/rc.d/package stop but that is not the problem this is
working.
i have a own package and there a install script, which is calling
the /etc/rc.d/package stop if it is running and some colored messages,
the problem seems is about the tty:
pacman 2.7.9 says with the script;
/dev/vc/2
speed 38400 baud; line = 0;
-brkint ixoff -imaxbel
-iexten
pacman 2.8 says with the same:
not a tty
stty: standard input: Invalid argument
and this seems the problem, do you have any idea ?
here is my test install script:
post_install() {
tty
echo
stty
}
post_upgrade() {
post_install $2
}
pre_remove() {
/bin/true
}
post_remove() {
/bin/true
}
op=$1
shift
$op $*
regards albert
I just tried this, yes it is still an issue.
I have attached the dummy package that I used to test it, so you can see for yourself. Basically, the start/stop status line displayed by an /etc/rc.d/blah script called from within an install script of a package; is displayed sort of corrupted.
stty: standard input: Invalid argument
:: Starting Secure Shell Daemon [-9G [BUSY] [-9G [DONE]
it still is a bug.