Michael Schwendt wrote on 30.04.2010 13:10:
On Fri, 30 Apr 2010 18:02:07 +0800 (CST), Chen wrote:
> All ppc(64) Broken deps are caused by
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1166, I think it already fixed days ago.
Thanks for the pointer.
BTW, he pointed to it a few days ago when we discussed the ppc problem
already (it iirc was a mail from Dominik about a mplayer build problem;
the root of that problem was exactly the same)
Not responding to that ticket is exactly one thing that should not
happen.
I understand that some people hate Plague [for sometimes dubious reasons],
but undermining it with lack of support is just rude.
Just FYI, I still try to stay away from infra work, but if there is
something help from my side is needed please ping me (maybe I'm the only
one that has access to the ppc builder -- there was the plan to switch
to a different one months (a year?) ago and give others from RPM Fusion
access to it, but that work stalled).
And as brought up a few days ago already: Xavier or others from the
sysadmin team, is there anything that changed recently that might be the
reason for this problem?
Are the Plague config files for ppc and ppc64 available in some
public
place?
I maintained those in CVS (
cvs.rpmfusion.org, /cvs/rpmfusion/), but you
might need a RPM Fusion FAS-Account to be able to access them. And the
sysadmins now use puppet for some services, so those files might not be
up2date in cvs.
Download failures not killing the build job would only occur for
testing targets, but none of RPM Fusions targets should be set up like
that. Also, please save a copy of the server and builder logs.
/me will do that later and sent the config by private mail when back
home from work
/me will then also look into the multilib problem for the testing repos
CU
knurd