[CentOS-devel] Interested in IA64 build.

Lamar Owen lowen at pari.edu
Tue Oct 9 22:46:47 EDT 2012


On Oct 8, 2012, at 9:28 AM, Lamar Owen wrote:

> ...but in the meantime I'll put the builder to work getting the 5.8 changed/new packages built.  
> 
> Again, my first order of business is to get up to a 5.8, even if that 5.8 is not fully upstream binary compatible.  

And, well, after 34 hours, 9 minutes, and 53 seconds (with an average of 213% CPU usage; having multiple CPUs does help some), the 5.8 GA tree is built, with no build failures that weren't expected (final buildstatus run:

[lowen at winterstar ~]$ buildstatus58
No IA64 target: 	5
No Package Found: 	4
Scratch total:		9
Built binaries:		991
Built SRPMS:		237
[lowen at winterstar ~]$ 

and all the No Package Found errors are due to requirements that aren't available in IA64 form...)  Cool, the first build run with no real build failures.  Nice.

And so, my first goal is met: I have a yummable 5.8 tree (through steps; I have a reasonably full 5.5 tree, and the 5.6, 5.7, and 5.8 incrementals).  The test upgrade on my Altix 3200 demonstrated yet again how my misstep with a 'dotless' %dist tag is going to continue to bite me, and how that I need to do a full rebuild at some point. (yum reinstall \* doesn't help here, since the dist tag belongs to the release, and reinstall only replaces identical NEVRA with identical NEVRA, so the older disttag doesn't get replaced, and the older disttag is leftover from the interim bootstrap tree..... argh).

But, after correcting the one issue, I then did the standard two-step (yum upgrade kernel glibc rpm yum; yum upgrade) after editing the repo files (and renaming CentOS-Vault.repo to CentOS-Vault.repo.rpmsave, since there are no ia64 files in the Vault....), and some waiting ( 19:34.69, to be exact), and a reboot later, I have:

CentOS release 5.8 (Final)
Kernel 2.6.18-308.el5 on an ia64

...

The next step is step building the 5.8 updates, probably in %{BUILDTIME} order as the first attempt, and getting a fully updated system.  given some of the substantial changes since 5.8 GA (like Firefox 10, for one) the updates will likely take some time, and I'm honestly not sure if I should just try to rebuild the latest (although that's essentially what I've done up until now, for each point release)).  I haven't yet looked at the full contents of the 5.8/updates/SRPMS dir, since I've been 'blinders on get 5.8 GA built' for the last two and a half weeks (of spare time work; the buildbox has churned essentially 'round the clock building, but my time has been in relatively short spurts getting things ready to kick off).  So that's a task for tomorrow.

Then I'll upgrade my SLC 5.4 buildhost, now that the bulk of the initial grunt work is done.  And I'll make sure to backup all the repos, logs, and other items prior to the upgrade.....

A full rebuild, using the automated QA stuff for QA (neat logging to the #centos-devel IRC channel!), and binary compatibility checking is in my long-term plans; short term there are the straggler packages from 5.5 and 5.6, some third party packages, and some third party whole repos to work on for packages I need on these boxes, like xrdp, and some manual QA of packages as I use the boxes, since they are still in the 'commissioning' phase.  And I have a 20 CPU box to do a scratch install on, once I fix its hardware issues, so actually getting an installable tree and making an installable ISO would be a nice thing, and another skillset to learn a little about.....

But the first major milestone is met, and that's cool.



More information about the CentOS-devel mailing list