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

Travis Crawford commented on HCATALOG-429:
------------------------------------------

I just downloaded {{hcatalog-src-0.4.0-incubating.tar.gz}} and confirmed this 
is an issue. Thanks for letting us know!

It looks like 0.4.0 puts {{NOTICE.txt}} in the root, but it was later moved to 
{{share/doc/hcatalog/NOTICE.txt}}.

Both in 0.4.0 and trunk, {{hcat_server_install.sh}} references the notice file 
in a subdirectory.

Would moving the scripts & docs files to match what's in trunk and the 
documentation be too invasive for a release branch? If not I think that's 
preferable since there's never a good time to move stuff, so might as well get 
it over with.

Thoughts?
                
> scripts/hcatalog_server_install.sh references 'share/doc/hcatalog/NOTICE.txt' 
> instead of NOTICE.txt
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HCATALOG-429
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-429
>             Project: HCatalog
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.4
>         Environment: Amazon EMR
>            Reporter: Russell Jurney
>            Priority: Blocker
>              Labels: blog, hcatalog, installation, post, problems
>             Fix For: 0.4.1
>
>         Attachments: HCATALOG-429.patch
>
>
> Installing HCatalog from 
> http://incubator.apache.org/hcatalog/docs/r0.4.0/install.html
> hadoop@ip-10-4-115-51:~/hcatalog-src-0.4.0-incubating$ 
> ./scripts/hcat_server_install.sh -r root -d hive_081 -h $HADOOP_HOME -p 9933
> head: cannot open `share/doc/hcatalog/NOTICE.txt' for reading: No such file 
> or directory
> Reading the script shows that the problem is: dir_check=`head -1 
> share/doc/hcatalog/NOTICE.txt`
> Submitting patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to