Opened 2 years ago

Closed 2 years ago

#2198 closed help (fixed)

Problem creating branch

Reported by: charlie Owned by: ros
Component: MOSRS Keywords:
Cc: Platform: PUMA
UM Version:

Description (last modified by ros)

Hi,

I'm having a problem creating a branch - I'm wanting to create a branch from version 10.3, using newly created ticket number 3167, but get the error below when I do:

fcm branch-create -k 3167 mh_orb_v1 fcm:um.x@vn10.3

Why is it taking my username as Dragon17_[3~[3~[3charliewilliams, instead of just charliewilliams? Without giving too much information away, this is the beginning of my MOSRS password! So why is it becoming my username? I'm wondering if there is a problem with my login details, because every time I log into puma it asks me for my MOSRS password, as below:

Disk quotas for user charlie (uid 1055):

Filesystem blocks quota limit grace files quota limit grace

/dev/sdb3 1343980 2000000 2100000 91763 0 0

Met Office Science Repository Service password:
First time use: enter your password again
Subversion password cached
https://code.metoffice.gov.uk/rosie/u/hello: Hello charliewilliams
Rosie password cached

Is this part of the problem?

Charlie

charlie@puma:/home/charlie/branches/pacmedy_branch1> fcm branch-create -k 3167 mh_orb_v1 fcm:um.x@vn10.3
[info] Source: https://code.metoffice.gov.uk/svn/um/main/trunk@13189 (13189)
[info] nedit: starting commit message editor…
UTF8 locale not supported.
Change summary:


A https://code.metoffice.gov.uk/svn/um/main/branches/dev/Dragon17_[3~[3~[3charliewilliams/vn10.3_mh_orb_v1


Commit message is as follows:


#3167: Created /main/branches/dev/Dragon17_[3charliewilliams/vn10.3_mh_orb_v1 from /main/trunk@13189.


Create the branch?
Enter "y" or "n" (or just press <return> for "n") y
svn: E160005: Invalid control character '0x08' in path 'Dragon17_\010\010\010\010\010\010\010\010\010\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\033[C\010\010\010\010\010\033[C\033[C\033[C\033[C\033[C\033[3~\033[3~\033[3~\010\010\010\033[C\010\010\010\010\010\010\010j\010charliewillias\010ms/vn10.3_mh_orb_v1'
[FAIL] svn copy —file /tmp/60qnFn7nf5 —parents https://code.metoffice.gov.uk/svn/um/main/trunk@13189 https://code.metoffice.gov.uk/svn/um/main/branches/dev/Dragon17_ [3charliewilliams/vn10.3_mh_orb_v1 # rc=1

Change History (3)

comment:1 Changed 2 years ago by ros

  • Component changed from UM Model to MOSRS
  • Description modified (diff)
  • Owner changed from um_support to ros
  • Platform set to PUMA
  • Status changed from new to accepted
  • UM Version <select version> deleted

Hi Charlie,

Your username is rather mangled in your ~/.subversion/servers file. If you fix it in there and try again it should work correctly.

As to why you are prompted for your MOSRS username when log into PUMA this is to cache your MOSRS password so that you can use the Rose/FCM commands which you set up on the training course, otherwise you would be prompted to enter your password loads of times/things wouldn't work.

If you are logging into PUMA and know you are not planning on using Rose/FCM then just hit return when prompted for your MOSRS password and it won't set up the caching for that login.

Cheers,
Ros

comment:2 Changed 2 years ago by charlie

Thanks very much Ros, I have no idea why my servers file was so garbled. Is that something I would have done by accident

I have now successfully created my branch, using the command line rather than the GUI.

I wasn't sure if I needed to create my branch from the main 10.3 trunk, as I did, or if it would have been better (or indeed possible) to have taken my branch from the one I was given and have been working with i.e.

https://code.metoffice.gov.uk/trac/um/log/main/branches/test/alistairsellar/vn10.3_mid_holocene_orbital?rev=39922

In the end, I did the former i.e.

fcm branch-create -k 3167 mh_orb_v1 fcm:um.x@vn10.3

Was this correct? Presumably, if this has worked, I will need to copy the relevant files so that it matches the modified one in his branch?

Charlie

comment:3 Changed 2 years ago by grenville

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

Charlie

Looks like this is working - I'll close the ticket.

Grenville

Note: See TracTickets for help on using tickets.