On Thu, Nov 17, 2011 at 5:39 PM, Dennis Gilmore <den...@ausil.us> wrote: > El Thu, 17 Nov 2011 09:39:58 +0000 > Peter Robinson <pbrobin...@gmail.com> escribió: >> Hi John, >> >> On Thu, Nov 17, 2011 at 7:55 AM, Jon Masters >> <jonat...@jonmasters.org> wrote: >> > Folks, >> > >> > My take on current progress is that we have a lot of packages with >> > bits still needing to head upstream, and we have a number of >> > package deltas between v5 and v7, but the core set of packages we >> > actually need to get a minimal build done is about there. Minus: >> > >> > * gcc - making sure the bitfields patches are in place for v5 >> > * glibc - delta needs attention >> > >> > I'm not so concerned about lorax and anaconda at this stage, and I >> > don't think we have critical reps on python3. In reading through >> > the package lists again tonight on DJ's graphs, I can't help but >> > think we could partially import enough packages to get Koji running >> > almost immediately tomorrow, then pull in the rest as we get that >> > resolved. Assuming that is the case, we should focus on gcc and >> > glibc reconciliation and get this going asap. > > since we are using external repos and not using importing anything. we > are going to be building the same nvrs in koji so we can not import. > we need to set up the tags specially. without inheritance otherwise the > f14 armv5tel builds will override all the f15 ones. but there really > is no reason that we can not start building today. i am working on one > patch for koji to deal with how it writes out the mock config files. > >> > Please reply to this mail with your input. Let's have a status sync >> > up on IRC later. >> >> Absolutely agree. None of the lists I've seen have core build root >> packages except for the two you mention. There's a number of >> differences between the lists I've seen and a lot of the spec patches >> that are in the stage4 repos were already upstreamed from the work I'd >> done with F-14. >> >> Once the gcc/glibc fixes are in we're good to go. I'd not looked at >> pushing them upstream as I'd figured the people who'd been dealing >> with them likely had them in hand and knew a lot more of the issues in >> hand than I do. > even with these still to be resolved, there is zero reason right now > why we cannot go ahead and build everything else. > >> I think for the F-15 build its going to a little break/fix as we go >> along as there's likely other bits we've missed or have changed since, >> as long as the people that fix those problems commit the fix to all >> F-15/16/rawhide branches then and there so the fixes don't get lost >> and have to be repeated again. > Im sure there will be some small issues crop up, but shouldnt be too > horrible. > > I vote that we get building today. why we make sure we get the > gcc/glibc etc things resolved. we can the start mshing some repos and > getting bits out there :)
Do we have softfp and hardfp builder ready to go? koji3 is still online for armv5tel for builds that need lots of RAM, let me know if it needs any config updates. Peter _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
