build-pkgs will by default run in parallel mode. This means two things, a different build order than the serial build, and the possibility that earlier packages built in a different mock environment. It likely works in a serial build because an earlier package has a "Require: X" where X is shadow-utils or something that depends on shadow-utils. Since we reuse the mock environment rather than clearing it after each package (faster builds), the shadow-utils package is available for later packages and might allow then to get away with a missing dependency. The real solution is to add 'Requires: shadow-utils' to the spec file of the package that breaks. Adding it via modify-build-cfg was based on the theory (unconfirmed) that @buildsys-build macro has been redefined on newer CentOS systems and shadow-utils has been dropped from the set of packages that @buildsys-build maps to. It seems like a quicker way to enable folks, rather than adding 'Requires: shadow-utils' to potemtially a lot of packages. Scott On 18-07-04 03:15 AM, Hu, Yong wrote:
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!