-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Has anyone else experienced this? I went to do a selfupdate today (just like yesterday), only it hangs on the first rsync:

% fink -b selfupdate
Password:
rsync -az -q rsync://master.us.finkmirrors.net/finkinfo// TIMESTAMP /sw/fink/TIMESTAMP.tmp
[hangs here for several minutes]
^C
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(328)
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(328)
### execution of rsync failed, exit code 20
Failed to fetch the timestamp file from the rsync server: rsync:// master.us.finkmirrors.net/finkinfo/. Check the error messages above.
(1)     Give up
(2)     Retry the same mirror
(3)     Retry another mirror from your country
(4)     Retry another mirror
How do you want to proceed? [3] 3
rsync -az -q rsync://uox.ms.us.finkmirrors.net/finkinfo// TIMESTAMP /sw/fink/TIMESTAMP.tmp
[hangs here for a few minutes and times out by itself]
rsync error: error in socket IO (code 10) at clientserver.c(88)
### execution of rsync failed, exit code 10
Failed to fetch the timestamp file from the rsync server: rsync:// master.us.finkmirrors.net/finkinfo/. Check the error messages above.
(1)     Give up
(2)     Retry the same mirror
(3)     Retry another mirror from your country
(4)     Retry another mirror
How do you want to proceed? [3] 3
...

Is anyone else experiencing this? It doesn't seem to matter which mirror I attempt to use. Any help is greatly appreciated.

    --Matt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFDSwfhnLpDzL5I7l8RAsMrAJ9z0clSehMHCTMPjox6uXjg7ebalACgjuNS
PMCPuJTsnI+Fgdjudc/y+OI=
=l4Xh
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to