Legacy ImageMagick Discussions Archive

imagemagick svn is down

https://www.imagemagick.org/subversion/ImageMagick/ is 404

please add some redirection

Thanks

Bastien

Please stop this crap:
svn co https://www.imagemagick.org/subversion/ ... gick/trunk ImageMagick
svn: OPTIONS of 'https://www.imagemagick.org/subversion/ ... gick/trunk': 200 OK (https://www.imagemagick.org)

Thanks

bastien

Try now. We had a couple of glitches during our move to a bigger, better, faster ImageMagick server (thanks to Network Redux).

Thanks

(I don't know if someone manually intervened to get my account activated or if the activation email just finally got through. So I'm posting this svn-related bug report here in case something funky is happening with my email.)

Hello,

Your rsync server on mirror.imagemagick.org has been down for the last few days. Probably also related to the server move, since it seems to have happened around the same time.

I tried working around the problem by doing a local svnsync of the svn repos that I had been getting via rsync, then changing the source url to point to your svn server. But then I got a "repository permanently moved... please relocate" error, which googling tells me is actually a problem with your server's config (something along the lines of apache on virtual servers gets confused when svn is under the same directory structure. So it sounds like something got mis-configured when your servers moved to a new host).

I'll just keep watching this thread to see when things are fixed.

thanks!
j

PS: Would it be better in terms of server/bandwidth load for you guys if I used rsync or svnsync from here on out? (Don't want to needlessly tax your site.)

Can you try rsync again? We tried it and its working fine. If it fails for you, post your command so we can reproduce the problem.

Subversion works fine for us too. If it fails, give us the circumstances. We need to reproduce the problem before we can comment.

Here's the rsync command: This is the output: svnsync still isn't working either. The circumstances are:

Case 1:
I svnsync'd from a local mirror of the svn repos that was obtained via rsync before the problems began. This is almost identical to Case 2, except the source URL is the path to the repos copy obtained via rsync (home/username/mirror/im/svn-rsync) instead of your server.

Changed the source url of the svnsync'd mirror to point to your server instead of the local rsync'd copy: Did an svnsync update: That didn't work: so I deleted the failed svnsync copy, and tried fetching it via svnsync directly from your server:


Case 2:
Created an empty svn repos: Added hooks to allow svnsync: Initialized for svnsync: Did an svnsync to get the repos: The result is identical: I hope this is helpful.

Ok, try your commands again and let us know if you have any further problems with rsync / subversion.

Terrific! Both rsync and svnsync work like a charm now! Thanks for getting that fixed guys.

Now that everything is working, do you guys have a preference for how people grab repository updates? It's painfully slow to use svnsync for initial downloads of repos, but it's ok for getting updates if that would put less load on your servers/bandwidth usage. Let me know.

J