Committing old branches

Hi, I have a few old branches on PUMA which I hadn’t committed and just went to tidy them up now before transferring them to Cirrus but I got this error:

Transmitting file data .done
Committing transaction…
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
2026-11-16T15:41:19Z+ 134623-2wij by hannahbryant
U main/branches/dev/hannahbryant/vn11.1_CCMI_vn11.1_copy_for_aeroclim_chem_bug/src/control/misc/science_fixes_mod.F90
error: WARNING: Changes to the UM repository are not permitted since 15 Nov 2026. Please contact the UM project manager if this is unexpected

I had thought I had until the 18th to do these changes. Is there anyway to extend it?

Thanks,

Hannah

Hi, I’ve just seen this is on the monsoon newsletter. As I run on Archer2 and didn’t plan to move these over I had missed this guidance, is there any suggestion of what to do here?

i.e. if I migrate over these branches to cirrus as they are will I still be able to see the changes I have made? (I wont be able to run with any of them as the versions are too old anyway)

Hi Hannah

If you move your branches over to the new Cirrus-hosted $HOME you will still be able to see your local working copy changes, you just can’t commit them back to MOSRS which has now gone read-only for the UM.

Cheers

Jonny

Hi Jonny,

Ok great thank you this is totally fine as none of them are being used anymore! Sorry for missing that deadline, I had confused that with the PUMA one in my calendar sorry!

For transfer to Cirrus for my data on PUMA2, can I just check the best course of action? I can see in the documentation many options but I was going to try this: module load rclone
rclone --progress copy <archer2_directory> remote:<sftp_directory>. Can I do this from where I am ssh’d into PUMA or do I do this from Archer? Sorry I am quite overwhelmed by all the different methods.

Thanks,

Hannah

(asking as the module load rclone command did not work on puma)

Hi Hannah.

You can just copy things over from your current $HOME on PUMA2 to /mnt/cephfs/n02/n02-puma2/<username>, also on PUMA2.

The reason this is happening is that PUMA2 is currently mounted on ARCHER2, which is very nearly at the end of its service period.

You should have received an email (titled IMPORTANT - PUMA2 Migration to Cirrus) on November 6th with this and some other information. Let me know if you didn’t receive this and I can forward it or put the info here.

Cheers

Jonny

Hi Jonny,

Ok thanks, no I did get that email but I was really confused because all of the other information told me to put it on /nscds which I couldn’t find on puma only on archer

I’ll try that all now.

Thanks,

Hannah

@jonnyhtw I did this command and it completed but I cannot see it on Cirrus in /home/n02/n02/s2261584 or /epccfs/n02/n02/s2261584/??

[s2261584@puma2 ~]$ cp -r branches /mnt/cephfs/n02/n02-puma2/s2261584/

The path is still on PUMA2, it should have gone here /mnt/cephfs/n02/n02-puma2/s2261584/branches

How do I get it onto cirrus though?

Might be easier to have a quick call Hannah. I’ve emailed you. Cheers