Mailinglist Archive: opensuse-buildservice (100 mails)

< Previous Next >
Re: [opensuse-buildservice] It is not possible to register an account.
  • From: Graham Anderson <graham.anderson@xxxxxxxxx>
  • Date: Sun, 06 May 2012 01:16:07 +0200
  • Message-id: <4382916.0EDXzSfZDL@excession>
On Sunday 06 May 2012 02:19:02 Eugene K. Goleshev wrote:
I've taken the source code from GitHub
(https://github.com/openSUSE/open-build-service.git), because if I'm not
mistaken, there are no other options to get it. OBS version must be 2.3.

I don't want to speak for the OBS developers but I would imagine you can get a
working 2.3.x version image from the OBS home page:

http://www.open-build-service.org/download/

I think you might have inadvertantly built a development version from the main
dev git tree. I have personally had great success using the raw images and
writing those to my desired VM volumes. After the image writing, you can
continue to update your OBS server and workers from the pre-configured
repositories using the standard zypper and/or yast cli tools.

If you need to install OBS 2.3.x without using an image, then I'm not the man
to ask and I'll defer to the advice I'm sure the OBS devs can offer you.

Could I also please ask you not to use URL shortener/redirecter style URLS
if posting to the list, it made me somewhat uneasy to follow the link and
I'm sure some others felt the same way. Since email lists can be verbose
anyway, I don't think anyone would mind if you posted the long URL.

I'm sorry. It will not happen again.

Oh it's no problem, it's just more likely someone will follow your link if
it's not obfuscated, and there's no limit on text string size of any form on
the mailing list. If you have a script that does short url replacement its not
really a problem. I was more commenting on human nature being suspicious of
short url type links on a mailing list.


Cheers the noo,
Graham
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups