Re: GitLab migration and existing links to source code

Erik Huelsmann <[email protected]>
Newsgroups gmane.lisp.common-lisp-net.devel
Message-ID <CACOoB6h41WD8aQFtzRoCwanP4_p86n3msqLJPu4yUM_b=nRjeA@mail.gmail.com>
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=summary
>
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.