Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
I upgraded a tree from 1.6.x directly to 1.7.1 and I'm getting this, so the bug (or a similar one) definitely persists. I've got very big trees, so checkouts take most of a day, so redoing the checkout isn't so convenient. From: Stefan Sperling stsp_at_elego.de Date: Wed, 2 Nov 2011 12:13:03 +0100 On Wed, Nov 02, 2011 at 06:58:47PM +0800, Kun Wang wrote: I did not installed 1.7.0. I updated my working copy using 1.7.1. And the working copy worked for days... OK, thanks. This probably means that there is another bug in the upgrade code. A new checkout should work fine, though.
Re: Couldn't open rep-cache database (post commit FS processing)
Since posting the question, I tried using svnserve instead of Apache (the mod_dav_svn module), and the error does NOT occur in this case (we would still prefer to stick with mod_dav_svn). How did you manage permissions using svnserver? You mentioned a group which you gave read/write access for the file. Did you made svnserve-deamon member of thet group or did something else? I thought of lock files rep-cache.db which may be not created during insufficient permissions on the parent directory. But I don't know if SQLite works this way. I ran the svnserver test as root, without any restrictions. But I don't think it's a permission issue on the rep-cache.db file since I even tried giving it unrestricted read/write access to be sure that wasn't the case. Could other files be involved?
error message
--- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list archives for the error message to avoid reporting the same problem repeatedly. You can find the mailing list archives at http://subversion.apache.org/mailing-lists.html Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_client\switch.c' line 137: assertion failed (switch_url (switch_url[0] != '\0')) --- OK --- __ Christophe Doumenc Software Engineer Novabase Digital TV, EURL Building Innovaparc - Gate A3 2 rue Jean Perrin 14460 Colombelles - France Tel. (+33) (0)2 50 01 15 22 christophe.doum...@novabasedigitaltv.commailto:christophe.doum...@novabasedigitaltv.com Skype : christophe.doumenc [cid:image001.png@01CCA325.DE05A0D0] www.novabase.pt http://www.novabase.pt This message is confidential, please do not copy or reveal it. If you've received this e.mail by mistake, please notify the sender and then delete it from your system. Print only when absolutely necessary. Thank you! inline: image001.png
Re: Cannot cleanup
Am 14.11.2011 19:45, schrieb Andy Creed: But please first search the mailing list archives for the error message Please do this, the error has been reported all over since the 1.7 release. IIRC, in this case you will have to check out a new working copy and manually copy the changes over. Also, 1.7.1 brings some enhancements in that area, so please upgrade TSVN, too. 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: Client commit hangs, server svnlook.exe hogs CPU
Aha - yes, we are running windows 64 bit server. We use subversionnotify for pre-commit hooks but by default there is a post commit hook that I guess could be doing a diff so this looks very promising. When 1.7.2 is released via SVN Edge I'll re-instate the post commit hook (just to test). Thanks for the response Mark. Thanks also to Stefan Markus who also pointed out that it was not SVN that calls svnlook.exe - I removed the post commit hook (not used anyway) and so far so good. Paul Hester From: Mark Phippard [mailto:markp...@gmail.com] Sent: 11 November 2011 13:40 To: Hester, Paul Cc: users@subversion.apache.org Subject: Re: Client commit hangs, server svnlook.exe hogs CPU On Fri, Nov 11, 2011 at 3:06 AM, Hester, Paul paul.hes...@cobham.com wrote: Since upgrading to 1.7.0, and 1.7.1 via subversion edge, about half the commits being done by users (via tortoise) result in the commit hanging after most of the work has been done. Whilst hung, the repository shows the commit has taken place, but on the server svnlook.exe is hogging all the CPU. Killing the svnlook.exe process allows the commit to continue (normally). Is the server Windows 64-bits? There is an infinite loop bug that is fixed for 1.7.2 that can occur on Windows 64-bit with diff algorithm. So if you are making a diff for a post-commit email or something like that it could be that you are running into. -- Thanks Mark Phippard http://markphip.blogspot.com/ This e-mail and any files transmitted with it (E-mail) is intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the addressee(s), any disclosure, reproduction, copying, distribution or other use of the E-mail is prohibited. If you have received this E-mail in error, please delete it and notify the sender immediately via our switchboard or return e-mail. Neither the company nor any subsidiary or affiliate or associated company nor any individual sending this E-mail accepts any liability in respect of the content (including errors and omissions) nor shall this e-mail be deemed to enter the company or any subsidiary or affiliate or associated company into a contract or to create any legally binding obligations unless expressly agreed to in writing under separate cover and timeliness of the E-mail which arise as a result of transmission. If verification is required, please request a hard copy version from the sender.
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
Ethan Bradford ethan.bradf...@swype.com writes: I upgraded a tree from 1.6.x directly to 1.7.1 and I'm getting this, so the bug (or a similar one) definitely persists. I've got very big trees, so checkouts take most of a day, so redoing the checkout isn't so convenient. What did the 1.6 working copy look like? Was it a sparse working copy? Did it have any local modifications? Any switched subdirectories? Any uncommitted moves, copies or deletes? Do you have the sqlite3 tool available to query the 1.7 working copy? sqlite3 .svn/wc.db select count(*) from nodes where op_depth 0 -- Philip
RE: error message
...and I don't remember anymore now. Will be for next time, then... Christophe Doumenc -Original Message- From: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com] Sent: Tuesday, November 15, 2011 9:10 AM To: users@subversion.apache.org Cc: Christophe Doumenc Subject: Re: error message Am 15.11.2011 08:49, schrieb Christophe Doumenc: Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. Please consider this part of the message, you don't provide any information about what you did, making your bug report effectively useless. 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. **
user access
Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2[dev accesses this using domain\unamepwd] \product3[dev accesses this using domain\unamepwd] \temprepo[dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise
RE: user access
-Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c
Re: user access
Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On DAV svn SVNListParentPath on SVNParentPath F:\SVN #SVNIndexXSLT /svnindex.xsl AuthType SSPI AuthName Subversion repositories #AuthUserFile passwd #AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\companyname Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c
RE: user access
[We normally bottom-post on this list to make it easier to read in order... See in-line below] -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 14:47 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following ...is this in a Location or Directory etc section? SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On AuthType SSPI AuthName Subversion repositories Require valid-user Require group DOMAIN\companyname ...using SSPI to _authenticate_ the user against Active Directory OK... NB: also provides basic _authorisation_ by rejecting non-group users. DAV svn SVNListParentPath on SVNParentPath F:\SVN ...sets the path and enables subversion... #SVNIndexXSLT /svnindex.xsl ...you would use this to provide a nice view of the repository (TortoiseSVN has a section on this in their help file)... #AuthUserFile passwd ...this is for basic http authentication, you can delete this... #AuthzSVNAccessFile F:/SVN/auth.conf ...this is the line where you point svn to your file that controls authorisation (who can access what) but it is commented out? Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. What exactly do you not understand? Is it the authz file contents (described on the page linked above) or the apache config? ~ mark c
Re: user access
From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 10:05 AM Subject: RE: user access [We normally bottom-post on this list to make it easier to read in order... See in-line below] -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 14:47 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following ...is this in a Location or Directory etc section? SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On AuthType SSPI AuthName Subversion repositories Require valid-user Require group DOMAIN\companyname ...using SSPI to _authenticate_ the user against Active Directory OK... NB: also provides basic _authorisation_ by rejecting non-group users. DAV svn SVNListParentPath on SVNParentPath F:\SVN ...sets the path and enables subversion... #SVNIndexXSLT /svnindex.xsl ...you would use this to provide a nice view of the repository (TortoiseSVN has a section on this in their help file)... #AuthUserFile passwd ...this is for basic http authentication, you can delete this... #AuthzSVNAccessFile F:/SVN/auth.conf ...this is the line where you point svn to your file that controls authorisation (who can access what) but it is commented out? Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. What exactly do you not understand? Is it the authz file contents (described on the page linked above) or the apache config? ~ mark c Dear Mark, As you correctly pointed out, the following lines are commented out #AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\companyname This was initially set up to allow all developers access to all repositories with F:\svn From the article you sent me, i now have to un-comment the line #AuthzSVNAccessFile F:/SVN/auth.conf and use a auth.conf file and define the users [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw user4=r where would i define this user name and pwd as this is not being authenticated against the domain. do not want to create a domain user account for this user. would this be the correct set up?
Re: user access
From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 10:05 AM Subject: RE: user access [We normally bottom-post on this list to make it easier to read in order... See in-line below] -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 14:47 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following ...is this in a Location or Directory etc section? SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On AuthType SSPI AuthName Subversion repositories Require valid-user Require group DOMAIN\companyname ...using SSPI to _authenticate_ the user against Active Directory OK... NB: also provides basic _authorisation_ by rejecting non-group users. DAV svn SVNListParentPath on SVNParentPath F:\SVN ...sets the path and enables subversion... #SVNIndexXSLT /svnindex.xsl ...you would use this to provide a nice view of the repository (TortoiseSVN has a section on this in their help file)... #AuthUserFile passwd ...this is for basic http authentication, you can delete this... #AuthzSVNAccessFile F:/SVN/auth.conf ...this is the line where you point svn to your file that controls authorisation (who can access what) but it is commented out? Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. What exactly do you not understand? Is it the authz file contents (described on the page linked above) or the apache config? ~ mark c Also, the following is part of Location /SVN Location /svn SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On DAV svn SVNListParentPath on SVNParentPath F:\SVN #SVNIndexXSLT /svnindex.xsl AuthType SSPI AuthName Subversion repositories #AuthUserFile passwd #AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\companyname /Location
Downloading Link for Ankh SVN 1.7.x for 64 Bit
Hi I am already using r Ankh SVN 1.7.x for 32 Bit. Pls refer a link for 64 Bit as I am unable to get this. Cheers,
Re: user access
From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com Sent: Tuesday, November 15, 2011 10:36 AM Subject: RE: user access From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 10:05 AM Subject: RE: user access [We normally bottom-post on this list to make it easier to read in order... See in-line below] -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathba sedauthz.html ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 14:47 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following ...is this in a Location or Directory etc section? SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On AuthType SSPI AuthName Subversion repositories Require valid-user Require group DOMAIN\companyname ...using SSPI to _authenticate_ the user against Active Directory OK... NB: also provides basic _authorisation_ by rejecting non-group users. DAV svn SVNListParentPath on SVNParentPath F:\SVN ...sets the path and enables subversion... #SVNIndexXSLT /svnindex.xsl ...you would use this to provide a nice view of the repository (TortoiseSVN has a section on this in their help file)... #AuthUserFile passwd ...this is for basic http authentication, you can delete this... #AuthzSVNAccessFile F:/SVN/auth.conf ...this is the line where you point svn to your file that controls authorisation (who can access what) but it is commented out? Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. What exactly do you not understand? Is it the authz file contents (described on the page linked above) or the apache config? ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 15:25 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Dear Mark, As you correctly pointed out, the following lines are commented out #AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\companyname This was initially set up to allow all developers access to all repositories with F:\svn From the article you sent me, i now have to un-comment the line #AuthzSVNAccessFile F:/SVN/auth.conf and use a auth.conf file and define the users [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw user4=r where would i define this user name and pwd as this is not being authenticated against the domain. do not want to create a domain user account for this user. would this be the correct set up? The three lines:- SSPIAuthoritative On Require valid-user Require group DOMAIN\companyname ...mean that they have to have a domain account! If you want to offern non-domain accounts then you need to configure apache to offer this (start here: http://httpd.apache.org/docs/2.2/howto/auth.html), turn off SSPIAuthoritative and add appropriate `require` directives. For the authz file, you can define groups of users to make the permissions sections easier to read. If you have lots of developers this could get tedious though! By the way, you are using https aren't
Re: WC database corruption (1.7.1)
Around about 10/11/11 17:01, Philip Martin typed ... It may be as simple as sqlite .svn/wc.db reindex nodes sqlite .svn/wc.db reindex pristine Nope. “Error: database disk image is malformed”. sqlite3 .svn/wc.db select sql from sqlite_master where name='NODES' sqlite3 .svn/wc.db select sql from sqlite_master where name='I_NODES_PARENT' will show you the SQL for the table and index that need to be recreated. These work. Make a backup copy of wc.db before going further! Create a duplicate table NODES_COPY: OK Copy NODES into NODES_COPY OK Drop and recreate NODES: OK Copy NODES_COPY into NODES: sqlite3 .svn/wc.db insert into NODES select * from NODES_COPY Oops. “Error: database disk image is malformed”. Which is a bit odd, since we copied NODES to NODES_COPY OK, and have since re-created NODES! I didn't go any further. I should also point out that at this stage this is academic, as I'm using a new checkout (actually, maybe naughtily, I renamed my dead WC, checked out a clean WC to the same (old) name, then re-shuffled the names back, and replaced the dead .svn with the fresh one. I think that was safe, as they were based on the same rev.). But I don't mind continuing to fiddle if it'll highlight anything. I have kept a copy of the dead .svn just for that. -- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
Thank you for investigating this, Philip. Answers below. On Tue, Nov 15, 2011 at 2:06 AM, Philip Martin philip.mar...@wandisco.comwrote: Ethan Bradford ethan.bradf...@swype.com writes: I upgraded a tree from 1.6.x directly to 1.7.1 and I'm getting this, so the bug (or a similar one) definitely persists. I've got very big trees, so checkouts take most of a day, so redoing the checkout isn't so convenient. What did the 1.6 working copy look like? Was it a sparse working copy? I did not have a sparse working copy -- I had a full recursive checkout. Did it have any local modifications? It had a couple of local mods, though I don't remember what exactly. Nothing I need to keep. Any switched subdirectories? No, I don't know what this is, so I probably didn't do it. Any uncommitted moves, copies or deletes? No, I'm pretty sure I don't. Do you have the sqlite3 tool available to query the 1.7 working copy? sqlite3 .svn/wc.db select count(*) from nodes where op_depth 0 I installed sqlite3 to check this. The answer it gets is 0. (I checked that it is basically working. .tables shows a reasonable set of tables. select * from nodes yields quite a bit.) I should add that this data was recently moved to this computer from my old laptop (which precipitated my move to SVN version 1.7). I mostly access through TortoiseSVN. -- Philip
RE: user access
From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 10:05 AM Subject: RE: user access [We normally bottom-post on this list to make it easier to read in order... See in-line below] -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 13:29 To: users@subversion.apache.org Subject: user access Have svn running on windows/apache and currently dev team accesses svn repo's using http and tortoisesvn They access the repos using their domain credentials set up in apache config. we now have a group of temps that we want to create a new repo for and that they should only access that repo either by using uname/pwd or via domain access. current set up [server name]\c:\svnrepo \product1 [dev accesses this using domain\unamepwd] \product2 [dev accesses this using domain\unamepwd] \product3 [dev accesses this using domain\unamepwd] \temprepo [dev accesses this using domain\unamepwd || the temp lackies access it using their uname and pwd only for this repo] Is this set up possible? how would i go about it? am open to changing access type based on best practise From: Cooke, Mark mark.co...@siemens.com To: j s jbluede...@yahoo.com; users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:51 AM Subject: RE: user access Take a read of the subversion book here:- http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathba sedauthz.html ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 14:47 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Mark, Looked at the link you provided. In my apache/conf/httpd.conf file i have the following ...is this in a Location or Directory etc section? SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On AuthType SSPI AuthName Subversion repositories Require valid-user Require group DOMAIN\companyname ...using SSPI to _authenticate_ the user against Active Directory OK... NB: also provides basic _authorisation_ by rejecting non-group users. DAV svn SVNListParentPath on SVNParentPath F:\SVN ...sets the path and enables subversion... #SVNIndexXSLT /svnindex.xsl ...you would use this to provide a nice view of the repository (TortoiseSVN has a section on this in their help file)... #AuthUserFile passwd ...this is for basic http authentication, you can delete this... #AuthzSVNAccessFile F:/SVN/auth.conf ...this is the line where you point svn to your file that controls authorisation (who can access what) but it is commented out? Unable to translate the link to sections in the apache/conf/httpd.conf file. appreciate any useful tips. What exactly do you not understand? Is it the authz file contents (described on the page linked above) or the apache config? ~ mark c -Original Message- From: j s [mailto:jbluede...@yahoo.com] Sent: 15 November 2011 15:25 To: Cooke, Mark; users@subversion.apache.org Subject: Re: user access Dear Mark, As you correctly pointed out, the following lines are commented out #AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\companyname This was initially set up to allow all developers access to all repositories with F:\svn From the article you sent me, i now have to un-comment the line #AuthzSVNAccessFile F:/SVN/auth.conf and use a auth.conf file and define the users [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw [/product1] mydomain\user1=rw mydomain\user2=rw mydomain\user3=rw user4=r where would i define this user name and pwd as this is not being authenticated against the domain. do not want to create a domain user account for this user. would this be the correct set up? The three lines:- SSPIAuthoritative On Require valid-user Require group DOMAIN\companyname ...mean that they have to have a domain account! If you want to offern non-domain accounts then you need to configure apache to offer this (start here: http://httpd.apache.org/docs/2.2/howto/auth.html), turn off SSPIAuthoritative and add appropriate `require` directives. For the authz file, you can define groups of users to make the permissions sections easier to read. If you have lots of developers this could get tedious though! By the way, you are using https aren't you?
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
Ethan Bradford ethan.bradf...@swype.com writes: Do you have the sqlite3 tool available to query the 1.7 working copy? sqlite3 .svn/wc.db select count(*) from nodes where op_depth 0 I installed sqlite3 to check this. The answer it gets is 0. Fine. Next: sqlite3 .svn/wc.db select * from work_queue There may be multiple lines. You should see something like: 6|(file-install A/f 1 0 1 1) A/f is just an example, in your case it will be the path of a file in your wc. So sqlite3 .svn/wc.db select * from nodes where local_relpath='A/f' You may see a checksum like: $sha1$7ab6a41b5d9bc8fad70cc0314c142c91feab4686 or it may be missing. If present: sqlite3 .svn/wc.db select * from pristine where checksum like '%ab6a41b5d9bc8fad70cc0314c142c91feab4686 or sqlite3 .svn/wc.db select * from pristine where checksum='\$sha1\$ab6a41b5d9bc8fad70cc0314c142c91feab4686 they should be the same (one escapes the '$' characters, the other drops them). -- Philip
Re: WC database corruption (1.7.1)
Neil Bird n...@jibbyjobby.co.uk writes: Copy NODES_COPY into NODES: sqlite3 .svn/wc.db insert into NODES select * from NODES_COPY Oops. “Error: database disk image is malformed”. Which is a bit odd, since we copied NODES to NODES_COPY OK, and have since re-created NODES! Odd indeed. Some sort of lazy, copy-on-write copy perhaps? I think that means that the corruption extends beyond the indices into the nodes table, and that makes it very hard to recover. -- Philip
error report
--- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list archives for the error message to avoid reporting the same problem repeatedly. You can find the mailing list archives at http://subversion.apache.org/mailing-lists.html Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\workqueue.c' line 672: assertion failed (checksum != NULL) --- OK --- -- Frank Liu Orite Group Pty Ltd http://www.orite.com.au e-mail: fr...@orite.com tel: +61(2) 8090 2030 ext. 100 fax: +61(2) 8212 9543 mob: 0414 583 962
Re: error report
Frank Liu - Orite Group fr...@orite.com writes: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\workqueue.c' line 672: assertion failed (checksum != NULL) That's the same error as reported in this thread: http://mail-archives.apache.org/mod_mbox/subversion-users/20.mbox/%3c87d3ctd7if@stat.home.lan%3E so the same questions apply. -- Philip
RE: svn server binaries for windows 2003
Have my current svn server on windows 2003 with apache. Looking to upgrade to svn 1.7.1 from 1.5 Looked at subversion edge. Is there an easier way wherein I can just replace the 1.5 binaries with 1.7.1 binaries?
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
sqlite3 .svn/wc.db select * from work_queue 3|(file-install 59 DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED] 1 0 1 1) sqlite3 .svn/wc.db select * from nodes where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' 1|DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|0|DBBuild/Wordlists/Belarusian|1|Trunk/DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|3936|normal|||file||infinity|||3323|1294867663142001|Erik.Larsson|504|1294985508149158|| So there's no checksum (according to other entries, it would be the field just after infinity). On Tue, Nov 15, 2011 at 9:33 AM, Philip Martin philip.mar...@wandisco.comwrote: Ethan Bradford ethan.bradf...@swype.com writes: Do you have the sqlite3 tool available to query the 1.7 working copy? sqlite3 .svn/wc.db select count(*) from nodes where op_depth 0 I installed sqlite3 to check this. The answer it gets is 0. Fine. Next: sqlite3 .svn/wc.db select * from work_queue There may be multiple lines. You should see something like: 6|(file-install A/f 1 0 1 1) A/f is just an example, in your case it will be the path of a file in your wc. So sqlite3 .svn/wc.db select * from nodes where local_relpath='A/f' You may see a checksum like: $sha1$7ab6a41b5d9bc8fad70cc0314c142c91feab4686 or it may be missing. If present: sqlite3 .svn/wc.db select * from pristine where checksum like '%ab6a41b5d9bc8fad70cc0314c142c91feab4686 or sqlite3 .svn/wc.db select * from pristine where checksum='\$sha1\$ab6a41b5d9bc8fad70cc0314c142c91feab4686 they should be the same (one escapes the '$' characters, the other drops them). -- Philip
svnadmin load is slow for many small revisions
Hi all, After transition from debian lenny to squeeze I recompiled my version of SVN 1.4 (yes, I do need exactly 1.4). I tried to load a dump with many 1 file revisions into the BDB-based repository. First 300 revisions are committed really fast, like 10 revisions per second. After 1000 revisions, it is about 1-2 seconds per one revision. And performance keeps degrading. I'm curious what that might be? I tried to compile against different versions of APR (from 1.3 to 1.5) with BDB 4.8. I used libtool 1.5 since autogen.sh does not work with libtool 2.2. May this be somehow related to my issue? Maybe some compilations flags are wrong for a new system, or some libraries that I'm linking against (e.g. neon)? I have no real clue what that might be, so I will highly appreciate if somebody can give me any pointers, even vague ones or possible hints to try, since I really need SVN 1.4 for my other projects. P.S. CPU usage is very high, waiting for IO was about high (that what I would expect) and decreases to 0% over the time. P.P.S. I also tried to compile in maintainer mode and without, with preinstalled APR, and by putting them into source tree, with mod_dav and without. Still the same... Thanks a lot in advance, Vyacheslav
Re: user access with subversion edge
Downloaded subversion edge to run on my current server serving svn 1.5.x with apache and repo's accessed via HTTP figured i use subversion edge to get the latest svn server - 1.7.1 as i could not find just the binaries to replace over my existing installation. in my 1.5.x i had this in my apache\conf\httpd.conf file Location /SVN SSPIAuth On SSPIAuthoritative On SSPIDomain domaincontroller SSPIOmitDomain on SSPIUsernameCase lower SSPIPerRequestAuth on SSPIOfferBasic On DAV svn SVNListParentPath on SVNParentPath F:\SVN #SVNIndexXSLT /svnindex.xsl AuthType SSPI AuthName Subversion repositories #AuthUserFile passwd AuthzSVNAccessFile F:/SVN/auth.conf Require valid-user Require group DOMAIN\COMPANYNAME /Location With subversion edge, i have things configured - however when i try to access my repo using [domainname]\[username] which previously worked, does not work with subversion edge. does subversion edge not support this?
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
Ethan Bradford ethan.bradf...@swype.com writes: sqlite3 .svn/wc.db select * from work_queue 3|(file-install 59 DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED] 1 0 1 1) sqlite3 .svn/wc.db select * from nodes where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' 1|DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|0|DBBuild/Wordlists/Belarusian|1|Trunk/DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|3936|normal|||file||infinity|||3323|1294867663142001|Erik.Larsson|504|1294985508149158|| So there's no checksum (according to other entries, it would be the field just after infinity). That's very odd. Do you know which version of Subversion is running on the server? Running something like curl -D - REPO_URL might help find out. Are there other files with no checksum? sqlite3 .svn/wc.db select count(*) from nodes where checksum is null and kind='file' If there are other files then is there any pattern in the filenames? All in the same directory? All modified in the same commit? etc. sqlite3 .svn/wc.db select local_relpath from nodes where checksum is null and kind='file' Can you describe the recent activity in the working copy? Do you normally update the whole working copy or do you update subtrees? Did you commit changes in the Belarusian directory just before the update? The NODES row shows that the update was trying to install revision 3936 of the file. The filename is BelarusianForceFreq.txt[MOVED]; has this file been moved/copied within the repository? The last modified revision of the file is 3323, would you have committed that revision from this working copy? Do you know the revision before the update? It's possible that you can identify it using sqlite3 .svn/wc.db select revision from nodes where revision != 3936 or perhaps sqlite3 .svn/wc.db select revision from nodes where parent_relpath='DBBuild/Wordlists/Belarusian' or perhaps you can guess the approximate revision based on dates? If you can identify the (approx?) revision before the update then running svn log -vq URL will allow you to see the sort of changes the update would have been making. I want to know what the update did to this file, did it just modify the content of the file, or add the file, or replace another file of the same name? Perhaps the whole directory was being added? Thanks for your help so far! -- Philip
wierd issue with subversion edge
my old svn set up had apache serving the respository as http://somewhere.com/SVNREPO/Project1 i upgraded to subversion edge and now i see the http access as http://somewhere.com/svnrepo/Project1 not sure how it became lover case. I don't want to instruct all developers to perform a switch within torstoiosesvn. is there a way i can rectify this wherein the casing of the repo in the url does not change?
Re: wierd issue with subversion edge
On Tue, Nov 15, 2011 at 20:10, j s jbluede...@yahoo.com wrote: my old svn set up had apache serving the respository as http://somewhere.com/SVNREPO/Project1 i upgraded to subversion edge and now i see the http access as http://somewhere.com/svnrepo/Project1 not sure how it became lover case. I don't want to instruct all developers to perform a switch within torstoiosesvn. is there a way i can rectify this wherein the casing of the repo in the url does not change? What is the name of the directory on the server's filesystem? Windows (NTFS) is case-preserving, but not case-sensitive. Apache on Windows will let you check out even if you have the case wrong, but when you commit you may run into trouble with AuthZ path rules (though I understand some of this has changed from 1.6 to 1.7, and there's at least one outstanding bug there).
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
On Tue, Nov 15, 2011 at 4:28 PM, Philip Martin philip.mar...@wandisco.comwrote: Ethan Bradford ethan.bradf...@swype.com writes: sqlite3 .svn/wc.db select * from work_queue 3|(file-install 59 DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED] 1 0 1 1) sqlite3 .svn/wc.db select * from nodes where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' 1|DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|0|DBBuild/Wordlists/Belarusian|1|Trunk/DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|3936|normal|||file||infinity|||3323|1294867663142001|Erik.Larsson|504|1294985508149158|| So there's no checksum (according to other entries, it would be the field just after infinity). That's very odd. Do you know which version of Subversion is running on the server? Running something like curl -D - REPO_URL might help find out. I don't know what the server version is. cURL won't accept an svn: URL. I can't figure out how to get the version out of the repro browser, which is the most direct serverconnection in the toolset I know. Are there other files with no checksum? sqlite3 .svn/wc.db select count(*) from nodes where checksum is null and kind='file' The answer to that query is 1, so that's the only pattern. (Old fashioned searches through the dumped list of nodes confirms this.) If there are other files then is there any pattern in the filenames? All in the same directory? All modified in the same commit? etc. sqlite3 .svn/wc.db select local_relpath from nodes where checksum is null and kind='file' Can you describe the recent activity in the working copy? Do you normally update the whole working copy or do you update subtrees? Normally I update a large subtree (several levels up from this file). Did you commit changes in the Belarusian directory just before the update? No, I haven't committed changes from that directory in months. Nobody else has either. The NODES row shows that the update was trying to install revision 3936 of the file. The filename is BelarusianForceFreq.txt[MOVED]; has this file been moved/copied within the repository? We moved these files to another repository, so that SVN couldn't (as far as we could figure out) understand the move. So we renamed the the files on the source side to keep their history conveniently available. The last modified revision of the file is 3323, would you have committed that revision from this working copy? That is the last revision, and I didn't commit it from this computer. (It was inf Do you know the revision before the update? It's possible that you can identify it using sqlite3 .svn/wc.db select revision from nodes where revision != 3936 or perhaps sqlite3 .svn/wc.db select revision from nodes where parent_relpath='DBBuild/Wordlists/Belarusian' or perhaps you can guess the approximate revision based on dates? If you can identify the (approx?) revision before the update then running svn log -vq URL will allow you to see the sort of changes the update would have been making. I want to know what the update did to this file, did it just modify the content of the file, or add the file, or replace another file of the same name? Perhaps the whole directory was being added? Using the repo browser I can see the whole history. There are just two versions of this file, none more recent than 3323. I think 3936 is a red herring -- that was perhaps the tip revision for the whole repository when the update was attempted. (The current tip is 4013.) I hate to confess to such absent mindedness, but I may have svn deleteed this file. I see that I don't have a local copy of it, which supports that theory. If I did that, I didn't commit the change -- the repository still has the file. Thanks for your help so far! I'm happy to help, and I appreciate your time. Just to be clear, I wouldn't dream of taking so much of your time just to solve my local problem. You're digging into this to figure out the bug with change to the 1.7.1 version (or maybe svn update within the 1.7.1 version), right? Since I will likely need to do another checkout anyhow, I'm happy to try experiments which might be destructive to my local copy. -- Philip
Re: wierd issue with subversion edge
From: Andy Levy andy.l...@gmail.com To: j s jbluede...@yahoo.com Cc: users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:17 PM Subject: Re: wierd issue with subversion edge On Tue, Nov 15, 2011 at 20:10, j s jbluede...@yahoo.com wrote: my old svn set up had apache serving the respository as http://somewhere.com/SVNREPO/Project1 i upgraded to subversion edge and now i see the http access as http://somewhere.com/svnrepo/Project1 not sure how it became lover case. I don't want to instruct all developers to perform a switch within torstoiosesvn. is there a way i can rectify this wherein the casing of the repo in the url does not change? What is the name of the directory on the server's filesystem? Windows (NTFS) is case-preserving, but not case-sensitive. Apache on Windows will let you check out even if you have the case wrong, but when you commit you may run into trouble with AuthZ path rules (though I understand some of this has changed from 1.6 to 1.7, and there's at least one outstanding bug there). Dear Andy, This is the name on the file system F:\SVNREPO When I access the repo using IE with upper case it fails as well.
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
To test whether dealing with the SVN DELETE was the problem, I copied that directory from another computer in 1.6 format, did SVN DELETE on that file, and then updated the format to to 1.7.1. The update happened w/o error, and the updated directory seems to work fine. So I wasn't able to repro the problem there. One difference with the previous test is that for this test, Belarusian was the root directory (so it keeps its .svn subdirectory). Before, it was a child of the directory I updated. On Tue, Nov 15, 2011 at 5:21 PM, Ethan Bradford ethan.bradf...@swype.comwrote: On Tue, Nov 15, 2011 at 4:28 PM, Philip Martin philip.mar...@wandisco.com wrote: Ethan Bradford ethan.bradf...@swype.com writes: sqlite3 .svn/wc.db select * from work_queue 3|(file-install 59 DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED] 1 0 1 1) sqlite3 .svn/wc.db select * from nodes where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' 1|DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|0|DBBuild/Wordlists/Belarusian|1|Trunk/DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]|3936|normal|||file||infinity|||3323|1294867663142001|Erik.Larsson|504|1294985508149158|| So there's no checksum (according to other entries, it would be the field just after infinity). That's very odd. Do you know which version of Subversion is running on the server? Running something like curl -D - REPO_URL might help find out. I don't know what the server version is. cURL won't accept an svn: URL. I can't figure out how to get the version out of the repro browser, which is the most direct serverconnection in the toolset I know. Are there other files with no checksum? sqlite3 .svn/wc.db select count(*) from nodes where checksum is null and kind='file' The answer to that query is 1, so that's the only pattern. (Old fashioned searches through the dumped list of nodes confirms this.) If there are other files then is there any pattern in the filenames? All in the same directory? All modified in the same commit? etc. sqlite3 .svn/wc.db select local_relpath from nodes where checksum is null and kind='file' Can you describe the recent activity in the working copy? Do you normally update the whole working copy or do you update subtrees? Normally I update a large subtree (several levels up from this file). Did you commit changes in the Belarusian directory just before the update? No, I haven't committed changes from that directory in months. Nobody else has either. The NODES row shows that the update was trying to install revision 3936 of the file. The filename is BelarusianForceFreq.txt[MOVED]; has this file been moved/copied within the repository? We moved these files to another repository, so that SVN couldn't (as far as we could figure out) understand the move. So we renamed the the files on the source side to keep their history conveniently available. The last modified revision of the file is 3323, would you have committed that revision from this working copy? That is the last revision, and I didn't commit it from this computer. (It was inf Do you know the revision before the update? It's possible that you can identify it using sqlite3 .svn/wc.db select revision from nodes where revision != 3936 or perhaps sqlite3 .svn/wc.db select revision from nodes where parent_relpath='DBBuild/Wordlists/Belarusian' or perhaps you can guess the approximate revision based on dates? If you can identify the (approx?) revision before the update then running svn log -vq URL will allow you to see the sort of changes the update would have been making. I want to know what the update did to this file, did it just modify the content of the file, or add the file, or replace another file of the same name? Perhaps the whole directory was being added? Using the repo browser I can see the whole history. There are just two versions of this file, none more recent than 3323. I think 3936 is a red herring -- that was perhaps the tip revision for the whole repository when the update was attempted. (The current tip is 4013.) I hate to confess to such absent mindedness, but I may have svn deleteed this file. I see that I don't have a local copy of it, which supports that theory. If I did that, I didn't commit the change -- the repository still has the file. Thanks for your help so far! I'm happy to help, and I appreciate your time. Just to be clear, I wouldn't dream of taking so much of your time just to solve my local problem. You're digging into this to figure out the bug with change to the 1.7.1 version (or maybe svn update within the 1.7.1 version), right? Since I will likely need to do another checkout anyhow, I'm happy to try experiments which might be destructive to my local copy. -- Philip
Re: wierd issue with subversion edge
From: Mark Phippard markp...@gmail.com To: j s jbluede...@yahoo.com Cc: users@subversion.apache.org users@subversion.apache.org Sent: Tuesday, November 15, 2011 8:39 PM Subject: Re: wierd issue with subversion edge Subversion Edge is a managed server. It writes the Apache configuration for you based on fairly minimal input. Your URL should actually be something like: http://somewhere.com/svn/repos_name Subversion Edge configures the directive as Location /svn which is where the /svn and it sets the SVNParentPath to the folder that stores your repositories. You can still change the httpd.conf file to have whatever configuration you want, but you will be giving up the bulk of the features that the SVN Edge web UI brings you. If you just want to use it to deliver binaries you can certainly do this. You do not have to run the CollabNet Subversion Edge windows service if you do not need the web UI. The Apache service name is CollabNet Subversion Server. You can just manage it like any other Windows service and write the configuration yourself. Mark On Tue, Nov 15, 2011 at 8:10 PM, j s jbluede...@yahoo.com wrote: my old svn set up had apache serving the respository as http://somewhere.com/SVNREPO/Project1 i upgraded to subversion edge and now i see the http access as http://somewhere.com/svnrepo/Project1 not sure how it became lover case. I don't want to instruct all developers to perform a switch within torstoiosesvn. is there a way i can rectify this wherein the casing of the repo in the url does not change? -- Thanks Mark Phippard http://markphip.blogspot.com/ Dear Mark, On the svn server the repos are located as such F:\SVNREPO\Project1 from client machine, i can access it using IE with following url http://somewhere.com/svn/Project1 and not this http://somewhere.com/svn/project1
Re: wierd issue with subversion edge
On Tue, Nov 15, 2011 at 8:49 PM, j s jbluede...@yahoo.com wrote: On the svn server the repos are located as such F:\SVNREPO\Project1 from client machine, i can access it using IE with following url http://somewhere.com/svn/Project1 and not this http://somewhere.com/svn/project1 I am not aware of anything that would be forcing everything to lower case other than the underlying filesystem name of the directory. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)
Ethan Bradford ethan.bradf...@swype.com writes: I don't know what the server version is. cURL won't accept an svn: URL. Ah! svnserve. Then telnet server.com 3690 will get the handshake which will tell us something. Using the repo browser I can see the whole history. There are just two versions of this file, none more recent than 3323. I think 3936 is a red herring -- that was perhaps the tip revision for the whole repository when the update was attempted. (The current tip is 4013.) Yes. 3936 is the revision to which you were updating. I hate to confess to such absent mindedness, but I may have svn deleteed this file. I see that I don't have a local copy of it, which supports that theory. If I did that, I didn't commit the change -- the repository still has the file. I'll have to think about that. The nodes row was presence=normal. I wonder if the update was creating a tree conflict? Unlikely if there are no more recent changes than 3323. sqlite3 .svn/wc.db select tree_conflict_data from actual_node Thanks for your help so far! I'm happy to help, and I appreciate your time. Just to be clear, I wouldn't dream of taking so much of your time just to solve my local problem. You're digging into this to figure out the bug with change to the 1.7.1 version (or maybe svn update within the 1.7.1 version), right? Yes. Since I will likely need to do another checkout anyhow, I'm happy to try experiments which might be destructive to my local copy. We may be able to recover it. Please make a copy of the wc.db file first. The following instructions assume there is no tree conflict. First we look at the workqueue, to confirm there is just one row. sqlite3 .svn/wc.db select * from work_queue Next look at the parent dir: sqlite3 .svn/wc.db select op_depth, local_relpath, presence from nodes where local_relpath='DBBuild/Wordlists/Belarusian' to confirm there is just one row with op-depth=0 and presence=normal or presence=incomplete. If the presence is something else then stop, the instuctions below do not apply. If presence is normal then set the parent dir to presence=incomplete: sqlite3 .svn/wc.db update nodes set presence='incomplete' where local_relpath='DBBuild/Wordlists/Belarusian' Now remove the corrupt file row: sqlite3 .svn/wc.db delete from nodes where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' sqlite3 .svn/wc.db delete from actual_node where local_relpath='DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' Remove the now unversioned file (except you say it doesn't exist so skip this step). rm 'DBBuild/Wordlists/Belarusian/BelarusianForceFreq.txt[MOVED]' Remove the workqueue: sqlite3 .svn/wc.db delete from work_queue Run cleanup to remove locks: svn cleanup The working copy should be fixed; the next update will pull the missing file. -- Philip
