Mailinglist Archive: opensuse-buildservice (258 mails)

< Previous Next >
Re: [opensuse-buildservice] Linking two (private) OBS servers at different sites.
  • From: Robert Xu <robxu9@xxxxxxxxx>
  • Date: Tue, 10 Aug 2010 12:37:44 -0400
  • Message-id: <AANLkTik8oF-qnHrQoWSSg8K8sCsb-eEn36utF_2Rb_E7@xxxxxxxxxxxxxx>
On Tue, Aug 10, 2010 at 05:29, Adrian Schröter <adrian@xxxxxxx> wrote:
On Tuesday 10 August 2010 03:23:38 Robert Xu wrote:
On Mon, Aug 9, 2010 at 20:07, Troy Telford <ttelford.groups@xxxxxxxxx> wrote:
Is there a guide anywhere that talks about how to link two different OBS
servers, so that when a project/package that is on one server can be
linked to
on another server (separated by distance and low-bandwidth; so it makes
to send source code instead of keeping the package mirror constantly

I've seen the example where (openSUSE 11.3's obs packages) have
/srv/obs/packages has

I've tried modifying that example, and set it to point between the two
servers, and had some success; I've linked some packages and when the
on one system is updated, the changes transfer to the other.  I can
linkpac, aggregate pac, for the most part.

However, if I look in /srv/obs/log/scheduler_arch.log, I see the following
repeated endlessly:

2010-08-09 19:02:13: waiting for an event...
retrying watcher for
setting up watcher for
2010-08-09 19:03:16: waiting for an event...
response from watcher for
400 remote error: Bad Request
retrying in 60 seconds

Any ideas on what I might be missing?

Not really, I would either add some debug code to print the request or look
in the logs
of the remote instance.

You need to enable anonymous access.
Otherwise, the API will reject everything w/o an auth.

Erm, no, anonymous access is only for webui. /public is independend of that.

Really? Because it doesn't seem that way to me... I just pointed my
browser to the API/public and it asked for credentials.

later, Robert Xu
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >