On Mon, Oct 16, 2006 at 07:11:47PM -0400, Aaron Bockover wrote:

So my questions:

a) Any reason why libstdc++ can't be pulled down? (would be nice if this were fixed)

This may be a bug in the API that prevents downloading packages with '+' in the name. Andreas?

b) Why is it taking 4 hours to start building libipoddevice in the build service? What if it comes back failed after it's finally started to build - do I have to wait another 4 hours for my second try?

No, I think the build service was just under heavy load at that time. You don't have to wait 4 hours for every, this would indeed be insane. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Tuesday 17 October 2006 01:11 schrieb Aaron Bockover: ..

I first tried to build locally using osc:

osc build SLE_10 i586 libipoddevice.spec

This started pulling down (slowly) SLE packages, but failed here:

Error: No more mirrors to try. Failed to retrieve libstdc++-4.1.0-28.4.i586.rpm from the following locations (in order): file:///var/tmp/osbuild-packagecache/SUSE:SLE-10/standard/i586/libstdc ++-4.1.0-28.4.i586.rpm/ http://software.opensuse.org/download/SUSE:SLE-10/standard/i586/libstdc ++-4.1.0-28.4.i586.rpm

this is correct, because SLE_10 is not public downloadable.

http://api.opensuse.org/rpm/SUSE:SLE-10/standard/_repository/i586/libstdc++

This should work, because it does download from the build service as fallback.

I then committed libipoddevice to the "Banshee" project and clicked "Trigger Rebuild" in the web interface. It has been scheduled there for almost 4 hours I think.

yes, we run only with 25% of our build hosts atm and lots of jobs have been triggered.

So my questions:

a) Any reason why libstdc++ can't be pulled down? (would be nice if this were fixed)

it should work via the api, please make a bugreport if it does not.

b) Why is it taking 4 hours to start building libipoddevice in the build service? What if it comes back failed after it's finally started to build - do I have to wait another 4 hours for my second try? This seems like an insane amount of time - and libipoddevice is a very simple package to build. I'm worried that when I actually get to Banshee itself, the process will take hours and hours and hours.

well, this will always depend on the load of the service. However, it does make sense to do local builds always for working on a package. It will work in the build service, when it does work locally (because the build should happen in exactly the same way).

c) Maybe there's something else I should be doing altogether? I'm completely new to the build service and am mostly just poking around, although at the same time I would very seriously like to host Banshee's builds inside the build service. I'm dead set on providing easy to use and updated packages for Banshee for SUSE/SLED at the same time I release my tarballs.

You found a bad time for starting ;) Usually we have more hardware running and less jobs. However, we are still in development phase, so we do not guarantee anything atm. I hope we get some more hardware running during the week. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org