Author Topic: Version control configuration not migrated  (Read 4370 times)

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Version control configuration not migrated
« on: September 08, 2014, 06:46:24 pm »
Hi!

I just installed the beta on my Linux and Windows machines.

On my Linux machine, I just noticed that my version control configuration was not transferred. I had customized the "clearcase checkout" command, and the customized command was not in v19.

Other parts of my configuration did transfer over, but not the version control setup.

Thanks,
Rob

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #1 on: September 08, 2014, 06:54:00 pm »
Did it copy over a uservc.slk file?

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #2 on: September 08, 2014, 06:57:14 pm »
At this moment, there does exist a file:

/home/robb/.slickedit/19.0.0/uservc.slk

But I don't know if it was copied over or created.

I did manually modify the command for "clearcase checkout" once I noticed it was not migrated.

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #3 on: September 10, 2014, 05:15:28 pm »
I upgraded from beta2 and beta3, and it did not keep my setting for the changed clearcase checkout command :(

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #4 on: September 16, 2014, 01:22:29 am »
I just upgraded from beta3 to beta4, and my clearcase settings got reset again to the defaults :(

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #5 on: September 16, 2014, 12:31:50 pm »
Had they been lost when you went to beta 3?  Did you re-set them before upgrading to beta 4?

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #6 on: September 16, 2014, 12:51:44 pm »
Had they been lost when you went to beta 3?

Yes, they were lost when I went to beta 3. I had manually set them in beta 2 because it was not transferred from SE v18 to v19.

Had they been lost when you went to beta 3?  Did you re-set them before upgrading to beta 4?

Yes, they were lost in beta 3. After install of beta 3 I manually set the version control settings to my preference. Then after I upgraded to beta 4, the configuration was back to the default.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #7 on: September 16, 2014, 01:27:07 pm »
Can you send me your vusrdefs.e file?  You can post it here or PM me for an email address.

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #8 on: September 16, 2014, 01:37:15 pm »
I can't find a 'vusrdefs.e' file in my directory ~/.slickedit (linux machine).

Am I looking in the right place?

Is there a typo in the spelling of vusrdefs.e?

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #9 on: September 16, 2014, 01:54:54 pm »
Sorry.  On unix it would be vunxdefs.e.

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #10 on: September 16, 2014, 01:58:30 pm »
it is attached to this message.

Thanks!

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #11 on: September 16, 2014, 02:00:29 pm »
Are your custom commands:

cleartool co -nc -unr %f
cleartool ci -cfile %c %f
cleartool unco -rm %f
cleartool mkelem -cfile %c %f

?

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #12 on: September 16, 2014, 02:01:39 pm »
Yes, that is correct.

In fact, I only customized one of them, the checkout:

cleartool co -nc -unr %f

rowbearto

  • Senior Community Member
  • Posts: 1468
  • Hero Points: 111
Re: Version control configuration not migrated
« Reply #13 on: September 16, 2014, 02:03:13 pm »
I also made another customization that was not carrying over.

In the options, Tools->Version Control->Version Control Providers->Clearcase->Advanced, I had set "Always show output" to "ON".

This setting went back to the default when doing beta3->beta4.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2369
  • Hero Points: 132
Re: Version control configuration not migrated
« Reply #14 on: September 16, 2014, 02:33:06 pm »
I can't seem to reproduce this.  I put your vunxdefs.e in my config and went from beta3 to beta4 and it moved the commands over and the other setting too.  It's like your vunxdefs.e did not run, but I don't see any reason it should not have.  If you haven't adjusted the commands already, you could try running it on the command SlickEdit line (xcom /path/vunxdefs.e).