Bug 7439 - Attempting to publish solution to existing version control repo should give descriptive error
Summary: Attempting to publish solution to existing version control repo should give d...
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 3.0.x
Hardware: All All
: --- enhancement
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2012-09-25 05:49 UTC by Saurabh
Modified: 2012-11-06 10:07 UTC (History)
5 users (show)

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

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 INVALID

Description Saurabh 2012-09-25 05:49:56 UTC
Steps to reproduce this issue:
1. Open MonoDevelop.
2. Create or open any project.
3. Right click over Solution/Project.
4. Select Version Control->Publish.
5. Verify 'Select Repository' pop up window appears.
6. Enter correct details and URL like: https://github.com/atin360/AtinRepro.git
7. Click OK.
8. Click 'Publish'.

Actual result: After publishing project using MonoDevelop, error appears "Version control operation failed: . Access to the path 'pack-9e4f6b5423118f007996fa8acaeab6a41a868e27.idx' is denied."

Expected result:
Project/solution should be published using MonoDevelop.

Supplement information:
https://gist.github.com/3780887

Environment details:
All Mac and windows
MD 4.0 20c0d15443a7f71cf8c290f1038e119001efedb4
MFA 4.2.6 Stable
MT 6.0.0 Stable
MonoFramework-MDK-2.10.10 9e961425a3534530e404326cd81a82a789539e38
Git repository: https://github.com/atin360/AtinRepro.git

Regression Status: This is also happening with MD 3.0.4.7 Stable and MFA 4.2.6 Stable and MT 6.0.0 Stable.
Comment 1 Alan McGovern 2012-11-05 12:05:32 UTC
You cannot publish to that repository because it is not empty. You'll need to create a new empty repository to publish source code to it.
Comment 2 PJ 2012-11-05 12:18:04 UTC
Perhaps we could detect this case and say something like 'It looks like you're trying to publish to an existing repository - would you like to push your changes instead?'


That error is not very descriptive. I'll mark it as an enhancement.
Comment 3 Alan McGovern 2012-11-05 13:21:06 UTC
If there is a repro for the exact error message listed above, that'd be great. When I followed the instructions I got the standard error of "MonoDevelop cannot push to this repository because it is not empty." or something along those lines. We've given that message for months. The error above is something different, and potentially platform specific.

Saurabh, are you 100% sure the error message was identical on both Windows and Mac?
Comment 4 PJ 2012-11-05 15:12:31 UTC
Yeah I can't repro - I see the correct message. Perhaps it has to do with the exact details entered. Saurabh please screencast the issue if you can reproduce it on current stables or masters - it's not the basic case listed in those steps.
Comment 5 narayanp 2012-11-06 06:09:51 UTC
Today, we have verified this issue with following build:

Mono Framework-MDK 2.10.10- a0f2930ea5c6042ff896c137fa138bba8ebbdb9c
MD 4.0 - 79ea8016b872accc3628e15a7294e1c54ab3a8dc
MFA 4.5.21.23664171 - 169162bacf931a47857a917958fb2aa77842cf12
MT 6.1.0 - bef1956a9c282489b8af39dcca3f9aca8147e8a5

The same issue still exist with this build.

After clicking 'Publish' button an error  "Version control operation failed: . The remote repository already contains branches. MonoDevelop can only publish to an empty repository" appears. 

Supplement info:
https://gist.github.com/4024053
Comment 6 narayanp 2012-11-06 07:37:23 UTC
I have also verified this issue on following Stable build:

MonoFramework-MDK-2.10.9_11.macos10.xamarin.x86
MonoDevelop-3.0.4.7 Stable
mono-android-4.2.6.103999197  Stable
monotouch-6.0.4 Stable

The same issue still exist with stable build.

Screencast:
http://screencast.com/t/F2w0EfGLwC
Comment 7 Alan McGovern 2012-11-06 07:53:53 UTC
This is expected behaviour as per comment  1. You cannot publish to a repository which already contains code. You must publish to an empty repository, as described in the error message.
Comment 8 PJ 2012-11-06 10:07:47 UTC
Yeah guys - the only real bug would have been if the error message reported in the original description :

After publishing project using MonoDevelop, error appears
"Version control operation failed: . Access to the path
'pack-9e4f6b5423118f007996fa8acaeab6a41a868e27.idx' is denied."


The descriptive error you are seeing now is fine.