From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L1f6H-0007op-QV for garchives@archives.gentoo.org; Sun, 16 Nov 2008 10:43:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EAC00E0267; Sun, 16 Nov 2008 10:43:29 +0000 (UTC) Received: from smtprelay08.ispgateway.de (smtprelay08.ispgateway.de [80.67.29.8]) by pigeon.gentoo.org (Postfix) with ESMTP id BC248E0267 for ; Sun, 16 Nov 2008 10:43:29 +0000 (UTC) Received: from [62.224.158.178] (helo=arkane.local) by smtprelay08.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1L1f6F-0008BX-6C for gentoo-dev@lists.gentoo.org; Sun, 16 Nov 2008 11:43:27 +0100 Received: by arkane.local (Postfix, from userid 1000) id 3030B4124; Sun, 16 Nov 2008 11:42:26 +0100 (CET) Date: Sun, 16 Nov 2008 11:42:25 +0100 From: Torsten Veller To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors? Message-ID: <20081116105129.TAa22b4.tv@veller.net> Mail-Followup-To: gentoo-dev@lists.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=us-ascii Content-Disposition: inline Jabber-ID: tove@jabber.ccc.de X-PGP-Fingerprint: 0416 3C11 8D79 65B9 AAD0 2065 BBC7 14D1 9C67 CD96 User-Agent: Mutt/1.5.18 (2008-10-30) X-Df-Sender: 1067115 X-Archives-Salt: b8236f9a-f0e3-4e61-87ef-8867f04f7774 X-Archives-Hash: a3084f82aff32463b6211dedc6339ba5 It is time to finish the move of some new dual-lifed perl modules from dev-perl to perl-core (plus virtual/). It involves updating of 120 packages all over the tree but mostly in dev-perl. As this takes some time the tree will be inconsistent until it is finished. I don't know how long it'll take. So the question is: Can we stop updating the rsync mirrors during that time easily? Or even better: Can *I* stop it? As there were problems while moving packages before, I remember we were talking about a way to stop updating rsync mirrors from cvs. I guess nothing was implemented? Thanks.