You have to download these tarballs through stx download script, it will change the arcname of the tarball. In this case mux-456bcfa82d672db7cae587c9b541463f65bc2718 will be changed to gorilla-mux in the download script. Mingyuan From: xiongzhiwei@baicells.com<mailto:xiongzhiwei@baicells.com> [mailto:xiongzhiwei@baicells.com] Sent: Wednesday, January 23, 2019 15:20 To: Lin, Shuicheng <shuicheng.lin@intel.com<mailto:shuicheng.lin@intel.com>>; Qi, Mingyuan <mingyuan.qi@intel.com<mailto:mingyuan.qi@intel.com>>; starlingx-discuss <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: RE: [Starlingx-discuss] Mount error when executing build-pkgs Hi Shuicheng, Yes, I had checked /localdisk/loadbuild/ubuntu/starlingx/std/results/ubuntu-starlingx-tis-r5-pike-std/registry-token-server-1.0.0-1.tis.1/build.log, found below informations: + cd registry-token-server-1.0.0 + /usr/bin/pigz -dc /builddir/build/SOURCES/gorilla-mux-456bcfa82d672db7cae587c9b541463f65bc2718.tar.gz + /usr/bin/tar -xvvof - drwxrwxr-x root/root 0 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/ -rw-rw-r-- root/root 292 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/.travis.yml -rw-rw-r-- root/root 1476 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/LICENSE -rw-rw-r-- root/root 11972 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/README.md -rw-rw-r-- root/root 1399 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/bench_test.go -rw-rw-r-- root/root 380 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/context_gorilla.go -rw-rw-r-- root/root 868 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/context_gorilla_test.go -rw-rw-r-- root/root 380 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/context_native.go -rw-rw-r-- root/root 690 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/context_native_test.go -rw-rw-r-- root/root 8528 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/doc.go -rw-rw-r-- root/root 15842 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/mux.go -rw-rw-r-- root/root 58658 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/mux_test.go -rw-rw-r-- root/root 17516 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/old_test.go -rw-rw-r-- root/root 8956 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/regexp.go -rw-rw-r-- root/root 19752 2017-05-22 15:17 mux-456bcfa82d672db7cae587c9b541463f65bc2718/route.go + STATUS=0 + '[' 0 -ne 0 ']' + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + mkdir -p _build/src/github.com/gorilla/ + mv gorilla-mux _build/src/github.com/gorilla/mux BUILDSTDERR: mv: cannot stat 'gorilla-mux': No such file or directory BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.fu9L2u (%prep) RPM build errors: BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.fu9L2u (%prep) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 636, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/registry-token-server.spec It seems there is no 'gorilla-mux' in gorilla-mux-456bcfa82d672db7cae587c9b541463f65bc2718.tar.gz, is this package correct? I had added its download link in tarball-dl.lst as https://github.com/openstack/stx-tools/blob/master/centos-mirror-tools/tarba.... How can I fix it? Thank you very much BR Tim Xiong From: Lin, Shuicheng<mailto:shuicheng.lin@intel.com> Date: 2019-01-23 09:37 To: xiongzhiwei@baicells.com<mailto:xiongzhiwei@baicells.com>; Qi, Mingyuan<mailto:mingyuan.qi@intel.com>; starlingx-discuss<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] Mount error when executing build-pkgs Hi Tim, Please check the “build.log” in below folder. You should get the failure info in it. INFO: Results and/or logs in: /localdisk/loadbuild/ubuntu/starlingx/std/results/ubuntu-starlingx-tis-r5-pike-std/registry-token-server-1.0.0-1.tis.1 Best Regards Shuicheng