freetype-freeworld build issues

Kevin Kofler kevin.kofler at chello.at
Sun Sep 22 19:18:37 CEST 2013


Hi,

my freetype-freeworld builds have been behaving strangely lately. Looking at 
buildsys.rpmfusion.org:

* The Plague results for 2.5.0.1-1.fc20 built on Sep 16 show only a 
freetype-debuginfo.i686 RPM, no freetype.i686 nor any x86_64 builds. I got a 
mail that the build "succeeded" hours after issuing it, but this doesn't 
look like a success to me. I see a build log for i686 which shows a 
freetype.i686 RPM having been produced, why is it not in the plague results? 
And for x86_64, the build log is entirely AWOL.

* For 2.5.0.1-2.fc20 and 2.4.11-3.fc19 built today, I see complete i686 
output, but still no x86_64 one, even though again, the mails claimed 
"success", and this time they arrived in a timely manner. For the F19 build, 
the build log for x86_64 looks fine (so why is the output not in the Plague 
results?), for the F20 one, i686 has only job.log and state.log and the 
x86_64 directory is empty.

* Today's 2.4.10-4.fc18 build failed, but I cannot find usable logs of the 
failure. For i686, build.log is only the first line with the Mock version, 
root.log is missing entirely, as is the whole x86_64 folder. This is on 
buildsys.rpmfusion.org; the failure e-mail gave links on 
builder1.rpmfusion.org, but those did not work at all.

I think we have some serious issues transfering output to 
buildsys.rpmfusion.org.

        Kevin Kofler


More information about the rpmfusion-developers mailing list