-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randall R Schulz wrote: > On Tuesday 22 November 2005 10:09, Eberhard Moenkeberg wrote: >> On Tue, 22 Nov 2005, Randall R Schulz wrote: >>> On Tuesday 22 November 2005 09:46, Eberhard Moenkeberg wrote: >>>> ... >>>> Maybe Pascal has forgotten to symlink some files. >>>> Nothing is missing at ftp or ftp4 - both are in sync with Pascal's >>>> home.
Hmhm, it's something that had to happen sooner or later. Some weeks ago, the rsync with my packages was done at a given time (I won't disclose here ;P) and I have a cronjob running a script that generates the repository metadata for yast2 and opencarpet. Now, Eberhard and I experienced very weird issues with rsync that were related to the extreme load the ftp*.gwdg.de servers were under. It seems it has gotten much better now, and rsyncs are reliable again (at least I didn't notice any failure the last weeks). It also has to do with the fact that Eberhard makes several syncs per night, at different times (that seem unpredictable to me, but maybe I'm just not looking hard enough ;)). So, what very likely happened: - - rsync with ftp.gwdg.de to fetch the packages - - at, say, 03:00 AM my cronjob generates the yast2 and opencarpet metadata - - no rsync happened after that Eberhard, could you please send me a private mail with the current sync time(s) ? Or maybe you have a better idea how to solve this consistently, which wouldn't be the first time :) Actually the apt-rpm repositories are generated on ftp*.gwdg.de, by Eberhard and with help from Richard Bos (who's pretty much the "apt-rpm on SUSE guru" :)). On the other hand, other repository formats such as YaST2 and opencarpet (Red Carpet) are generated by myself on my server before it gets synched on gwdg.de. That explains why you should never have such issues when using the apt-rpm repositories on gwdg, but it might happen with my YaST2 repository. But we're going to work on that. The bugger is on my side, sorry for that. >>> For crying out loud! Why are we having this exchange if you cannot >>> or will not do anything about the problem? >> Crazy, man... >> There is no problem at ftp or ftp4. > > So you keep repeating. But I don't care where the problem isn't. If the > problem isn't yours, stop replying! I didn't address this to you, I > addressed it to the list so someone who _does_ know what the problem is > and _can_ do something about the problem will do so. If that's not you, > then I don't need to hear from you. Gosh... Randall, could you please calm down a bit... You had an issue with my repository, so I would have been the first person to contact.. well.. at least it's what I would do ;) Thanks for reporting the issue, I'm sure Eberhard and I can find a way to avoid that from happening again. Believe me, he's a technically very savvy person and has always been tremendously helpful, especially with regards to the SUSE community. If he wasn't so committed (as well as Richard Bos), we wouldn't have all those package repositories (except for packman, although even packman uses the gwdg.de infrastructure for the apt repositories). Sidenote: again, Eberhard, I'll never say "thank you" often enough, kudos ;))) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDg5cUr3NMWliFcXcRAtYmAJ9P5d2k6wiBwf7D3hj1QMbfeLa1XQCggnDv 0j35LXIWsyPccBS+UC0Se/Q= =jmlF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
