Bug 13818 - 4.1.9: Error: No subversion operation is in progress
Summary: 4.1.9: Error: No subversion operation is in progress
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 4.1.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2013-08-07 10:43 UTC by Neal
Modified: 2013-08-07 11:13 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
svn error (59.60 KB, image/png)
2013-08-07 10:43 UTC, Neal
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Neal 2013-08-07 10:43:01 UTC
Created attachment 4564 [details]
svn error

I just installed 4.1.9 as I desperately need SVN fixes, sadly, I re-registered my repo as it was gone, I now get an error when expanding my svn node in the checkout dialog.  See attached!
Comment 1 Marius Ungureanu 2013-08-07 11:02:37 UTC
This has just been just been fixed in tip of master.

Will be hotfixed in the current releases.
Comment 2 Alan McGovern 2013-08-07 11:13:17 UTC
Hi,

We do not issue hotfixes for alpha releases as they are generally unstable and have very little/no QA. I'd recommend either downgrading to the previous alpha, 4.1.8, or using a stable release for now.

Thanks for reporting the issue though and we will try to get a fix shipped as soon as possible.