Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 29963 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
If any version prior to 4.0.1 of the mono-complete package is installed, then "yum upgrade" to mono 4.0.1 will fail, because the mono-entityframework and mono-data-postgresql packages would have their dependencies broken. The workaround for this is to manually remove these two packages before upgrading, though this forces monodevelop to be removed as well because of transitive dependencies.
I believe the rpm spec file should obsolete these two packages, so they will be removed automatically when updating:
Obsoletes: mono-entityframework < 4.0.0
Obsoletes: mono-data-postgresql < 4.0.0