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 1SXAvA-0005lu-90 for garchives@archives.gentoo.org; Wed, 23 May 2012 12:44:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E60FDE061F; Wed, 23 May 2012 12:43:47 +0000 (UTC) Received: from spot.xmw.de (spot.xmw.de [176.9.87.236]) by pigeon.gentoo.org (Postfix) with ESMTP id 74897E05E8 for ; Wed, 23 May 2012 12:42:55 +0000 (UTC) Received: from [IPv6:2001:6f8:1cd1:0:221:5cff:fe97:1a8f] (unknown [IPv6:2001:6f8:1cd1:0:221:5cff:fe97:1a8f]) by spot.xmw.de (Postfix) with ESMTPSA id EE6F3254788CD for ; Wed, 23 May 2012 14:42:52 +0200 (CEST) Message-ID: <4FBCDB3D.1070009@gentoo.org> Date: Wed, 23 May 2012 14:42:37 +0200 From: Michael Weber User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 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 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] Portage Git migration - clean cut or git-cvsserver X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 99acaf5a-6c2f-4c9b-9a45-eb1874de2659 X-Archives-Hash: 9c0d10814fb4188e0becbcda2f55490b -----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-----