-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-05-16 at 08:29 -0400, Carl Hartung wrote:
Follow-up:
It worked, Carlos. Thanks for the heads-up!
Good. Or bad, it shouldn't be that way, it is a bug (and I think it was reported as solved).
My impression is that something in the installation source verification process is still intolerant of server-side delays, including those induced by incorrect paths (which has always been the case.) It seems now to take an excessive amount of time to error out... when it *does* error out... but it now acts as though it's having a difficult time distinguishing between proper, or 'hard' errors (such as incorrect paths) and 'soft' errors like sluggish responses from busy servers.
Once I saw that the network was active, downloading something; but Yast doesn't say a word about what it is doing, so it seems hung. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEad4btTMYHG2NR9URAjYBAJ0b8tSFgTlBMOtdnLtPmZfzh9InXwCgi/g2 9qCA+cMEo9fzcS63dLTUdEo= =+j5l -----END PGP SIGNATURE-----