GitLab migration and existing links to source code
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=su... 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
Hi Anton, 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=su...
Ah. And that link is dead. Same as the ViewCVS link that was mailed about yesterday.
As I understand, darcs repos were migrated to GitLab.
Actually, that's not entirely correct: they *will* be migrated to GitLab, but they have not yet: the only repositories migrated so far were any Git repositories that already existed on the system.
Maybe it makes sense to map the old URLs to the corresponding GitLab URls?
Absolutely. And they will once the repositories get migrated. We went through quite a bit of effort to do this correctly for Git (gitweb), so I'm expecting the same for darcsweb. The reason the link is broken is because the web-browsing utilities have been hosted at various different paths in the common-lisp.net webspace. I've introduced URL rewriting to the place where darcsweb currently is being hosted.
Best regards, - Anton
Thanks for the report! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Anton, On Mon, Mar 23, 2015 at 10:44 PM, Anton Vodonosov <avodonosov@yandex.ru> wrote:
Thanks for the response!
No the link shows a python error "repo not found". Something with file system locations?
The problem was Apache URL-encoding URL while redirecting the non-https version to https which apparently confuses darcsweb. I've configured Apache to simply pass the URL string instead of encoding the semi-colon which darcsweb and gitweb use as their parameter separation character. Long story cut short: it should work now. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
24.03.2015, 11:44, "Erik Huelsmann" <ehuels@gmail.com>:
The problem was Apache URL-encoding URL while redirecting the non-https version to https which apparently confuses darcsweb. I've configured Apache to simply pass the URL string instead of encoding the semi-colon which darcsweb and gitweb use as their parameter separation character.
Long story cut short: it should work now.
Yest, it works. Thanks. Best regards, - Anton
participants (2)
-
Anton Vodonosov -
Erik Huelsmann