Re: Recursively correct moved External repository paths (that no longer exist) in the current SVN Repository
Hello, I am observing another issue: git.exe clone --progress --branch 806 -v " https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx/Libraries/nnn_Developed/AsyncCommunications_Library"; "E:\xxx\SVN-newrepo-SW-PR-xxx\AsyncCommunications_Library" Cloning into 'E:\xxx\SVN-newrepo-SW-PR-xxx\AsyncCommunications_Library'... fatal: unable to access ' https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx/Libraries/nnn_Developed/AsyncCommunications_Library/': SSL certificate problem: *self signed certificate* How to fix above issue? Thanks, Rajeev On Tue, Oct 19, 2021 at 7:42 PM Raeev Arora wrote: > Hello, > > Please help me with: > *Recursively *correcting moved External repository paths (that no longer > exist) in the current SVN Repository > > I am looking out for a way to update external projects links used within a > current SVN project, so that no errors are thrown while downloading the > repository. > > Example of current reported error is: > Unable to connect to a repository at URL > ' > https://kkkvisualsvn.kkkus.local/svn/CmpDpt/Libraries/Vender_Libraries/STM_StdPeriph_Driver > ' > > The old SVN path (for the external repositories), which cannot be accessed > (because it does not exist), looks similar to > https://kkkvisualsvn.kkkus.local/svn/aaa/xxx > > Above link need to be changed to, where the external project copy exists > on the moved / Current SVN: > https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx > > Please suggest a SVN command and method to execute it, which shall help me > archive what I am looking for. I want the change to be permanent and > available on the SVN server as well. > > Thanks, > Rajeev >
Re: Recursively correct moved External repository paths (that no longer exist) in the current SVN Repository
Hello, Please help me with recursively updating external project path in the SVN repository. Please *ignore *email that informed an error thrown when git.exe was invoked. I am unable to fetch an old version / revision (806) from a branch that had been recently deleted. There are two old external links that point to two deleted repositories. Please help with resolving the issue. Thanks, Rajeev +91-9620231177 On Tue, Oct 19, 2021 at 8:45 PM Raeev Arora wrote: > Hello, > > I am observing another issue: > > git.exe clone --progress --branch 806 -v " > https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx/Libraries/nnn_Developed/AsyncCommunications_Library"; > "E:\xxx\SVN-newrepo-SW-PR-xxx\AsyncCommunications_Library" > Cloning into 'E:\xxx\SVN-newrepo-SW-PR-xxx\AsyncCommunications_Library'... > fatal: unable to access ' > https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx/Libraries/nnn_Developed/AsyncCommunications_Library/': > SSL certificate problem: *self signed certificate* > > How to fix above issue? > > Thanks, > Rajeev > > On Tue, Oct 19, 2021 at 7:42 PM Raeev Arora > wrote: > >> Hello, >> >> Please help me with: >> *Recursively *correcting moved External repository paths (that no longer >> exist) in the current SVN Repository >> >> I am looking out for a way to update external projects links used within >> a current SVN project, so that no errors are thrown while downloading the >> repository. >> >> Example of current reported error is: >> Unable to connect to a repository at URL >> ' >> https://kkkvisualsvn.kkkus.local/svn/CmpDpt/Libraries/Vender_Libraries/STM_StdPeriph_Driver >> ' >> >> The old SVN path (for the external repositories), which cannot be >> accessed (because it does not exist), looks similar to >> https://kkkvisualsvn.kkkus.local/svn/aaa/xxx >> >> Above link need to be changed to, where the external project copy exists >> on the moved / Current SVN: >> https://tue-p-yyy.newrepo.sw.pr/svn/aaa/xxx >> >> Please suggest a SVN command and method to execute it, which shall help >> me archive what I am looking for. I want the change to be permanent and >> available on the SVN server as well. >> >> Thanks, >> Rajeev >> >
Re: Recursively correct moved External repository paths (that no longer exist) in the current SVN Repository
please do not change ther topic mid thread (without even changing the subject) Raeev Arora wrote: >[...] >I am unable to fetch an old version / revision (806) from a branch that had >been recently deleted. There are two old external links that point to two >deleted repositories. the description is unclear. What does not work exactly? 1) Fetching an old revision from a deleted branch? 2) Fetching the externals from the deleted repositiories? Please state the exact error message, the OS, the svn-client and version you are using. Assuming 1) to check out from a deleted branch, you need to use a "peg" revision. svn co URL@806 to point the client to a revision where the branch still exist -- Lorenz
