Thank you! Importing the binary rpms solved the previous issue!
Now I am seeing the following problem. I have imported all the necessary rpms
which show up as required (binaries) and I still see these errors. How do I
resolve them?
DEBUG util.py:314: Executing command: ['/usr/bin/yum', '--installroot',
'/var/lib/mock/dist-ncs-build-31-76/root/', 'groupinstall', 'build',
'--setopt=tsflags=nocontexts'] with env {'LANG': 'en_US.UTF-8', 'TERM':
'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n
"<mock-chroot>"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG util.py:264: Error: Package: libcurl-7.19.7-35.el6.x86_64 (build)
DEBUG util.py:264: Requires: libk5crypto.so.3()(64bit)
DEBUG util.py:264: Error: Package: openssl-1.0.0-27.el6.x86_64 (build)
DEBUG util.py:264: Requires: libk5crypto.so.3()(64bit)
DEBUG util.py:264: Error: Package: sed-4.2.1-10.el6.x86_64 (build)
DEBUG util.py:264: Requires: /sbin/install-info
DEBUG util.py:264: Error: Package: rpm-libs-4.8.0-32.el6.x86_64 (build)
DEBUG util.py:264: Requires: liblzma.so.0()(64bit)
DEBUG util.py:264: Error: Package: libcurl-7.19.7-35.el6.x86_64 (build)
DEBUG util.py:264: Requires:
libgssapi_krb5.so.2(gssapi_krb5_2_MIT)(64bit)
DEBUG util.py:264: Error: Package: which-2.19-6.el6.x86_64 (build)
DEBUG util.py:264: Requires: /sbin/install-info
DEBUG util.py:264: Error: Package: libnih-1.0.1-7.el6.x86_64 (build)
DEBUG util.py:264: Requires: libdbus-1.so.3()(64bit)
DEBUG util.py:264: Error: Package: binutils-2.20.51.0.2-5.36.el6.x86_64 (build)
DEBUG util.py:264: Requires: /sbin/install-info
DEBUG util.py:264: Error: Package: grep-2.6.3-3.el6.x86_64 (build)
DEBUG util.py:264: Requires: /sbin/install-info
DEBUG util.py:264: Error: Package: rpm-libs-4.8.0-32.el6.x86_64 (build)
DEBUG util.py:264: Requires: libelf.so.1()(64bit)
DEBUG util.py:264: Error: Package: upstart-0.6.5-12.el6.x86_64 (build)
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Mike Bonnet
Sent: Thursday, September 05, 2013 2:33 PM
To: [email protected]
Subject: Re: ERROR: Could not find useradd in chroot, maybe the install failed?
in mock_output.log
On 9/5/13 2:01 PM, Radha Venkatesh (radvenka) wrote:
> Yes, I have run the below commands.
>
> Here is the output of
>
> [kojiadmin@vos-cm20 koji]$ koji list-groups ncp-build
> build [ncp-basedeps]
> bash: None, default [ncp-basedeps]
> bzip2: None, default [ncp-basedeps]
> coreutils: None, default [ncp-basedeps]
> cpio: None, default [ncp-basedeps]
> cvs: None, default [ncp-basedeps]
> diffutils: None, default [ncp-basedeps]
> findutils: None, default [ncp-basedeps]
> gawk: None, default [ncp-basedeps]
> gcc: None, default [ncp-basedeps]
> gcc-c++: None, default [ncp-basedeps]
> gnupg: None, default [ncp-basedeps]
> grep: None, default [ncp-basedeps]
> gzip: None, default [ncp-basedeps]
> info: None, default [ncp-basedeps]
> make: None, default [ncp-basedeps]
> patch: None, default [ncp-basedeps]
> redhat-rpm-config: None, default [ncp-basedeps]
> rpm-build: None, default [ncp-basedeps]
> rpmdevtools: None, default [ncp-basedeps]
> sed: None, default [ncp-basedeps]
> shadow-utils: None, default [ncp-basedeps]
> tar: None, default [ncp-basedeps]
> unzip: None, default [ncp-basedeps]
> util-linux-ng: None, default [ncp-basedeps]
> wget: None, default [ncp-basedeps]
> which: None, default [ncp-basedeps]
> srpm-build [ncp-basedeps]
> bash: None, default [ncp-basedeps]
> bzip2: None, default [ncp-basedeps]
> coreutils: None, default [ncp-basedeps]
> cpio: None, default [ncp-basedeps]
> cvs: None, default [ncp-basedeps]
> diffutils: None, default [ncp-basedeps]
> findutils: None, default [ncp-basedeps]
> gawk: None, default [ncp-basedeps]
> gcc: None, default [ncp-basedeps]
> gcc-c++: None, default [ncp-basedeps]
> gnupg: None, default [ncp-basedeps]
> grep: None, default [ncp-basedeps]
> gzip: None, default [ncp-basedeps]
> info: None, default [ncp-basedeps]
> make: None, default [ncp-basedeps]
> patch: None, default [ncp-basedeps]
> redhat-rpm-config: None, default [ncp-basedeps]
> rpm-build: None, default [ncp-basedeps]
> rpmdevtools: None, default [ncp-basedeps]
> sed: None, default [ncp-basedeps]
> shadow-utils: None, default [ncp-basedeps]
> tar: None, default [ncp-basedeps]
> unzip: None, default [ncp-basedeps]
> util-linux-ng: None, default [ncp-basedeps]
> wget: None, default [ncp-basedeps]
> which: None, default [ncp-basedeps]
>
> [kojiadmin@vos-cm20 koji]$ koji taginfo ncp-build
> Tag: ncp-build [7]
> Arches: x86_64
> This tag is a buildroot for one or more targets
> Current repo: repo#11: 2013-09-05 13:21:13.623486
> Targets that build from this tag:
> ncp
> External repos:
> 5 dist-ncp-external-repo (/auto/tps/centos/6/x86_64/)
> Inheritance:
> 0 .... ncp [5]
>
> 1 .... ncp-basedeps [8]
>
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Michael
> Cronenworth
> Sent: Thursday, September 05, 2013 1:54 PM
> To: [email protected]
> Subject: Re: ERROR: Could not find useradd in chroot, maybe the install
> failed? in mock_output.log
>
> On 09/05/2013 03:41 PM, Radha Venkatesh (radvenka) wrote:
>> I still see the same error.
>
> Going back to your original e-mail, I don't see the group "build". The output
> of
> list-groups should echo "build" such as this:
>
> $ koji list-groups f18-build
> build [f18-build]
> bash: None, default [f18-build]
> bzip2: None, default [f18-build]
> coreutils: None, default [f18-build]
> ...
>
> Are you running this?
> $ koji add-group ncp-build build
> $ koji add-group-pkg ncp-build build <pkg1> etc...
In your first email you said "all the source rpms have been imported
into the build server." If you're using external repos (as it appears
you are from looking at the output of "koji taginfo") then you shouldn't
need to import anything. Please see:
https://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap
I would recommend using this aproach when setting up a new Koji server.
Note that the external repo URL should be a full http:// URL that is
accessible by the build machines, not merely a local path.
If you choose to import rpms rather than using the external repo method,
as documented in:
https://fedoraproject.org/wiki/Koji/ServerBootstrap
then you need to import both source *and* binary rpms. The binary rpms
are required to create the chroots where builds will happen.
--
buildsys mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/buildsys
--
buildsys mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/buildsys
