Opened 2 years ago

Closed 2 years ago

#2059 closed help (fixed)

cannot create a branch for UKCA vn10.4 tutorial

Reported by: ggxmy Owned by: ros
Component: FCM Keywords:
Cc: Platform: PUMA
UM Version: 10.4

Description

Dear CMS,

I'm trying to go through the UKCA vn10.4 tutorial and in section 4.3 I need to create a branch. Although I'm familiar with creating a branch for vn8.4, I don't seem to be able to create a branch for vn10.4 for some reason. I get messages as follows;

puma:/home/ggxmy/Branches [k]$ fcm branch-create --type dev Tutorial fcm:um@vn10.4
[FAIL] svn info --xml fcm:um@vn10.4 # rc=1
[FAIL] svn: E205000: Try 'svn help info' for more information
[FAIL] svn: E205000: Syntax error parsing peg revision 'vn10.4'

Same thing if I include a ticket number or I use um.x_tr instead of um as instructed. If I do this for vn8.4 simply by replacing 10 with 8, it seems to work. Can you see what is the problem?

Thanks,
Masaru

Change History (2)

comment:1 Changed 2 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Masaru,

The repository keyword for UM10.x is fcm:um.x

Please make sure you have your MOSRS password cached in gpg-agent. You set this up the other week, if I recall correctly and you should be prompted for it when you login to PUMA. Being unable to parse the peg revision usually means it's not been able to see the remote repository where the revisions are stored.

Please then try running the command:

puma$ fcm ls fcm:um.x

Which should give the response:

branches/
trunk/

If that fails or you are prompted for a password then your MOSRS password is not cached properly. If this is so try running the mosrs-cache-password script to recache your password.

Once your password is cached try running the above command again and if all is ok you can then go on to create your branch as detailed in the UKCA tutorial. If you get any errors please post them here with the command you ran.

Cheers,
Ros.

comment:2 Changed 2 years ago by ggxmy

  • Resolution set to fixed
  • Status changed from accepted to closed

Hi Ros.,

Thank you. The first line solved the problem.

Masaru

Note: See TracTickets for help on using tickets.