Re: [opensuse-buildservice] Build Service Project Cleanup Round

Small top-post heads up. Since we were not able to agree how to deal with removing the repositories, I will just disable build for the projects this week. This can get reverted in any case, nothing gets lost. (except for the projects where people wrote me not do it of course) But I really would like also free our stage server and the mirrors with not used packages also later .... I think this is acceptable so far for everybody. bye adrian Am Montag, 22. Juni 2009 17:11:48 schrieb Greg Freemyer:

On Mon, Jun 22, 2009 at 5:43 AM, Adrian Schröter wrote:

...

Hello,

we got more than 6500 projects since the start of the opensuse.org Build Service instance (plus the projects which got removed again by their owners). These projects contain more than 13000 repositories, which get need to get in sync by our service.

This takes obviously resources on the server side and quite a number of these projects are not touched since a while. So I assume they are not needed anymore.

So I think it is a good idea to free the resources from these projects and give it to us active people :)

This will basically affect all projects, where no source changes happened since 1 year or more.

I'm afraid that seems too aggressive.

As an example I needed a little used package called open2300 for opensuse 10.3 a few months ago. It was last fully released in 2005. I doubt the source has been edited in a long time. It links to MySQL so I think that means it should be rebuilt from time to time?

I found it on that build service at https://build.opensuse.org/package/show?package=open2300&project=home%3Afse idel

And as you can see the 10.3 version still builds. On the other hand the 11.0 and 11.1 versions do not.

Certainly if you totally dropped it because it had not seen any activity in a while I would have not found it. Or are you just proposing leaving it published in its last built state?

Possibly even more important, I assume if you dropped it I would not have even found the package when doing a search. Even if the builds are broken, currently I can search for a package, grab the specfile, etc. and create my own project with that as a starting point. Otherwise I would have to start from scratch on the specfile.

In fact, in this case I pulled open2300 from svn and built my own set of projects. Having the several year old version around to leverage simplified things somewhat.

Thus if I understand your proposal, I don't care for it.

I would prefer:

If a package builds, keep building it regardless.

If a package fails to build, only try again if there has been a source change.

If a package fails, have a new search option that allows me to search for them so I can evaluate using that package as a launch point for creating a new subproject.

Thanks Greg

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org