On Nov 28, 2010, at 11:16 AM, Thorsten Leemhuis wrote: > On 28.11.2010 12:45, solarflow99 wrote: >> On Sun, Nov 28, 2010 at 3:18 AM, Thorsten Leemhuis <[email protected]> >> wrote: >>> On 28.11.2010 11:51, solarflow99 wrote: >>>> On Sun, Nov 28, 2010 at 2:38 AM, Thorsten Leemhuis <[email protected]> >>>> wrote: >>>>> Just FYI, building RPM Fusion packages for EL6 is possible now. Guess >>>>> there will be a few rough edges here and there, so keep the eyes open >>>>> and report any problems. >>>> oh good, do you know if we have an EL-5 build system? There's no >>>> rush, but I noticed my package in waiting status. >>> Note that problems in our build infrastructure (like this) are one of >>> the main reasons why I'm really unhappy about the state of RPM Fusion >>> and want to have a break (see the other mail I just sent). >>> This case for me boils down to: There are people that are supposed to >>> take care about the build infrastructure and they are obviously not >>> doing their work. Please ask them, not me, as I multiple times made >>> clear that I don't want to do the administration of our build infra. In >>> case you don't get satisfying results within a few days then ask me >>> again please and I'll see what I can do to get a EL-5 builder running again. >> ok, and if there's something I can help you out with just let me know, >> rpmfusion has always been short staffed, so we have to do the best we >> can I suppose. I'm willing to help where I can. > > The direct problems at hand: The only x86 builder that is left has no > local CentOS/RHEL mirror; the admin of this machine might be able to > create one in the local net on the machine where other repos are > mirrored.
Screw it, why not. I'm rsync'ing down the CentOS 5.5 trees right now. Nb: the el6 trees on my builder are restricted to local access only, as they're true-blue (er, red?) RHEL6 GA trees. We should switch probably switch to CentOS 6 once its available. Also, the configs will likely also need to point at the optional trees to pick up an array of additional BuildReqs for a lot of things. > Then all what is needed is creating a few config files, which > can be done in ~15 minutes or so. I can do that, but as I indicated > already: I'd say it's the job of our infra group and would prefer to > hear from them first before I once again step on their toes and do their > work (which I often did in the past and which might be more harmful then > helpful; don't know) > > Some of the overall RPM Fusion problem we are facing in this area: > > * where did the other x86 builders we had go? Seems they simply got > lost over time Good question. On the bright side, my builder has finally stabilized again, after a RAM and CPU upgrade. > * you and others iirc applied to help with infra work earlier; why > haven't you got access and/or instructions? Indeed. :( Of course, in my case, I don't really have the time anyway, so perhaps its better I never got access. ;) > * seems there is not much interest in the el5 repo; some packages were > build, but nobody really cared and for a lot of people it seems the el5 > branch was "fire once and forget" (part of the problem: > ownership/responsibilities were not clearly solved and owners.list for > el is wrong in some places); that's one of the reasons why I left all > the packages in testing I know I don't give a lick about el5 (outside of work) myself, but I'm quite interested in el6 support (all my mythtv boxen at home are slowly being moved to el6). However, there are a few issues that still need to be overcome -- off the top of my head, most notably, the lack of qt-webkit support in el6 (I'm solving this with a local rebuild of the el6 qt packages w/webkit support re-enabled, for the moment). -- Jarod Wilson [email protected]
