mono 4.2.1.102 appears incompatible with CumulusMX 3032

[PapaOz]

I run CumulusMX 3032 on Linux Mint 17.

My station is Ambient 2080 (which is a fine offset station).

I had been running successfully since November 11th. Tuesday night the system offered, and I installed, mono update 4.2.1.102. After the update CumulusMX was unable to find my weather station. I reverted mono to 4.0.1 and the station/software are working together again.

I am posting here in hopes of warning other users away from updating mono until this incompatibility is resolved.

[jank]

I am on debian 8, (raspbian) but still on mono 4.0.5. but i just checked and a Mono Update is being offered to be installed. But before i Check this Version, I will make a dd backup of my sd card. Let s See what Happens tomorrow.

[jank]

Hello
today I updated my Raspberry PI, woth Raspbian OS (Debian 8 Jessie) with the most current mono

mono -V: Mono JIT compiler version 4.0.5 (Stable 4.0.5.1/1d8d582 Thu Nov 12 12:22:41 UTC 2015)

and I am not having any problems.
But my Mono version is still showing 4.0.5.1

Are you really sure, that you have installed mono 4.2.1.102 ? I think you mixed it up with some libs with this kind of version number shipped along with mono

grep 4.2.1.102 /var/log/dpkg.log

Code: Select all

2015-11-20 12:37:44 upgrade libmonosgen-2.0-1:armhf 4.0.5.1-0xamarin1 4.2.1.102-0xamarin1
2015-11-20 12:37:46 status unpacked libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1
2015-11-20 12:37:46 status unpacked libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1
2015-11-20 12:38:10 configure libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1 <keine>
2015-11-20 12:38:10 status unpacked libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1
2015-11-20 12:38:10 status half-configured libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1
2015-11-20 12:38:11 status installed libmonosgen-2.0-1:armhf 4.2.1.102-0xamarin1

However, I just updated and my station is still recognized on the USB Port.
No Problems with Mono 4.0.5.1
Jan

[PapaOz]

It's a little hard to know exactly what combination of mono programs I had at the time of the failure, now that I have uninstalled and reinstalled mono.

When I first installed mono I searched for it on the web and found directions which included adding the developer's repository to my sources. I fetched and installed using that, but the install didn't go well. I uninstalled, got smarter, found 4.0 in the Ubuntu repository, installed that and was running well.

I did not remove the developer's repo from my source list. I believe what happened next was that the developer's repo offered an upgrade to 4.1, which I installed. Checking the site today I discover that 4.1 is in beta. As my dad used to say, "Why doesn't somebody tell me these things?"

I would assume that if one sticks to the Ubuntu or other distro repo they will get only stable versions. That may explain why jank did not encounter 4.1.

[steve]

Do the instructions in this thread - https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=13587 - now cause the incompatible version of Mono to be installed?

If so, what instructions do we now need instead to get a later version than 3.2.8 installed for decimal comma users?

[jank]

Hallo Steve
I just updated my Pi2 with Debian 8, 3 days ago with the most current , avalable mono version
Mono JIT compiler version 4.0.5 (Stable 4.0.5.1/1d8d582 Thu Nov 12

i am still updating mono from this Source
deb http://download.mono-project.com/repo/debian wheezy main

So I have no Problems with an Alpha Version of Mono, but today I Can See a deferred version of Mono, when trying to Update

libwebkit2gtk-4.0-37 libwebkitgtk-3.0-0 mono-4.0-gac mono-4.0-service mono-complete mono-csharp-shell
mono-devel mono-gac mono-jay mono-mcs mono-runtime mono-runtime-common mono-runtime-sgen mono-utils
mono-xbuild monodoc-base monodoc-manual nuscratch raspberrypi-ui-mods sonic-pi
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 158 nicht aktualisiert.

It's in german but I am sure you Know what it mean.
I assume he was on the alphafeed of mono
Is this helpful?

[steve]

I don't understand why people are apparently getting 4.2.1.102 now.

[jank]

Good question,but
My Pi was on debian wheezy (Originally)and i updated it to Jessie, by modifying one Source by changing the Word wheezy to Jessie. When you Look at my Feed for Mono, it seem to be still the Feed you mentioned in your Post for people with comma problems. I guess that all debian 8 installations are getting Mono from an Offizial Feed which mighty bei updating directly this new version?

[jank]

so finally, here is what I get

Currently I am on Debian 8 (Jessie) and my last mono verison is:
uname -a: Linux cumulus 4.1.7-v7+ #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015 armv7l GNU/Linux
mono -v: Mono JIT compiler version 4.0.5 (Stable 4.0.5.1/1d8d582 Thu Nov 12 12:22:41 UTC 2015)
when trying to update Mono with apt-get upgrade I am getting

0 upgraded, 0 newly installed, 0 to remove and 151 not upgraded.
these 151 Packages are all Mono related and I assume it is: mono 4.2.1.102

when I am doing a dist-upgrade to the most current Debian Version Firmware I am getting:

151 updated, 2 newly installed, 0 to remove and 0 not upgraded.
so I assume, after the Dist Upgrade to
Linux raspberrypi 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l GNU/Linux
I would get this new Mono mono 4.2.1.102 Version.

but I will test it, after I made a DD Backup of my SD Card and will report here.