Bug 12791 - Cannot install Addins (4.0.9)
Summary: Cannot install Addins (4.0.9)
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: master
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-06-20 11:47 UTC by Benj
Modified: 2013-11-24 13:06 UTC (History)
2 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 NOT_REPRODUCIBLE

Description Benj 2013-06-20 11:47:25 UTC
Whenever I try to install an Addin, I get the following errors:
The selected add-ins can't be installed because there are dependency conflicts.
The package '::MonoDevelop.Ide v4.0' could not be found in any repository
The package '::MonoDevelop.Core v4.0' could not be found in any repository

I installed MonoDevelop 4.0.9 from Git. I'm using Mono 3.0.12, also from Git.
Comment 1 Benj 2013-06-20 11:56:04 UTC
I just tested a clean install of MonoDevelop 4.0.8 from Git. This bug does not exist.
Comment 2 Marius Ungureanu 2013-11-24 13:06:32 UTC
Packaging and versioning has been changed. I don't think this bug is an issue any longer.