From: Torsten Veller <tove@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors?
Date: Sun, 16 Nov 2008 11:42:25 +0100 [thread overview]
Message-ID: <20081116105129.TAa22b4.tv@veller.net> (raw)
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.
next reply other threads:[~2008-11-16 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 10:42 Torsten Veller [this message]
2008-11-16 22:00 ` [gentoo-dev] Moving packages -- breaking the tree or stop updating mirrors? Alec Warner
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=20081116105129.TAa22b4.tv@veller.net \
--to=tove@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