From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.50)
	id 1EdbY3-0002w8-2V
	for garchives@archives.gentoo.org; Sat, 19 Nov 2005 22:51:07 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAJMmdNb015971;
	Sat, 19 Nov 2005 22:48:39 GMT
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194])
	by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAJMifOn009134
	for <gentoo-dev@lists.gentoo.org>; Sat, 19 Nov 2005 22:44:42 GMT
Received: by wproxy.gmail.com with SMTP id 68so251798wri
        for <gentoo-dev@lists.gentoo.org>; Sat, 19 Nov 2005 14:44:41 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=eNb+Q8WYUgPFbUKaYKAXkE38KO/aojBsSlubfibk8tVQqcEpjuTOVRedPyfuCsBqmvvQAPPJI9q2td3URb9yv8hrBwRZcfP83Vi0zXEpHIKg4V5PUdGH7/xDRy3z004zO7Ymlc/862H44hpLdv7fNGUA+zYZ3ijNlxbp3A1NPs8=
Received: by 10.54.77.10 with SMTP id z10mr85625wra;
        Sat, 19 Nov 2005 14:44:41 -0800 (PST)
Received: by 10.54.110.15 with HTTP; Sat, 19 Nov 2005 14:44:41 -0800 (PST)
Message-ID: <46059ce10511191444u26638588qbba94f158c19327e@mail.gmail.com>
Date: Sat, 19 Nov 2005 17:44:41 -0500
From: Dan Meltzer <parallelgrapefruit@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] implementation details for GLEP 41
In-Reply-To: <20051119224241.GC12982@mail.lieber.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
References: <20051119170615.GW12982@mail.lieber.org>
	 <20051119224241.GC12982@mail.lieber.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by robin.gentoo.org id jAJMifOn009134
X-Archives-Salt: e4eae0fe-40f2-453e-97c8-2e1af50c8574
X-Archives-Hash: 69ed4e548454b90718e4c9300b034f74

On 11/19/05, Kurt Lieber <klieber@gentoo.org> wrote:
> On Sat, Nov 19, 2005 at 05:06:15PM +0000 or thereabouts, Kurt Lieber wrote:
> > For instance, the way GLEP 41 suggests doing r/o cvs is not going to work.
>
> So, in the interests of trying to find a solution to this particular
> problem...
>
> As I understand the GLEP, the main requirement here is to give the arch
> testers faster access to the ebuilds in CVS.  Is this accurate?

This is the main idea behind it I believe.
>
> If so, is there any reason we have to use CVS?  Lance and I are both
> concerned about the extra load that another 50-100 people (extrapolating
> from the 20 folks that amd64 says they have currently) will place on
> cvs.g.o and I'd rather break this out onto a separate server.

Funy, I was just pondering that myself...  is authenticated rsync
really possible?  I was thinking about some sort of on-the-fly access
list updating based on a daemon running on AT's computers, that sent
current IP.. but that sounded kind of messy, I suppose you are better
at figuring this out than I am, though :)

The only downside to this that I can see would be the lack of
history... FEX an upgraded -rX ebuild breaks something, I could test
against previous -rX's in turn to find out exactly which broke it, and
other history like stuff.  This may or may not be necessary/helpful,
hard to say without it having happened :)

Thanks for coming back and thinking about the implementation,
reguardless of which way its done.
>
> One proposal being discussed is setting up a dedicated rsync server for
> this purpose that a) syncs from CVS more frequently and b) has no ban
> limits imposed on it.  Arch testers would have some way of authenticating
> to the box and being able to sync as frequently as they wanted to.  Current
> goal is to have all data in this new repository within 30 minutes of it
> hitting CVS.  (current average is about 1 hour)
>
> If the requirement is for r/o CVS access to the same CVS server that the
> pure-blooded developers use (sorry, couldn't resist) then it may require
> upgrades to our existing server and/or purchasing a new server.
>
> --kurt
>
>
>

-- 
gentoo-dev@gentoo.org mailing list