FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 02-05-2010, 09:17 PM
Michael Cronenworth
 
Default Koji and mock init failure

I finally have my own Koji instance ironed out, using SSL instead of
Kerberos.

I was able to add a dist-f12 target and tags to Koji, and specified a
localhost FTP site for a external repo. I submitted a custom SRPM I have
as a scratch build to just test it out. The task resulted in a failure:

BuildrootError: could not init mock buildroot, mock exited with status
20; see root.log for more information

The root.log doesn't have any visible errors. I see it did a yum install
of the base packages. I see that /var/lib/mock has two directories (for
my two arches: i386, x86_64) and directories and binary files inside.
Google didn't reveal any hints either. What am I missing?
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-05-2010, 10:00 PM
Dennis Gilmore
 
Default Koji and mock init failure

On Friday 05 February 2010 04:17:43 pm Michael Cronenworth wrote:
> I finally have my own Koji instance ironed out, using SSL instead of
> Kerberos.
>
> I was able to add a dist-f12 target and tags to Koji, and specified a
> localhost FTP site for a external repo. I submitted a custom SRPM I have
> as a scratch build to just test it out. The task resulted in a failure:
>
> BuildrootError: could not init mock buildroot, mock exited with status
> 20; see root.log for more information
>
> The root.log doesn't have any visible errors. I see it did a yum install
> of the base packages. I see that /var/lib/mock has two directories (for
> my two arches: i386, x86_64) and directories and binary files inside.
> Google didn't reveal any hints either. What am I missing?
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys


Make sure you have setup the build group its at the bottom of the
"Bootstrapping a new External Repo Koji build environment" section on
http://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap

Dennis
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-08-2010, 04:13 PM
Michael Cronenworth
 
Default Koji and mock init failure

Dennis Gilmore wrote:
> Make sure you have setup the build group its at the bottom of the
> "Bootstrapping a new External Repo Koji build environment" section on
> http://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap

I believe I had done that.

$ koji list-groups dist-f12-build
build [dist-f12-build]
bash: None, default [dist-f12-build]
coreutils: None, default [dist-f12-build]
gcc: None, default [dist-f12-build]
make: None, default [dist-f12-build]
util-linux-ng: None, default [dist-f12-build]
srpm-build [dist-f12-build]

This was before I ran my scratch build.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-08-2010, 04:23 PM
Dennis Gilmore
 
Default Koji and mock init failure

On Monday 08 February 2010 11:13:23 am Michael Cronenworth wrote:
> Dennis Gilmore wrote:
> > Make sure you have setup the build group its at the bottom of the
> > "Bootstrapping a new External Repo Koji build environment" section on
> > http://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap
>
> I believe I had done that.
>
> $ koji list-groups dist-f12-build
> build [dist-f12-build]
> bash: None, default [dist-f12-build]
> coreutils: None, default [dist-f12-build]
> gcc: None, default [dist-f12-build]
> make: None, default [dist-f12-build]
> util-linux-ng: None, default [dist-f12-build]
> srpm-build [dist-f12-build]
>
> This was before I ran my scratch build.
You need more in the minimal buildroot than that.

build [f9-build-cutoff]
bash: None, default [f9-build-cutoff]
bzip2: None, default [f9-build-cutoff]
coreutils: None, default [f9-build-cutoff]
cpio: None, default [f9-build-cutoff]
diffutils: None, default [f9-build-cutoff]
fedora-release: None, default [f9-build-cutoff]
findutils: None, default [f9-build-cutoff]
gawk: None, default [f9-build-cutoff]
gcc: None, default [f9-build-cutoff]
gcc-c++: None, default [f9-build-cutoff]
grep: None, default [f9-build-cutoff]
gzip: None, default [f9-build-cutoff]
info: None, default [f9-build-cutoff]
make: None, default [f9-build-cutoff]
patch: None, default [f9-build-cutoff]
redhat-rpm-config: None, default [f9-build-cutoff]
rpm-build: None, default [f9-build-cutoff]
sed: None, default [f9-build-cutoff]
shadow-utils: None, default [f9-build-cutoff]
tar: None, default [f9-build-cutoff]
unzip: None, default [f9-build-cutoff]
util-linux-ng: None, default [f9-build-cutoff]
which: None, default [f9-build-cutoff]

fedoras has that in it you really need all of that.

Dennis
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-08-2010, 06:56 PM
Mike McLean
 
Default Koji and mock init failure

On 02/05/2010 05:17 PM, Michael Cronenworth wrote:
> I finally have my own Koji instance ironed out, using SSL instead of
> Kerberos.
>
> I was able to add a dist-f12 target and tags to Koji, and specified a
> localhost FTP site for a external repo. I submitted a custom SRPM I have
> as a scratch build to just test it out. The task resulted in a failure:
>
> BuildrootError: could not init mock buildroot, mock exited with status
> 20; see root.log for more information
>
> The root.log doesn't have any visible errors. I see it did a yum install
> of the base packages. I see that /var/lib/mock has two directories (for
> my two arches: i386, x86_64) and directories and binary files inside.
> Google didn't reveal any hints either. What am I missing?

Just a few notes about debugging mock failures. Hopefully, Dennis is
right and all you need is to expand your build group. If not, maybe this
will help.

Koji tries to guess which of the logs has the error. Sometimes it gets
it wrong. If you don't see anything you should probably go ahead and
check the other logs too.

Also, sometimes the error in the log may not jump out at you. If at
first you don't find it, look again.

Sometimes you may need to replicate the mock error manually. Log into
the build host and either user koji mock-config to clone the config (the
--task option is handy for this situation). Optionally, as long as the
failure was recent, you can just make a copy of the mock config that
koji wrote for the task. It will be under /etc/mock/koji on the build
host. Make a copy so that kojid doesn't delete it out from under you.
You'll also want to edit config_opts['root'] in you copy so that you use
a different chroot.

With some issues you may need to get yum to show more detail, you can
set the debuglevel and/or errorlevel options higher in the
config_opts['yum.conf'] setting of your mock config.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-08-2010, 08:11 PM
Michael Cronenworth
 
Default Koji and mock init failure

Dennis Gilmore wrote:
> You need more in the minimal buildroot than that.

You're correct. I now have scratch builds working. Thanks!
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 08:23 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org