All NON-developers should switch to using one of the anonymous mirrors, because cvs.moodle.org itself will NOT support anonymous access in future: http://docs.moodle.org/en/CVS_for_Administrators
All developers should be using cvs.moodle.org as your CVS repository to minimise problems later on (it's currently just an alias to Sourceforge but that will change). All your usernames/passwords will have to be regenerated on the new server - I'll post more info about that soon.
All mirror sites will be rsync-ing from cvsmirror.moodle.org that itself mirrors the developer repository very closely. I'll post more info on this soon too.
At that exact moment I'll disable all write access to the old server to avoid any code going into a black hole.
IMPORTANT: We need to re-create all the accounts on the new server. Can ALL current developers please email email@example.com with an email containing:
- Your full name
- Your email address
- Your new CVS username
- Your new CVS password
- Your old Sourceforge username (only if it's different)
- Your ssh public key if you have one
Put "CVS access" in the subject, please. Thanks!
I was hoping to keep things on the new server exactly the same for you, so that it would be transparent, but I've decided it's better to run a dedicated rsync service so we have a bit more efficiency, control and logging.
Basically it means you'll just need to modify the commands you use to mirror the repository to something like this:
rsync -av cvsmirror.moodle.org::moodle .
NOT YET though ... wait until the CVS moves on Thursday 6th December.
Could you please post a message here once you've moved CVS and enabled the new syncing mirror so we can switch to the new configuration?
If its whilst i'm awake i'll try and be available to switch it ;)
At the same time I'm going to bump the release name of the MOODLE_19_STABLE branch to "1.9 Beta 3" just to help distinguish the new server from the old one (could help in debugging).
Any ideas? Thanks!
Maybe they haven't switched to the new master CVS mirror yet? We (es.cvs.moodle.org) are doing it right now, so you'll still get the 'old' files in the following 30-45 minutes or so.
Uh.. by the way, is the site http://download.moodle.org/ currently down right now (local time is pacific standard time 10:14pm)?
I've received an email asking me if we provide the rsync service for the CVS repository. When the CVS was hosted at SourceForge, anyone could rsync the repository.
Should we (the final mirrors) provide this service? I don't mind providing it on our server, but some consensus on the subject would be better
I am providing moodle services from moodle 1.5 to HEAD and checking them all out is just not practical for me. I am running my own cvs server, and rsyncing the moodle repo into my cvs server. Since the move to the new moodle.com cvs server, I cannot use this technique anymore. Is there any possibility on providing this service again?
I have just enabled rsync access to es.cvs.moodle.org.
Just a couple of 'warnings':
- Compression is disabled/refused. The machine is a little bit underpowered and rsync is CPU-intensive (espcially with compression).
- We are using cvsd with a chroot setup (instead of plain cvs). This means the CVSROOT of the top of the repository is different than the one you'd get from the real repository. Note that this shouln't make a difference to anonymous users, but I felt I should mention it.
I've updated the How to set up a CVS mirror docs with the new rsync info.
The ViewCVS site is here now: http://cvs.moodle.org
There is also a firstname.lastname@example.org mailing lists here (the mailing lists site is still being tidied up but it works if you want to subscribe to it). Commits are now pretty-printed with colors (using cvsspam).
Email email@example.com (or skype me) if there are any problems!
I know.... I'm almost certainly being dumb again
It's all up and running
And that has made for a BIG difference. 'cvs update -dPRA' used to take 10-25 minutes with sourceforge for me. I've just done it in under 30 seconds with the new server
(and waiting to be whitelisted for the cvsmirror - at least it rejects my approaches... instantly!)
Note about the rsync invocation for mirror maintainers! You will want 2 things:
- --delete so files moved to the Attic (and perhaps then moved back out!) are removed/readded correctly from your mirror!
- --exclude '#cvs.*' -- you don't want to bring in any of the silly lockfiles cvs scatters all around, as they can render your mirror unusable (clients will get "waiting for lock held by user blah"
P.S. I have problem with the setting of the CVS root.
I let somebody with more knowledge on all these processes put the info on the Docs.
P.S. I used my editor (uedit) do a files find and replace all the Root files.
I just switched to the new repository using Martín's command
$ find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@cvs\.moodle\.org/'
and it seems to work fine! I just had to accept server's RSA key fingerprint. Well, I was waiting about a minute before an update started to work, but it is probably because of everybody wants the new server right now
TODO: modify instructions at http://docs.moodle.org/en/CVS_for_Developers
1) I've fixed Moodle docs to remove all the Sourceforge references.
2) UK/EU and ES mirrors are running fine, but the US server is behind (they are not responding to my emails). I should also have mentioned that we have a whitelist on hosts allowed to download the whole repository via rsync ... for a while yesterday this wasn't working correctly but it's all fine now.
So USA mirror site should be fully functional now..
Also, I just noticed that all of the Browse CVS links in the Modules and plugins database are still pointing to sourceforge.
I can confirm that es.cvs.moodle.org includes it.
Also if anyone else who is using US mirror site please help us testing the site to see if there are any other glitches, really appreciate that!
Except the Tortoise screenshots--could you update those too.
I still can't get this to work with Tortoise--either with a name and password, or with anonymous--maybe seeing the new setup in a screenshot will help?
I get this message:
q checkout -P moodle
connect to cvs.moodle.org:2401 failed: No connection could be made because the target machine actively refused it.
Error connecting to host SERVER.cvs.moodle.org: No such host is known.
I still can't get this to work with Tortoise--either with a name and password, or with anonymous
Anonymous connections are not supported on the master CVS server. You need to use one of the mirrors for that.
:pserver:firstname.lastname@example.org:/cvsroot/moodle :pserver:email@example.com:/cvsroot/moodle :pserver:firstname.lastname@example.org:/cvsroot/moodle :pserver:email@example.com:/cvsroot/moodle
(depending on what mirror server you want to use) should do it. I have updated the TortoiseCVS screen shots to reflect the new settings.
Okay, thanks Inaki--I've got it now.
>>>>Anonymous connections are not supported on the master CVS server. <<<<
Hence the confusion, since the docs (and your newly posted screenshots--thanks) show this:
Copy this text into the CVSROOT field:
If anonymous access isn't allowed--why is this in the docs?
If anonymous access isn't allowed--why is this in the docs?
Because a few lines above, just below the list of anonymous CVS mirrors, there is the following text:
"Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!"
(so we don't need to repeat the instructions with every possible CVS mirror, and we don't specify only one and send everyone to that mirror, thus defeating the point of having several mirrors to spread the load).
[Edit: I have updated the docs to reflect this in the Unix and Windows instructions too.]
A good improvement
Yet another note for cvs mirror operators!
Shortly after going live with the new cvs server, rsync got set to publish CVSROOT, together with the rest if the repository. This was done for good reasons (to support the gitsters in the wild!). But that means that it pushes out the config file (CVSROOT/config) which has settings that probably won't match your server. Specifically, it tries to use /locks/ as the locks directory, which will break in most cases.
So, even if your mirror was usable initially, it may not be usable now. Depends on a few variables, probably a good idea to check. If you try a checkout or update and see a 'cannot stat /locks' error, you know you have a problem.
How to fix it?
- Change your rsync line to also --exclude 'CVSROOT/config'
- Remove CVSROOT/config or just comment out the LockDir line
I've updated the instructions in the wiki too
Please discontinue sending requests to the Moodle Helpdesk for new CVS accounts or modifications. Instead, go here and click the "Apply for CVS access" tab to make your requests known. Thanks.