Jim Perrin wrote:

On 12/19/05, Karanbir Singh mail-lists@karan.org wrote:

...

Connie Sieh wrote:

...

Centos-devel,

Do you have scripts/code to harvest RedHat SRPMS for errata? Rebuild the .src.rpms and then send out email with the "technical" details included?

Trying to automate our release system more than it is now.

Thanks

-Connie Sieh

Scientific Linux Developer

Hi Connie,

We are actually working on something of this nature ourselves.

--

Would it be considered heresy to suggest combining forces on this one?

sure, we could - its not really a very long drawn out process - if SciLinux already have something that does some part of the job, we can pickup and grow from there ?

We need to start with this as we only have our developer for 1 month. He has already written some code for this project.

I see 3 main areas, some of these we have more done than others.

1. a) Determine if there is a new errata b) Download description of errata c) Download .src.rpm

2. Build rpm out of .src.rpm

3. a) Populate ftp/http areas with new errata b) Send mail to mailing list containing description and rpms updated.

I think we both already have item 2. We currently do item 1 manually. The populate part of item 3 we have automated along with the list of rpms updated. We manually do the descriptions.

So our work will focus on item 1 parts a,b,c and item 3 part b.

Have you done any of this work yet?

Is there someother place where we should be having these discusions.

-Connie Sieh On Mon, 19 Dec 2005, Connie Sieh wrote:

On Mon, 19 Dec 2005, Jim Perrin wrote:

...

On 12/19/05, Karanbir Singh mail-lists@karan.org wrote:

...

Connie Sieh wrote:

...

Centos-devel,

Do you have scripts/code to harvest RedHat SRPMS for errata? Rebuild the .src.rpms and then send out email with the "technical" details included?

Trying to automate our release system more than it is now.

Thanks

-Connie Sieh

Scientific Linux Developer

Hi Connie,

We are actually working on something of this nature ourselves.

--

Would it be considered heresy to suggest combining forces on this one?

Not as far as we are concerned. I think Troy talked to some of the CentOS developers at the February Linux World in Boston about working together on some projects.

...

-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel

-Connie Sieh _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel

On Tue, 20 Dec 2005, Bogdan Costescu wrote:

On Tue, 20 Dec 2005, Connie Sieh wrote:

...

I see 3 main areas, some of these we have more done than others.

Sorry to come late into this thread. I think that something similar is already implemented for TaoLinux:

ftp://taolinux.org/pub/taolinux/tmtools

These tools seem to be mostly for making new build trees and then rebuilding them. Also for updating the trees for the quarterly Updates. It does not seem to have code to handle the potential daily errata.

So based on my prior item list, it does item 2.

Thanks for the link, I already use the CentOS verify scripts but will now use the ones in here too along with a couple other utils in there.

-Connie Sieh

On Tue, 2005-12-20 at 12:54 -0600, Johnny Hughes wrote:

On Tue, 2005-12-20 at 11:40 -0600, Connie Sieh wrote:

...

On Tue, 20 Dec 2005, Bogdan Costescu wrote:

...

On Tue, 20 Dec 2005, Connie Sieh wrote:

...

I see 3 main areas, some of these we have more done than others.

Sorry to come late into this thread. I think that something similar is already implemented for TaoLinux:

ftp://taolinux.org/pub/taolinux/tmtools

These tools seem to be mostly for making new build trees and then rebuilding them. Also for updating the trees for the quarterly Updates. It does not seem to have code to handle the potential daily errata.

So based on my prior item list, it does item 2.

Thanks for the link, I already use the CentOS verify scripts but will now use the ones in here too along with a couple other utils in there.

I currently have something that monitors the SRPM directory and tries to build anything new that it sees (unless it is a package that is marked as a manual build).

This is not really production grade, but I would be happy to send you what I have.

Let me try to put it together in a tar file with the build directory.

OK, here is the file: http://centos.hughesjr.com/testing/autobuilder.tgz

all the directories would reside in a user's home directory ... and /home/updatecentos in each script would need to change to the user's home directory.

the file that gets called to start it all is ~/bin/getupdates_wrapper

this is from my x86_64 autobuilder user named updatecentos

like I said before ... this is WorksForMe and not production grade :)

I can work on this to make it one script and not several with lots of repeated code.

---- Johnny Hughes

On Tue, 20 Dec 2005, Tru Huynh wrote:

Hello :P

On Tue, Dec 20, 2005 at 11:17:12AM -0600, Connie Sieh wrote:

...

We need to start with this as we only have our developer for 1 month. He has already written some code for this project.

I see 3 main areas, some of these we have more done than others.

a) Determine if there is a new errata b) Download description of errata c) Download .src.rpm

2. Build rpm out of .src.rpm

2.1 compare the resulting rpms against the genuine one? (that is the worst part of the QA check from my point of view)

Yes, the verify is not fun. That is why I will try to use both the CentOS and the TAO script.

-> manually downloading the $arch.rpm :( 2.2 rpm signing

...

a) Populate ftp/http areas with new errata b) Send mail to mailing list containing description and rpms updated.

I think we both already have item 2. We currently do item 1 manually.

1 (a,b,c) can be triggered by the RHSA's email 1.c can be also done by mirroring updates.redhat.com and push the new src.rpm to the build process.

Issue with just looking at the mirrors is that RedHat ocasionally puts in a bugfix errata in the updates ftp area even though it is NOT bugfix(Update) time.

It is cleaner just to get the src.rpm info from the RHSA announcment.

...

The populate part of item 3 we have automated along with the list of rpms updated. We manually do the descriptions.

...

So our work will focus on item 1 parts a,b,c and item 3 part b.

Have you done any of this work yet?

Centos-3 (x86/x86_64) speaking :) no but the the only scripted feature is the pre-filled email from the $arch.rpm. I am sure the CentOS-4 have more progress on this.

Is the pre-filling code available?

...

Is there someother place where we should be having these discusions.

#centos-devel ?

Was there a while back, kind of quiet. Will try again.

Cheers,

Tru

Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

-Connie Sieh

On Tue, 20 Dec 2005, Johnny Hughes wrote:

On Tue, 2005-12-20 at 13:44 -0600, Connie Sieh wrote: [snip]

...

Issue with just looking at the mirrors is that RedHat ocasionally puts in a bugfix errata in the updates ftp area even though it is NOT bugfix(Update) time.

It is cleaner just to get the src.rpm info from the RHSA announcment.

We (CentOS) release those when RH does.

Do you collect the info from RH manually or do you have a program that does it for you? You include this info in your email message about the new errata. Is that done manually or do you have scripts?

-Connie Sieh