SVNversion returns "exported" instead of revision number
679 views
Skip to first unread message
Becky Clark
Nov 16, 2012, 7:08:58 PM11/16/12
to us...@tortoisesvn.tigris.org
I am very new to SVN, so I am not sure I even have the correct vocabulary with which to ask the question.
The command svnversion.exe xxxx, which I expect should return the current revision number for the path xxxx, instead returns the string "exported"
I see quite a few instructions for exporting a working copy to eliminate the .svn folders. I wonder if that is, perhaps, what I have done? I would be inclined to conclude that is what I am dealing with, were I not able to update and commit from this copy - SVN Log shows the expected version information.
Can anyone recommend a way to get my copy to the state where the command line returns the correct value?
Thank You!
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3028924
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
The command svnversion.exe xxxx, which I expect should return the current revision number for the path xxxx, instead returns the string "exported"
I see quite a few instructions for exporting a working copy to eliminate the .svn folders. I wonder if that is, perhaps, what I have done? I would be inclined to conclude that is what I am dealing with, were I not able to update and commit from this copy - SVN Log shows the expected version information.
Can anyone recommend a way to get my copy to the state where the command line returns the correct value?
Thank You!
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3028924
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
Stefan Küng
Nov 17, 2012, 3:12:21 AM11/17/12
to us...@tortoisesvn.tigris.org
On 17.11.2012 01:08, Becky Clark wrote:
> I am very new to SVN, so I am not sure I even have the correct vocabulary with which to ask the question.
> The command svnversion.exe xxxx, which I expect should return the current revision number for the path xxxx, instead returns the string "exported"
> I see quite a few instructions for exporting a working copy to eliminate the .svn folders. I wonder if that is, perhaps, what I have done? I would be inclined to conclude that is what I am dealing with, were I not able to update and commit from this copy - SVN Log shows the expected version information.
> Can anyone recommend a way to get my copy to the state where the command line returns the correct value?
> Thank You!
First, svnversion is part of the svn command line tools. This mailing
> I am very new to SVN, so I am not sure I even have the correct vocabulary with which to ask the question.
> The command svnversion.exe xxxx, which I expect should return the current revision number for the path xxxx, instead returns the string "exported"
> I see quite a few instructions for exporting a working copy to eliminate the .svn folders. I wonder if that is, perhaps, what I have done? I would be inclined to conclude that is what I am dealing with, were I not able to update and commit from this copy - SVN Log shows the expected version information.
> Can anyone recommend a way to get my copy to the state where the command line returns the correct value?
> Thank You!
list is for TortoiseSVN. So you might ask questions about the command
line tools on the correct mailing list (subversion users list).
But something seems wrong here. svnversion does not output any text
"exported" at all, which you can check in it's (short) source file:
http://svn.apache.org/repos/asf/subversion/branches/1.7.x/subversion/svnversion/main.c
If you have TSVN installed, you might want to use SubWCRev instead,
depending on what you want to achieve:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-subwcrev.html
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3029007
Becky Clark
Nov 19, 2012, 1:06:57 PM11/19/12
to us...@tortoisesvn.tigris.org, Stefan Küng
Stefan! Many Thanks! You gave me exactly what I needed to resolve the problem, even if I have never really diagnosed it.
You sent a link to the code for version 1.7.x. That is the version I have installed on my machine, but the call to svnversion that returns the value "exported" refers to the version which is in our repository - and that is 1.6.6. Looking, along the same path as the link you provided, at the code for the 1.6.x version, there is this comment:
" If invoked on a directory that is not a working copy, an\n"
" exported directory say, the program will output 'exported'.\n"
So, clearly, that version is not recognizing mine as a working copy. And while I am curious as to how I managed to get it into that state, I found that using the 1.7.7 version returns the correct value. So I will chalk it up to either the difference in the versions or outright user error and just be content for the moment that it is working.
Thank you for your gracious and WONDERFULLY helpful response!
Becky
PS. SubWCRev looks both useful and powerful. I put the end in end-user, but I love to learn and that is a goodie!
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3029451
You sent a link to the code for version 1.7.x. That is the version I have installed on my machine, but the call to svnversion that returns the value "exported" refers to the version which is in our repository - and that is 1.6.6. Looking, along the same path as the link you provided, at the code for the 1.6.x version, there is this comment:
" If invoked on a directory that is not a working copy, an\n"
" exported directory say, the program will output 'exported'.\n"
So, clearly, that version is not recognizing mine as a working copy. And while I am curious as to how I managed to get it into that state, I found that using the 1.7.7 version returns the correct value. So I will chalk it up to either the difference in the versions or outright user error and just be content for the moment that it is working.
Thank you for your gracious and WONDERFULLY helpful response!
Becky
PS. SubWCRev looks both useful and powerful. I put the end in end-user, but I love to learn and that is a goodie!
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3029451
Simon Large
Nov 19, 2012, 5:43:45 PM11/19/12
to us...@tortoisesvn.tigris.org
On 19 November 2012 18:06, Becky Clark <imaf...@aol.com> wrote:
> Stefan! Many Thanks! You gave me exactly what I needed to resolve the problem, even if I have never really diagnosed it.
> You sent a link to the code for version 1.7.x. That is the version I have installed on my machine, but the call to svnversion that returns the value "exported" refers to the version which is in our repository - and that is 1.6.6. Looking, along the same path as the link you provided, at the code for the 1.6.x version, there is this comment:
> " If invoked on a directory that is not a working copy, an\n"
> " exported directory say, the program will output 'exported'.\n"
> So, clearly, that version is not recognizing mine as a working copy. And while I am curious as to how I managed to get it into that state, I found that using the 1.7.7 version returns the correct value. So I will chalk it up to either the difference in the versions or outright user error and just be content for the moment that it is working.
>
> Thank you for your gracious and WONDERFULLY helpful response!
> Becky
>
> PS. SubWCRev looks both useful and powerful. I put the end in end-user, but I love to learn and that is a goodie!
If you are using TortoiseSVN 1.7.x then your working copy will be in
> Stefan! Many Thanks! You gave me exactly what I needed to resolve the problem, even if I have never really diagnosed it.
> You sent a link to the code for version 1.7.x. That is the version I have installed on my machine, but the call to svnversion that returns the value "exported" refers to the version which is in our repository - and that is 1.6.6. Looking, along the same path as the link you provided, at the code for the 1.6.x version, there is this comment:
> " If invoked on a directory that is not a working copy, an\n"
> " exported directory say, the program will output 'exported'.\n"
> So, clearly, that version is not recognizing mine as a working copy. And while I am curious as to how I managed to get it into that state, I found that using the 1.7.7 version returns the correct value. So I will chalk it up to either the difference in the versions or outright user error and just be content for the moment that it is working.
>
> Thank you for your gracious and WONDERFULLY helpful response!
> Becky
>
> PS. SubWCRev looks both useful and powerful. I put the end in end-user, but I love to learn and that is a goodie!
1.7 format. You may recall from the release notes that there was a
major change to the working copy format moving from 1.6 to 1.7. So if
you try to use svnversion 1.6.x on a 1.7.x working copy then it will
not recognise the new format at all and just see unversioned files.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
Reply all
Reply to author
Forward
0 new messages