On Tue, Feb 15, 2005 at 11:51:10PM +0800, Dan Jacobson wrote: > S> You've been told this before -- *debian-devel does not control the > mirroring > S> implementation used by arbitrary Debian mirrors*. Either talk to the > mirror > S> team and give them enough information to track this down, or -- since you > S> know him well enough to be kept in the loop about his vacation schedule -- > S> talk to your local mirror operator directly and get him to stop using > broken > S> mirroring scripts. > > I'm saying that bug 6786 has the potential to turn the current perhaps > two hour per day down time for apt-get, aptitude, etc. into a several > day long down time.
How mirrors do their mirroring is up to the local mirror administrator, not to the general debian developer's community. Debian could promote this two-phase mirroring a bit more maybe, and/or provide nice scripts, that's probably why #6786 is still open. BUT DEBIAN CANNOT IN ANY WAY FORCE/CONTROL HOW MIRRORS OPERATE, especially not the secundary mirrors. > D> > Failed to fetch http://xxxxxx.linux.org.xx/debian/pool/main/xxxxx > > S> Yeah, real helpful of you to blot out the only potentially useful bit of > S> information in your post... > > No. The root of the problem is bug 6786. Indeed if 6786 were fixed, #6786 doesn't need to be fixed for this, the mirror admin of xxxxxx.linux.org.xx just needs to implement two-phase mirroring, something that anyone with a bit shell/rsync foo can implement on his/her own, and ttbomk, already a lot of mirrors actually _do_. As numerous people have told you before, bugger your local mirror admin, especially since he seems to have slow bandwidth and therefore the 'dark period' takes long. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]