Re: What's up with the CVS sever?
>>>> "Michael" == Michael Kifer
<kifer(a)cs.sunysb.edu> writes:
>> >>>> "Michael" ==
Michael Kifer <kifer(a)cs.sunysb.edu> writes:
>>
Michael> cvs server: Updating skk/etc
Michael> cvs [server aborted]: out of memory; can not allocate 2808685 bytes
>
> skk/etc is a problem child because of the huge file it contains.
>
> Try using :pserver:, not :ext:, for your read-only CVS commands.
>
> Try rm -rf skk/etc before doing the cvs update.
>
> If nothing else works, you can omit the skk directory.
Michael> Thanks, Martin. Switching to pserver in the mule directory has helped
Michael> somewhat (at least, with downloading) However, this is very inconvenient.
Michael> Is it a memory problem with the server? Would moving the main repository to
Michael> sourceforge help? I know this means loosing some degree of control and
Michael> convenience, but form my experience they are reasonably good at running it,
Michael> and are getting better.
The XEmacs project is also at SourceForge. The plan was to put the
web site there, and move the rest of the project if things worked out.
We are still evaluating SourceForge.
I would still prefer getting our own machine that we have complete
control over. I hate feeling like a guest at cvs.xemacs.org,
ftp.xemacs.org, and SourceForge. I want root!
Michael> The real problems came when I then ran "make all" in the
Michael> xemacs-packages directory and got lots of errors. Some of
Michael> them seem, indeed, to be errors. For instance,
Paging Steve Youngs...
Michael> Worst of all, when I start xemacs after that it fails to recognize the
Michael> packages in xemacs-packages, even though I have a symbolic link
Michael> from xemacs/xemacs-packages to the xemacs-packages directory, which is a
Michael> CVS copy of that module.
I'm embarrassed to admit that I have never built xemacs-packages. I
just use the pre-built sumos. Just call me `Linus'.
Martin