Ticket #132 (closed: fixed)
Syntax error parsing revision
| Reported by: | stratvio | Owned by: | alwin |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.x |
| Component: | All | Version: | 0.11.x |
| Severity: | minor | Keywords: | RESOLVED |
| Cc: |
Description
Some of my directories need '@' symbols in them (as dictated by matlab object-oriented syntax), but when using kdesvn on that repository I get errors like "Syntax error parsing revision 'dirname'", where the directory was named '@dirname'.
ADDITIONAL INFORMATION: I get this error on both kdesvn-0.9.2-2 as packaged by mandriva for 2007, as well as the latest snapshot from the repository. I tried grepping through the code base for the error message but didn't see it, so I'm not sure if this is really a bug in the rapidsvn wrapper? I'm using subversion 1.3.2-5 (from mandriva 2007), and running on a 64-bit system.
Attachments
Change History
comment:1 Changed 6 years ago by stratvio
- Owner changed from anonymous to alwin
- Status changed from new to assigned
comment:2 Changed 6 years ago by alwin
- Keywords ACKNOWLEDGED added
- Status changed from assigned to new
This message comes from subversion libs itself.... thinking. Yes, I think I should fix that or setup a workaround. No idea this moment how I should do, but I'll check it out.
tnx for your feedback, I'll tell here whats going on.
comment:3 Changed 6 years ago by alwin
checked it...
ralbrecht@br:/tmp/testco/trunk$ svn mkdir test@mathlabsyntax A test@mathlabsyntax ralbrecht@br:/tmp/testco/trunk$ svn info test@mathlabsyntax svn: Syntax error parsing revision 'mathlabsyntax' ralbrecht@br:/tmp/testco/trunk$
-> this is a real problem with subversion :S Think it should reported to subversion team, seems to be a design problem.
comment:4 Changed 6 years ago by alwin
http://subversion.tigris.org/issues/show_bug.cgi?id=2349
it is reported.
sorry, seems that I can not help you without doing stuff subversion must do.
comment:5 Changed 6 years ago by alwin
- Keywords RESOLVED added; ACKNOWLEDGED removed
- Status changed from new to closed
- Resolution set to fixed
- Milestone set to 0.11.x
comes with next bugfix release next week, backport to 0.9.x - not sure that moment.
comment:6 Changed 6 years ago by stratvio
- Keywords FEEDBACK added; RESOLVED removed
- Status changed from closed to assigned
- Resolution fixed deleted
Hi, I just downloaded 11.1 and tried it out but I'm still getting the syntax error message. Do I also need to upgrade my svn libraries? Also, I noticed that in your test case you have test@matlabsyntax, when Matlab actually requires '@' signs at the beginning of the directory, so I thought that maybe kdesvn worked for @ in the middle but not at the beginning. I just tried creating a "test@testing" directory, though, and I get "Syntax error parsing revision 'testing'." Thanks a lot for looking at this!
comment:7 Changed 6 years ago by alwin
Sure that you used the 0.11.1? I'd checked it again and again - it works fine here (there is another bug on repository browser different to that one here which is fixed in trunk).
Be care: if you just installed the kdesvn-binary somewhere and called this, this is just a simple container. The main application is inside libkdesvnpart.so, so this plugin must exchanged!
comment:8 Changed 6 years ago by stratvio
You're right that I was running it incorrectly... I just ran ./bin/kdesvn from the build directory and saw that the about->kdesvn read 11.1, but it was really running the 9.3 kpart. I uninstalled my old kdesvn and did make install for the new one, but now I'm getting the "Could not find our part" error like in issue 128, but the ld_preload commands aren't working for me. I thought that maybe kdesvn is just installing itself to something outside of kde's kpart search directories, so I tried comparing where it was installing to where the rpm version that works installs... the rpm goes to /usr/lib64, the source was going to /usr/local/lib. I tried adding the -DCMAKE_INSTALL_PREFIX=/usr/ option for cmake and that changed things to go to /usr/lib, but I still get the error, and after about an hour of googling I can't figure out how to a) install to /usr/lib64 instead of /usr/lib or b) figure out where kde is looking for kparts and add locations. I also tried copying from the /usr/lib locations to the corresponding /usr/lib64 locations, but that didn't seem to help (although I may have missed a file?). Any ideas for what I'm doing wrong?
comment:9 Changed 6 years ago by alwin
you may try
-DCMAKE_INSTALL_PREFIX=/usr -DLIB_SUFFIX=64 -DCMAKE_BUILD_TYPE=Release
comment:10 Changed 6 years ago by stratvio
Works great, thanks!
comment:11 Changed 6 years ago by alwin
- Keywords RESOLVED added; FEEDBACK removed
- Status changed from assigned to closed
- Resolution set to fixed
