On Dec 2, 2007, at 10:14 PM, Jean-François Mertens wrote: > > On 03 Dec 2007, at 04:03, Alexander Hansen wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Jean-François Mertens wrote: >>> I get since some time regularly failures of fink selfupdate with >>> msgs like cvs update: cannot open directory >>> /cvsroot/fink/dists/10.4/unstable/ crypto/finkinfo: Cannot allocate >>> memory >>> >>> I get those as well when using explicitly /usr/bin/cvs, so it is >>> not due to fink's cvs pkg. This happens even when local memory >>> usage is low _ say 1.4 out of 2 G. >>> >>> In general when retrying, especially dir after dir and with a naked >>> 'cvs up' without adornations, things go away and one gets through. >>> Tonight not... >>> >>> The ref to "/cvsroot/fink/dists/" suggests it may be either a >>> memory problem or an error on the other side.. (In general I get >>> this on rather big dirs _ eg, 'libs' _ but tonight even on smaller >>> ones like crypto) >>> >>> Anyone else experiencing this ? Is it really a sourceforge problem >>> ? >>> >>> JF >>> >>> PS: crypto finally got through, after ~8 iterations >> I have, and others have talked about it on IRC. > > And ? _ the conclusion of the talking ? > > JF Unfortunately the usual conclusion: sourceforge has issues that aren't communicated well or resolved quickly.
Dave -- David Reiser [EMAIL PROTECTED] ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
