[
https://issues.apache.org/jira/browse/ZOOKEEPER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084078#comment-15084078
]
Wenjie Ding commented on ZOOKEEPER-2352:
----------------------------------------
Hi Chris,
I tracked down to the issue with 'pushd'. It turns out that in ubuntu, the
/bin/sh is a symbol link to /bin/dash (not bash) which does not have 'pushd'.
After I have fixed this, it went further. The new problem is described from
the output:
[rpm] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iOquiw
[rpm] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.aymsm1
[rpm] /tmp/zookeeper_package_build_wding/BUILD
/tmp/zookeeper_package_build_wding/BUILD/zookeeper-3.6.0-SNAPSHOT
[rpm]
[rpm]
[rpm] RPM build errors:
[rpm] + cp -a
/tmp/zookeeper_package_build_wding/BUILD/zookeeper-3.6.0-SNAPSHOT/sbin/update-zookeeper-env.sh
/tmp/zookeeper_package_build_wding/BUILD/zookeeper-3.6.0-SNAPSHOT/sbin/zkServer-initialize.sh
/tmp/zookeeper_package_build_wding/BUILD/zookeeper-3.6.0-SNAPSHOT/sbin/zkServer.sh
/tmp/zookeeper_package_build_wding/BUILD/usr/sbin
[rpm] + rm -r /tmp/zookeeper_package_build_wding/BUILD/usr/include
[rpm] + rm -r /tmp/zookeeper_package_build_wding/BUILD/usr/man
[rpm] + mv etc usr var
/tmp/zookeeper_package_build_wding/BUILDROOT/zookeeper-3.6.0_SNAPSHOT-1.x86_64
[rpm] mv: target
'/tmp/zookeeper_package_build_wding/BUILDROOT/zookeeper-3.6.0_SNAPSHOT-1.x86_64'
is not a directory
[rpm] error: Bad exit status from /var/tmp/rpm-tmp.aymsm1 (%install)
[rpm] Bad exit status from /var/tmp/rpm-tmp.aymsm1 (%install)
Cheers!
-Wenjie
> rpm build broke
> ---------------
>
> Key: ZOOKEEPER-2352
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2352
> Project: ZooKeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.5.1
> Environment: ubuntu 15.10
> Reporter: Wenjie Ding
> Fix For: 3.5.1
>
> Attachments: rpm-tmp.G8hNUf
>
> Original Estimate: 10h
> Remaining Estimate: 10h
>
> rpm ‘cd’ to the BUILD directory, delete the directory it just ‘cd’ to. What
> was going on from that point was that it called some script which was loading
> /bin/bash and crashed since ‘getcwd’ cannot access the parent directory which
> had been deleted.
> build output messages;
> ...
> [rpm] + cd /tmp/zkpython_build_root/BUILD
> [rpm] + '[' /tmp/zkpython_build_root/BUILD '!=' / ']'
> [rpm] + rm -rf /tmp/zkpython_build_root/BUILD
> [rpm] ++ dirname /tmp/zkpython_build_root/BUILD
> [rpm] + mkdir -p /tmp/zkpython_build_root
> [rpm] + mkdir /tmp/zkpython_build_root/BUILD
> [rpm] + /usr/lib/rpm/check-buildroot
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
> [rpm] + /usr/lib/rpm/redhat/brp-compress
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
> [rpm] chdir: error retrieving current directory: getcwd: cannot access
> parent directories: No such file or directory
> [rpm] + /usr/lib/rpm/redhat/brp-strip /usr/bin/strip
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
> [rpm] + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
> [rpm] + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip
> /usr/bin/objdump
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
> [rpm] + /usr/lib/rpm/brp-python-bytecompile
> [rpm] shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: No such file or directory
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
