Book a Demo

Author Topic: Unable to checkout modules  (Read 3714 times)

nraponi

  • EA Novice
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Unable to checkout modules
« on: January 23, 2006, 06:49:06 pm »
Hi,
I am trying to set up version control with CVS for a model stored in a mysql database.

I'm using EA 6.1 build 785 and CVSNT
as repository.

I am able to check files in and out from WinCVS as a client however have problems with using EA.

when I add a package to version control in EA it works fine. However when I attempt to check the package out of CVS (again using EA) I get a "checkout failed" message with no other explanatory text.

Does anyone know why this is?

Thanks
Nick

BushnellD

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Unable to checkout modules
« Reply #1 on: February 04, 2006, 06:13:38 am »
I get exactly the same problem. Same version of EA and am using CVSNT. Is there a known solution out there?

HowardB

  • EA Administrator
  • EA User
  • *****
  • Posts: 55
  • Karma: +0/-0
  • I love YaBBies!
    • View Profile
Re: Unable to checkout modules
« Reply #2 on: February 05, 2006, 08:04:56 pm »
From your description of the problem, I suspect that the file CVS\Root, in your working copy directory, does not contain a connection string that takes the form ":pserver:userName@hostName:/repository/folder".

Another user has reported that WinCVS created a CVS\Root file with contents like "protocol=<value>; user=name; password=pwd; etc...".

EA expects to find your CVS userID, following the second ":" in the file CVS\Root, in the working copy directory.  When you checkout a file from EA, it issues a "cvs edit" command to mark the file as checked out by you.  EA then verifies that the check-out process was successful, by examining the status of the file.  One of the things that it checks, is that the reported "editor" matches the userID it extracted from the file CVS\Root.  If these do not match, EA will conclude that the check-out operation failed and that the package is now checked out to someone else.  Hence the package will appear locked.

Please check the contents of the file CVS\Root.  If the contents are not of the form that EA expects, please modify it so that it is, and try again with EA.

There is a series of steps outlined in the help topic "CVS with Remote Repositories" to verify that your CVS installation will work with EA.  Please run through these steps and confirm that your CVS installation is compatible with EA, before trying to use CVS from within EA.

We will investigate a more reliable means that EA can use to determine the CVS userID, for inclusion in an upcoming release.

dedmoroz345

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Unable to checkout modules
« Reply #3 on: April 04, 2006, 04:50:37 am »
Thank a lot. This message is very useful.
I solve my problem


BushnellD

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Unable to checkout modules
« Reply #4 on: April 04, 2006, 04:55:40 am »
for me it turned out to be a inconsistency between the username for CVS and the windows username. EA insisted on applying the windows username (in lowercase) as my CVS username. Once I change the CVS repository to be consistent with my lowercase windows username it worked fine.

Don't forget to  'unedit' everything in the CVS repository that is locked against your current user before changing your username.