- clo-devel - mailman3.common-lisp.net

Deletion of empty CVS repositories (268 of them)
by Erik Huelsmann 21 Mar '15

21 Mar '15

Hi, In my on-going efforts to clean up common-lisp.net, I'll be deleting all empty CVS repositories -- all 268 of them. The large number of empty repositories can be explained by the fact that in the old days, for each project, repositories were created for CVS and Subversion. No project starts using both and in recent years many projects chose to use Mercurial, Darcs or Git. If nobody objects, I'll remove the list of directories below on Saturday March 28th. This is the list of directories that will disappear from the system: /project/able/cvsroot /project/adw-charting/cvsroot /project/ait/cvsroot /project/alexandria/cvsroot /project/ansi-test/cvsroot /project/araneida/cvsroot /project/armedbear/cvsroot /project/armish/cvsroot /project/arxana/cvsroot /project/asdf-addons/cvsroot /project/asdf-binary-locations/cvsroot /project/asdf-packaging/cvsroot /project/asdf-system-connections/cvsroot /project/asia/cvsroot /project/aspectl/cvsroot /project/babel/cvsroot /project/bdb/cvsroot /project/berkeley-db/cvsroot /project/bknr/cvsroot /project/boston-lisp/cvsroot /project/bpm/cvsroot /project/buclet/cvsroot /project/bytemap/cvsroot /project/c2ffi/cvsroot /project/caleb/cvsroot /project/cdr/cvsroot /project/chemboy/cvsroot /project/chtml-matcher/cvsroot /project/cl-amqp/cvsroot /project/cl-api/cvsroot /project/clappa/cvsroot /project/cl-applescript/cvsroot /project/clarity/cvsroot /project/claw/cvsroot /project/cl-bench/cvsroot /project/cl-berkeley-db/cvsroot /project/cl-bio/cvsroot /project/cl-buchberger/cvsroot /project/clbuild/cvsroot /project/cl-bzip2/cvsroot /project/cl-cactus-kev/cvsroot /project/cl-cairo2/cvsroot /project/cl-captcha/cvsroot /project/cl-clickatell/cvsroot /project/cl-colors/cvsroot /project/cl-cont/cvsroot /project/cl-couch/cvsroot /project/cl-curl/cvsroot /project/cl-darcs/cvsroot /project/cl-def/cvsroot /project/cl-dises/cvsroot /project/cl-dwim/cvsroot /project/cl-ec2/cvsroot /project/cl-emb/cvsroot /project/cleric/cvsroot /project/cl-facebook/cvsroot /project/cl-fuse/cvsroot /project/clget/cvsroot /project/cl-glpk/cvsroot /project/cl-graph/cvsroot /project/cl-graphviz/cvsroot /project/cl-gtk2/cvsroot /project/cl-heap/cvsroot /project/cl-hooks/cvsroot /project/cliki/cvsroot /project/climplayer/cvsroot /project/cl-irregsexp/cvsroot /project/cl-json/cvsroot /project/cl-kanren-trs/cvsroot /project/clkd/cvsroot /project/cl-launchpad/cvsroot /project/cl-lazy-list/cvsroot /project/cl-lexer/cvsroot /project/cl-librarian/cvsroot /project/cl-machine-learning/cvsroot /project/cl-markdown/cvsroot /project/cl-match/cvsroot /project/cl-mathstats/cvsroot /project/cl-memcached/cvsroot /project/cl-migrations/cvsroot /project/cl-monad-macros/cvsroot /project/cl-mpd/cvsroot /project/cl-mpi/cvsroot /project/cl-muproc/cvsroot /project/cl-ncurses/cvsroot /project/cl-neo4j/cvsroot /project/cl-net-snmp/cvsroot /project/cl-objc/cvsroot /project/cl-octave/cvsroot /project/cl-ode/cvsroot /project/clois-lane/cvsroot /project/clonsigna/cvsroot /project/cl-opengl/cvsroot /project/cl-openid/cvsroot /project/cl-org-mode/cvsroot /project/closer/cvsroot /project/clotnet/cvsroot /project/cloud/cvsroot /project/cl-pdf/cvsroot /project/cl-peg/cvsroot /project/cl-perec/cvsroot /project/cl-plus-j/cvsroot /project/cl-pop/cvsroot /project/cl-proc/cvsroot /project/clpython/cvsroot /project/cl-quasi-quote/cvsroot /project/cl-rdbms/cvsroot /project/cl-rundown/cvsroot /project/cl-serializer/cvsroot /project/cl-sockets/cvsroot /project/clsql-fluid/cvsroot /project/cl-sqlite/cvsroot /project/clsql-mysql-introspect/cvsroot /project/cl-stm/cvsroot /project/cl-stomp/cvsroot /project/cl-syntax-sugar/cvsroot /project/cl-taint/cvsroot /project/cltl3/cvsroot /project/cl-trane/cvsroot /project/cl-twitter/cvsroot /project/cl-typesetting/cvsroot /project/cl-uri/cvsroot /project/cl-variates/cvsroot /project/cl-walker/cvsroot /project/cl-weblocks/cvsroot /project/cl-wiki/cvsroot /project/cl-xml/cvsroot /project/cl-xmlspam/cvsroot /project/cl-yacc-ebnf/cvsroot /project/common-lisp-beginner/cvsroot /project/common-math/cvsroot /project/commonqt/cvsroot /project/computed-class/cvsroot /project/core-services/cvsroot /project/css-sexp/cvsroot /project/decl/cvsroot /project/defclass-star/cvsroot /project/defmud/cvsroot /project/de-setf-amqp/cvsroot /project/de-setf-graphics/cvsroot /project/docudown/cvsroot /project/docutrack/cvsroot /project/drakma/cvsroot /project/dynamic-classes/cvsroot /project/dyslexia/cvsroot /project/eager-future/cvsroot /project/ecl-readline/cvsroot /project/editor-hints/cvsroot /project/encline/cvsroot /project/erlang-in-lisp/cvsroot /project/erlisp/cvsroot /project/external-program/cvsroot /project/f2cl/cvsroot /project/flexi-streams/cvsroot /project/fret/cvsroot /project/fset/cvsroot /project/ftd/cvsroot /project/fucc/cvsroot /project/geco/cvsroot /project/gecol/cvsroot /project/geohash/cvsroot /project/gestalt/cvsroot /project/gnucard/cvsroot /project/grand-prix/cvsroot /project/graphic-forms/cvsroot /project/gzip-stream/cvsroot /project/ht-ajax/cvsroot /project/iaxphone/cvsroot /project/ieee-floats/cvsroot /project/innen/cvsroot /project/ip-interfaces/cvsroot /project/isidorus/cvsroot /project/israel-lisp/cvsroot /project/iterate/cvsroot /project/iterate-clsql/cvsroot /project/jess-parse/cvsroot /project/kpax/cvsroot /project/langutils/cvsroot /project/liards/cvsroot /project/lifp/cvsroot /project/limp/cvsroot /project/lineal/cvsroot /project/lispbox/cvsroot /project/lisplab/cvsroot /project/lisp-matrix/cvsroot /project/lisp-on-lines/cvsroot /project/lisp-res-kit/cvsroot /project/l-math/cvsroot /project/local-time/cvsroot /project/log5/cvsroot /project/lw-vim-mode/cvsroot /project/macho/cvsroot /project/macondoolap/cvsroot /project/magicffi/cvsroot /project/mel-base/cvsroot /project/metacopy/cvsroot /project/metatilities/cvsroot /project/metatilities-base/cvsroot /project/mirror/cvsroot /project/misrouted/cvsroot /project/mkcl/cvsroot /project/modisc/cvsroot /project/mod-lisp/cvsroot /project/movies/cvsroot /project/named-readtables/cvsroot /project/names-and-paths/cvsroot /project/new-op/cvsroot /project/nixies/cvsroot /project/nrw-xmcl/cvsroot /project/nxtlisp/cvsroot /project/objective-cl/cvsroot /project/okra/cvsroot /project/openair/cvsroot /project/parenscript/cvsroot /project/parse-declarations/cvsroot /project/patty/cvsroot /project/pg-introspect/cvsroot /project/phorplay/cvsroot /project/plexippus-xpath/cvsroot /project/ply/cvsroot /project/portage-overlay/cvsroot /project/postmodern/cvsroot /project/pretty-function/cvsroot /project/protobuf/cvsroot /project/py-configparser/cvsroot /project/python-on-lisp/cvsroot /project/quiz/cvsroot /project/rcl/cvsroot /project/rclg/cvsroot /project/rfc2109/cvsroot /project/same/cvsroot /project/sequence-iterators/cvsroot /project/sexpc/cvsroot /project/sheeple/cvsroot /project/sicl/cvsroot /project/snow/cvsroot /project/sparklines/cvsroot /project/sqlisp/cvsroot /project/ssc/cvsroot /project/stdutil/cvsroot /project/steeldump/cvsroot /project/stefil/cvsroot /project/suave/cvsroot /project/submarine/cvsroot /project/sudoku/cvsroot /project/tbnl/cvsroot /project/teepeedee2/cvsroot /project/the-feebs-war/cvsroot /project/tinaa/cvsroot /project/tioga/cvsroot /project/trivial-features/cvsroot /project/trivial-garbage/cvsroot /project/trivial-http/cvsroot /project/trivial-timeout/cvsroot /project/trivial-utf-8/cvsroot /project/ubf/cvsroot /project/ucs-sort/cvsroot /project/ucw/cvsroot /project/ucw-extras/cvsroot /project/umpa-lumpa/cvsroot /project/uri-template/cvsroot /project/vial/cvsroot /project/vivace-graph/cvsroot /project/wispylisp/cvsroot /project/xcvb/cvsroot /project/xml-psychiatrist/cvsroot /project/xmls/cvsroot /project/xuriella/cvsroot -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Cannot log in?
by Drew C 19 Mar '15

19 Mar '15

Hey, So I have not tried to log in to the new server until now. ssh dcrampsie(a)common-lisp.net Permission denied (publickey). and ssh drewc(a)common-lisp.net Permission denied (publickey). I used to be able to do just that, or use a password if/when my pkey did not work. Things have changed, but I would like to login :) -- drewc

2 1

Two ssh keys for common-lisp.net?
by Mark Evenson 16 Mar '15

16 Mar '15

I keep getting messages about SSH key mismatch for common-lisp.net. It seems that two SSH keys are being negotiated for my client where it isn’t clear which one is chosen: 148.251.248.130 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBJi/0OMu3anrn4jRBQ0KumZUaIWLKb59q4egMU2ljgvBk7Fgvl3tcwphJzETqB0Rap0n8naR/pj5SDNzenjLgQo= 148.251.248.130 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC1/IAysdjPDZvOfpFESxhhokPmPrXi2n3dy3HfWDe0mQvkki0cJYPwhsKDe28uIneMUOMWUYCDI6FD6/phLrQQww2K88SXs3hskj4ZWjwNz0UTaYBoutRc9KxIPC6/heglREC2JMrnQBVDqPoKQalt3JfU6rFA93kpzF/gEvQ/toEOVZi55KpKDzdd/gjPsUCKOzNxCptFkkkOsigeOfNgSu9J/ptrqseu3T0zJtCnuIudvkgRUj0RMVNBJ/UvvWb3XSCAVMkMtF8Ml7pRy3+JV1RCbwbgZZDchQnwsunIFXhc/hWUyCfsX4nmZgx1qPeGYmUdo/Un5QNT6MKyFrm1 And indeed <file://common-lisp.net/etc/sshd_config> lists three keys: HostKey /etc/ssh/ssh_host_rsa_key HostKey /etc/ssh/ssh_host_dsa_key HostKey /etc/ssh/ssh_host_ecdsa_key I’m not familiar with this practice. What is the purpose of having multiple sshd keys? Shouldn’t we just pick the most secure kind of host key (probably ECDSA)? -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

[Clo-devel] Fwd: Testing GitLab installation & migration nearing completion: steps to cut-over
by Erik Huelsmann 09 Mar '15

09 Mar '15

Accidentally hit Reply instead of Reply-to-all. ---------- Forwarded message ---------- From: Erik Huelsmann <ehuels(a)gmail.com> Date: Mon, Mar 9, 2015 at 9:08 PM Subject: Re: [Clo-devel] Testing GitLab installation & migration nearing completion: steps to cut-over To: Raymond Toy <toy.raymond(a)gmail.com> Hi Raymond, On Mon, Mar 9, 2015 at 4:41 PM, Raymond Toy <toy.raymond(a)gmail.com> wrote: > >>>>> "Erik" == Erik Huelsmann <ehuels(a)gmail.com> writes: > > [snip] > > Erik> Another important thing to note is that repositories having > Erik> been brought under GitLab control, will no longer be > Erik> available on their old locations. For gitweb, there will be > Erik> redirect rules instated, as will there be for direct > Erik> repository access over https. > > Does that mean any repos using hg will get converted too and not be > available from their old locations? No: they'll stay right where they currently are. I've thought about offering migration to GitLab, but there's relatively little for common-lisp.net to win (I think): we don't support (and won't in the future) repository browsing with any tools (right?). So, all that we'd win is to be able to delete the 'hg' binary from the system. Well, that's too little gain for the pain. > What does this mean for the Trac "Browse Source" button? Will these get > updated appropriately? > Hmm. I don't know how to do that, really. Basically, the plan as it's laid out now, assumes that all git projects move their source browsing over to gitlab. CMUCL uses a non-common-lisp.net-standard configuration for Trac. I don't really know how many projects currently do the same. I'll need to look into that. Basically, my solution would be to redirect all "browse", "tickets" and "wiki" urls to the gitlab namespace for those projects that used Trac to go with Git/Darcs. Not that it matters all that much. I do plan on converting my one and > only hg repo to git, if it's not done for me as part of the migration. > It's planned, but not for this migration. You're absolutely welcome to do it yourself as soon as the system is opened for general access. May I ask that you mark the Mercurial repository in some recognizable way that it should not be migrated, or better yet, that you make a local copy for yourself and remove the repository from the common-lisp.net system, so it doesn't get migrated twice? Thanks! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

[Clo-devel] Fwd: Testing GitLab installation & migration nearing completion: steps to cut-over
by Erik Huelsmann 09 Mar '15

09 Mar '15

The conversation below may be relevant to the members of this mailing list. ---------- Forwarded message ---------- From: Erik Huelsmann <ehuels(a)gmail.com> Date: Mon, Mar 9, 2015 at 8:57 PM Subject: Re: Testing GitLab installation & migration nearing completion: steps to cut-over To: Robert Swindells <rjs(a)fdy2.co.uk> Hi Robert, On Mon, Mar 9, 2015 at 1:33 PM, <rjs(a)fdy2.co.uk> wrote: > "Erik Huelsmann" <ehuels(a)gmail.com> wrote: > > Hi all, > > > > > > As some of you have noticed this weekend, we're still working on > migrating > > the common-lisp.net repositories to GitLab. While doing so, a few > e-mails > > have been sent out while they should have been held and deleted on the > > testing system. My appologies if it caused confusion or inconvenience. > > Would it be possible to keep using Subversion for the mit-cadr repository ? > > Yes! *Nothing* is going to happen to Subversion repositories. This migration concerns Git repositories for now, but the bigger trend will impact the following VC systems: CVS, darcs, Git, mercurial (but not Subversion) as laid out in this mail: https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000168.ht… -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

[Clo-devel] Fwd: Access to group was granted
by Jean-Claude Beaudoin 09 Mar '15

09 Mar '15

Hello cl.net admins, Yesterday I received the email here below. Does this mean that I now have an account on gitlab? And if yes, then how can I come to know its password? I guess that this is part of the coming migration to gitorious/gitlab as git service of cl.net, isn't it? Regards, Jean-Claude Beaudoin ---------- Forwarded message ---------- From: GitLab <gitlab(a)common-lisp.net> Date: Sat, Mar 7, 2015 at 6:11 PM Subject: Access to group was granted To: jcbeaudoin(a)common-lisp.net You have been granted Owner access to group cl-plus-j <https://gitlab-test.common-lisp.net/groups/cl-plus-j> — View it on GitLab <https://gitlab-test.common-lisp.net/groups/cl-plus-j>

3 2

[Clo-devel] Testing GitLab installation & migration nearing completion: steps to cut-over
by Erik Huelsmann 09 Mar '15

09 Mar '15

Hi all, As some of you have noticed this weekend, we're still working on migrating the common-lisp.net repositories to GitLab. While doing so, a few e-mails have been sent out while they should have been held and deleted on the testing system. My appologies if it caused confusion or inconvenience. So far, we've run multiple successful installation-and-configuration runs. We have also successfully completed seeding the system with users, groups and group members. There are a few things that need some more testing, which will be done over the next week or so: * Importing of users' public SSH keys * Apache gitweb redirect rules to the relevant GitLab URLs * Repository migration script (the script that moves the repositories under GitLab control) While we're working on these last steps, it would be highly appreciated if people would take a bit of time to review the repository mapping published on https://common-lisp.net/gitlab-migration-repository-mapping/ . The page lists all existing public git repositories, from both users and projects. On the listing, you can see under which name the repository will be mapped to the GitLab system. We expect to complete testing in the next two weeks, so if you could provide your feedback by Friday 13th, that would fit the timelines best. Then a little about the actual cut-over. On the day of the cut-over (most likely a Sunday morning, CET), the scripts that we have developed over the past weeks will be run in close succession. This means we'll be installing GitLab, creating users, creating groups, assigning users to groups (creating members, in GitLab terminology) and importing git repositories in the GitLab system. The entire process should not take more than a few hours. The system sends out a number of mails during the seeding phase, some or all of which you may receive: * Account confirmation - after account creation, the system requires verification before the account can be used * Membership creation - after your account has been assigned membership in a project, you'll be notified by mail about that * Import of SSH keys - after an SSH key has been associated with a user that user is notified of that fact It's possible that you won't get mail from account creation, if your common-lisp.net account doesn't have a .forward file. In that case, now would be a good time to create one, if you want to use your GitLab account. Another important thing to note is that repositories having been brought under GitLab control, will no longer be available on their old locations. For gitweb, there will be redirect rules instated, as will there be for direct repository access over https. If you have questions, please follow up to this mail on clo-devel(a)common-lisp.net. The announcements channel is closed for posting. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

[Clo-devel] Trac logins
by Raymond Toy 07 Mar '15

07 Mar '15

Did something happen to trac lately? I tried to login to cmucl's trac instance and my saved password no longer works. (I'm not 100% sure my saved password is correct, but whatever was saved always worked before.) If something did happen, please feel free to reset my password. Thanks, Ray

2 2

[Clo-devel] IP4 address change
by Mark Evenson 04 Mar '15

04 Mar '15

We’ve recently changed the IP4 address of common-lisp.net. Is this change intended to be permanent? illin:~$ host lisp.not.org lisp.not.org has address 144.76.188.67 lisp.not.org has IPv6 address 2a01:4f8:200:4310::30 illin:~$ host common-lisp.net common-lisp.net has address 148.251.248.130 common-lisp.net has IPv6 address 2a01:4f8:200:4310::30 common-lisp.net mail is handled by 10 mail.common-lisp.net. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 2

[Clo-devel] Proposed organization of projects, groups and members in GitLab for common-lisp.net
by Erik Huelsmann 24 Feb '15

24 Feb '15

Hi, Trying to keep the mail short; sent too many essays already :-) So, some context regarding GitLab's structure: - each project has: + one repository + at most one issue tracker + at most one wiki + at most one snippets archive + at least one member - each group has: + one or more members + zero or more projects - each user: + has zero or more projects + is a member of zero or more groups and/or projects with a certain access level Now, every member of a group is automatically a member of the group's projects. I propose we map common-lisp.net's projects to gitlab's groups since our projects can (and do) have multiple repositories. Since our current projects don't distinguish in access level between project members, we should map access level to the highest available: owner. Our repositories map to GitLab's projects. All GitLab projects are owned by a group if found in the /project filesystem hierarchy. All personal repositories (those found in /home) will be directly owned to users. Users may choose to assign others access rights other than reading. The system's login accounts will map to GitLab users. GitLab group membership will be determined using the current method of project membership: being member of a certain group in the /etc/group file. Then there's one aspect left not discussed: project visibility. All project repositories (those found in the /project hierarchy) will be assigned to public projects. All public user repositories (those found in /home/<user>/public_html/* or those linked from /var/git/projects/users/*) will be assigned public visibility. All other user repositories will be assigned "Internal" visibility (visible only to logged-in users). Comments? -- Bye, Erik. http:// <http://efficito.com/>efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock in.

1 0