[opensuse] BuildService

2007-08-13 Thread Ciro Iriarte
Anyone knows if the BuildService subscription circuit still works?, i
asked for an account weeks ago and i'm still getting "Errorcode:
unconfirmed_user".

Ciro
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse] BuildService

2007-08-13 Thread Rajko M.
On Monday 13 August 2007 05:38, Ciro Iriarte wrote:
> Anyone knows if the BuildService subscription circuit still works?, i
> asked for an account weeks ago and i'm still getting "Errorcode:
> unconfirmed_user".
>

Hi Ciro,

I would ask the same in opensuse-buildservice mail list. 

-- 
Regards,
Rajko.
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse] BuildService

2007-08-14 Thread Ciro Iriarte
2007/8/14, Rajko M. <[EMAIL PROTECTED]>:
> On Monday 13 August 2007 05:38, Ciro Iriarte wrote:
> > Anyone knows if the BuildService subscription circuit still works?, i
> > asked for an account weeks ago and i'm still getting "Errorcode:
> > unconfirmed_user".
> >
>
> Hi Ciro,
>
> I would ask the same in opensuse-buildservice mail list.
>
> --
> Regards,
> Rajko.

Thanks, i will..

Ciro
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[opensuse] Re: [opensuse-buildservice] keep previous major versions?

2007-08-13 Thread Jan Engelhardt

On Aug 13 2007 10:02, Adrian Schröter wrote:
>On Monday 13 August 2007 09:57:27 wrote Marcus Meissner:
>> Hi,
>>
>> I am getting occasional request to keep stable Wine
>> versions for some of the older releases.
>>
>> Is there a mechanism that would allow that?
>
>In general you have two options:
>
>1. You could build multiple versions of the same package. You can do this by
>   creating multiple packages in the build service in one project. For example
>   you create a "wine-1.0" package and a "wine-2.0" package.
>Inside of these workspaces, you can still use "wine.spec", which produces
>   a wine-1.0-0.i386.rpm and a wine-2.0-0.i386.rpm. The Build Service does not
>   remove old versions, if the src.rpm does still get build.
>
>   While this works nicely with the build service, your users might run into 
>   trouble since their used installer might want to update to 2.0, even when
>   they do not want this.
>
>2. To solve this, you can simply create another project, like "Wine:OLD" to
>   get a separated repository on our servers.

3. Maybe it's possible to do configure --prefix=/opt/wine-2.0 and then have
wine1 and wine2 installed side-by-side on a system.



Jan
-- 

[opensuse] From the build service lists...Re: [opensuse-buildservice] Redirector availability

2007-09-16 Thread Boyd Lynn Gerber
This is from the build service.  It is in response to a question on
opensuse.

--
Boyd Gerber <[EMAIL PROTECTED]>
ZENEZ   1042 East Fort Union #135, Midvale Utah  84047

-- Forwarded message --
Date: Sat, 15 Sep 2007 20:38:59 +0200
From: Marcus Rueckert <[EMAIL PROTECTED]>
To: Benji Weber <[EMAIL PROTECTED]>
Cc:  <[EMAIL PROTECTED]>
Subject: Re: [opensuse-buildservice] Redirector availability

On 2007-09-15 11:43:46 +0100, Benji Weber wrote:
> So the redirector has gone down /again/ this weekend.

wrong. the redirector is still working:
http://download.opensuse.org/repositories/

many people still have http://software.opensuse.org in their repository
list. that host is broken. yes. (it looks like hardware problems)

> And of course we get all the users coming asking why their package
> management isn't working while there are no suse people around to fix
> it.
>
> Having a high availability redirector is probably the single most
> important thing the project needs right now. It goes down far too
> often, and with our current strategy of adding repositories from the
> community repositories module, installation,  and YMPs using the
> redirector this means that *every openSUSE user* is without package
> management on a regular basis.
>
> This inconveniences people and damages the reputation of the
> distribution amongst users. it also means that users cannot download
> the distribution at all as there is no static fallback for
> download.opensuse.org.
>
> The fact that it always goes down at weekends is a problem too, as
> most people have jobs this is when "hobbyist" people are likely to be
> wanting to try things out etc.
>
> Given how much adding repositories is automated in 10.3 we can no
> longer rely on users distributing themselves amongst mirrors.
> Therefore I think we either need to:
>
> - Have a co-hosted redirector, with monitoring to ensure uptime in
> place for 10.3 or very soon after.

we are working on a HA setup for download.o.o already. but so far the
host is holding up pretty good. peter is doing a good job to optimize
and improve the redirector.

> - Have the build service YMP & installation/community repositories
> suggestions use alternating mirrors instead of the redirector. Whilst
> this would be suboptimal as we would lose tracking of statistics etc
> it would be better than the situation currently where everyone loses
> package management regularly.

the ymps should be using download.opensuse.org already. if not that
would be a critical bug.

darix

-- 
  openSUSE - SUSE Linux is my linux
  openSUSE is good for you
  www.opensuse.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]