public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alec Warner" <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors?
Date: Sun, 16 Nov 2008 14:00:23 -0800	[thread overview]
Message-ID: <b41005390811161400k740fb409yf4868fd7a32f7319@mail.gmail.com> (raw)
In-Reply-To: <20081116105129.TAa22b4.tv@veller.net>

On Sun, Nov 16, 2008 at 2:42 AM, Torsten Veller <tove@gentoo.org> 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.



      reply	other threads:[~2008-11-16 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 10:42 [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors? Torsten Veller
2008-11-16 22:00 ` Alec Warner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b41005390811161400k740fb409yf4868fd7a32f7319@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox