unable to build

[mator]

is it just me, or it is broken?

build host is centos-7 x86_64 .

build log :

sudo mock /home/mator/zookeeper-rpms/zookeeper-3.5.5-3.el7.src.rpm

...
Start: rpmbuild zookeeper-3.5.5-3.el7.src.rpm
Building target platforms: x86_64
Building for target x86_64
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.VhHO1I
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf apache-zookeeper-3.5.5
+ /usr/bin/gzip -dc /builddir/build/SOURCES/apache-zookeeper-3.5.5.tar.gz
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd apache-zookeeper-3.5.5
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.R4ghuN
+ exit 0
+ umask 022
+ cd /builddir/build/BUILD
+ cd apache-zookeeper-3.5.5
+ mvn -DskipTests package
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/18/apache-18.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.apache.zookeeper:parent:3.5.5 (/builddir/build/BUILD/apache-zookeeper-3.5.5/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not transfer artifact org.apache:apache:pom:18 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: Name or service not known and 'parent.relativePath' points at no local POM @ line 23, column 11: Unknown host repo.maven.apache.org: Name or service not known -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException


RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.R4ghuN (%build)
    Bad exit status from /var/tmp/rpm-tmp.R4ghuN (%build)
Finish: rpmbuild zookeeper-3.5.5-3.el7.src.rpm
Finish: build phase for zookeeper-3.5.5-3.el7.src.rpm
ERROR: Exception(/home/mator/zookeeper-rpms/zookeeper-3.5.5-3.el7.src.rpm) Config(epel-7-x86_64) 1 minutes 31 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-7-x86_64/result
ERROR: Command failed:
 # /usr/bin/systemd-nspawn -q -M 5aaae1721dc846f4991d934fff1e02ed -D /var/lib/mock/epel-7-x86_64/root --capability=cap_ipc_lock --bind=/tmp/mock-resolv.90gvi26v:/etc/resolv.conf --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$  --setenv=LANG=en_US.UTF-8 -u mockbuild bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/zookeeper.spec

[kofemann]

It's turned out that mock creates a disconnect environment. I didn't have a time to work on it.

As a workaround, you can just run:

rpmbuild -ba --nodeps --define '_sourcedir `pwd`' --define '_srcrpmdir `pwd`' zookeeper.spec

[mafgh]

FWIW, passing --enable-network to mock worked for me.