deciphering a build failure
Mike McGrath
mmcgrath at fedoraproject.org
Tue Feb 21 10:50:54 UTC 2006
>
> This is weird. There is no indication that yum exited with any errors,
> yet the build stops. At first I thought the following:
>
> ls: readlink:: No such file or directory
> ls: file: No such file or directory
> ls: expected: No such file or directory
> cp: cannot stat `/dev/md1': No such file or directory
>
> were relevant, but you find them in logs of successful builds.
>
> The problem seems to have occurred between
>
> Mon Feb 20 05:06:54 2006 (when the last FC4 job succeeded (4939:
> dap-server-3.5.3-1.fc4)
> Mon Feb 20 08:29:27 2006 (when this job failed)
>
> At this point I think it points to the build systems. I can't reproduce
> in mock locally.
>
>
> It might be boa though:
>
> warning: user apache does not exist - using root
> warning: group apache does not exist - using root
>
> is new.
>
> boa is not installed when I run mock locally. why?
I may be getting the same issue:
http://buildsys.fedoraproject.org/logs/fedora-4-extras/5004-ytalk-3.3.0-3.fc4/i386/job.log
devel builds fine, FC4 does not.
-Mike
More information about the fedora-extras-list
mailing list