Re: svn update issue
On 7/19/2016 23:26, Pavel Lyalyakin wrote: > Hello, > > On Tue, Jul 19, 2016 at 10:44 PM, ujjwala kaushik > wrote: >> Hi, >> >> I am using a I-Mac(Macintosh) and I am trying to update the svn from >> terminal. I had a old version which I uninstalled and then installed the >> latest subversion. The latest 1.9.2 is there on my system but I cannot >> update my files using that. I get the error message below: >> >> What should i do? Any help would be appreciated. >> >> en4102194:~ ujjwalak15$ svn update >> >> Skipped '.' >> >> svn: E155007: None of the targets are working copies > The error means that the current working directory where you run `svn > update` is not a Subversion working copy. Make sure to provide correct > path to the working copy you are trying to update. > > BTW, make sure to `svn upgrade`[*] your working copies after upgrading > SVN client to 1.9 from 1.8 or older version. It's not related to the > error you've specified, though. > > [*]: http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.upgrade.html Pavel, svn upgrade is not required if you upgrade from 1.8 to 1.9 (only if u upgrade from <= 1.7 to >= 1.8) as far as I know, or am I wrong (aka: the WC format stayed the same between 1.8 and 1.9 [1])? [1] https://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade Regards, Stefan smime.p7s Description: S/MIME Cryptographic Signature
HTTP 403: Forbidden after upgrading to SVN Edge 5.1.3
Hi There My SVN Edge 5.0.1 setup was 100% operational, but I decided to upgrade to version 5.1.3 After the upgrade, luckily the SVN server is still working fine (I can update, commit etc), but I can’t connect to SVN Edge to manage my repositories, users. All I get is a page with *HTTP ERROR 403* Problem accessing /csvn/. Reason: Forbidden *Powered by Jetty://* I’ve tried to upgrade to JRE 8, running the CollabNet Subversion Edge service as a named administrator account, change the permissions on my csvn folder, repairing the install. But none of these helped. Any other ideas please? Thanks Niel
Re: svn update issue
Stefan, On Wed, Jul 20, 2016 at 11:47 AM, Stefan wrote: > On 7/19/2016 23:26, Pavel Lyalyakin wrote: >> Hello, >> >> On Tue, Jul 19, 2016 at 10:44 PM, ujjwala kaushik >> wrote: >>> Hi, >>> >>> I am using a I-Mac(Macintosh) and I am trying to update the svn from >>> terminal. I had a old version which I uninstalled and then installed the >>> latest subversion. The latest 1.9.2 is there on my system but I cannot >>> update my files using that. I get the error message below: >>> >>> What should i do? Any help would be appreciated. >>> >>> en4102194:~ ujjwalak15$ svn update >>> >>> Skipped '.' >>> >>> svn: E155007: None of the targets are working copies >> The error means that the current working directory where you run `svn >> update` is not a Subversion working copy. Make sure to provide correct >> path to the working copy you are trying to update. >> >> BTW, make sure to `svn upgrade`[*] your working copies after upgrading >> SVN client to 1.9 from 1.8 or older version. It's not related to the >> error you've specified, though. >> >> [*]: http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.upgrade.html > Pavel, svn upgrade is not required if you upgrade from 1.8 to 1.9 (only > if u upgrade from <= 1.7 to >= 1.8) as far as I know, or am I wrong > (aka: the WC format stayed the same between 1.8 and 1.9 [1])? > > [1] https://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade Yep, you are right. I should've said that `svn upgrade` is required when upgrading the SVN client to 1.9 from 1.7 or older. When upgrading from 1.8 to 1.9 `svn upgrade` is not needed. -- With best regards, Pavel Lyalyakin VisualSVN Team
Re: HTTP 403: Forbidden after upgrading to SVN Edge 5.1.3
Hi I've now uninstalled SVN Edge and reinstalled it. Error now changed to HTTP ERROR: 503 Problem accessing /csvn/. Reason: Service Unavailable Powered by Jetty://
Re: HTTP 403: Forbidden after upgrading to SVN Edge 5.1.3
Hello, On Wed, Jul 20, 2016 at 11:42 AM, Niel de Clerk wrote: > > Hi There > > My SVN Edge 5.0.1 setup was 100% operational, but I decided to upgrade to version 5.1.3 > > After the upgrade, luckily the SVN server is still working fine (I can update, commit etc), but I can’t connect to SVN Edge to manage my repositories, users. This is a mailing list for Apache Subversion users. Since the problem is about SVN Edge's console and not SVN in general, I guess that you may want to ask on another forum: https://subversion.open.collab.net/ds/viewForumSummary.do?dsForumId=3 > All I get is a page with > > HTTP ERROR 403 > > Problem accessing /csvn/. Reason: > > Forbidden > > Powered by Jetty:// > > I’ve tried to upgrade to JRE 8, running the CollabNet Subversion Edge service as a named administrator account, change the permissions on my csvn folder, repairing the install. But none of these helped. > > Any other ideas please? The error 403 means that you don't have permissions to access /csvn/, error 503 means that there is a generic problem with the services. Checking the logs should give you more clues on what's going on. In any case, there is a similar thread on Edge's forum that may be relevant to the problem you are reporting: https://subversion.open.collab.net/ds/viewMessage.do?dsForumId=3&dsMessageId=565423 -- With best regards, Pavel Lyalyakin VisualSVN Team
Re: Intermittent 'apr_exit_why_e was 2' Precommit Block
> First of all Apache 2.2.24 as well as SVN 1.7.14/1.6.2 are rather > ancient and SVN 1.6/1.7 is also no longer actively supported. No surprise there. I know they're old, but that's what got installed years ago. I'm probably the first to change anything in close to half a decade (if our documentation is even reliable). I've already verified we have some repositories that still use Berkely-DB backend, but those ones are collecting dust thankfully. > If at all possible, I'd highly recommend you upgrade at least Apache to > the latest 2.2 version (at the time of writing this is 2.2.31). The same > goes for SVN. At least make sure to have SVN 1.7.20 or 1.7.21 on the > Slight correction here: I mean SVN 1.7.21 or 1.7.22. > server and no mixture of two different versions. Depending on how builds > were made, you have a hard time determining which SVN version is used > (refering here to the fact that Windows prefers using already loaded > DLLs over loading them separately, if manifest information of the > calling process are missing or not specific enough). > > If the issue persists after the upgrade you at least have a stable basis > to start troubleshooting from. I look into updating the binaries first, since that should be much simpler. I'll try and see if we can update Apache, but due to my company's red tape, I know that'll be a couple of months away. Thanks for the suggestions Stefen. -Tim Tim
