Re: Exception at Subversion

[Ulrich Eckhardt]

Am 17.01.2012 16:31, schrieb Césare - Reitech TI:

Could you please help me out?

[...]


with as much information as possible about what you were trying to do.


Please consider this part.



But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.


And consider this part, too.



'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\lib
svn_wc\wc_db.c'


Lastly, TSVN has a feature that it reminds you of pending upgrades. Turn 
this feature on and upgrade.


You will probably have to throw away your current working copy and check 
out a new one to get around the symptoms.


Good luck!

Uli

**
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
Visit our website at http://www.dominolaser.com
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**

Re: svn:externals to another svn:externals issue

[Daniel Shahaf]

Stephen Butler wrote on Wed, Jan 18, 2012 at 08:56:34 +0100:
> One idea is to
> 
>   svn rm ^/libs/tags/latest
>   svn cp ^/libs/tags/1.1 ^/libs/tags/latest

ITYM

svnmucc rm ^/libs/tags/latest cp HEAD ^/libs/tags/1.1 ^/libs/tags/latest

Re: svn:externals to another svn:externals issue

[Ryan Schmidt]

On Jan 17, 2012, at 10:33, Andrew wrote:

> So I've got a pair of projects, we'll call them /tools and /libs.
> Under each I'm using ./tags/v1.0 ./tags/v2.0 as well as an
> svn:externals of ./tags/latest which points to the most recent tagged
> version.  This all works fine.  What I'd like to do and seem to be
> unable is to use svn:externals to point from /tools/tags/v2.0/libs to
> /libs/tags/latest, as that directory only exists as a property of it's
> parent.  I'd like to use this so that I don't have to worry about
> updating the libs path for my tools every time I release a new
> version.
> 
> Does anyone have any ideas on how I might be able to accomplish this
> or a more effective way of managing this code?

My advice is don't. Instead, continue doing what you've presumably been doing: 
update the external to the specific version that your code works with. How can 
you guarantee today that you won't next month modify the library in a way that 
is not backwards-compatible?

svn: E175002: Server sent unexpected return value (500 Internal Server Error)

[Fridman Galit-R58634]

HI,

I have a problem with svn 1.7.2 with collabnet edge that uses svn 1.7.2 from 
time to time I receive the following error, in different svn commands.

This is an example:
svn ci -m 'release
notes: license server' doc/release_notes.txt Authentication realm: 

CollabNet Subversion Repository
Password for 'user':
svn: E175002: Commit failed (details follow):
svn: E175002: Unable to connect to a repository at URL 
'http://xx:18080/svn/rocoo/trunk/doc'
svn: E175002: Server sent unexpected return value (500 Internal Server
Error) in response to OPTIONS request for 
'http://xx:18080/svn/rocoo/trunk/doc'

I looked for solutions for this issue in the internet, so far no solution 
solved this problem.
This is disturbing the developers in their work.

We moved from SVN 1.5.4.


Thanks,

Galit

Re: Subversion Exception

[Philip Martin]

Frank Capodieci  writes:

> I got an exception on update; Windows 7 Home Premium 64-bit.  I have been
> using Tortoise for over a year without problem.  I don't think I was doing
> anything unusual today except for having a large number of unversioned
> binary files in the folder.
>
> In file
>  
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.3\ext\subversion\subversion\libsvn_wc\update_editor.c'
>  line 1583: assertion failed (action == svn_wc_conflict_action_edit ||
> action
>  == svn_wc_conflict_action_delete || action ==
> svn_wc_conflict_action_replace)

Are there any Unix/Linux users using the repository?  Do you, or did
you, have any files with svn:special set in your working copy?

-- 
Philip

Re: Subversion Exception

[Daniel Shahaf]

Frank Capodieci wrote on Tue, Jan 17, 2012 at 12:13:43 -0800:
> I got an exception on update; Windows 7 Home Premium 64-bit.  I have been
> using Tortoise for over a year without problem.  I don't think I was doing
> anything unusual today except for having a large number of unversioned
> binary files in the folder.
> 

What is the nature of the changes that update was trying to pull?  (You
can determine that with 'svn log -q -v -r BASE:HEAD', or with the
equivalent Tortoise screen.)  Specifically, do they include any tree
changes, or symlink changes?

Do you have any outstanding uncommitted modifications in your working
copy?

> ---
> Subversion Exception!
> ---
> ...
> 
> In file
>  
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.3\ext\subversion\subversion\libsvn_wc\update_editor.c'
>  line 1583: assertion failed (action == svn_wc_conflict_action_edit ||
> action
>  == svn_wc_conflict_action_delete || action ==
> svn_wc_conflict_action_replace)
> ---
> OK
> ---

Re: svn: E175002: Server sent unexpected return value (500 Internal Server Error)

[Daniel Shahaf]

What does httpd's error log say?

Fridman Galit-R58634 wrote on Wed, Jan 18, 2012 at 09:44:47 +:
> HI,
> 
> I have a problem with svn 1.7.2 with collabnet edge that uses svn 1.7.2 from 
> time to time I receive the following error, in different svn commands.
> 
> This is an example:
> svn ci -m 'release
> notes: license server' doc/release_notes.txt Authentication realm: 
> 
> CollabNet Subversion Repository
> Password for 'user':
> svn: E175002: Commit failed (details follow):
> svn: E175002: Unable to connect to a repository at URL 
> 'http://xx:18080/svn/rocoo/trunk/doc'
> svn: E175002: Server sent unexpected return value (500 Internal Server
> Error) in response to OPTIONS request for 
> 'http://xx:18080/svn/rocoo/trunk/doc'
> 
> I looked for solutions for this issue in the internet, so far no solution 
> solved this problem.
> This is disturbing the developers in their work.
> 
> We moved from SVN 1.5.4.
> 
> 
> Thanks,
> 
> Galit
> 
> 
> 
> 

Re: Internal assertion when updating symlink changes on 64-bit Ubuntu 10.04 LTS

[Philip Martin]

Chad Austin  writes:

> I don't recall exactly the issue, but it all started when someone made a
> code checkout with Cygwin and then committed with TortoiseSVN.  Because
> Cygwin and native Windows builds of Subversion use different working copy
> representations of symlinks, suddenly all of the symlinks in the repository
> were broken.

If you run 'svn diff -cN' it should show the changes made to the
symlinks.  What actually changed?

-- 
Philip

RE: svn: E175002: Server sent unexpected return value (500 Internal Server Error)

[Fridman Galit-R58634]

Hi Daniel


In the access log - I think this is the message related to this, but I'm not 
sure.

223.137.95.5 - - [18/Jan/2012:11:52:26 +0200] "OPTIONS 
/svn/rocoo/trunk/demo/lab_demo/demo/template_design/rtl_v/shared_addr/demo_design.v
 HTTP/1.1" 401 401
223.137.95.5 - r56614 [18/Jan/2012:11:52:30 +0200] "OPTIONS 
/svn/rocoo/trunk/demo/lab_demo/demo/template_design/rtl_v/shared_addr/demo_design.v
 HTTP/1.1" 500 539
223.137.95.5 - - [18/Jan/2012:11:53:15 +0200] "OPTIONS 
/svn/rocoo/trunk/demo/lab_demo/demo/template_design/rtl_v/shared_addr/demo_design.v
 HTTP/1.1" 401 401
223.137.95.5 - r56614 [18/Jan/2012:11:53:18 +0200] "OPTIONS 
/svn/rocoo/trunk/demo/lab_demo/demo/template_design/rtl_v/shared_addr/demo_design.v
 HTTP/1.1" 200 189
223.137.95.5 - r56614 [18/Jan/2012:11:53:19 +0200] "REPORT 
/svn/rocoo/!svn/rvr/2081/trunk/demo/lab_demo/demo/template_design/rtl_v/shared_addr/demo_design.v
 HTTP/1.1" 200 756
223.137.95.5 - - [18/Jan/2012:12:22:41 +0200] "OPTIONS /svn/rocoo/trunk 
HTTP/1.1" 401 401
223.137.95.5 - r56614 [18/Jan/2012:12:22:45 +0200] "OPTIONS /svn/rocoo/trunk 
HTTP/1.1" 500 539
223.137.95.5 - - [18/Jan/2012:12:22:47 +0200] "OPTIONS /svn/rocoo/trunk 
HTTP/1.1" 401 401
223.137.95.5 - r56614 [18/Jan/2012:12:22:50 +0200] "OPTIONS /svn/rocoo/trunk 
HTTP/1.1" 200 189
223.137.95.5 - r56614 [18/Jan/2012:12:22:51 +0200] "OPTIONS /svn/rocoo/trunk 
HTTP/1.1" 200 189
223.137.95.5 - r56614 [18/Jan/2012:12:22:51 +0200] "PROPFIND 
/svn/rocoo/!svn/rvr/2082/trunk HTTP/1.1" 207 702


In all other log files there isn't anything.

The problem is that they can run the same command with same user/password and 
it can work.
It once work and once not.

Regards,
Galit

-Original Message-
From: Daniel Shahaf [mailto:danie...@elego.de] 
Sent: Wednesday, January 18, 2012 12:41 PM
To: Fridman Galit-R58634
Cc: users@subversion.apache.org
Subject: Re: svn: E175002: Server sent unexpected return value (500 Internal 
Server Error)

What does httpd's error log say?

Fridman Galit-R58634 wrote on Wed, Jan 18, 2012 at 09:44:47 +:
> HI,
> 
> I have a problem with svn 1.7.2 with collabnet edge that uses svn 1.7.2 from 
> time to time I receive the following error, in different svn commands.
> 
> This is an example:
> svn ci -m 'release
> notes: license server' doc/release_notes.txt Authentication realm: 
>  CollabNet Subversion Repository Password for 
> 'user':
> svn: E175002: Commit failed (details follow):
> svn: E175002: Unable to connect to a repository at URL 
> 'http://xx:18080/svn/rocoo/trunk/doc'
> svn: E175002: Server sent unexpected return value (500 Internal Server
> Error) in response to OPTIONS request for 
> 'http://xx:18080/svn/rocoo/trunk/doc'
> 
> I looked for solutions for this issue in the internet, so far no solution 
> solved this problem.
> This is disturbing the developers in their work.
> 
> We moved from SVN 1.5.4.
> 
> 
> Thanks,
> 
> Galit
> 
> 
> 
> 

commit issue

[Herbert]

Tortoise version:
TortoiseSVN 1.7.4, Build 22459 - 64 Bit , 2012/01/13 12:57:07
Subversion 1.7.2,
apr 1.4.5
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.0e 6 Sep 2011
zlib 1.2.5


Issue:
Commit dialogue will fail on description messages containing quotes like 
"..."


Problem is probably related to the command line:
svn commit -m "..."..."" - will fail

Error displayed (translated):
Pre-Commit blocking with exit-code 255.
"""="*" can not be processed

Re: commit issue

[Ryan Schmidt]

On Jan 18, 2012, at 04:59, Herbert wrote:

> Tortoise version:
> TortoiseSVN 1.7.4, Build 22459 - 64 Bit , 2012/01/13 12:57:07
> Subversion 1.7.2,
> apr 1.4.5
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.0e 6 Sep 2011
> zlib 1.2.5
> 
> 
> Issue:
> Commit dialogue will fail on description messages containing quotes like "..."
> 
> Problem is probably related to the command line:
> svn commit -m "..."..."" - will fail
> 
> Error displayed (translated):
> Pre-Commit blocking with exit-code 255.
> """="*" can not be processed

If you're saying that typing a quotation mark into the TortoiseSVN commit 
dialog produces this error, then that's a TortoiseSVN issue that should be 
reported to their mailing list, not here.

Certainly running that command on the command line will not work because the 
quotes are not escaped according to shell escaping rules.

Re: commit issue

[Stephen Butler]

On Jan 18, 2012, at 11:59 , Herbert wrote:

> Tortoise version:
> TortoiseSVN 1.7.4, Build 22459 - 64 Bit , 2012/01/13 12:57:07
> Subversion 1.7.2,
> apr 1.4.5
> apr-utils 1.3.12
> neon 0.29.6
> OpenSSL 1.0.0e 6 Sep 2011
> zlib 1.2.5
> 
> 
> Issue:
> Commit dialogue will fail on description messages containing quotes like "..."
> 
> Problem is probably related to the command line:
> svn commit -m "..."..."" - will fail
> 
> Error displayed (translated):
> Pre-Commit blocking with exit-code 255.
> """="*" can not be processed

This is an error message from a pre-commit hook script installed by 
your Subversion administrator.  It's not a Subversion (or TortoiseSVN)
bug.  FWIW, TortoiseSVN calls the Subversion API directly, so no shell 
escaping is involved on the client side.

Ask your administrator why he or she chose to forbid quotes in the
commit messages.

Regards,
Steve

Re: commit issue

[Ryan Schmidt]

On Jan 18, 2012, at 05:22, Stephen Butler wrote:

> On Jan 18, 2012, at 11:59 , Herbert wrote:
> 
>> Error displayed (translated):
>> Pre-Commit blocking with exit-code 255.
>> """="*" can not be processed
> 
> This is an error message from a pre-commit hook script installed by 
> your Subversion administrator.  It's not a Subversion (or TortoiseSVN)
> bug.  FWIW, TortoiseSVN calls the Subversion API directly, so no shell 
> escaping is involved on the client side.
> 
> Ask your administrator why he or she chose to forbid quotes in the
> commit messages.

Ah, right. I'm guessing the administrator did not intend to prevent commit 
messages with quotation marks, merely that the administrator never tested that 
scenario and is not escaping things properly in their script.

Re: commit issue

[Andy Levy]

On Wed, Jan 18, 2012 at 06:24, Ryan Schmidt
 wrote:
> On Jan 18, 2012, at 05:22, Stephen Butler wrote:
>
>> On Jan 18, 2012, at 11:59 , Herbert wrote:
>>
>>> Error displayed (translated):
>>> Pre-Commit blocking with exit-code 255.
>>> """="*" can not be processed
>>
>> This is an error message from a pre-commit hook script installed by
>> your Subversion administrator.  It's not a Subversion (or TortoiseSVN)
>> bug.  FWIW, TortoiseSVN calls the Subversion API directly, so no shell
>> escaping is involved on the client side.
>>
>> Ask your administrator why he or she chose to forbid quotes in the
>> commit messages.
>
> Ah, right. I'm guessing the administrator did not intend to prevent commit 
> messages with quotation marks, merely that the administrator never tested 
> that scenario and is not escaping things properly in their script.
>
>

The latter is the most likely scenario. Escaping characters in DOS
batch files isn't as obvious as it is in sane programming
environments. My own pre-commit hook has the same flaw. I just haven't
gotten around to fixing it because I have few enough users that it's
easier to just tell them "don't do that" - and I haven't been given
the time to redo my hooks in a better language.

Re: how to disable svn's copy and move command?

[Nico Kadel-Garcia]

On Thu, Dec 1, 2011 at 6:23 PM, David Brodbeck  wrote:
>
>
> On Thu, Dec 1, 2011 at 3:01 AM, zhiwei chen  wrote:
>>
>> hi,all.
>>
>> I use webdav to host a svn repository, for some reason I want to
>> disable copy and move command, ie. uses can't use 'svn copy' and 'svn
>> move' to commit.
>>
>> I know I can use pre-commit to disable copy and move, and is there
>> another way to do this?
>
>
> I'm not sure this will accomplish what you want.  It won't prevent users
> from checking out files, using their system's own filesystem commands to
> move them, then checking them in in a new location.

I can actually see reasons for this. Forcing an import forces a new
history to be started, and breaks the cross-branch dependencies that
are the sworn archenemy of clearing out debris with svndumpfilter when
rebuilding or transferring a repository.

Re: commit issue

[OBones]

Andy Levy wrote:
My own pre-commit hook has the same flaw. I just haven't gotten around 
to fixing it because I have few enough users that it's easier to just 
tell them "don't do that" - and I haven't been given the time to redo 
my hooks in a better language. 

If that helps, you can strip "forbidden" characters like that:

set LOGMSG=%LOGMSG:>=_%
set LOGMSG=%LOGMSG:'=_%
set LOGMSG=%LOGMSG:"=_%


but the LOGMSG variable must not be empty for it to work. So if you 
extract the log message from the transaction, be sure to always put at 
least one character into LOGMSG and adjust your length checks accordingly.

A full example is here:

http://svnwintools.tigris.org/source/browse/*checkout*/svnwintools/trunk/sources/SVNHookScripts/check-empty-log.bat?revision=HEAD&content-type=text%2Fplain

Re: how to disable svn's copy and move command?

[Les Mikesell]

On Wed, Jan 18, 2012 at 6:14 AM, Nico Kadel-Garcia  wrote:
>>>
>>> hi,all.
>>>
>>> I use webdav to host a svn repository, for some reason I want to
>>> disable copy and move command, ie. uses can't use 'svn copy' and 'svn
>>> move' to commit.
>>>
>>> I know I can use pre-commit to disable copy and move, and is there
>>> another way to do this?
>>
>>
>> I'm not sure this will accomplish what you want.  It won't prevent users
>> from checking out files, using their system's own filesystem commands to
>> move them, then checking them in in a new location.
>
> I can actually see reasons for this. Forcing an import forces a new
> history to be started, and breaks the cross-branch dependencies that
> are the sworn archenemy of clearing out debris with svndumpfilter when
> rebuilding or transferring a repository.

The pre-commit hook should work, but it will prevent the
normal/expected use of branching, tagging etc., so it isn't going to
act much like a subversion repository when you break those operations.

-- 
   Les Mikesell
  lesmikes...@gmail.com

Re: Subversion Exception

[Frank Capodieci]

> Are there any Unix/Linux users using the repository?  Do you, or
> did you, have any files with svn:special set in your working copy?

We have a couple of Mac OS X (Lion) and Ubuntu 10.X users.  I don't think
there are any svn:special settings.

Re: Subversion Exception

[Frank Capodieci]

> What is the nature of the changes that update was trying to pull?  (You
> can determine that with 'svn log -q -v -r BASE:HEAD', or with the
> equivalent Tortoise screen.)  Specifically, do they include any tree
> changes, or symlink changes?

There were a couple of files Moved, in a check in made on Ubuntu 10.10.  I
did have some local modifications, but the problem persisted after I copied
the changes out and reverted.

I tried deleting the folders with the tree changes, but the exception still
happens when I update.

Another programmer is getting the same problem, also on Windows.