-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonarr and Radarr Default to Outdated Mono-5.10 #238
Comments
Both Sonarr and Radarr work with mono6.8. |
I take that back it seems to break searching and syncing, had to rollback to mono510. Will try mono520 tomorrow. |
@jasker5183 there was another issue about upgrading to mono 6.X here: #165. I still haven't really heard anything new when it comes to the 6.X mono packages for FreeBSD. |
Upgraded Radarr's version of Mono to 5.20 and an update became available (3.2.2.5080) even though the package is version 3.0.2.4552. Radarr is running fine and the sync and search function is working. But now it's telling me "Please upgrade to the .NET Core version of Radarr, Mono versions will not be supported in the next release". Sonarr's Mono 5.20 update went off without a hitch and the sync and search functions seem to be working. |
This issue might technically be closed as a new container might install it with Mono version 6.8.0.123 in which case you might run into: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258709. Downgrading to Mono 6.8.0.105 might not work as well in which case you have to go back to mono520. Going to have to test this when I have some time. |
The problem was mono6.8-6.8.0.123 if you use 6.8.0.105 everything works fine, there is a copy inside the Jackett jail at |
Been trying to follow https://www.truenas.com/community/threads/how-to-manually-upgrade-mono-from-5-10-to-5-20-in-a-freenas-jail.78871/page-8#post-623120 but wanted to test with another jail first but am having networking issues running different Radarr on different port (separate problem). I guess I could try snapshot and rollback if it fails, I'll try 6.8 first.
The text was updated successfully, but these errors were encountered: