COPYING · b5ae251535fcd53945c089a06689dd1cadcdcf2b · abcl / abcl · GitLab

The gitlab.common-lisp.net system has migrated to a new host. One consequence of this is that the remotes for all cloned repos must now refer to the host gitlab.common-lisp.net rather than simply common-lisp.net.

You can see your current remotes from a cloned directory with git remote -v

If you see common-lisp.net in there without the gitlab. in front of it, then please update your remotes by using e.g. the following command:

git remote set-url origin git@gitlab.common-lisp.net:/{$user|$group}/{$repo}.git (assuming your remote name is origin).

gitlab-runner users: If you are running gitlab-runner on your own infrastructure, you need to update your config to point to https://gitlab.common-lisp.net, if it was previously pointing at simply https://common-lisp.net. The common-lisp.net host can no longer be used interchangeably with gitlab.common-lisp.net as may have worked previously. N.B. you can simply edit your gitlab-runner config and change the hostname; it should not be necessary to change anything with the token which you'll see along with that host url in the gitlab-runner config file.

Jun 11, 2017

Maintenance on file structure · 7d12939e

mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f authored Jun 11, 2017

Explicitly note which paragraph constitutes our "classpath exception"
in COPYING.

Use '1.5.0-SNAPSHOT' in POM for publishing snapshots.

7d12939e

Maintenance on file structure

mevenson@1c010e3e-69d0-11dd-93a8-456734b0d56f authored Jun 11, 2017

Explicitly note which paragraph constitutes our "classpath exception"
in COPYING.

Use '1.5.0-SNAPSHOT' in POM for publishing snapshots.

This project is licensed under the GNU General Public License v2.0 or later. Learn more