[opensuse-buildservice] local obs behind a proxy
Hi, recognized that obs has no proxy support. :( So I can't use linking prj via openSUSE.org: has someone a solution for this ? Kind Reagrds Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, I try to be more clear. I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid) So is there a possibility to tell obs to use a '$http_proxy' ? Thank you Chris Christian schrieb:
Hi,
recognized that obs has no proxy support. :( So I can't use linking prj via openSUSE.org:
has someone a solution for this ? Kind Reagrds Chris
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
oups forgot the list : "Hi Very wired, when i wrote MonoOSC, some user ask me to add proxy (client side) feature, so i guess OBS support proxy ?" sorry christian for the double message 2010/3/24 Christian <chris@computersalat.de>:
Hi,
I try to be more clear.
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
Thank you Chris
Christian schrieb:
Hi,
recognized that obs has no proxy support. :( So I can't use linking prj via openSUSE.org:
has someone a solution for this ? Kind Reagrds Chris
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- Cordially. windows take you more($), Linux give you more!! Political Power cannot be wisdom! Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 24/03/10 13:37, Petit Eric wrote:
oups forgot the list : "Hi Very wired, when i wrote MonoOSC, some user ask me to add proxy (client side) feature, so i guess OBS support proxy ?"
Works here with 'https_proxy' and 'http_proxy' set. An older version of osc used to delete these env variables assuming that urllib2 didn't support proxies (and I had locally modified osc to remove this code), but this seems to no longer be the case. John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
On 2010-03-24 15:56:25 +0000, John Beranek wrote:
On 24/03/10 13:37, Petit Eric wrote:
oups forgot the list : "Hi Very wired, when i wrote MonoOSC, some user ask me to add proxy (client side) feature, so i guess OBS support proxy ?"
Works here with 'https_proxy' and 'http_proxy' set. An older version of osc used to delete these env variables assuming that urllib2 didn't support proxies (and I had locally modified osc to remove this code), but this seems to no longer be the case.
Chris is *not* talking about the client side. he is talking about proxy support in the obs backend code, which is written in perl. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 24, 2010 at 11:29:43AM -0500, Marcus Rueckert wrote:
On 2010-03-24 15:56:25 +0000, John Beranek wrote:
On 24/03/10 13:37, Petit Eric wrote:
oups forgot the list : "Hi Very wired, when i wrote MonoOSC, some user ask me to add proxy (client side) feature, so i guess OBS support proxy ?"
Works here with 'https_proxy' and 'http_proxy' set. An older version of osc used to delete these env variables assuming that urllib2 didn't support proxies (and I had locally modified osc to remove this code), but this seems to no longer be the case.
Chris is *not* talking about the client side. he is talking about proxy support in the obs backend code, which is written in perl.
My suggestion: tsocks It may be sort of involved to set up, but tsocks is a transparent socks forwarder. It intercepts socket calls and transparently forwards the connection via a socks proxy. I have had success using tsocks to forward both 'osc' as well as 'git' and a few other network things. I think it would likely work ok with the obs server, just modify the init scripts for the services. You can test your setup with osc before modifying the server bits. Getting a socks proxy is the difficult part. My personal solution is to use an ssh tunnel and the built-in socks proxy support in ssh. -- Michael
Perhap's it's time to write a nice perl GUI to setup and check param of OBS :-) (i don't speak perl) 2010/3/24 Michael E Brown <Michael_E_Brown@dell.com>:
On Wed, Mar 24, 2010 at 11:29:43AM -0500, Marcus Rueckert wrote:
On 2010-03-24 15:56:25 +0000, John Beranek wrote:
On 24/03/10 13:37, Petit Eric wrote:
oups forgot the list : "Hi Very wired, when i wrote MonoOSC, some user ask me to add proxy (client side) feature, so i guess OBS support proxy ?"
Works here with 'https_proxy' and 'http_proxy' set. An older version of osc used to delete these env variables assuming that urllib2 didn't support proxies (and I had locally modified osc to remove this code), but this seems to no longer be the case.
Chris is *not* talking about the client side. he is talking about proxy support in the obs backend code, which is written in perl.
My suggestion: tsocks
It may be sort of involved to set up, but tsocks is a transparent socks forwarder. It intercepts socket calls and transparently forwards the connection via a socks proxy. I have had success using tsocks to forward both 'osc' as well as 'git' and a few other network things. I think it would likely work ok with the obs server, just modify the init scripts for the services. You can test your setup with osc before modifying the server bits.
Getting a socks proxy is the difficult part. My personal solution is to use an ssh tunnel and the built-in socks proxy support in ssh.
-- Michael
-- Cordially. windows take you more($), Linux give you more!! Political Power cannot be wisdom! Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ). Feedback, remarks, objections etc. are always welcome:) Marcus
On 25/03/10 16:45, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Why not just 'use LWP::UserAgent'? John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
On 2010-03-25 16:59:12 +0000, John Beranek wrote:
On 25/03/10 16:45, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Why not just 'use LWP::UserAgent'?
The backend provides its own modules/framework for doing requests etc. so using something like that won't help/work. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Mar 25, 2010 at 04:59:12PM +0000, John Beranek wrote:
On 25/03/10 16:45, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Why not just 'use LWP::UserAgent'?
Because it's not event based? I.e. we can't do a big select() on all file descriptors with it. M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 25/03/10 17:13, Michael Schroeder wrote:
On Thu, Mar 25, 2010 at 04:59:12PM +0000, John Beranek wrote:
On 25/03/10 16:45, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Why not just 'use LWP::UserAgent'?
Because it's not event based? I.e. we can't do a big select() on all file descriptors with it.
OK, that does seem to be a fundamental limitation then, I'll go back to sleep... John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
On 25/03/10 17:24, John Beranek wrote:
On 25/03/10 17:13, Michael Schroeder wrote:
On Thu, Mar 25, 2010 at 04:59:12PM +0000, John Beranek wrote:
On 25/03/10 16:45, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Why not just 'use LWP::UserAgent'?
Because it's not event based? I.e. we can't do a big select() on all file descriptors with it.
OK, that does seem to be a fundamental limitation then, I'll go back to sleep...
The only thing from LWP that seems vaguely applicable is Net::HTTP::NB[1] but that hardly provides much beneficial abstraction over what you already have. John. [1] http://search.cpan.org/~gaas/libwww-perl-5.834/lib/Net/HTTP/NB.pm -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
On Thu, Mar 25, 2010 at 05:45:54PM +0100, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
- I would prefer a proxy setting for each remote host, but maybe there's no real life use case for it. - I don't like your BSWatcher changes, that looks pretty hackish ;-) Otherwise, nice work! Cheers, Michael -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg 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
On 2010-03-25 18:19:38 +0100, Michael Schroeder wrote:
On Thu, Mar 25, 2010 at 05:45:54PM +0100, Marcus Hüwe wrote:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
- I would prefer a proxy setting for each remote host, but maybe there's no real life use case for it. Ok.
- I don't like your BSWatcher changes, that looks pretty hackish ;-)
Hehe yes I was unsure how to implement it. The initial idea was to add something like a "rpc_proxy_connect_send" and a "rpc_proxy_connect_recv" handler but then I realized that this would lead to some code "duplication" (or we move some parts of "rpc_recv_handler" and "rpc_send_handler" into new functions). At least in the SSL case we need one handler for writing the CONNECT and another one for reading the response because all other approaches would be contrary to the "non-blocking" strategy in BSWatcher or am I wrong? Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
Marcus
-- 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
On Thu, Mar 25, 2010 at 06:20:25PM +0100, Adrian Schröter wrote:
Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
Eeek. I absolutely hate it when applications look into the environment... Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg 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 Donnerstag, 25. März 2010 18:31:31 schrieb Michael Schroeder:
On Thu, Mar 25, 2010 at 06:20:25PM +0100, Adrian Schröter wrote:
Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
Eeek. I absolutely hate it when applications look into the environment...
and I hate it when they ignore system defaults and you need to manual configure each single application again ;) -- 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
Am 25.03.2010 18:36, schrieb Adrian Schröter:
Am Donnerstag, 25. März 2010 18:31:31 schrieb Michael Schroeder:
On Thu, Mar 25, 2010 at 06:20:25PM +0100, Adrian Schröter wrote:
Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
Eeek. I absolutely hate it when applications look into the environment...
and I hate it when they ignore system defaults and you need to manual configure each single application again ;)
Using a config file to overwrite the envirnoment settings would be still nice, at least when it comes to proxy auth. :) And for some reasons I don't want to set a proxy in the environment. Regards, Reik -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, is this patch by Marcus OK ? Or should I wait for an official released Obs-server RPM ? or is it already in git ? Thanks Reik Keutterling schrieb:
Am 25.03.2010 18:36, schrieb Adrian Schröter:
Am Donnerstag, 25. März 2010 18:31:31 schrieb Michael Schroeder:
On Thu, Mar 25, 2010 at 06:20:25PM +0100, Adrian Schröter wrote:
Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe:
On 2010-03-24 14:33:01 +0100, Christian wrote:
I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
Eeek. I absolutely hate it when applications look into the environment...
and I hate it when they ignore system defaults and you need to manual configure each single application again ;)
Using a config file to overwrite the envirnoment settings would be still nice, at least when it comes to proxy auth. :) And for some reasons I don't want to set a proxy in the environment.
Regards, Reik
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/25/2010 at 18:20, Adrian Schröter<adrian@suse.de> wrote: Am Donnerstag, 25. März 2010 17:45:54 schrieb Marcus Hüwe: On 2010-03-24 14:33:01 +0100, Christian wrote: I want to use the 'remoturl' feature. (added PRJ openSUSE.org) And my local obs is not able to connect to 'api.opensuse.org' directly. Access to internet is only allowed via proxy (e.g. squid)
So is there a possibility to tell obs to use a '$http_proxy' ?
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
great, but I would prefer if the setting would simply use the enviroment variables by default.
Proper guessing of proxy configuration is done using libproxy nowadays :) /me is now running. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Dominique, Dominique Leuenberger schrieb:
Proper guessing of proxy configuration is done using libproxy nowadays :) /me is now running. do you have a patch for me ?
Dominique Chris
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Marcus, Marcus Hüwe schrieb:
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy. our $proxy = 'http://<ip>:<port>' should be our $proxy = 'http://<ip>:<port>/' otherwise you will get "bad url"
The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:) i tried your patch with latest stable build (1.7.2).
and build is then failing on worker with: fetching sources, packages, 404 remote error: Bad arg length for Socket pack_sockaddr_in, length is 0, should be 4 at /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/Socket.pm line 386. build failed, send back logfile... Thank you Chris
Marcus
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Marcus, can you help to get this running ? Thanks Chris Christian schrieb:
Hi Marcus,
Marcus Hüwe schrieb:
I just wrote a small patch which adds basic http proxy support to the backend. To enable it add 'our $proxy = "http://<ip>:<port>";' to the BSConfig.pm file. Afterwards all remoteurl requests will be sent to proxy.
our $proxy = 'http://<ip>:<port>' should be our $proxy = 'http://<ip>:<port>/' otherwise you will get "bad url"
The current implementation doesn't support proxy-authorization yet but it should be trivial to implement it (before concentrating on those details I want to know if the current code is ok:) ).
Feedback, remarks, objections etc. are always welcome:)
i tried your patch with latest stable build (1.7.2).
and build is then failing on worker with:
fetching sources, packages, 404 remote error: Bad arg length for Socket pack_sockaddr_in, length is 0, should be 4 at /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/Socket.pm line 386. build failed, send back logfile...
Thank you Chris
Marcus
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-04-14 14:38:29 +0200, Christian wrote:
i tried your patch with latest stable build (1.7.2).
and build is then failing on worker with:
fetching sources, packages, 404 remote error: Bad arg length for Socket pack_sockaddr_in, length is 0, should be 4 at /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/Socket.pm line 386. build failed, send back logfile...
Hmm is everything else working or do you get similar errors in the scheduler log etc.? I'm not quite sure if the error has something todo with the patch. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hmm is everything else working or do you get similar errors in the scheduler log etc.? I'm not quite sure if the error has something todo with the patch.
Hi Marcus, Marcus Hüwe schrieb: problem solved with 1.7.3. Thank you Chris
Marcus
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (10)
-
Adrian Schröter -
Christian -
Dominique Leuenberger -
John Beranek -
Marcus Hüwe -
Marcus Rueckert -
Michael E Brown -
Michael Schroeder -
Petit Eric -
Reik Keutterling