[fedora-arm] ghc bootstrapped for armv5tel (and armv7hl earlier)
Bootstrapping of GHC is now completed for both armv7hl and armv5tel.
armv7hl packages is in stage4 since a month back.
mock built amv5tel packages can be found at
http://repos.fedorapeople.org/repos/hno/armv5tel/fedora-15/
ghc
hscolour
ghc-rpm-macros
redhat-rpm-config
built from current Fedora-15 mainline releases, where ghc, hscolour
ghc-rpm-macros is all in updates-testing and redhat-rpm-macros is only
in koji (trivial change adding armv7hl armv5tel to ghc supported arch
list).
In the armv7hl stage4 repository there is also a large number of
slightly modified ghc related packages adding armv7hl as a supported
arch. It's not yet decided how many of these will be updated for F15 to
use the right arch specifications %{ghc_arches}. None of these needs to
be dealt with before moving to koji and will build fine as F15 updates
later on, or when we move to F16 where this change was already done.
Regards
Henrik
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
Ho Jon, On Wed, Oct 19, 2011 at 6:41 AM, Jon Masters j...@redhat.com wrote: On Tue, 2011-10-18 at 22:09 -0500, Dennis Gilmore wrote: So ive done some thinking, and talked with some of the stakeholders. Ive come to the conclusion that we should skip f16 and shoot straight for rawhide. two reasons for this. one to become a primary arch at some point we need to be caught up and doing releases at the same time. my long term goal is for arm to become a primary arch and the second reason why i think that we should skip f16 is that its easier to get help from maintainers when doing things in rawhide. I wanted to get a quick note out there to get discussion going. Thanks for sending this Dennis. We spoke about this briefly at the tail end of last week since you were out this way, and as I said then, I think this is both a good idea and essential to us making progress toward being a primary architecture by this time next year. If we can get ourselves building rawhide by the new year, we get F17 for free. That then gives us a compelling case for F18 as primary arch. If we miss this time around, we're back in the cycle we've been in which isn't really going to let us achieve satisfactory world domination ;) So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: * Sync up the armv5tel and armv7hl pre-koji package sets = We are here * Do final F15 build in Koji * Release F15 ( start F15-updates builds) * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl rootfs) * Do necessary prebuilds for rawhide (build-previous or other) * Build for rawhide, shadow PA as closely as possible * Branch F17 when PA does At the end of this process we'll be building for at least three releases (F15updates, F17, rawhide) across two archs - 6 builds total. -- Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] F15 armv5tel update
So Moji has burned through all of the armv5tel builds at least once[0]; we have 4092 successful builds and 915 error builds at this point. Jon and Paul are pulling in some lovingly hand-crafted builds done on the weekend (thanks tinker915 and Henrick) and working through the error'd builds -- any help is appreciated if you have some free cycles. I think we're about ready to... - compare the armv5tel and armv7hl package sets again - solve any discrepancies - double-check that patches have been upstreamed ...and then do the koji external repo setup. -Chris [0] http://moji.proximity.on.ca/moji ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
- compare the armv5tel and armv7hl package sets again Do we need another pretty chart? ;-) ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: * Sync up the armv5tel and armv7hl pre-koji package sets = We are here * Do final F15 build in Koji It was my understanding from dgilmore's proposal above that we were going to skip F-15 and just go straight to F-17. Ultimately whether we do a final F-15 or F-17 it doesn't really matter, the current build tool chain for them both is derived from gcc 4.6.1 * Release F15 ( start F15-updates builds) * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl rootfs) * Do necessary prebuilds for rawhide (build-previous or other) * Build for rawhide, shadow PA as closely as possible * Branch F17 when PA does At the end of this process we'll be building for at least three releases (F15updates, F17, rawhide) across two archs - 6 builds total. Why? I thought the above process was with the idea of just using the F-15 work that was done as a base to go straight to F-17 and forget the rest. Clearly people need to start documenting the exact process for all to see. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
On Tue, Oct 25, 2011 at 7:17 PM, Peter Robinson pbrobin...@gmail.com wrote: On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: Oh and I'm not saying short circuit it, I'm saying educate people so there's not random dumps and then deathly silence. According the previously announced schedule we should be building from koji by now. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On Tue, Oct 25, 2011 at 6:53 PM, DJ Delorie d...@redhat.com wrote: - compare the armv5tel and armv7hl package sets again Do we need another pretty chart? ;-) yes please ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
On Tue, 2011-10-25 at 19:17 +0100, Peter Robinson wrote: On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: * Sync up the armv5tel and armv7hl pre-koji package sets = We are here * Do final F15 build in Koji It was my understanding from dgilmore's proposal above that we were going to skip F-15 and just go straight to F-17. Ultimately whether we do a final F-15 or F-17 it doesn't really matter, the current build tool chain for them both is derived from gcc 4.6.1 The proposal was to skip F16. We're close to F15 and we need it. If we don't ship it, we have a substantial time gap where we have no supported Fedora release. Shipping F15 also gives us experience with systemd on ARM (and other pieces of a fairly complete release, such as haskell and ocaml) which can feed into the F17 development cycle. * Release F15 ( start F15-updates builds) * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl rootfs) * Do necessary prebuilds for rawhide (build-previous or other) * Build for rawhide, shadow PA as closely as possible * Branch F17 when PA does At the end of this process we'll be building for at least three releases (F15updates, F17, rawhide) across two archs - 6 builds total. Why? I thought the above process was with the idea of just using the F-15 work that was done as a base to go straight to F-17 and forget the rest. Clearly people need to start documenting the exact process for all to see. The goal is to get as close to PA as possible, as quickly as possible. If we follow only the F17 branch, we're in a catch-up position *again* for F18. If we follow both rawhide and F17, we're in much better shape for F18. And if we ship F15 for ARM, we need to ship updates (and prove that we can ship timely updates, which will be important when making the case for primary arch status). -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On Tue, 2011-10-25 at 13:53 -0400, DJ Delorie wrote: - compare the armv5tel and armv7hl package sets again Do we need another pretty chart? ;-) Ideally, crontab'd! -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
On Tue, Oct 25, 2011 at 7:35 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 19:17 +0100, Peter Robinson wrote: On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: * Sync up the armv5tel and armv7hl pre-koji package sets = We are here * Do final F15 build in Koji It was my understanding from dgilmore's proposal above that we were going to skip F-15 and just go straight to F-17. Ultimately whether we do a final F-15 or F-17 it doesn't really matter, the current build tool chain for them both is derived from gcc 4.6.1 The proposal was to skip F16. We're close to F15 and we need it. If we don't ship it, we have a substantial time gap where we have no supported Fedora release. Shipping F15 also gives us experience with systemd on ARM (and other pieces of a fairly complete release, such as haskell and ocaml) which can feed into the F17 development cycle. * Release F15 ( start F15-updates builds) * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl rootfs) * Do necessary prebuilds for rawhide (build-previous or other) * Build for rawhide, shadow PA as closely as possible * Branch F17 when PA does At the end of this process we'll be building for at least three releases (F15updates, F17, rawhide) across two archs - 6 builds total. Why? I thought the above process was with the idea of just using the F-15 work that was done as a base to go straight to F-17 and forget the rest. Clearly people need to start documenting the exact process for all to see. The goal is to get as close to PA as possible, as quickly as possible. If we follow only the F17 branch, we're in a catch-up position *again* for F18. If we follow both rawhide and F17, we're in much better shape for F18. And if we ship F15 for ARM, we need to ship updates (and prove that we can ship timely updates, which will be important when making the case for primary arch status). That's what I mean. F-17 doesn't fork from rawhide until alpha, so at the moment F-17 == rawhide for a couple of months yet and hence there is no F17 branch to discuss. I'm sort of hoping we have a lot of that build by branch time and its hence not a problem. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
- compare the armv5tel and armv7hl package sets again Do we need another pretty chart? ;-) yes please Is there a suitable rsync target we can use to get a local copy of the appropriate files? Note: the answer to that partly depends on what kinds of comparisons you're interested in for this script... Hint, hint. ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On Tue, 2011-10-25 at 14:41 -0400, DJ Delorie wrote: Ideally, crontab'd! Heh. The trick is finding a machine that has both access to the repos *and* access to a web server, and is powerful enough to run the script in a reasonable time. But I'll see what I can do ;-) We can host on Australia -- send me an ssh public key for access. -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
We can host on Australia -- send me an ssh public key for access. Will do. What sort of information do we want this new chart to convey? ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On 10/25/2011 11:52 AM, DJ Delorie wrote: We can host on Australia -- send me an ssh public key for access. Will do. What sort of information do we want this new chart to convey? Packages only in armv7hl build (latest version) Packages only in armv5tel build (latest version) Changes only in armv7hl build Changes only in armv5tel build -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On Tue, 2011-10-25 at 14:52 -0400, DJ Delorie wrote: We can host on Australia -- send me an ssh public key for access. Will do. What sort of information do we want this new chart to convey? I think we need to see if the package sets are congruent, so a display of the differences between the package sets would be good: package missing in A or in B, EVR mismatches. I have scripts for http://hongkong.proximity.on.ca/f13-arm-beta2/ type output if you want them for a starting point. -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] Fedora 16
Plan was to release a good enough F15 but absolutely to do some kind of release (just cap when we will move on to keep momentum - a couple more weeks and we need to be focused on rawhide). It's F16 we are wanting to skip in order to focus on rawhide by the new year. -- Sent from my phone - message formatted and/or shortened accordingly. -Original Message- From: Peter Robinson [pbrobin...@gmail.com] Received: Tuesday, 25 Oct 2011, 11:17 To: Chris Tyler [ch...@tylers.info] CC: Fedora ARM secondary architecture list [arm@lists.fedoraproject.org] Subject: Re: [fedora-arm] Fedora 16 On Tue, Oct 25, 2011 at 6:09 PM, Chris Tyler ch...@tylers.info wrote: On Tue, 2011-10-25 at 17:49 +0100, Peter Robinson wrote: So what's the status of this? Are we using the F-15 as the external repo base for building F-17? When is it going to happen? My understanding is we have enough of both arches built that we can start this rolling. It would be good to see some public movement on this now and to get this rolling rather than delaying further. No one's delaying, but there is a sequence to this that we shouldn't short-circuit: * Sync up the armv5tel and armv7hl pre-koji package sets = We are here * Do final F15 build in Koji It was my understanding from dgilmore's proposal above that we were going to skip F-15 and just go straight to F-17. Ultimately whether we do a final F-15 or F-17 it doesn't really matter, the current build tool chain for them both is derived from gcc 4.6.1 * Release F15 ( start F15-updates builds) * Finalize koji changes for rawhide (rpm, rpmbuild, yum, koji, armv7hl rootfs) * Do necessary prebuilds for rawhide (build-previous or other) * Build for rawhide, shadow PA as closely as possible * Branch F17 when PA does At the end of this process we'll be building for at least three releases (F15updates, F17, rawhide) across two archs - 6 builds total. Why? I thought the above process was with the idea of just using the F-15 work that was done as a base to go straight to F-17 and forget the rest. Clearly people need to start documenting the exact process for all to see. Peter ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
- compare the armv5tel and armv7hl package sets again Do we need another pretty chart? ;-) yes please http://djdelorie.fedorapeople.org/armv5tel-vs-armv7hl.html ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Re: [fedora-arm] F15 armv5tel update
On 10/25/2011 04:06 PM, DJ Delorie wrote: http://djdelorie.fedorapeople.org/armv5tel-vs-armv7hl.html Cool! What is the plan for reconciling the differences? A few packages stand out as being particularly concerning: gcc: There are patches in the armv7hl build that affect volatile bitfields and memory consumption. The lack of the volatile bitfield patch may result in a few broken packages on armv5tel while the absence of the memory consumption patch may result in some packages failing to build. glibc: Both have arm patches, but are they the same patches? rpm: Special armv7hl handling was required. Is this as upstream acceptable as it's going to be for the foreseeable future? -- Brendan Conoboy / Red Hat, Inc. / b...@redhat.com ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
[fedora-arm] Rescheduled to 2011-10-26: Outage: Fedora ARM Build Farm 2011-10-25 14:00 UTC
On Fri, 2011-10-21 at 02:37 -0400, Chris Tyler wrote: There will be an outage starting at 2011-10-25 14:00 UTC, which will last approximately 4 hours. (Services will be restored incrementally, with the x86_64 hosts coming up first, followed by the ARM builders). To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-10-25 14:00 UTC' Reason for outage: Physical maintenance/rearrangement/rewiring to improve cooling and manageability. Affected Services: ARM Koji - arm.koji.fedoraproject.org Moji - moji.proximity.on.ca ARM builders: cdot-guru-*-* cdot-smarttop-*-* cdot-panda-*-* cdot-beagle*-*-* cdot-openrd-*-* cdot-sheeva-*-* Related servers: hongkong.proximity.on.ca = arm.koji.fedoraproject.org australia.proximity.on.ca = moji.proximity.on.ca scotland.proximity.on.ca ireland.proximity.on.ca Unaffected Services: Non-ARM Secondary Architecture services Non-Seneca ARM servers Contact Information: cty...@fedoraproject.org - irc://cty...@irc.freenode.net/fedora-arm jordran.cw...@senecac.on.ca - irc://jacw...@irc.freenode.net/fedora-arm Please join #fedora-arm in irc.freenode.net Rescheduled to 2011-10-26 at approx. 14:00 UTC. -Chris ___ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
