On 07/06/10 08:40, Adrian Schröter wrote:
On Donnerstag, 3. Juni 2010 20:47:11 Marcus Hüwe wrote: [snip]
Anyway I just committed it.
No, it would error out, because the proxy object does not exist. It is fixed now. (there were also some typos, so this code could never have worked).
Hmm, did this proxy code get into OBS 2.0? I've got a local OBS Appliance behind a corporate proxy that I just 'zypper update'd to: obs-common-2.0-2.1.i586 obs-server-2.0.0-5.2.i586 obs-worker-2.0.0-5.2.noarch obs-api-2.0.0-5.2.i586 And if I configure a proxy in BSConfig.pm like: our $proxy = "http://proxy.example.com:8080"; The scheduler is still having trouble accessing api.opensuse.org. From /srv/obs/log/scheduler_i586.log: response from watcher for https://api.opensuse.org/public setting up watcher for https://api.opensuse.org/public, start=12813181 2010-06-16 13:17:53: waiting for an event... response from watcher for https://api.opensuse.org/public 502 remote error: Bad Gateway retrying in 60 seconds 2010-06-16 13:18:58: waiting for an event... retrying watcher for https://api.opensuse.org/public setting up watcher for https://api.opensuse.org/public, start=12813181 2010-06-16 13:19:58: waiting for an event... response from watcher for https://api.opensuse.org/public 504 remote error: Gateway Time-Out retrying in 60 seconds 2010-06-16 13:22:59: waiting for an event... Ah, however, it seems I was premature to think the build wasn't working due to this. My local OBS has just built a package using a remote repository! So, I guess the scheduler is still occasionally trying to contact api.opensuse.org without a proxy in particular cases? Cheers, John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org