On 02/19/2011 11:02 AM, js wrote:
Le 19/02/11 20:46, Lamar Owen a écrit :
On Saturday, February 19, 2011 11:09:43 am js wrote:
If yes, when a member find the problem, he can upload the srpm with the patch and let you rebuild it on a "genuine" centos.org
I think you missed Johnny's earlier point: the SRPM should not need patching to build, and in fact except for those packages that have to be patched to remove trademarks the CentOS SRPMs aren't patched in order to build; the build system is patched.
Hello, I'm curious how you can patch the build system.
In other words, a patched SRPM won't (and shouldn't!) be accepted; a pointer to what is needed to make a package build correctly might be. The goal is to put vanilla Red Hat SRPMS in and get CentOS binary RPMs out without patching the SRPM in any way, shape, or form (again, except for trademarks/artwork/branding). I took that as axiomatic until seeing Johnny's post this morning, and then the light came on that some people simply aren't understanding what I 'just knew' all along.
I don't remember (I think it was for Centos4 I think), but Centos fix a bug that was present in RHEL4; So ... sometimes you have no choice; you need to add a patch and hope it will no have consequences.
And at this point, I don't think any of the CentOS gurus (there are more than one) need a whole lot of help in the C6 buildsystem (I reserve the right to be wrong should a CentOS core dev say so), and the C5 and C4 buildsystems are in maintenance mode. For C6 it's a matter of churning through the build and tweaking the build scripts (or order, or buildhost package versions, or whatnot).
Johnny asked for some specific help with the updates for C4u9 (I really don't like the point version notation, since upstream doesn't use that; you can't go to Red Hat and order 'RHEL 4.9' for instance; you order RHEL4, and get update 9's packages through RHN). There is a case where some grunt work is needed that could genuinely help C4 get its updates faster, but I guess that's not 'glamorous' enough for people....
That make sense, So Centos, because of that, need to be like it is today... because this is only a "perfect clone of RHEL" :-/
but it will be very useful to be able to reproduce the build env anyway; seems to be a recurrent request.
The build environment is a staged install of CentOS. And mock. Every buildroot is created with a command to mock.
Here is an example scripts that I use to build "staged" extra's stuff for CentOS5:
http://people.centos.org/hughesjr/buildsystem/
You will notice there is nothing particularly special about any of that.
It just uses a local file:\ dir in the config, there is a createrepo in the build script between packages if it builds successfully.
The cfg files are the mock configs, the other files are the build scripts (the generate script creates some "lock files" in a list directory so we can have more than one machine build against the same directory of SRPMS. It orders them in reverse date order (build oldest file first).
There is no magic here.
Once built ... we use the tmverifyrpms against it from here:
http://mirror.centos.org/centos-4/4/build/distro/
The RPM either passes or fails the link test, the files test, and the size test ... if it fails, we figure out why and fix it.
Not sure what else you are looking for.