From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SXCRT-0004JZ-OZ for garchives@archives.gentoo.org; Wed, 23 May 2012 14:21:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B4BDAE05F1; Wed, 23 May 2012 14:21:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id B308BE05EC for ; Wed, 23 May 2012 14:20:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 61E1F1B4033 for ; Wed, 23 May 2012 14:20:18 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.912 X-Spam-Level: X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5.5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-N0c3vmPBPb for ; Wed, 23 May 2012 14:20:11 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 61A331B4025 for ; Wed, 23 May 2012 14:20:08 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SXCPz-00026l-Qj for gentoo-dev@gentoo.org; Wed, 23 May 2012 16:20:03 +0200 Received: from ppp118-209-108-208.lns20.mel4.internode.on.net ([118.209.108.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 May 2012 16:20:03 +0200 Received: from kensington by ppp118-209-108-208.lns20.mel4.internode.on.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 May 2012 16:20:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Michael Palimaka Subject: [gentoo-dev] Re: Portage Git migration - clean cut or git-cvsserver Date: Thu, 24 May 2012 00:17:20 +1000 Message-ID: References: <4FBCDB3D.1070009@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ppp118-209-108-208.lns20.mel4.internode.on.net User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 In-Reply-To: <4FBCDB3D.1070009@gentoo.org> X-Archives-Salt: 91a9e930-9fb5-4968-ac50-541a37a7e1b0 X-Archives-Hash: e5781f29a6a7ac6126acc8b7b3047968 On 2012-05-23 22:42, Michael Weber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi, > > i've looked at the blockers of "[TRACKER] portage migration to git" > [1] and want to discuss "testing git-cvsserver" [2]. > > There are two proposed scenarios how to migrate the developers write > access to the portage tree. > > "Clean cut" turns of cvs access on a given and announced timestamp, > rsync-generation/updates is suspended (no input -> no changes), some > magic scripts prepare the git repo (according to [3], some hours > duration) and we all checkout the tree (might be some funny massive load). > > "testing git-cvsserver" proses "Clean cut" with the additional ability > to continue using cvs update/commit, - in best case - on the old > checkout w/o alteration on the developers side. > > "Clean cut" forces us to clean up out dirty checkouts (I have some > added directories, added ebuilds i hesitated to `repoman commit`). > Plus we have to alter all our hot-wired portage mangling scripts from > cvs'ish to git'ish (I use my read/write checkout as portage tree (cvs > checkout + egencache for checkout) and have an automated google-chrome > bump script). But this can be accomplished on a per developer basis, > and slackers don't stall the process. > > "testing git-cvsserver" forces us all to test these cvs'ish scripts > and behaviours against a git-cvsserver and report. > We all know that this test-runs will never happen, stalling this bug > till infinity. > Plus infra/"subset of devs marshalling the migration" get stuck > between fixing git issues and git-cvsserver. > > *if you still read this* *wow* > > Please discuss my arguments and come to the conclusions to > RESO/WONT-FIX "testing git-cvsserver", make a "clean cut" and remove > this bug from the blockers of "[TRACKER] portage migration to git". > > My lengthy 2 cents. > > [1] https://bugs.gentoo.org/333531 > [2] https://bugs.gentoo.org/333699 > [3] https://bugs.gentoo.org/333705#c2 > - -- > Gentoo Dev > http://xmw.de/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iF4EAREIAAYFAk+82z0ACgkQknrdDGLu8JBUWAD/dmuqyES/mYDrMam+/txnHmgd > VaQaqwHMlwzzqQwbpY4A/0h+5Vp8sLbOE78k4SCaGE2dCQtmeOz0jd1YxkDzP+YW > =jXLQ > -----END PGP SIGNATURE----- > > Another vote for clean cut.