Gentoo Archives: gentoo-dev

From: Michael Weber <xmw@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Portage Git migration - clean cut or git-cvsserver
Date: Wed, 23 May 2012 12:44:08
Message-Id: 4FBCDB3D.1070009@gentoo.org
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 Hi,
5
6 i've looked at the blockers of "[TRACKER] portage migration to git"
7 [1] and want to discuss "testing git-cvsserver" [2].
8
9 There are two proposed scenarios how to migrate the developers write
10 access to the portage tree.
11
12 "Clean cut" turns of cvs access on a given and announced timestamp,
13 rsync-generation/updates is suspended (no input -> no changes), some
14 magic scripts prepare the git repo (according to [3], some hours
15 duration) and we all checkout the tree (might be some funny massive load).
16
17 "testing git-cvsserver" proses "Clean cut" with the additional ability
18 to continue using cvs update/commit, - in best case - on the old
19 checkout w/o alteration on the developers side.
20
21 "Clean cut" forces us to clean up out dirty checkouts (I have some
22 added directories, added ebuilds i hesitated to `repoman commit`).
23 Plus we have to alter all our hot-wired portage mangling scripts from
24 cvs'ish to git'ish (I use my read/write checkout as portage tree (cvs
25 checkout + egencache for checkout) and have an automated google-chrome
26 bump script). But this can be accomplished on a per developer basis,
27 and slackers don't stall the process.
28
29 "testing git-cvsserver" forces us all to test these cvs'ish scripts
30 and behaviours against a git-cvsserver and report.
31 We all know that this test-runs will never happen, stalling this bug
32 till infinity.
33 Plus infra/"subset of devs marshalling the migration" get stuck
34 between fixing git issues and git-cvsserver.
35
36 *if you still read this* *wow*
37
38 Please discuss my arguments and come to the conclusions to
39 RESO/WONT-FIX "testing git-cvsserver", make a "clean cut" and remove
40 this bug from the blockers of "[TRACKER] portage migration to git".
41
42 My lengthy 2 cents.
43
44 [1] https://bugs.gentoo.org/333531
45 [2] https://bugs.gentoo.org/333699
46 [3] https://bugs.gentoo.org/333705#c2
47 - --
48 Gentoo Dev
49 http://xmw.de/
50 -----BEGIN PGP SIGNATURE-----
51 Version: GnuPG v2.0.17 (GNU/Linux)
52 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
53
54 iF4EAREIAAYFAk+82z0ACgkQknrdDGLu8JBUWAD/dmuqyES/mYDrMam+/txnHmgd
55 VaQaqwHMlwzzqQwbpY4A/0h+5Vp8sLbOE78k4SCaGE2dCQtmeOz0jd1YxkDzP+YW
56 =jXLQ
57 -----END PGP SIGNATURE-----

Replies