Folks,
We are hosting another one of our regular Fedora 15 hardfp Virtual Fedora Activity Day today Friday July 8th, at 14:00UTC (10:00 Eastern Daylight Time). The purpose of this session is to co-ordinate the bootstrap of F15 hardfp (hardware floating point). Going forward, the proposal is that these remain on Fridays, and at the same time.
Last week, we succeeded in reaching a point where we have a native RPM (and therefore rpmbuild) running, and we are therefore now entering what we call "stage3" (stage1 was cross-compilation, stage2 was limited native building from the sources) in which we can build packages natively. Dennis has made some progress building python and a priority will be to get native packages built sufficient to have a python RPM. Once we have python, we then get to yum, mock, and finally Koji. At that point, we just have to rebuild everything twice more (once in rpmbuild, then use those bits in a full koji) before we can build the many more packages we will require for a self-hosted system! Lots of fun! :)
You can find a lot more detail here, along with all the pre-reqs/bits:
https://fedoraproject.org/wiki/Architectures/ARM/Fedora15_HardFP_Bootstrap_V...
That page contains links to the general instructions on (note that documentation on "stage3" is being updated, by me, at the moment - the above link has some notes sufficient for Friday, but these will be incorporated into the generic instructions I link to below):
https://fedoraproject.org/wiki/Architectures/ARM/Fedora15_HardFP_Bootstrap
Be sure you follow the instructions to use an armv7hl-YOUR_FAS_USERNAME or group name branch so that we can track who is doing what, and more easily back out changes if you/we discover a problem with your setup.
Jon.
On Fri, 2011-07-08 at 00:52 -0400, Jon Masters wrote:
We are hosting another one of our regular Fedora 15 hardfp Virtual Fedora Activity Day today Friday July 8th, at 14:00UTC (10:00 Eastern Daylight Time). The purpose of this session is to co-ordinate the bootstrap of F15 hardfp (hardware floating point). Going forward, the proposal is that these remain on Fridays, and at the same time.
As a followup, we now have a working yum installation. Next week, we will be working on support for mock. Once we have these, we can build up missing dependencies, then rebuild everything we have with rpmbuild. At that point, we can rebuild everything within mock and Koji-fyificate.
It's becoming clear that several points do need raising with FESCo: * Fedora should (IMO) institute mandatory mass rebuilds. Either every cycle, or every other cycle. I've briefly discussed with Dennis. Bootstrapping (and similar activities) are far easier with a clean set of deps, which is the case for F15. It should always be the case that we know everything builds and self-hosts through a mass rebuild per cycle. * Fedora would benefit from an explicit position on the dependency explosion we're seeing in basic packages. Without going off too far into my personal opinions on a need to respect UNIX heritage, etc. I will say that the explosion of requirements is going to be a problem for any future efforts and will get worse without guidance.
Meanwhile, enjoy working yum. Next week, working mock, hopefully.
Thanks,
Jon.
On Sat, Jul 09, 2011 at 11:45:33PM -0400, Jon Masters wrote:
It's becoming clear that several points do need raising with FESCo:
- Fedora should (IMO) institute mandatory mass rebuilds. Either every
cycle, or every other cycle. I've briefly discussed with Dennis. Bootstrapping (and similar activities) are far easier with a clean set of deps, which is the case for F15. It should always be the case that we know everything builds and self-hosts through a mass rebuild per cycle.
I agree with Jon 100%.
As folks know, I have been an ardent supporter of self-hosting since I started working with Linux (and RHL/Fedora) 12 years ago. I'm not alone in this position, and have had the help of many maintainers over the years to fix FTBFS bugs as I've uncovered and reported them - Thank You!
However, I haven't had as much time to put into that effort recently as I believe it deserves. FESCo asked me to draft a procedure [1], a task from [2] for ensuring identified FTBFS packages were blocked, which I've done. But the procedure lacks a key component - identifying, through Fedora Project-maintained efforts (and not my own private efforts), the list of pacakges that FTBFS. That could be a rel-eng mass rebuild run. That could be a stand-alone rebuild effort. I'm not going to dictate. I have had some interest from individuals asking how they could help, but they seemed to be daunted by the need for a good deal of builder resources to do a mass rebuild in a reasonable amount of time. And unfortunately, I'm not in a position to put the builders I scrounged up on the public internet for use.
If self-hosting and reliable package building is important to you, please chime in with ideas for how we can make this a standard part of the Fedora release process.
[1] https://fedoraproject.org/wiki/Deprecate_FTBFS_packages [2] https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets
Thanks, Matt
-
Jon Masters -
Matt Domsch