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 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.
Created attachment 1330 [details]
Version Info from "About MonoDevelop"
Description of Problem:
On startup MonoDevelop announces updates are available for Mono, despite being on a newer version of Mono than the update it would install.
Steps to reproduce the problem:
1. Install Mono 2.10.8 [from DMG]
2. Install MonoDevelop 18.104.22.168 [from DMG]
3. Install Mono 22.214.171.124 [from DMG]
4. Start MonoDevelop
5. Wait for Updates Available to popup or run manual update check
Updates Available dialog shows up listing Mono 2.10.8 as an avaialble update.
No Updates listed.
How often does this happen?
On every startup, and on demand when update check is run.
Version Info included as attachment.
This is by design, the updater tries to update you to the packages of the current update channel, even if you have "newer" versions. This is so that you can switch to a more stable channel, and it will downgrade the packages appropriately. It also ensures that you have a set of packages that work together.
Michael, thanks for clarifying that for me. I thought since I had the Beta channel selected for the updated I thought it would accept the 126.96.36.199 update as the latest beta at the time. Since 2.0.9 has been released in the meantime it's a moot point anyway now.
Hm, if the active channel *was* the beta channel and it was trying to downgrade you to 2.10.8 from 188.8.131.52, then that would have been a bug. That said, there was a bug in Mono 184.108.40.206 that meant MacOS thought it was the same version as 2.10.8, so upgrades would silently become no-ops. It might have been a side effect of that. As you say, it's moot now that 2.10.9 is is the beta channel.
FYI, I have a similar problem with recently installed MonoDevelop 220.127.116.11 in a Snow Leopard in which I installed Mono 2.11: it tells me it found an update of mono 2.10 (older).
If it's by design (because of the update-channel that is selected) fair enough, but I would recommend a rewording of what is announced by the update-channel (like mentioning the name of the update-channel, and mentioning that the update is to a "stabler" version than the current one, as opposed to "newer").