[jira] [Commented] (CLOUDSTACK-6123) package.sh fails when env var GREP=--color=always

["John Kinsella (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902620#comment-13902620 ] 

John Kinsella commented on CLOUDSTACK-6123:
-------------------------------------------

The fix for this is a one-liner so I'll commit it, but I suspect this probably not the only place in the code where grep could break like this. So larger question is if this is a ACS problem, or just user problem...

> package.sh fails when env var GREP=--color=always
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-6123
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6123
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Packaging
>    Affects Versions: 4.2.1, 4.3.0, 4.4.0
>         Environment: CentOS 6.4
> Shell environment variable GREP="--color=always"
>            Reporter: John Kinsella
>            Assignee: John Kinsella
>            Priority: Minor
>
> When attempting to build CloudStack RPMs on a system where the user's shell environment is setting grep's colors to always on via the GREP environment variable, 
> $ ./package.sh
> 4.2.1-SNAPSHOT
> error: line 37: Illegal char in: Version:   4.2.1
> Looking at the source directory and tarball built for the RPM build process, the issue becomes more clear:
> $ ls -l dist/rpmbuild/SOURCES/
> total 533172
> drwx------. 32 build build      4096 Feb 15 17:54 cloudstack-?[01;31m?[K4.?[m?[K2.1-SNAPSHOT
> -rw-------.  1 build build 545959884 Feb 15 18:45 cloudstack-?[01;31m?[K4.?[m?[K2.1-SNAPSHOT.tgz



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)