Re: commit failed - No such file or directory

, May 11, 2010 at 10:59 AM, Cooke, Mark wrote: > > On Mon, May 10, 2010 at 3:42 PM, Vikrama Sanjeeva > > wrote: > > > > Hi, > > > > 1: Did backup of live repository as below: > > hot-backup.py --archive-type=zip /my/svn/repo /my/svn/backup

Re: commit failed - No such file or directory

Hi All, Someone please help me to troubleshoot this issue. Thanks. Bye, Viki. On Mon, May 10, 2010 at 3:42 PM, Vikrama Sanjeeva wrote: > Hi, > > 1: Did backup of live repository as below: > hot-backup.py --archive-type=zip /my/svn/repo /my/svn/backup > > 2: Unzipped /my

commit failed - No such file or directory

Hi, 1: Did backup of live repository as below: hot-backup.py --archive-type=zip /my/svn/repo /my/svn/backup 2: Unzipped /my/svn/backup/repo-7.zip 3: checkout /my/svn/backup/repo-7 (using Tortoise) 4: On commit, am getting below error in Apache error_log ### Can't create directory

svn backup strategy

Hello, We've recently shifted to SVN. Suppose there are three repositories R1, R2 and R3. And each repostory has three projects in it. So we have: R1: P1, P2, P3 R2: P1, P2, P3 R3: P1, P2, P3 R1-P1 and R1-P2 are changed almost daily, whereas, R1-P3 is changed very rare (once a month) Change of

Re: fixing bug in multiple releases

On Wed, Apr 21, 2010 at 8:13 PM, Les Mikesell wrote: > On 4/21/2010 8:48 AM, Vikrama Sanjeeva wrote: > >> >> > >>Also, in case of web-applications what is the best practice to >>deploy REL-1.7 on production ? Do we replace whole REL-1.6 code >

Re: fixing bug in multiple releases

On Wed, Apr 21, 2010 at 5:18 PM, David Weintraub wrote: > On Wed, Apr 21, 2010 at 4:27 AM, Vikrama Sanjeeva > wrote: > > Hi, > > > > Thanks Andy and David for your answers. > > > > As I said, it was just a supposition in a case where it becomes necessar

Re: fixing bug in multiple releases

On Wed, Apr 21, 2010 at 3:42 PM, Les Mikesell wrote: > Vikrama Sanjeeva wrote: > >> >> Also, in case of web-applications what is the best practice to deploy >> REL-1.7 on production ? Do we replace whole REL-1.6 code with REL-1.7 or >> just update the production wi

Re: fixing bug in multiple releases

. Also, in case of web-applications what is the best practice to deploy REL-1.7 on production ? Do we replace whole REL-1.6 code with REL-1.7 or just update the production with modified binaries of REL1.7 ? Bye, Viki, On Mon, Apr 19, 2010 at 10:46 PM, David Weintraub wrote: > On Mon

Re: [SVN] mod_dav_svn.so and mod_authz_svn.so files

Hello, I did recently on solaris and both modules was installed by SVN installed in "/modules" directory of Apache HTTPD. I think same should happen in Windows as well. I saw below note somewhere "MUST INSTALL SVN "svn-x.x.x-setup.exe" BEFORE CONFIGURING APACHE FOR SUBVERSION(SVN) AND RESTAR

fixing bug in multiple releases

Hi, Suppose I have total 6 releases in /tag which are considered as stable releases. Now if, at 6th release we realize that there is a "bug" which should be fixed in all previous releases then what should be the strategy ? Is there any way in SVN which allows to fix bug in all releases "at-a-ti

Re: multiple projects per repository and versions

On Sat, Apr 3, 2010 at 3:51 AM, Andy Levy wrote: > On Fri, Apr 2, 2010 at 20:22, Vikrama Sanjeeva > wrote: > > Hi all, > > > > Suppose If I have project A and project B in a same repository then > project > > B's version will change every time project A has

multiple projects per repository and versions

Hi all, Suppose If I have project A and project B in a same repository then project B's version will change every time project A has something committed to it, even if no work is being done in project B ? Please confirm my understanding. Bye, Viki.