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
-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
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:
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
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
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
