Git Migration

[Goblin Hero]

How about this?
https://github.com/TheGoblinHero/Forge
It's even possible to map existing GitHub users to the old commits.

[KrazyTheFox]

That's kind of impressive. How far back does the history go? It looks like it's a couple tens of thousands of commits short. I could convert a shortened version of the repository much more easily, but I was going for the entire history. I also wanted to host on our own GitLab instance instead of GitHub, as it opens the project more, but keeps the public visibility down.

As for keeping svn around, we'll need to for the time being, due to the fact that the migration has taken much longer than anticipated.

[Goblin Hero]

That's kind of impressive. How far back does the history go?

It's an automatic GitHub importing. I do not know the details.
Did you try this:
https://git-scm.com/docs/git-svn

[Goblin Hero]

SVN is moved. You can access it as usual at
http://svn.slightlymagic.net/forge/
But I have problems with the old WebSVN http interface. Should I spend my time at fixing it or it's not needed?

[Agetian]

SVN is moved. You can access it as usual at
http://svn.slightlymagic.net/forge/
But I have problems with the old WebSVN http interface. Should I spend my time at fixing it or it's not needed?

It could be useful if it's not too difficult to fix - I use it from time to time to track changes and whatnot, as well as view recent commit diffs from other users. It can be done via other means, of course, but it's quite convenient to do it from a browser, especially when away from home and when not having svn set up on a particular machine.

- Agetian

[Agetian]

Hmm, it looks like I can't commit anymore (it won't accept my credentials for commit).

- Agetian

[Goblin Hero]

Hmm, it looks like I can't commit anymore (it won't accept my credentials for commit).

Looks like old auth module doesn not work properly with the new apache. Try to commit w/o login/pass now.

[Agetian]

Hmm, it looks like I can't commit anymore (it won't accept my credentials for commit).

Looks like old auth module doesn not work properly with the new apache. Try to commit w/o login/pass now.

Just tried it and it says this:
svn: E170013: Unable to connect to a repository at URL 'http://svn.slightlymagic.net/forge/trunk'
svn: E000111: Error running context: Access denied

(this is before I have a chance to input any auth data whatsoever).

- Agetian

[Goblin Hero]

I've just commited r35250 for testing purposes w/o password. May be you still has the old dns? Run `ping www.slightlymagic.net` It should resolve to 94.130.75.10

[Agetian]

I've just commited r35250 for testing purposes w/o password. May be you still has the old dns? Run `ping http://www.slightlymagic.net` It should resolve to 94.130.75.10

Hmm www.slightlymagic.net resolves to that, but svn.slightlymagic.net resolves to 78.46.39.100 :/
How can I update that on my end?

- Agetian

[Agetian]

For the record, trying a checkout operation directly by IP fails as well:
svn co http://94.130.75.10/forge/trunk

- Agetian

[Goblin Hero]

Hmm http://www.slightlymagic.net resolves to that, but svn.slightlymagic.net resolves to 78.46.39.100 :/
How can I update that on my end?

Just wait. Full DNS propagation may takes up to 24 hours. Until then you can add a static dns entry to your hosts file.
Auth is disabled now, but because of that commit author name is not registered. I've enabled the ability to edit the author after the commit to temporary fix the problem.
PS. Checkout by ip won't work, because one ip is used for several subdomains.

[Agetian]

Ok, thanks! Is there any chance auth can be restored at a later point? I'm afraid the integrity of the repository might be at risk if anyone can commit with no limitations and with no special permission requirements...

- Agetian

[Goblin Hero]

Ok, thanks! Is there any chance auth can be restored at a later point?

Sure. I will try to restore the old functionality (using passwords from the forum).

[Agetian]

Alrighty, sounds good!

- Agetian