Hi Araham, I changed modify-build-cfg according to your below solution, below issue fixed
23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? Now, RPM build is ongoing normally, and I can see some "Success building".
Thank you so much! BRs zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月13日 9:40 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi ZhipengS,
After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally.
Important to get your feedback on the activities asked to be executed by Scott and Yong.
23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/t is- extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx -tis-r5- pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build:
You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE