Had this problem with cmucl src/code and src/compiler directories a
while ago but it was fixed.
However, try getting the file list for ansi-tests/ansi-tests and
scroll down a bit. It brings firefox to its knees. Chrome is a bit
better but it still takes a while on my 3GHz imac.
Compare this with github.com/rtoy/ansi-cl-tests. It's very smooth and
takes no time at all.
(It would probably be nice for its own sake if ansi-tests put related
tests into subdirectories instead of all the files in one directory.
But that's a different issue.)
--
Ray
I didn't realize that I was in charge, and there was a different PW. I
have gotten it taken care of.
The mailman admin page does not play very well with password safe
programs.....
Sorry to bother you,
r
Looks like when asdf-devel(a)common-lisp.net was moved over, I didn't get
access to asdf-announce. Would you please set me up as the admin for
that? Also, if it *could* use the same password as asdf-devel, that
would be really nice.
thanks,
r
I was wondering why a git fetch was taking 2+ minutes, then I discovered
that common-lisp.net has an AAAA record configured, but that address
doesn't work, it doesn't even respond to ICMPv6; and since I have an
IPv6-native connection at home, and newer distros are configured to give
priority to IPv6 addresses, ssh connections timeout until fallback to
the IPv4 address.
I suggest removing the record.
--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
The ASDF-devel list is acquiring a bunch of bogus Twitter messages.
[These aren't really spam, but are admin messages that are leaking onto
asdf-devel.] Unfortunately, these don't all come form a single email
address.
Would it be possible for us to simply dump any email from any address
@twitter.com?
thanks!
R
/custom/bin/add-project.sh apparently needs some debugging to keep it in
sync with system changes, as running it produced the following errors:
common-lisp.net# sudo /custom/bin/add-project.sh cl-player clin
Creating project cl-player, using handle cl-player in 5 seconds.
Adding group `cl-player' (GID 1008) ...
Done.
Adding user `clin' to group `cl-player' ...
Adding user clin to group cl-player
Done.
ln: failed to create symbolic link `/var/lib/svnroots/cl-player': No
such file or directory
Hit enter to notify cl-player-devel owner...
Subscribed: clin(a)common-lisp.net
Subscribed: sxhash(a)gmail.com
Add members to a list from the command line.
Usage:
add_members [options] listname
Options:
[…]
You must supply at least one of -r and -d options. At most one of the
files can be `-'.
No such list: cl-player-announce
Configure a list from a text file description.
Usage: config_list [options] listname
Options:
--inputfile filename
[…]
The options -o and -i are mutually exclusive.
No such list "cl-player-cvs"
Creating a default page for cl-player in /project/cl-player/public_html
--
"A screaming comes across the sky. It has happened before, but there
is nothing to compare to it now."
Hi all,
As proposed earlier this year [1], common-lisp.net will stop running
darcsweb repository browsing and in fact will stop "supporting" Darcs
completely. As a result, it makes sense to the common-lisp.net admins to
convert projects with Darcs repositories to Git+GitLab, as that's the only
remaining DVC option on the system.
This is my current thinking with respect to the migration. The migration is
inspired on the approach with the CVS migration with the notable exception
that I do not envision offering projects to migrate to Subversion (offering
only to migrate to Git+GitLab where we supported both Subversion and Git
for CVS migration). Offering to migrate to Subversion doesn't seem to make
sense as it would mean migrating to a centralized VC from a decentralized
one.
These are the steps that I forsee in the preparation of the migration:
1) Determine if there are any Darcs source repositories that map to
existing target repositories,
e.g. because equally named Git repository which was already migrated to
GitLab
2) Run a few test conversions on a test-installation
*** looking for volunteers to help out validate the conversion-runs ***
3) Post a full listing of all paths which will be affected by the
conversion on the common-lisp.net
site for review by anyone interested
These are the steps that I forsee for the migration itself:
1) One week before migration: notify the affected project/user of the
intended migration date
[requesting projects/users to remove any repositories that should not
be migrated]
2) Migrate the repositories as announced
* Repositories in /home will be migrated to individual user accounts
* Repositories in /project will be migrated to GitLab groups
3) Send migration confirmation to the respective affected users/projects
As some users and projects seem to use Darcs repositories to manage their
public_html directories, my current thinking is to convert those
repositories, but leave these in-place so projects can replace them with
git check-outs at a later date
Same as with the CVS migration, it's likely that the migration/conversion
of repositories will be executed in batches.
[1]
https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht…
Could you provide me with your questions and opinions?
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Hi all,
This mail is to announce - with great pleasure, I must add - that today the
last batch of CVS repositories was converted to Git+GitLab, meaning that
CVS is now officially deprecated on common-lisp.net! Again nobody opted to
migrate to Subversion+Trac.
At this point, we have:
379 Git repositories ("projects")
395 GitLab users
435 Groups ("common-lisp.net projects")
Thanks to everybody who helped make the migrations complete smoothly.
It's possible that you find repositories for projects which used to have
their main ("canonical") project repository on common-lisp.net, but which
have their main repository now elsewhere, e.g. on GitHub.com or GitLab.com.
If this is the case, we probably converted an old repository. Please report
these cases so we can set up mirrorring from the canonical source to the
gitlab.common-lisp.net repository. That way we don't serve outdated
content. Thanks in advance!
Next steps include dismantling the CVS infrastructure on the box as well as
moving on to migrating the Darcs repositories to Git+GitLab in the same way
as has happened with the CVS repositories.
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
