This sounds like an indication of a busy server, but I've never seen it before so I thought I'd ask.

Doing selfupdate-cvs, I've been getting stuck waiting for a cvs lock on stable/main/finkinfo (only) for the past 24 hours or so. It _flies_ through fink/10.2, fink/10.2/stable, fink/10.2/stable/crypto, and fink/10.2/stable/crypto/finkinfo and fink/10.2/stable/main...
but when it gets to fink/10.2/stable/main, it waits indefinitely:


> sudo /sw/bin/fink selfupdate-cvs
...
cvs server: Updating fink/10.2/stable/main
U fink/10.2/stable/main/.cvsignore
cvs server: Updating fink/10.2/stable/main/finkinfo
cvs server: [21:53:44] waiting for anoncvs_fink's lock in /cvsroot/fink/dists/10.2/stable/main/finkinfo
cvs server: [21:54:14] waiting for anoncvs_fink's lock in /cvsroot/fink/dists/10.2/stable/main/finkinfo
cvs server: [21:54:44] waiting for anoncvs_fink's lock in /cvsroot/fink/dists/10.2/stable/main/finkinfo
[ repeat forever, every 30 seconds ]


Busy server?  It's new to me.
Thanks,
Dan




------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to