strange build errors

[Mike McLean]

On 10/27/2013 05:36 AM, Bojtos Péter wrote:
> Dear List,
> 
> I have a working koji setup with several clients. When I submit a few jobs, it works great. However when I submit lots of package (>100), some of the builds fail with the following error when mock is populating the buildroot (in root.log):
> 
> DEBUG util.py:264:  Installed:
> DEBUG util.py:264:    bash.x86_64 0:4.1.2-15.el6_4                                                  
> DEBUG util.py:264:    bzip2.x86_64 0:1.0.5-7.el6_0                                                  
> DEBUG util.py:264:    coreutils.x86_64 0:8.4-19.el6_4.2                                             
> ....                                        
> DEBUG util.py:264:    xz.x86_64 0:4.999.9-0.5.beta.20091007git.slxrv3                               
> DEBUG util.py:264:  Dependency Installed:
> DEBUG util.py:264:    audit-libs.x86_64 0:2.2-2.el6                                                 
> DEBUG util.py:264:    basesystem.noarch 0:10.0-4.el6                                                
> ....              
> DEBUG util.py:264:    xz-lzma-compat.x86_64 0:4.999.9-0.5.beta.20091007git.slxrv3                   
> DEBUG util.py:264:    zlib.x86_64 0:1.2.3-29.el6                                                    

Is this really all that is getting installed in your chroot? If so, I
suspect this is the root of the problem. You probably need to adjust
your groups data for the build tag.

See what the following commands gives:
# koji list-groups dist-slxrv3-build

You need to have at least some basic packages listed in the build and
srpm-build groups. For reference, see what similar commands against
koji.fedoraproject.org give.


> Is it because newRepo task is not finished but somehow creates the
> softlink to latest (and unfinished) koji repo? Have anyone seen the
> same error before?

Highly unlikely. Each newRepo task creates an entirely new repo (the old
one stays around for a while until kojira clears it). When a build
starts, it asks the hub for the current active repo, so there should be
no way for a build to recieve a repo that is still being created.

Of course, the repo could be broken in many other ways.

> Thanks for your reply,
> Peter Bojtos
> --
> buildsys mailing list
> buildsys at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
>