clo-devel January 2018

clo-devel@common-lisp.net

5 participants
7 discussions

Start a nNew thread

https://gitlab.common-lisp.net returns http status 502
by R. Matthew Emerson 11 Feb '18

11 Feb '18

Hi. https://gitlab.common-lisp.net is currently returning http 502.

3 4

Additional darcs repositories to be migrated? (working to convert the darcs repositories)
by Erik Huelsmann 31 Jan '18

31 Jan '18

Hi all, The current list of repositories to migrate from darcs to GitLab, is the list shown on https://common-lisp.net/cgi-bin/darcsweb.cgi . Are there any other repositories that need to be migrated to GitLab that this community is aware of? Thanks! Regards, Erik. On Wed, Jan 31, 2018 at 9:21 AM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi, > > While running the first conversion tests, I ran into the following > repositories (browsable through https://common-lisp.net/cgi- > bin/darcsweb.cgi) already have GitLab repositories in place > (<project>/<repository>): > > * adw-charting/adw-charting > * alexandria/alexandria > * bordeaux-threads/bordeau-threads > * cl-store/cl-store > * editor-hints/named-readtables > * elephant/elephant > * gestalt/gestalt > * mel-base/mel-base > * parenscript/parenscript > > > Given the age of all of these repositories, I'm planning to archive these > duplicated repositories and not migrate them to GitLab (as that would mean > the repositories would be either duplicating other repositories or prior > repositories would be overwritten). > > > Any comments regarding this plan? Maybe someone knows that some of these > repositories need to be migrated to GitLab - replacing what's currently > there? > > > Regards, > > > Erik. > > > On Sat, Jan 27, 2018 at 11:56 PM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > >> Hi all, >> >> After converting common-lisp.net to LetsEncrypt/certbot, I've taken a >> bit of time to research the long-overdue move from darcs to Git. >> >> Fortunately, taking time away from a task allows for creativity to kick >> in: I've found an (acceptable to me) way to bulk convert all repositories >> listed in https://common-lisp.net/cgi-bin/darcsweb.cgi >> >> I'm likely to implement a minimal redirect from the existing darcsweb >> URLs to the resulting GitLab git projects. However, since the commit SHAs >> don't match, anything more complex requires pretty extensive mapping >> tables. Please consider this as an invitation to do that work! :-) >> >> >> Final announcement of a cut-over will be done 1 week in advance of the >> cut-over itself. Cut-over will roughly take 4 hours when the window is >> there (although I can't imagine anybody actually *using* these repositories >> other than as read-only sources). >> >> -- >> 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. > -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Darcs & darcsweb deprecation; working to convert the darcs repositories
by Erik Huelsmann 31 Jan '18

31 Jan '18

Hi all, After I complete the migration of all repositories listed in darcsweb (excluding the ones below), I'll be installing a rewrite rule on the darcsweb, redirecting to GitLab. At that time, I'm planning to remove both Darcs and Darcsweb support from common-lisp.net, unless there are objections from the community, of course. Regards, Erik. On Wed, Jan 31, 2018 at 9:21 AM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi, > > While running the first conversion tests, I ran into the following > repositories (browsable through https://common-lisp.net/cgi- > bin/darcsweb.cgi) already have GitLab repositories in place > (<project>/<repository>): > > * adw-charting/adw-charting > * alexandria/alexandria > * bordeaux-threads/bordeau-threads > * cl-store/cl-store > * editor-hints/named-readtables > * elephant/elephant > * gestalt/gestalt > * mel-base/mel-base > * parenscript/parenscript > > > Given the age of all of these repositories, I'm planning to archive these > duplicated repositories and not migrate them to GitLab (as that would mean > the repositories would be either duplicating other repositories or prior > repositories would be overwritten). > > > Any comments regarding this plan? Maybe someone knows that some of these > repositories need to be migrated to GitLab - replacing what's currently > there? > > > Regards, > > > Erik. > > > On Sat, Jan 27, 2018 at 11:56 PM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > >> Hi all, >> >> After converting common-lisp.net to LetsEncrypt/certbot, I've taken a >> bit of time to research the long-overdue move from darcs to Git. >> >> Fortunately, taking time away from a task allows for creativity to kick >> in: I've found an (acceptable to me) way to bulk convert all repositories >> listed in https://common-lisp.net/cgi-bin/darcsweb.cgi >> >> I'm likely to implement a minimal redirect from the existing darcsweb >> URLs to the resulting GitLab git projects. However, since the commit SHAs >> don't match, anything more complex requires pretty extensive mapping >> tables. Please consider this as an invitation to do that work! :-) >> >> >> Final announcement of a cut-over will be done 1 week in advance of the >> cut-over itself. Cut-over will roughly take 4 hours when the window is >> there (although I can't imagine anybody actually *using* these repositories >> other than as read-only sources). >> >> -- >> 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. > -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Duplicate repositories: working to convert the darcs repositories
by Erik Huelsmann 31 Jan '18

31 Jan '18

Hi, While running the first conversion tests, I ran into the following repositories (browsable through https://common-lisp.net/cgi-bin/darcsweb.cgi) already have GitLab repositories in place (<project>/<repository>): * adw-charting/adw-charting * alexandria/alexandria * bordeaux-threads/bordeau-threads * cl-store/cl-store * editor-hints/named-readtables * elephant/elephant * gestalt/gestalt * mel-base/mel-base * parenscript/parenscript Given the age of all of these repositories, I'm planning to archive these duplicated repositories and not migrate them to GitLab (as that would mean the repositories would be either duplicating other repositories or prior repositories would be overwritten). Any comments regarding this plan? Maybe someone knows that some of these repositories need to be migrated to GitLab - replacing what's currently there? Regards, Erik. On Sat, Jan 27, 2018 at 11:56 PM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi all, > > After converting common-lisp.net to LetsEncrypt/certbot, I've taken a bit > of time to research the long-overdue move from darcs to Git. > > Fortunately, taking time away from a task allows for creativity to kick > in: I've found an (acceptable to me) way to bulk convert all repositories > listed in https://common-lisp.net/cgi-bin/darcsweb.cgi > > I'm likely to implement a minimal redirect from the existing darcsweb URLs > to the resulting GitLab git projects. However, since the commit SHAs don't > match, anything more complex requires pretty extensive mapping tables. > Please consider this as an invitation to do that work! :-) > > > Final announcement of a cut-over will be done 1 week in advance of the > cut-over itself. Cut-over will roughly take 4 hours when the window is > there (although I can't imagine anybody actually *using* these repositories > other than as read-only sources). > > -- > 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

abcl.org & cliki.net moved to TLS / *.common-lisp.net certs moved to letsencypt
by Erik Huelsmann 29 Jan '18

29 Jan '18

Hi all, As the common-lisp.net wildcard certificate was going to expire next week, I've moved all the *.common-lisp.net subdomains to LetsEncrypt. While I was at it, I've also added TLS to two other domains running on the server: abcl.org and cliki.net. >From now on, the certificates should auto-renew! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

Gitlab down?
by Raymond Toy 29 Jan '18

29 Jan '18

Visiting gitlab results in a 502 error for me. Is gitlab down? The web server (common-lisp.net) appears to be working, and I can ssh in just fine. -- Ray

1 0

common-lisp.net: working to convert the darcs repositories
by Erik Huelsmann 27 Jan '18

27 Jan '18

Hi all, After converting common-lisp.net to LetsEncrypt/certbot, I've taken a bit of time to research the long-overdue move from darcs to Git. Fortunately, taking time away from a task allows for creativity to kick in: I've found an (acceptable to me) way to bulk convert all repositories listed in https://common-lisp.net/cgi-bin/darcsweb.cgi I'm likely to implement a minimal redirect from the existing darcsweb URLs to the resulting GitLab git projects. However, since the commit SHAs don't match, anything more complex requires pretty extensive mapping tables. Please consider this as an invitation to do that work! :-) Final announcement of a cut-over will be done 1 week in advance of the cut-over itself. Cut-over will roughly take 4 hours when the window is there (although I can't imagine anybody actually *using* these repositories other than as read-only sources). -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel January 2018