On 09.05.25 10:34, Noé Lopez wrote:
That would make a ton of dead links to cgit. How about writing on the
savannah page and README that the repository is archived with the new
url?
If I have a clone of the guix and still have savannah as origin after
the migration, I won't immediately see any effect.
I would run =git pull=, would get one commit (the changed README) but
wouldn´t pay attention to it. I would continue working on it, and maybe,
after a few days or weeks (depending how active I am with guix at the
moment (e.g. I could be on vacation for a few weeks) I would start to
wonder why there aren't any new commits to pull from origin. I might be
clever enough at that moment to look at the git log and if it says
something like "THIS REPOSITORY HAS BEEN MOVED TO
https://whatever.is/the/new/url.git";, and only then will I know.
Until then, my checkout will be outdated, potentially missing critical
security updates or bug-fixes. I would consider this situation as
silently broken.
IMHO if things are broken they should be verbose about this. So the
server could e.g. return an HTTP 403. In git this would look like this:
#+BEGIN_EXAMPLE text
fatal: unable to access 'https://intern.nomike.com/403test.git/': The
requested URL returned error: 403
#+END_EXAMPLE
If I were seeing this, the first thing I would to is open the URL in my
browser to see what's up, and there could be a custom 403 error page
telling me that the repo has been moved with a link to the new locations
and ideally also the command I could copy/paste into my shell right now,
to change the origin.
Another maybe even better way is to configure the webserver in a way to
respond with a "HTTP 301 Moved Permanently" or even a "HTTP 308
Permanent Redirect". This way it would seamlessly work, git would
display a warning, which might alert at least some people that they have
to switch to a new URL (but as long as the redirect is in place, they
don't have to).
If people are using other transport methods to access the repo (e.g.
SSH) this won't work of course. But I would still block access to it
(e.g. file permissions) so that people are aware that they need to act.
Have a nice day.
nomike
