On 07/09/2009 07:05 AM, Sascha Thomas Spreitzer wrote:

Good morning hackers,

me and others tried to form a special interest group and didn't succeed well. So im starting my own rebuild now.

how did you work that out ? there are two parallel builds going on at the moment! also, you missed all three meetings so far :)

I have access to a z/VM guest and some hercules with 1k mips, too Ill inform you next time the CentOS 5.3 basic package set has been created.

Id be thankful if the final version could be mirrored upstream.

Since there is already a 'centos' version building now ( one is upto 5.1+updates, the other is directly targetting 5.3 ) - the official one will come from there, however it would be good to have another one to check against. So dont hold off, got for it.

- KB

On Thu, 9 Jul 2009, Sascha Thomas Spreitzer wrote:

me and others tried to form a special interest group and didn't succeed well. So im starting my own rebuild now. I have access to a z/VM guest and some hercules with 1k mips, too Ill inform you next time the CentOS 5.3 basic package set has been created.

I've been at this task for a while now. The initial 'stupid' rebuilder is done; the smarter version is making a new pass through the package set, and the chrooted builder is next on tap once I have completed getting all needed pieces for the bootstrapping of the chroot elements.

I think one of the other project members also has a binary transaction set, but his Z instance is not continuously available to him, so it is harder to 'tweak' the build process. Looking ahead in my mailspool, I see that KB has chimed in

I have set up a rsyncable and FTPable export at: s390x.owlriver.net which should also presents a suitable yum target for a stanza like this (to be placed in a file in /etc/yum.repos.d/ or in /etc/yum.conf ):

[base] name=CentOS-$releasever - s390x gpgcheck=0 baseurl=ftp://s390x.owlriver.net/

--------------------------------

It is a work in progress, and the repodata may lag as much as 24 hours, as I am adding to it fairly continuously. It is space constrained. Any comments about it should come through this mailing list, as I monitor it at least every weekday.

--------------------------------

Anon FTP of the binaries is available at: s390x.owlriver.net

I do not store the SRPMs and sources locally at that machine because of space constraints, but are a simply pulled from current CentOS 4 and 5 SRPM archives as needed

--------------------------------

An rsync script might look like this:

#!/bin/sh # # rsync mirror template # edit target to taste # SRC="s390x.owlriver.net" TGT="orc_s390z" DST="/var/ftp/pub/mirror/centos/s390x/to53" [ ! -d $DST ] && mkdir -p $DST # QUIET="-q " # VERBOSE="-v -v " # the man page ' examples single quotes are deceptive # and do not work in a script's dereferencing, it seems EXCLUDE="--exclude=*debuginfo* " # # KBPS next line BW="--bwlimit=100 " # rsync -aSHP $QUIET $VERBOSE $FILTER $EXCLUDE $BW \ --delete --delete-excluded \ $SRC::$TGT/ $DST/ #

I do have some bandwidth caps on the instance as it is in donated network bandwidth from IBM

I would note that IBM has been very kind with this donation of the instance, both here, and in the 'Chiphopper' certification project for matters not directly related to CentOS, but to another FOSS project I participate in: http://www.trading-shim.org/

-- Russ herrold