[Fink-devel] cvs up : Cannot allocate memory
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 - 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
Re: [Fink-devel] cvs up : Cannot allocate memory
-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. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHU3H3B8UpO3rKjQ8RArXqAJ9LEO5iTyPe6llFsDQLGEJJywGoSQCfbSB8 ojF+TIcycqU4afzigWfiH8s= =yNIT -END PGP SIGNATURE- - 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
Re: [Fink-devel] cvs up : Cannot allocate memory
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 - 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
Re: [Fink-devel] cvs up : Cannot allocate memory
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
Re: [Fink-devel] cvs up : Cannot allocate memory
On Mon, Dec 03, 2007 at 03:55:12AM +0100, 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 ? Yup. Often (but sporadically) over past week or two. Certainly a problem on SF's server end, not ours. Please file a bug with SourceForge. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks - 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
Re: [Fink-devel] cvs up : Cannot allocate memory
On 03 Dec 2007, at 05:03, Daniel Macks wrote: Yup. Often (but sporadically) over past week or two. Certainly a problem on SF's server end, not ours. Please file a bug with SourceForge. Done. http://sourceforge.net/tracker/index.php? func=detailaid=1843109group_id=1atid=21 JF - 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
