[
https://issues.apache.org/jira/browse/MESOS-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591578#comment-15591578
]
Till Toenshoff commented on MESOS-6425:
---------------------------------------
The most practical but maybe not cleanest way of fixing this for me is moving
the include of {{colors.sh}} above the {{set -e}} of the hosting script.
> Release scripts fail due to missing BLINK capability.
> -----------------------------------------------------
>
> Key: MESOS-6425
> URL: https://issues.apache.org/jira/browse/MESOS-6425
> Project: Mesos
> Issue Type: Bug
> Reporter: Till Toenshoff
>
> Our release-scripts {{support/tag.sh}} & {{support/vote.sh}} both fail
> entirely due to their way of initializing the terminal.
> Specifically the included {{support/colors.sh}} script's line:
> {noformat}
> BLINK=$(tput blink)
> {noformat}
> When changing the initializing to allow for better debugging {{set -e -x}}
> the resulting trace makes the problem apparent:
> {noformat}
> $ ./support/tag.sh 1.1.0 2
> ++ dirname ./support/tag.sh
> + . ./support/atexit.sh
> ++ declare -a __atexit_cmds
> ++ dirname ./support/tag.sh
> + . ./support/colors.sh
> ++ test -t 1
> +++ tput colors
> ++ NUM_COLORS=8
> ++ test -n 8
> ++ test 8 -ge 8
> +++ tput sgr0
> ++ NORMAL=''
> +++ tput bold
> ++ BOLD=''
> +++ tput smul
> ++ UNDERLINE=''
> +++ tput smso
> ++ REVERSE=''
> +++ tput blink
> ++ BLINK=
> {noformat}
> My terminal (iTerm2 with xterm-color256) apparently does not support blinking
> this way.
> {noformat}
> $ tput blink
> $ echo $?
> 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
