Update Mono

[itdaboyz]

Hi,

Can you please update mono ?
We have the 4.2.2 and the last one is 4.6.1.5.
Latest Emby version require 4.4.2 at least.

You should provide a way for us to update those kind of packages without you, it's not the only one package outdated. Something like "apt-get"?

Thanks!

[mafredri]

Saw your post and decided to bump my package (mono-latest):

https://github.com/mafredri/asustor-mon ... t/releases

Installs a mono version (side-by-side with ASUSTOR version). The binary is called mono-latest (instead of mono) to not conflict with the ASUSTOR package.

If you wish to use it you can either update symlinks to point to mono-latest or change which mono-command Emby uses.


Cheers,
Mathias

[itdaboyz]

Thanks for this!
Is there a way to remove the Asustor package and use yours instead but to keep the binary named "mono"?

[mafredri]

It's possible, but I'd have to make a custom package for you. I'm do not want to make this the default since I don't want it conflicting with the ASUSTOR package.

Which platform do you use, arm, i386 or x86_64?

[itdaboyz]

That's really kind of you, but I hope it's not too much work for you.
I'm on i686 ? I have as AS302T.

I wonder if the best solution wouldn't be to check if Austor Mono is already installed and to ask to remove it. Or another way is if Asustor Mono is installed then it use mono-latest, else it can use mono. So you have only one package to maintain.

Thanks for your great job!

[mafredri]

That's really kind of you, but I hope it's not too much work for you.
I'm on i686 ? I have as AS302T.

I wonder if the best solution wouldn't be to check if Austor Mono is already installed and to ask to remove it. Or another way is if Asustor Mono is installed then it use mono-latest, else it can use mono. So you have only one package to maintain.

Thanks for your great job!

It's a bit more complicated than that. First off, there can only be one app named X installed at a time. Secondly, other applications (Y) can depend on X being installed, any attempt to remove X will result in Y being removed. So the only way to "remove" X is to make another package named X and install over it. This is why I've named my mono "mono-latest".

With these limitations in mind it's impossible to create "mono-latest" that allows removal of "mono".

For now, I've made a version of mono latest that has a start-up script:

https://app.box.com/s/xlj8ixvjq48z5r67lodjh9v9omg9xngx

To use mono-latest as default mono:

Edit: /usr/local/AppCentral/mono-latest/CONTROL/start-stop.sh
Change: REPLACE_MONO=0 to REPLACE_MONO=1
Restart mono-latest

I was thinking of making a mono that can entirely replace the ASUSTOR mono, but for now the application expects to be installed in: /usr/local/AppCentral/mono-latest and this is not easily changeable. Renaming the app to mono would install into /usr/local/AppCentral/mono


Regards,
Mathias

[itdaboyz]

Nice one! This is working really well!
Only downside, is the mono package by Asustor is still required in App Central : if I want to delete mono by Asustor, an error says that it will also delete Emby, Jackett, etc... But it's ok, I'll keep it

Thanks for the complete explanation. The way you handle the situation seems to be the best possible here.
If only Asustor maintained their package or kept "apt-get" in their OS.

[Shawn.S@AST]

Hi itdaboyz and Mathias,

Thanks for assistance! I have already reported to our development department some time back and the update is under way now. Hope we can finish the testing and update it in App Central soon!

[damien599901]

hi Mathias
thanks for your work

If you wish to use it you can either update symlinks to point to mono-latest or change which mono-command Emby uses.

how to proceed?