On Wed, May 08, 2013 at 11:03:45AM +0200, Kuba Serafinowski wrote:

I'd like to know what has changed in 2.4 wrt Arch support. I know it was already supported a long time ago in build.o.o. If I remeber right Arch repos were too outdated to be usable, has that changed? And what is the update schedule now?

As Arch is a rolling release we should setup a cronjob that updates it every weekend.

I'd be happy to talk about it to someone who takes care of it, but I asked and no one seems to be able to tell me who is responsible.

There's no one responsible in particular, just send an email to the buildservice list if you find that something doesn't work. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wednesday 2013-05-08 14:23, Michael Schroeder wrote:

On Wed, May 08, 2013 at 11:36:40AM +0200, Michael Schroeder wrote:

...

On Wed, May 08, 2013 at 11:03:45AM +0200, Kuba Serafinowski wrote:

...

I'd like to know what has changed in 2.4 wrt Arch support. I know it was already supported a long time ago in build.o.o. If I remeber right Arch repos were too outdated to be usable, has that changed? And what is the update schedule now?

As Arch is a rolling release we should setup a cronjob that updates it every weekend.

The cronjob is now in place, we'll sync every Sunday morning. (We also synced right now.)

If we now can do cronjobs, can't the CentOS updates be imported as well on a regular basis? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, May 08, 2013 at 02:34:25PM +0200, Jan Engelhardt wrote:

On Wednesday 2013-05-08 14:23, Michael Schroeder wrote:

...

On Wed, May 08, 2013 at 11:36:40AM +0200, Michael Schroeder wrote:

...

On Wed, May 08, 2013 at 11:03:45AM +0200, Kuba Serafinowski wrote:

...

I'd like to know what has changed in 2.4 wrt Arch support. I know it was already supported a long time ago in build.o.o. If I remeber right Arch repos were too outdated to be usable, has that changed? And what is the update schedule now?

As Arch is a rolling release we should setup a cronjob that updates it every weekend.

The cronjob is now in place, we'll sync every Sunday morning. (We also synced right now.)

If we now can do cronjobs, can't the CentOS updates be imported as well on a regular basis?

I don't think we have the CentOS updates in OBS. And CentOS isn't a rolling release distribution, is it? M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, May 08, 2013 at 02:44:54PM +0200, Adrian Schröter wrote:

Frankly, I do not want these hacks. How much do we bet that this cron hack is lost when we move the server the next time?

We should finish the download on demand support. If we are not able to do that we should neither waste our time with workarounds. They will eat more time in the long run.

Does that translate to "I, Adrian, will personally finish the download on demand support in the near future"? ;-) Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wednesday 2013-05-08 14:39, Michael Schroeder wrote:

On Wed, May 08, 2013 at 02:34:25PM +0200, Jan Engelhardt wrote:

...

On Wednesday 2013-05-08 14:23, Michael Schroeder wrote:

...

On Wed, May 08, 2013 at 11:36:40AM +0200, Michael Schroeder wrote:

...

On Wed, May 08, 2013 at 11:03:45AM +0200, Kuba Serafinowski wrote:

...

I'd like to know what has changed in 2.4 wrt Arch support. I know it was already supported a long time ago in build.o.o. If I remeber right Arch repos were too outdated to be usable, has that changed? And what is the update schedule now?

As Arch is a rolling release we should setup a cronjob that updates it every weekend.

The cronjob is now in place, we'll sync every Sunday morning. (We also synced right now.)

If we now can do cronjobs, can't the CentOS updates be imported as well on a regular basis?

I don't think we have the CentOS updates in OBS. And CentOS isn't a rolling release distribution, is it?

Well, it is rolling as much as openSUSE:*:Update is. CentOS:CentOS-5 is still at 5.5 instead of 5.9. CentOS:CentOS-6 is still at 6.2 instead of 6.4. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Wed, May 08, 2013 at 03:14:52PM +0200, Jan Engelhardt wrote:

Well, it is rolling as much as openSUSE:*:Update is. CentOS:CentOS-5 is still at 5.5 instead of 5.9. CentOS:CentOS-6 is still at 6.2 instead of 6.4.

I currently don't really want to support update repos, as - they tend to grow over time - they need to be kept in sync But I agree with you that we should always have to latest "minor" release in our CentOS repos, i.e. 5.9 and 6.4. I'll update the repos next week. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mittwoch, 8. Mai 2013, 16:14:33 wrote Hector Oron:

Hello,

2013/5/8 Adrian Schröter :

...

We should finish the download on demand support. If we are not able to do that we should neither waste our time with workarounds. They will eat more time in the long run.

What needs to be done on that area? Automate download on demand? Any ideas on how to proceed to implement that?

In short the following tasks need to be done: * The api should allow accept DoD URLs as part of the repository definition in project meta xml. * Some background process should monitor the URLs and update package meta data when needed. Either a backend cron job, or maybe more efficient, some api delayed job. * The DoD package update code should also remove not anymore existing packages. We are happy to assist if anyone wants to work on that :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org