|
List Info
Thread: cvs2svn issue:syntax error in options file after upgrading to 2.0.0
|
|
| cvs2svn issue:syntax error in options
file after upgrading to 2.0.0 |
|
2007-09-06 10:06:04 |
|
cvs2svn issue: Syntax error in the options file after upgrading
to release 2.0.0
F:Documents and Settingsadmin-grahamMy
Documents>python E:/PROGRA~1/Python24/
Scripts/cvs2svn.py --options FTIRopt.txt
1>f:/svn/FTIR.log
Traceback (most recent call last):
File
"E:/PROGRA~1/Python24/Scripts/cvs2svn.py", line 31, in ?
main(sys.argv[0], sys.argv[1:])
File
"buildbdist.win32eggcvs2svn_libmain.py";, line 49, in main
File
"buildbdist.win32eggcvs2svn_librun_options.py", line 241, in
__init__
File
"buildbdist.win32eggcvs2svn_librun_options.py", line 650, in
process_
options_file
File "FTIRopt.txt", line 179
ctx.svnadmin_executable = 'svnadmin'
^
SyntaxError: invalid syntax
I am working on Migrating our CVS repository to
Subversion. The installations are hosted on the ‘Windows’
platform. Most of the current software development is undertaken on the ‘Windows’
platform but some legacy code was developed in the ‘Linux’ environment.
The plan is to migrate one product range at a time using the
functionality available in the options file to select only certain folders in
CVS to go to a SVN repository for that product range. This was working
using version 1.5 and the output was validated by software engineering, looking
good. There was a single issue in one folder where an attic file had the
same name (in the windows environment) as a file in the folder and the job
errored as per the FAQ sheet. I tried the ‘212;retain-conflicting-attic-files’
switch but it was not documented in the sample options file and was not
accepted as an option using the command line method.
The solution looked to be to upgrade to version 2.0.0 to use
the ‘retain-conflicting-attic-files’; parameter in the new options
file format. Using version 2.0.0 I get the error shown above. It
seems to be missing a library but as I am not a software engineer I am not
sure. I tried using the version 1.5 options file but that came up with
another similar error. The options file has ‘ctx.’ on earlier
lines in the option file so I was not sure if that was the issue?
Any help you can give would be appreciated.
Thanks, Graham
|
| Re: cvs2svn issue:syntax error in
options file after upgrading to 2.0.0 |
|
2007-09-06 11:59:20 |
Rees, Graham wrote:
> cvs2svn issue: Syntax error in the options file after
upgrading to
> release 2.0.0
>
> F:Documents and Settingsadmin-grahamMy
Documents>python
> E:/PROGRA~1/Python24/
>
> Scripts/cvs2svn.py --options FTIRopt.txt
1>f:/svn/FTIR.log
>
> Traceback (most recent call last):
>
> [...]
> File "FTIRopt.txt", line 179
> ctx.svnadmin_executable = 'svnadmin'
> ^
>
> SyntaxError: invalid syntax
Probably there is an unclosed parenthesis or unterminated
string on an
earlier line in the file. It is hard to be sure without
seeing your
whole options file.
Please note that the options file format changes regularly
as cvs2svn
evolves. There is no reason to expect that an options file
that you
wrote for 1.5.x should work with 2.0.0. Check the
differences between
cvs2svn-example.options that came with the two cvs2svn
versions to see
the things that have to be changed in your own options
file.
Michael
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribe cvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
| RE: cvs2svn issue:syntax error in
options file after upgrading to 2.0.0 |
|
2007-09-06 13:27:01 |
Hi Michael,
Thanks for your help with that, I had missed a comment hash
that masked
a close bracket. I had been through the file several times
and missed
it each time!
Now I am back to the same error I started with on v1.5:
F:Documents and Settingsadmin-grahamMy
Documents>python
E:/PROGRA~1/Python24/
Scripts/cvs2svn.py --options FTIRopt.txt
1>f:/svn/FTIR.log
ERROR:
'F:\dataCVS\CVS\Engineering\FTIR2\Software\AutoSipher
SipherViewC
l
ient\ndd\res\toolbar.bmp,v' is not a valid ,v file
Pass 1 complete.
============================================================
============
===
Error summary:
ERROR:
'F:\dataCVS\CVS\Engineering\FTIR2\Software\AutoSipher
SipherViewC
l
ient\ndd\res\toolbar.bmp,v' is not a valid ,v file
Exited due to fatal error(s).
Any suggestions? I have included the options file I have
been using.
It has the retain conflicting attic files as True. I
apologise if this
is something obvious that I have missed again.
Again, thanks for your help.
-Graham
-----Original Message-----
From: Michael Haggerty [mailto:mhaggeralum.mit.edu]
Sent: 06 September 2007 17:59
To: Rees, Graham
Cc: userscvs2svn.tigris.org
Subject: Re: cvs2svn issue:syntax error in options file
after upgrading
to 2.0.0
Rees, Graham wrote:
> cvs2svn issue: Syntax error in the options file after
upgrading to
> release 2.0.0
>
> F:Documents and Settingsadmin-grahamMy
Documents>python
> E:/PROGRA~1/Python24/
>
> Scripts/cvs2svn.py --options FTIRopt.txt
1>f:/svn/FTIR.log
>
> Traceback (most recent call last):
>
> [...]
> File "FTIRopt.txt", line 179
> ctx.svnadmin_executable = 'svnadmin'
> ^
>
> SyntaxError: invalid syntax
Probably there is an unclosed parenthesis or unterminated
string on an
earlier line in the file. It is hard to be sure without
seeing your
whole options file.
Please note that the options file format changes regularly
as cvs2svn
evolves. There is no reason to expect that an options file
that you
wrote for 1.5.x should work with 2.0.0. Check the
differences between
cvs2svn-example.options that came with the two cvs2svn
versions to see
the things that have to be changed in your own options
file.
Michael
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
 |
| Re: cvs2svn issue:syntax error in
options file after upgrading to 2.0.0 |
|
2007-09-06 16:07:21 |
Rees, Graham wrote:
> Now I am back to the same error I started with on
v1.5:
>
> F:Documents and Settingsadmin-grahamMy
Documents>python
> E:/PROGRA~1/Python24/
> Scripts/cvs2svn.py --options FTIRopt.txt
1>f:/svn/FTIR.log
> ERROR:
>
'F:\dataCVS\CVS\Engineering\FTIR2\Software\AutoSipher
SipherViewC
> l
> ient\ndd\res\toolbar.bmp,v' is not a valid ,v file
> Pass 1 complete.
>
============================================================
============
> ===
> Error summary:
> ERROR:
>
'F:\dataCVS\CVS\Engineering\FTIR2\Software\AutoSipher
SipherViewC
> l
> ient\ndd\res\toolbar.bmp,v' is not a valid ,v file
> Exited due to fatal error(s).
>
> Any suggestions? I have included the options file I
have been using.
> It has the retain conflicting attic files as True. I
apologise if this
> is something obvious that I have missed again.
This is very likely some form of corruption in the file that
was
mentioned by cvs2svn. Don't be ashamed, it happens all the
time 
You should either open the file in an editor and attempt to
repair it,
or send it to the mailing list for diagnosis and
suggestions, or delete
it (if for some reason you don't need it in your
repository).
Michael
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org
|
|
[1-4]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|