[Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
scott.little at windriver.com
Fri Nov 2 20:22:55 UTC 2018
Try updating your stx-tools and running download_mirror.sh again.
Alternatively, you can find it here ...
On 18-11-02 05:19 AM, Rajesh Jha wrote:
> We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from
> https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror-repository document.
> when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
> b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
> now we are stuck and unable to build. Any suggestions would be welcome.
> on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
> and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
> Best Regards,
> Rajesh Jha
> The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
More information about the Starlingx-discuss