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 1L1pfN-0005tw-JX for garchives@archives.gentoo.org; Sun, 16 Nov 2008 22:00:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 932D0E034F; Sun, 16 Nov 2008 22:00:25 +0000 (UTC) Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.158]) by pigeon.gentoo.org (Postfix) with ESMTP id 6D829E0395 for ; Sun, 16 Nov 2008 22:00:25 +0000 (UTC) Received: by yw-out-1718.google.com with SMTP id 5so1005928ywm.46 for ; Sun, 16 Nov 2008 14:00:23 -0800 (PST) Received: by 10.100.197.7 with SMTP id u7mr1355882anf.72.1226872823475; Sun, 16 Nov 2008 14:00:23 -0800 (PST) Received: by 10.100.94.12 with HTTP; Sun, 16 Nov 2008 14:00:23 -0800 (PST) Message-ID: Date: Sun, 16 Nov 2008 14:00:23 -0800 From: "Alec Warner" Sender: antarus@scriptkitty.com To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors? In-Reply-To: <20081116105129.TAa22b4.tv@veller.net> 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 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081116105129.TAa22b4.tv@veller.net> X-Google-Sender-Auth: fa83c50cc75316ac X-Archives-Salt: b1c8e956-e62b-4495-bb41-cb2a49c5a75e X-Archives-Hash: ae1e2fec6af3b113efbc82cf54320cbb On Sun, Nov 16, 2008 at 2:42 AM, Torsten Veller wrote: > 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? I'm sure if you make a proposal to infra on a time window[1] they can possibly assist you. > Or even better: Can *I* stop it? not at this time, no. > > 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? I lost interest in this proposal as it seemed to not needed very often. It would be trivial to implement if ebuild developers think it is a priority. > > Thanks. > > [1] 'Now - until I'm finished' is typically an invalid window. I suggest you make some estimates on how long the moves will take you. Also give yourself some cushion time and make sure you have enough time to back out of the chance in case something goes awry.