Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ian Whyman <thev00d00@g.o>
Subject: Re: Portage Git migration - clean cut or git-cvsserver
Date: Wed, 23 May 2012 14:14:31 +0100
<p><br>
On May 23, 2012 1:55 PM, &quot;Johannes Huber&quot; &lt;<a href="mailto:johu@g.o">johu@g.o</a>&gt; wrote:<br>
&gt;<br>
&gt; Am Mittwoch 23 Mai 2012, 14:42:37 schrieb Michael Weber:<br>
&gt;<br>
&gt; &gt; -----BEGIN PGP SIGNED MESSAGE-----<br>
&gt;<br>
&gt; &gt; Hash: SHA256<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; Hi,<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; i&#39;ve looked at the blockers of &quot;[TRACKER] portage migration to git&quot;<br>
&gt;<br>
&gt; &gt; [1] and want to discuss &quot;testing git-cvsserver&quot; [2].<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; There are two proposed scenarios how to migrate the developers write<br>
&gt;<br>
&gt; &gt; access to the portage tree.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; &quot;Clean cut&quot; turns of cvs access on a given and announced timestamp,<br>
&gt;<br>
&gt; &gt; rsync-generation/updates is suspended (no input -&gt; no changes), some<br>
&gt;<br>
&gt; &gt; magic scripts prepare the git repo (according to [3], some hours<br>
&gt;<br>
&gt; &gt; duration) and we all checkout the tree (might be some funny massive load).<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; &quot;testing git-cvsserver&quot; proses &quot;Clean cut&quot; with the additional ability<br>
&gt;<br>
&gt; &gt; to continue using cvs update/commit, - in best case - on the old<br>
&gt;<br>
&gt; &gt; checkout w/o alteration on the developers side.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; &quot;Clean cut&quot; forces us to clean up out dirty checkouts (I have some<br>
&gt;<br>
&gt; &gt; added directories, added ebuilds i hesitated to `repoman commit`).<br>
&gt;<br>
&gt; &gt; Plus we have to alter all our hot-wired portage mangling scripts from<br>
&gt;<br>
&gt; &gt; cvs&#39;ish to git&#39;ish (I use my read/write checkout as portage tree (cvs<br>
&gt;<br>
&gt; &gt; checkout + egencache for checkout) and have an automated google-chrome<br>
&gt;<br>
&gt; &gt; bump script). But this can be accomplished on a per developer basis,<br>
&gt;<br>
&gt; &gt; and slackers don&#39;t stall the process.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; &quot;testing git-cvsserver&quot; forces us all to test these cvs&#39;ish scripts<br>
&gt;<br>
&gt; &gt; and behaviours against a git-cvsserver and report.<br>
&gt;<br>
&gt; &gt; We all know that this test-runs will never happen, stalling this bug<br>
&gt;<br>
&gt; &gt; till infinity.<br>
&gt;<br>
&gt; &gt; Plus infra/&quot;subset of devs marshalling the migration&quot; get stuck<br>
&gt;<br>
&gt; &gt; between fixing git issues and git-cvsserver.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; *if you still read this* *wow*<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; Please discuss my arguments and come to the conclusions to<br>
&gt;<br>
&gt; &gt; RESO/WONT-FIX &quot;testing git-cvsserver&quot;, make a &quot;clean cut&quot; and remove<br>
&gt;<br>
&gt; &gt; this bug from the blockers of &quot;[TRACKER] portage migration to git&quot;.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; My lengthy 2 cents.<br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; [1] <a href="https://bugs.gentoo.org/333531">https://bugs.gentoo.org/333531</a><br>
&gt;<br>
&gt; &gt; [2] <a href="https://bugs.gentoo.org/333699">https://bugs.gentoo.org/333699</a><br>
&gt;<br>
&gt; &gt; [3] <a href="https://bugs.gentoo.org/333705#c2">https://bugs.gentoo.org/333705#c2</a><br>
&gt;<br>
&gt; &gt; - --<br>
&gt;<br>
&gt; &gt; Gentoo Dev<br>
&gt;<br>
&gt; &gt; <a href="http://xmw.de/">http://xmw.de/</a><br>
&gt;<br>
&gt; &gt; -----BEGIN PGP SIGNATURE-----<br>
&gt;<br>
&gt; &gt; Version: GnuPG v2.0.17 (GNU/Linux)<br>
&gt;<br>
&gt; &gt; Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
&gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt; &gt; iF4EAREIAAYFAk+82z0ACgkQknrdDGLu8JBUWAD/dmuqyES/mYDrMam+/txnHmgd<br>
&gt;<br>
&gt; &gt; VaQaqwHMlwzzqQwbpY4A/0h+5Vp8sLbOE78k4SCaGE2dCQtmeOz0jd1YxkDzP+YW<br>
&gt;<br>
&gt; &gt; =jXLQ<br>
&gt;<br>
&gt; &gt; -----END PGP SIGNATURE-----<br>
&gt;<br>
&gt;  <br>
&gt;<br>
&gt; I support RESOLUTION WONTFIX, if nobody cares about the bug since it was opened it is obvious out of interest. There is no reason to support jurassic software.<br>
&gt;<br>
&gt;  <br>
&gt;<br>
&gt; Clean cut++<br>
&gt;<br>
&gt;  <br>
&gt;<br>
&gt; Cheers<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; Johannes Huber (johu)<br>
&gt;<br>
&gt; Gentoo Linux Developer / KDE Team<br>
&gt;<br>
&gt; GPG Key ID F3CFD2BD<br>
&gt;<br>
&gt;  </p>
<p>Another vote for clean cut from me.</p>
References:
Portage Git migration - clean cut or git-cvsserver
-- Michael Weber
Re: Portage Git migration - clean cut or git-cvsserver
-- Johannes Huber
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Next by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Previous by date:
Re: Portage Git migration - clean cut or git-cvsserver
Next by date:
Re: Portage Git migration - clean cut or git-cvsserver


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.