Re: mirror the Packages files _after_ the packages!
Dan Jacobson <[EMAIL PROTECTED]> schrieb: > Does http://www.debian.org/mirror/ at least have the > two-phase-mirroring script? Why don't you go and look? And if you find the information too sparse, submit a bug report with a patch? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: mirror the Packages files _after_ the packages!
Jeroen> Debian could promote this two-phase mirroring a bit more Jeroen> maybe, and/or provide nice scripts, that's probably why #6786 Jeroen> is still open. I suppose Debian is promoting one-phase mirroring and two phase mirroring is "roll your own". If you want me to tell my administrator to do something, I need something succinct, like "apt-get install two-phase-mirroring". Jeroen> #6786 doesn't need to be fixed for this, the mirror admin of Jeroen> xx.linux.org.xx just needs to implement two-phase mirroring, Jeroen> something that anyone with a bit shell/rsync foo can implement on Jeroen> his/her own, and ttbomk, already a lot of mirrors actually _do_. If this two-phase-mirroring is the way to go, then there ought to be a standard package to do it. How can there be 1+ packages but no package to make sure the 1+ packages get mirrored properly? Any approved recommended debugged method would certainly have its own package, where the administrator would merely enter some configuration parameters in some /etc file. Does http://www.debian.org/mirror/ at least have the two-phase-mirroring script? Is there any official documentation? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
Hi Jeroen, > 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. But Debian could at least offer an updated rsync-script. Its over a month ago, i posted an updated script to [EMAIL PROTECTED] but noone yet cared and updated it. Greetings Martin -- What's done to children, they will do to society. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
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://xx.linux.org.xx/debian/pool/main/x > > 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 xx.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]
Re: mirror the Packages files _after_ the packages!
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. D> > Failed to fetch http://xx.linux.org.xx/debian/pool/main/x 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, the mirror process could break at any time and users could still apt-get upgrade with yesterdays state instead of not being to apt-get upgrade at all (if the mirror process happen to break during the 2 hour dark period each day.) Indeed, no 2 hour dark period necessary too. Please double check 6786 to see if it is merely a local problem. Would you close it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mirror the Packages files _after_ the packages!
On Wed, Feb 09, 2005 at 09:51:44AM +0800, Dan Jacobson wrote: > I know you Debian people think it's just hilarious when users try to > apt-get upgrade during the period after when the Packages files > arrive on the mirrors, but before the packages they describe have > fully arrived. > "Haw haw haw, try again later", you say, never thinking that maybe > writing the Packages files last would be the right thing to do. > "The problem can't persist more then a couple of hours, what's the big > deal?" You've been told this before -- *debian-devel does not control the mirroring implementation used by arbitrary Debian mirrors*. Either talk to the mirror team and give them enough information to track this down, or -- since you know him well enough to be kept in the loop about his vacation schedule -- talk to your local mirror operator directly and get him to stop using broken mirroring scripts. > I can't think of any other case in Computer Science where one updates > a descriptor before updating the thing described!!! How can you defend > that??? No smug remarks can defend that! And no amount of moronic, misdirected ranting will get it fixed. > Err http://xx.linux.org.xx sid/main 404 Not Found > Failed to fetch http://xx.linux.org.xx/debian/pool/main/x > Fetched 26.6MB in 2m39s (167kB/s) > E: Some files failed to download > Error 100 Yeah, real helpful of you to blot out the only potentially useful bit of information in your post... -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: mirror the Packages files _after_ the packages!
Hi Dan, On Wednesday, 09 Feb 2005, Dan Jacobson <[EMAIL PROTECTED]> wrote: > I know you Debian people think it's just hilarious when users try to > apt-get upgrade during the period after when the Packages files > arrive on the mirrors, but before the packages they describe have > fully arrived. see http://lists.debian.org/debian-www/2005/01/msg00199.html Greetings Martin -- Love is the only game that is not called on account of darkness. -- M. Hirschfield -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mirror the Packages files _after_ the packages!
I know you Debian people think it's just hilarious when users try to apt-get upgrade during the period after when the Packages files arrive on the mirrors, but before the packages they describe have fully arrived. "Haw haw haw, try again later", you say, never thinking that maybe writing the Packages files last would be the right thing to do. "The problem can't persist more then a couple of hours, what's the big deal?" Well, the connection to mirror-upstream broke mid-mirror-push this time during Chinese New Years. Perhaps 10 days before the system administrator will be back in the office to see what happened. "Haw haw haw, try another mirror. Haw haw haw." The other local mirrors have the same problem, and their system admins are also on vacation. Foreign mirrors are on slow links. So not fixing bug 6786 (just write the [EMAIL PROTECTED] Packages file after writing the packages) causes users' apt-get upgrades to fail needlessly... down for 10 days. Great. The Debian whippersnappers don't see the danger of needlessly leaving mirrors in a broken state "for only a couple of hours a day, what's the big deal" ... well if the mirror mechanism breaks during this broken state, then "couple of hours" becomes indefinitely. I can't think of any other case in Computer Science where one updates a descriptor before updating the thing described!!! How can you defend that??? No smug remarks can defend that! "Never bothered me", yeah well wait until you are giving your next apt-get upgrade demonstration and now it's too late, you did apt-get update && apt-get upgrade instead of apt-get upgrade && apt-get update && apt-get upgrade and now you have to tell the class to "wait a couple of hours" until you can show them anything. Yeah I know, "the more I complain, the more it's not going to get done." OK, can somebody send me the section of code so I can fix it then? Err http://xx.linux.org.xx sid/main 404 Not Found Failed to fetch http://xx.linux.org.xx/debian/pool/main/x Fetched 26.6MB in 2m39s (167kB/s) E: Some files failed to download Error 100 P.S., "a couple hours" is for your fancy mirror's connections. Some mirrors far away might be in the broken state (Packages* arrived, not all packages arrived) for half a day each day! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]