clo-devel March 2015

clo-devel@common-lisp.net

12 participants
22 discussions

[clo-devel] Resigning as c-l.net administrator
by Hans Hübner 08 Apr '15

08 Apr '15

Hi folks, I have decided that after a few years, I do no longer want to be operating common-lisp.net - It was fun, but it is time to move on. I have been dealing with mailman administration (handling bounces, occasional password changes, list creation), and with user and project administration. I will be responding to RT requests until the end of this year. Afterwards, I won't do it anymore. I'll also revoke my own root access. If anyone reading this wants to seize responsibility and get some guidance from me, let me know. Cheers, Hans

6 5

[account-creation]
by Daniel Kochmański 30 Mar '15

30 Mar '15

Hello, I'm writing with a question and request. I've spotted a bug on wiki of cl-weblocks (its hosted on trac.common-lisp.net) - in order to modify it and correct, I do need trac.common-lisp.net account? If yes, how to acquire it? Best regards, Daniel Kochmański -- Daniel Kochmański | Poznań, Poland ;; aka jackdaniel "Be the change that you wish to see in the world." - Mahatma Gandhi

2 1

First trial migrating mailing list archives back in place
by Erik Huelsmann 29 Mar '15

29 Mar '15

Hi all, Migrating the old mailing list archives back in place will be a multi-step plan. I've copied over the archives of the mailman lists which don't have an active list. Please check out the test-outcome here: https://mailman-test.common-lisp.net/pipermail/ Any review and comments highly appreciated. Please do note that the archives of active lists need to be merged, something to be addressed in a later step. The same applies to the mmjlm archives: they still have to be merged with the mailman archives. This will happen later. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

GitLab migration and Go-Live
by Erik Huelsmann 28 Mar '15

28 Mar '15

Progress of the GitLab installation and migration scripts has been very good. With some last tests to go, we're confident we can complete installation and migration on *Friday March 20th, 2015. The window 08:00h - 12:00h UTC* has been designated to perform installation and migration. During that window *existing git repositories with public visibility* (i.e. http or gitweb access -- git:// access not counted) will be migrated into GitLab [0]. There's no impact on Subversion, CVS, mercurial, darcs or bazaar repositories. Users with git repositories without http or gitweb access, who want to use GitLab for their project are kindly requested to contact the site admins. After the migration, *migrated repositories will be removed from their current physical path locations*. Repositories will *only* be accessible through GitLab and stored in a location managed by GitLab. Users who want to make backups should do so by keeping a local clone of their git repository(-ies). As part of the migration, *GitLab accounts will be created for all users* of the common-lisp.net system. Each user with a .forward file in their home directory on the system will receive an account confirmation e-mail. This confirmation request is valid for 48 hours. *All accounts must be confirmed before use* - the system blocks accounts until confirmed. Your account can be used immediately after confirmation, even during the migration window. As part of the migration, SSH keys found in the user's home directory will be imported into the user's GitLab account. You will receive an e-mail to confirm this happened. As part of the migration, *Gitlab groups will be created*, mirroring the common-lisp.net "project" concept. Users currently part of a project by virtue of being member of a unix group on common-lisp.net will be assigned GitLab group membership for the mirror group in the role of Owner. Notification mails are sent out due to the migration process. Projects that wish to use GitLab's more fine-grained permisssions[1] can do so after migration completes. As part of the migration, *existing git repositories will be imported into GitLab* under the group or account which mirrors the common-lisp.net project or account. All repositories will have a *public* visibility. Each repository on common-lisp.net becomes a *project* in GitLab. This means each repository gets an issue tracker and wiki set up. Any project that wishes not to use those can turn those off in the Settings page for the GitLab project after the migration. Due to the nature of the migration process, *the Administrator account will be a member of all GitLab projects and groups.* This can be corrected after the migration. After the migration, gitweb access won't be available anymore. It will be replaced by URL redirection to GitLab. git:// protocol support won't be available anymore either. While the migration is in progress, SSH access to the system will be blocked to prevent repositories being updated while migrated. Should you want to start a new project in GitLab, please ask the site admins to create a group for it. Please note that this is just one of the steps in the restructuring plan for common-lisp.net. Further steps as indicated in [2] will be executed later and will affect repositories for other version control systems as well as other services. In case of questions please follow up to clo-devel(a)common-lisp.net: the announcements mailing list is closed for posting. [0] Full list of affected repositories: https://common-lisp.net/gitlab-migration-repository-mapping/ (note: updated today!) [1] https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/permissions/permiss… [2] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000161.ht… -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

4 7

Viewing cmucl src/lisp is really, really slow
by Raymond Toy 27 Mar '15

27 Mar '15

Not sure what's going on, but when I visit https://gitlab.common-lisp.net/cmucl/cmucl/tree/master/src/lisp to see the current changes, the "Loading commit data" just spins and spins for at least a minute. It still hasn't loaded any commit data yet. In fact most subdirectories from the top of the tree are really slow. Not a big deal, but thought it might be important to mention this. -- Ray

2 2

Re: Timing upgrade to GitLab 7.9
by Mark Evenson 26 Mar '15

26 Mar '15

> On 23 Mar 2015, at 20:13, Erik Huelsmann <ehuels(a)gmail.com> wrote: > > Hi Mark, > > GitLab 7.9.0 has been released. Even though the release blog mentions their content with the size of the release, I'm usually a bit weary when it comes to big releases, so, I'm also weary to install a .0 release. However, GitLab never seems to make it into the high patch release numbers. > > The reason I'd like to have the 7.9 release on common-lisp.net soon is: > > - Allow admins to override restricted project visibility settings > > Which means I can put /custom and the site in private repositories which seems to suit people best. > > Before I install it on the site, I want to be sure to run a test install (or two) on the secondary VM. This may or may not overlap with your work on Trac. Could you let me know of a suitable time to test this upgrade? I have no constraints on deployment: do when it suits you. trac-1.0.4 builds and installs fine, but that can be done as a live upgrade whenever we’re ready. The real problem is finding an OAuth 2 implementation, to enable OpenID Connect. I’m still working on the OAuth story. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 1

Error 500 getting blame info
by Raymond Toy 26 Mar '15

26 Mar '15

For kicks, I just tried to get some blame info for https://gitlab.common-lisp.net/cmucl/cmucl/blame/master/src/assembly/sparc/… by clicking on the blame button. I get error 500 that something (unspecified) went wrong. This happens for all the files I've tried. Pressing the History button works, though. -- Ray

1 0

mailman list info links, and archives
by Anton Vodonosov 25 Mar '15

25 Mar '15

Hi, Home pages of many projects have links to their mailing lists information page like https://common-lisp.net/cgi-bin/mailman/listinfo/cl-plus-ssl-devel Currently the links in this form are broken. Probably it makes sense to map such URLs to the current location: https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/cl-plus-ssl-devel Also, the archives only include messages since April 2014. As far as I know the archives from the old incarnation of common-lisp.net still exist. It would be nice to restore them. (It's a reminder, I suppose cl.net admins are aware about the archives problem) Best regards, - Anton

3 3

GitLab migration and existing links to source code
by Anton Vodonosov 24 Mar '15

24 Mar '15

Hi At the https://common-lisp.net/project/cl-stm/ there is a link "Browse the latest source code". It refers to https://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-stm-cl-stm%3ba=s… As I understand, darcs repos were migrated to GitLab. Maybe it makes sense to map the old URLs to the corresponding GitLab URls? Best regards, - Anton

2 4

Mailman moderation notices
by Stelian Ionescu 23 Mar '15

23 Mar '15

I've recently been receiving these messages saying "Notice: 1 old request(s) automatically expired", which weren't sent previously. Can you disable them globally ? They're not helpful at all. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

2 1

Gitlab anonymous access
by Stelian Ionescu 23 Mar '15

23 Mar '15

I just noticed that gitlab requires authentication. I don't think this is a good idea because it prevents all those that don't have an account to even view the repositories. Also, can we just use git.common-lisp.net ? That currently points to the ABCL homepage which is very confusing. -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

2 3

common-lisp.net GitLab deployment and migration completed successfully
by Erik Huelsmann 22 Mar '15

22 Mar '15

common-lisp.net has successfully deployed GitLab and migrated users, groups, group-memberships and the existing publicly visible git repositories to it. Redirection rules for git access, gitweb and trac have been established and tested. In the migration, we created 390 users, 434 gitlab groups (=projects) and 210 gitlab projects (= git repositories). Should you experience problems, please discuss on clo-devel(a)common-lisp.net or report to admin(a)common-lisp.net. Repositories are no longer available under their original locations. Repositories which *are* still in their original locations, have not been migrated to GitLab. The code to seed the system, was written in Common Lisp. In order to do so, we wrote a (minimal) web binding for GitLab's web API. The sources are in a Mercurial repository available at https://common-lisp.net/~ehuelsmann/cl-gitlab and will be moved to https://gitlab.common-lisp.net/cl-gitlab shortly. We hope you enjoy our improved user experience! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 7

Deletion of empty Subversion repositories (357 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 357 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/svn /project/adw-charting/svn /project/ait/svn /project/alexandria/svn /project/anaphora/svn /project/araneida/svn /project/armish/svn /project/arxana/svn /project/asdf-binary-locations/svn /project/asdf-packaging/svn /project/asdf-system-connections/svn /project/asia/svn /project/aspectl/svn /project/aspiwork-pdm/svn /project/babel/svn /project/bayescl/svn /project/bdb/svn /project/beep/svn /project/beirc/svn /project/berkeley-db/svn /project/bese/svn /project/boston-lisp/svn /project/bpm/svn /project/buclet/svn /project/bytemap/svn /project/c2ffi/svn /project/cdr/svn /project/cello/svn /project/cells/svn /project/cells-gtk/svn /project/cells-ode/svn /project/cffi/svn /project/chemboy/svn /project/chtml-matcher/svn /project/cinline/svn /project/cl-amqp/svn /project/cl-api/svn /project/clappa/svn /project/cl-applescript/svn /project/clazy/svn /project/cl-berkeley-db/svn /project/cl-bio/svn /project/cl-blog/svn /project/cl-buchberger/svn /project/clbuild/svn /project/cl-bzip2/svn /project/cl-cactus-kev/svn /project/cl-captcha/svn /project/cl-carbon/svn /project/cl-clickatell/svn /project/cl-cli-parser/svn /project/cl-cont/svn /project/cl-couch/svn /project/cl-cracklib/svn /project/cl-date-calc/svn /project/cl-dbf/svn /project/cl-def/svn /project/cl-dises/svn /project/cldoc/svn /project/cl-dwim/svn /project/cl-ec2/svn /project/cl-emb/svn /project/cl-enumeration/svn /project/cleric/svn /project/cl-fltk/svn /project/cl-fuse/svn /project/cl-gdbm/svn /project/clget/svn /project/cl-glpk/svn /project/cl-godb/svn /project/cl-graph/svn /project/cl-graphviz/svn /project/cl-gsl/svn /project/cl-gtk2/svn /project/cl-hooks/svn /project/clhp/svn /project/cliki/svn /project/climacs/svn /project/clim-desktop/svn /project/climplayer/svn /project/cl-interpol/svn /project/cl-ipc/svn /project/cl-irregsexp/svn /project/cl-jpeg/svn /project/cl-json/svn /project/clkd/svn /project/cl-l10n/svn /project/cl-launchpad/svn /project/cl-lazy-list/svn /project/cl-lexer/svn /project/cl-librarian/svn /project/cl-machine-learning/svn /project/cl-magick/svn /project/cl-markdown/svn /project/cl-match/svn /project/cl-mathstats/svn /project/cl-memcached/svn /project/cl-menusystem/svn /project/cl-migrations/svn /project/cl-mp3-parse/svn /project/cl-mpd/svn /project/cl-mpi/svn /project/cl-muproc/svn /project/cl-objc/svn /project/cl-octave/svn /project/cl-ode/svn /project/clois-lane/svn /project/clonsigna/svn /project/cl-opengl/svn /project/cl-openid/svn /project/cl-org-mode/svn /project/closer/svn /project/closure/svn /project/clotnet/svn /project/clouchdb/svn /project/cloud/svn /project/cl-pdf/svn /project/cl-peg/svn /project/cl-perec/svn /project/cl-plplot/svn /project/cl-plus-j/svn /project/cl-plus-ssl/svn /project/cl-pop/svn /project/cl-ppcre/svn /project/cl-prevalence/svn /project/cl-proc/svn /project/clpython/svn /project/cl-quasi-quote/svn /project/cl-rdbms/svn /project/cl-rope/svn /project/cl-rundown/svn /project/cl-sbml/svn /project/cl-screen/svn /project/cl-selenium/svn /project/cl-semantic/svn /project/cl-serializer/svn /project/cl-smogames/svn /project/cl-smtp/svn /project/cl-snmp/svn /project/cl-soap/svn /project/cl-sockets/svn /project/clsql-fluid/svn /project/cl-sqlite/svn /project/clsql-mysql-introspect/svn /project/cl-stm/svn /project/cl-stomp/svn /project/cl-store/svn /project/cl-syntax-sugar/svn /project/cl-syslog/svn /project/cl-taint/svn /project/cl-telnetd/svn /project/cl-test-grid/svn /project/cltl3/svn /project/cl-trane/svn /project/cl-twitter/svn /project/cl-typesetting/svn /project/cl-unification/svn /project/cl-uri/svn /project/cl-utilities/svn /project/cl-variates/svn /project/cl-walker/svn /project/cl-wav-synth/svn /project/cl-weblocks/svn /project/cl-who/svn /project/cl-wiki/svn /project/cl-x86-asm/svn /project/cl-xmlspam/svn /project/cl-xmms/svn /project/cl-xmpp/svn /project/cl-yacc-ebnf/svn /project/commonqt/svn /project/computed-class/svn /project/core-services/svn /project/corman-sdl/svn /project/cparse/svn /project/crypticl/svn /project/css-sexp/svn /project/cxml/svn /project/decl/svn /project/defclass-star/svn /project/defdoc/svn /project/defeditor/svn /project/definer/svn /project/defmud/svn /project/defplayer/svn /project/defwm/svn /project/de-setf-graphics/svn /project/docudown/svn /project/docutrack/svn /project/drakma/svn /project/dynamic-classes/svn /project/eager-future/svn /project/ecl/svn /project/eclipse/svn /project/ecl-readline/svn /project/elephant/svn /project/encline/svn /project/erlang-in-lisp/svn /project/erlisp/svn /project/external-program/svn /project/f2cl/svn /project/fiveam/svn /project/flexichain/svn /project/fret/svn /project/ftd/svn /project/fucc/svn /project/gamelib/svn /project/ganelon/svn /project/geco/svn /project/gecol/svn /project/geohash/svn /project/gestalt/svn /project/ginseng/svn /project/glouton/svn /project/gnucard/svn /project/grand-prix/svn /project/gsharp/svn /project/gtk-cffi/svn /project/gzip-stream/svn /project/html-template/svn /project/hyperdoc/svn /project/hyperspec-lookup/svn /project/iaxphone/svn /project/ieee-floats/svn /project/ieeefp-tests/svn /project/imago/svn /project/innen/svn /project/ip-interfaces/svn /project/iso8601-date/svn /project/israel-lisp/svn /project/iterate/svn /project/iterate-clsql/svn /project/jess-parse/svn /project/jnil/svn /project/kpax/svn /project/lambda-gtk/svn /project/langutils/svn /project/lgtk/svn /project/liards/svn /project/lifp/svn /project/limp/svn /project/lineal/svn /project/linedit/svn /project/lispbox/svn /project/lispfaq/svn /project/lisp-interface-library/svn /project/lisp-matrix/svn /project/lisp-on-lines/svn /project/lisppaste/svn /project/lisp-res-kit/svn /project/lispy/svn /project/l-math/svn /project/lmud/svn /project/local-time/svn /project/log4cl/svn /project/log5/svn /project/lw-vim-mode/svn /project/macho/svn /project/macondoolap/svn /project/magicffi/svn /project/mcclim/svn /project/mel-base/svn /project/metacopy/svn /project/meta-cvs/svn /project/metatilities/svn /project/metatilities-base/svn /project/mirror/svn /project/misrouted/svn /project/mkcl/svn /project/mk-defsystem/svn /project/modisc/svn /project/mod-lisp/svn /project/movies/svn /project/movitz/svn /project/named-readtables/svn /project/names-and-paths/svn /project/new-op/svn /project/nixies/svn /project/noctool/svn /project/nrw-xmcl/svn /project/objective-cl/svn /project/oct/svn /project/okra/svn /project/openair/svn /project/osicat/svn /project/pal/svn /project/parenscript/svn /project/parse-declarations/svn /project/patty/svn /project/pg/svn /project/pg-introspect/svn /project/phemlock/svn /project/phorplay/svn /project/plexippus-xpath/svn /project/ply/svn /project/portage-overlay/svn /project/postmodern/svn /project/pretty-function/svn /project/protobuf/svn /project/quiz/svn /project/rcl/svn /project/rclg/svn /project/rfc2109/svn /project/rfc2388/svn /project/rfc2822/svn /project/rjain-utils/svn /project/rucksack/svn /project/same/svn /project/sapaclisp/svn /project/sb-simd/svn /project/sequence-iterators/svn /project/sexpc/svn /project/sfip/svn /project/sheeple/svn /project/sicl/svn /project/slime/svn /project/snmp1/svn /project/sparklines/svn /project/spray/svn /project/sqlisp/svn /project/ssc/svn /project/stamp/svn /project/stdutil/svn /project/stefil/svn /project/suave/svn /project/submarine/svn /project/sudoku/svn /project/s-xml/svn /project/s-xml-rpc/svn /project/teepeedee2/svn /project/tinaa/svn /project/tioga/svn /project/trivial-features/svn /project/trivial-freeimage/svn /project/trivial-garbage/svn /project/trivial-gray-streams/svn /project/trivial-http/svn /project/trivial-iconv/svn /project/trivial-timeout/svn /project/trivial-utf-8/svn /project/ubf/svn /project/ucs-sort/svn /project/ucw/svn /project/ucw-extras/svn /project/umpa-lumpa/svn /project/unetwork/svn /project/uri-template/svn /project/vial/svn /project/vivace-graph/svn /project/wispylisp/svn /project/xcvb/svn /project/xhtmlambda/svn /project/xml-psychiatrist/svn /project/xmls/svn /project/xuriella/svn /project/zip/svn /project/zlib/svn -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel March 2015