- announcements - mailman3.common-lisp.net

CVS repository migration completed!
by Erik Huelsmann 12 May '15

12 May '15

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.netrepository. 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.

1 0

Migration of common-lisp.net CVS repositories -- GitLab push e-mail configuration
by Erik Huelsmann 11 Apr '15

11 Apr '15

Hi, This mail serves to announce two common-lisp.net related news items: 1. CVS repository migration 2. GitLab push e-mail configuration FAQ added == CVS repository migration == As previously discussed on clo-devel(a)common-lisp.net, common-lisp.net is dropping support for CVS [1]. To that extent, projects which have CVS repositories will receive an e-mail over the coming weeks offering the choice to migrate to Subversion or Git. Mails and migrations will be sent out in batches, so members may not receive messages for all projects at once. The default migration is to Git+GitLab [2]. Projects can request migration to Subversion+Trac when Git isn't acceptable. If projects want to file a request to migrate to Subversion in advance of their migration notice, please file a ticket at https://trac.common-lisp.net/clo/newticket After migration, the CVS repository will no longer be accessible. After all CVS repositories have been migrated, the following services will be scrapped: * Anonymous CVS checkout * ViewVC webbrowsing (for Subversion already available through Trac) [1] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht… [2] https://gitlab.common-lisp.net/ == GitLab push e-mail configuration == Some projects had push e-mail configured in conjunction with their <project>-cvs(a)common-lisp.net mailing list. Due to the migration to GitLab, this functionality stopped working. Today, we've published a FAQ item detailing how to configure GitLab and Mailman to get the same result. See https://common-lisp.net/faq/emailonpush/ how to get this configuration for your project. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

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

20 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.

1 0

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

16 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.

1 0

Testing GitLab installation & migration nearing completion: steps to cut-over
by Erik Huelsmann 08 Mar '15

08 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.

1 0

Intended policy changes for mailing list setup
by Erik Huelsmann 19 Feb '15

19 Feb '15

Dear common-lisp.net users, mailing list owners, You're receiving this message because you're listed as a mailing list owner or because you have a common-lisp.net login account. If you have different mail addresses associated with both, you may get multiple copies. Apologies for that in advance. We're sending this mail to announce policy changes intended to be executed as of March 15th regarding mailing list setup. [For further discussion, please direct to clo-devel(a)common-lisp.net.] Changes to mailing list headers and footer ========================================== Google is tightening their DKIM validation; most of our mailing lists cause invalid DKIM signatures on out-going mails: * Adding the Subject prefix '[<mailing list>]' invalidates the DKIM signature of the original sender * Adding the e-mail footer may invalidate the e-mail's DKIM signature Since Google, Yahoo! and other big mail providers are moving to signing their outgoing mail, the percentage of invalid mail sent by common-lisp.net increases. This hurts our reputation as a mail sender and has led to problems with Google accepting common-lisp.net mail. (Admitted, DKIM was not the only reason.) Due to the above, we will change the mailing list setup for all mailing lists: * No longer add the mailing list subject prefix * No longer add the mailing list footer * Add the List-* headers as per RFC-2369, filtering of mailing list messages can be done using these fields Change to moderation expiration ======================== Additionally, we've found that many mailing lists have been set to not expire mails in the moderation queue, resulting in a moderation queue of 10-thousands of mails some more than 8 months old. Recognizing most of these mails are probably not being moderated because they are spam, we intend to change all mailing lists which do not expire their moderation queue to expire moderation requests after 90 days. Again, the above is an intended policy change. Please send feedback on clo-devel(a)common-lisp.net. Kind regards, common-lisp.net admins

1 0

[Announcements] [Mkcl-announce] C-based runtime of MKCL passes Coverity scan.
by Jean-Claude Beaudoin 24 Oct '14

24 Oct '14

Hello all, I am happy to announce you that the C-based runtime of MKCL has passed with great success the scrutiny of the source code scanning tool of Coverity. After a bit more than a week of use of that tool, Coverity now reports a defect density of 0.01 per 1000 lines for MKCL C-runtime on Linux and a defect density of 0.00 per 1000 lines for MKCL C-runtime on Microsoft Windows (Win32 and Win64). The code submitted to Coverity for these results currently sits in our Github repository on head of the master branch. This code will be the basis of upcoming version 1.1.10. I hope to release 1.1.10 in a few weeks, after some updates to its "contrib" bundle. Cheers, Jean-Claude Beaudoin _______________________________________________ Mkcl-announce mailing list Mkcl-announce(a)common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/mkcl-announce

1 0

[Announcements] [Mkcl-announce] MKCL 1.1.9 is now available
by Jean-Claude Beaudoin 05 Jul '14

05 Jul '14

MKCL 1.1.9 is now available for general use. For the most part it is a compilation of minor bug fixes along with one notable sub-component upgrade, i.e.: the GC has been upgraded from bdwgc 7.2c to bdwgc 7.4 in hope it will be a better fit for the upcoming ARM/iOS/Android ports. One relevant change in the GC configuration happened on all MS-Windows versions where it is now hard configured to avoid the use of function SignalObjectAndWait since Microsoft has reneged on its promise of atomic behavior. If you observe a deadlock of MKCL 1.1.8 or earlier on MS-Windows 7 or later this would be a possible cause. You should then either upgrade to MKCL 1.1.9 or later, or set the environment variable MK_GC_MARKERS to 0 in order to prevent parallel marking and its use of SignalObjectAndWait. I hope that MKCL 1.1.9 will be the last in the MKCL 1.1.X line before the release of MKCL 1.2.0 in the coming months. Cheers, Jean-Claude Beaudoin _______________________________________________ Mkcl-announce mailing list Mkcl-announce(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/mkcl-announce

1 0

Welcome to iolib-announce@common-lisp.net
by iolib-announce+help＠common-lisp.net 12 Apr '13

12 Apr '13

Welcome! You have been subscribed to the iolib-announce(a)common-lisp.net mailinglist. To unsubscribe send a message to: iolib-announce+unsubscribe(a)common-lisp.net And for help send a message to: iolib-announce+help(a)common-lisp.net

1 0

Welcome to fiveam-announce@common-lisp.net
by fiveam-announce+help＠common-lisp.net 12 Apr '13

12 Apr '13

Welcome! You have been subscribed to the fiveam-announce(a)common-lisp.net mailinglist. To unsubscribe send a message to: fiveam-announce+unsubscribe(a)common-lisp.net And for help send a message to: fiveam-announce+help(a)common-lisp.net

1 0