[
https://issues.apache.org/jira/browse/BIGTOP-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-788:
------------------------------------
Attachment: 0001-BIGTOP-788.-Oozie-RPM-build-error-due-to-lack-of-usr.patch
Actually, I think the better fix would be to pass the absolute path name to the
install_oozie.sh.
New fix attached. Please let us know if it fixes it on your side and then I can
commit.
> Oozie RPM build error due to lack of
> usr/lib/oozie/{libserver,oozie-server,libext}
> ----------------------------------------------------------------------------------
>
> Key: BIGTOP-788
> URL: https://issues.apache.org/jira/browse/BIGTOP-788
> Project: Bigtop
> Issue Type: Bug
> Components: RPM
> Affects Versions: 0.5.0
> Reporter: Chen-hsiu Huang
> Labels: patch
> Fix For: 0.5.0
>
> Attachments:
> 0001-BIGTOP-788.-Oozie-RPM-build-error-due-to-lack-of-usr.patch,
> BIGTOP-788.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> error: File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/libserver
> error: File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/oozie-server
> error: File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/libext
> Processing files: oozie-client-3.2.0-1
> Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> Requires: /bin/bash /bin/sh bigtop-utils
> Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0
> RPM build errors:
> File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/libserver
> File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/oozie-server
> File not found:
> /home/source/git/hadoop/tm-bigtop/build/oozie/rpm/INSTALL/oozie-3.2.0/usr/lib/oozie/libext
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
