Manually running mock

[Mike McLean]

On 05/25/2012 12:21 PM, Moray Henderson wrote:
> 3 weeks ago, before I went on holiday, I could debug build problems by
> logging into my koji build server and get into the mock chroot with
> something like
>
>    su - kojibuilder -c "mock -v -r koji/slsbox-1.1-build-186-252 --shell"
>
> Now when I try it, it fails with

So mock init succeeds, but mock --shell fails? Perhaps the chroot is 
lacking /bin/bash. Have you looked? Were there any unusual errors in 
root.log?

>    Traceback (most recent call last):
>      File "/usr/sbin/mock", line 881, in<module>
>        main(retParams)
>      File "/usr/sbin/mock", line 759, in main
>        sys.exit(chroot.shell(options, cmd))
>      File "/usr/lib/python2.6/site-packages/mockbuild/backend.py", line 682,
> in shell
>        cmd=cmd)
>      File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 402, in
> doshell
>        return subprocess.call(cmdstr, preexec_fn=preexec, env=environ,
> shell=True)
>      File "/usr/lib64/python2.6/subprocess.py", line 478, in call
>        p = Popen(*popenargs, **kwargs)
>      File "/usr/lib64/python2.6/subprocess.py", line 639, in __init__
>        errread, errwrite)
>      File "/usr/lib64/python2.6/subprocess.py", line 1228, in _execute_child
>        raise child_exception
>    OSError: [Errno 2] No such file or directory
>
> I've done a mock clean and mock init, and the same thing happens.  Anyone
> seen anything like that before?