Hi,
I would like to ask you to please delete the cl-colors-devel and
cl-colors-announce mailing lists. Nobody is subscribed to them
besides me (the author of cl-colors), and all traffic is (or would be,
if I didn't discard it) spam.
Thanks,
Tamas
Hi!
Could you please add the 2 people in the CC to the 'armedbear' project
for commit access?
Alessio Stalla suggests 'alessiostalla' as a user name,
Ville Voutilainen suggests 'ville.voutilainen'.
I don't have any idea about the maximum length of user names though,
so maybe these long names are problematic.
Thanks in advance!
Bye,
Erik.
hello;
i had a couple updates to introduce into the svn repository, but i
can't get there.
if i try to use a svn+ssh://common-lisp.net/.... url or if i try to
ssh to the host directly, i get the same error: no such file or
directory.
it has been a long time.
do i still have an account? do i need a different host to ssh?
thanks,
I've added the armedbear and usocket projects to ohloh, however, they
seem to be unable to retrieve the repository content. Please see this
ohloh post for reference: http://www.ohloh.net/forums/10/topics/2423
The issue seems to be with common-lisp.net not allowing enough
connections or limiting the reconnection rate.
Could you have a look at this issue?
Thanks in advance,
Erik.
http://trac.common-lisp.net/ gives me:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Could not connect to remote machine: Connection refused
--------------------------------------------------------------------------------
Apache/1.3.33 Server at trac.common-lisp.net Port 80
Hi,
A week ago, I sent a message regarding working with darcs 2
repositories on common-lisp.net. There are two main problems with my
workaround:
* The darcs installed on cl.net (version 1) is completely incompatible
with version 2 repositories.
* When logging into cl.net via ssh, the shell bash is called by the
name sh rather than bash, causing bash to use a compatibility mode for
sh which makes it difficult to set PATH for non-interactive logins.
$ echo $SHELL
/bin/sh
The former means that I can't work with my repositories without an
additional, personal installation of darcs, and the latter makes it
difficult to put my ~/bin in PATH since bash doesn't read either
~/.bash_profile or ~/.bashrc when called by the name of sh.
Now since darcs depends on being in the PATH of the remote machine
when pushing via ssh, this effectively means I can't push to my darcs
2 repositories on cl.net.
Would it be possible to upgrade the darcs installation to version 2?
The people on the darcs-user list assure me that upgrading to version
2 shouldn't cause any incompatibilities with version 1 repositories,
so any projects using version 1 at the moment shouldn't notice the
upgrade, except for a possible performance boost. And the upgrade
itself shouldn't be difficult, as there are binaries available at
http://wiki.darcs.net/DarcsWiki/CategoryBinaries, as well as
up-to-date Debian packages at https://launchpad.net/~laney/+archive
(although these are intended primarily for Ubuntu, I believe).
--
Elliott Slaughter
"Any road followed precisely to its end leads precisely nowhere." -
Frank Herbert