[
https://issues.apache.org/jira/browse/OOZIE-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505022#comment-13505022
]
jdnurmi commented on OOZIE-1092:
--------------------------------
Great to know, though it looks like the package build suffers from the same
underlying issue:
dpkg -c oozie_3.3.0.27-1_all.deb|grep war; echo $?
1
and the build output looks similar:
http://bigtop01.cloudera.org:8080/job/Bigtop-git/27/label=lucid/console
...
16:28:29 + jar xf ./oozie.war
16:28:29 java.io.FileNotFoundException: ./oozie.war (No such file or directory)
...
The same fix seems to work in both cases (below), though a better fix may be
more obvious to you.
--- debian/rules.orig 2012-11-27 22:24:20.000000000 +0000
+++ debian/rules 2012-11-27 22:24:06.000000000 +0000
@@ -36,7 +36,7 @@
tar cf - --exclude=debian/\* . | (cd debian/tmp && tar xf -)
override_dh_auto_install:
- sh -x debian/install_oozie.sh --extra-dir=debian/ --build-dir=.
--server-dir=./debian/oozie --client-dir=./debian/oozie-client
--docs-dir=./debian/oozie-client/usr/share/doc/oozie
--initd-dir=./debian/oozie/etc/init.d
--conf-dir=./debian/oozie/etc/oozie/conf.dist
+ sh -x debian/install_oozie.sh --extra-dir=debian/ --build-dir=`pwd`
--server-dir=./debian/oozie --client-dir=./debian/oozie-client
--docs-dir=./debian/oozie-client/usr/share/doc/oozie
--initd-dir=./debian/oozie/etc/init.d
--conf-dir=./debian/oozie/etc/oozie/conf.dist
ln -s -f /var/lib/oozie/ext-2.2
debian/oozie/usr/lib/oozie/webapps/oozie/ext-2.2
rm -rf
debian/oozie/usr/lib/oozie/webapps/oozie/docs
ln -s -f /usr/share/doc/oozie
debian/oozie/usr/lib/oozie/webapps/oozie/docs
> Oozie packages don't contain oozie.
> -----------------------------------
>
> Key: OOZIE-1092
> URL: https://issues.apache.org/jira/browse/OOZIE-1092
> Project: Oozie
> Issue Type: Bug
> Components: build
> Reporter: jdnurmi
> Labels: debian, packaging, path
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Debian oozie packages built through bigtop do not appear to be valid;
> For example, the debs in:
> http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Oozie/label=lucid/
> contain neither the .war file, the exploded .war file, or the scripts to
> generate a new .war file.
> By overlaying the debianization patches (no idea where they come from, but it
> seems to be from bigtop...) onto a 3.2.0-incubator tarball and build, the
> problem becomes clearer:
> debian/rules calls debian/install_oozie.sh --build-dir=.
> install_oozie.sh effectively does (cd ${SOMEWORKDIR}; tar xvf
> ${BUILDDIR}/oozie.war);
> Changing build-dir=`pwd` seems to fix the issue for me, though there are also
> probably cleaner ways.
> Disconcertingly, this appears in the build output (
> http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Oozie/label=lucid/252/consoleText
> )
> + jar xf ./oozie.war
> java.io.FileNotFoundException: ./oozie.war (No such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:106)
> at java.io.FileInputStream.<init>(FileInputStream.java:66)
> at sun.tools.jar.Main.run(Main.java:238)
> at sun.tools.jar.Main.main(Main.java:1149)
> + failIfNotOK
> + [ 1 != 0 ]
> + exit 0
> which would suggest this failure is not failing the build, even though it
> produces unstartable packages.
--
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
