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

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 24 Mar '15

24 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