-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Unable to install Mono package on DSM 7.0 #4322
Comments
DSM7 support for all packages is still under development. See #4215. Contributions to the dsm7 branch are welcome. |
Thanks for working on this support. I hope you may find a solution soon. |
I built mono from dsm7 branch, it installed successfully. Any ideas why this one is still open? :) Are there issues with using it? |
You "built" Mono. This issue report is about using the Mono package from Synocommunity using the Package Center. Totally different thing. EDIT: If I re-read your post I get a different meaning. So not sure what you meant. Did you mean to say that you manually installed Mono and therefore you deduce that there should be no trouble creating a new package for the Package Center? |
Ahh, I see. Sorry for the confusion.
…On Fri, 15 Jan 2021 at 12:38, gus70 ***@***.***> wrote:
I built mono from dsm7 branch, it installed successfully. Any ideas why
this one is still open? :) Are there issues with using it?
You "built" Mono. This issue report is about using the Mono package from
Synocommunity using the Package Center. Totally different thing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4322 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGERNR2IXCZHWKGG5CPXGLS2ASKRANCNFSM4VDLVEQA>
.
|
I tend to close all such issues for packages not compatible with DSM7. I think the base problem is that the packages are shown in the package center in DSM, dispite the fact that the provided os_min_ver is < 7.0. This pretends that packages are available. @ymartin59 shall we ask synology what we need to change, for that DSM7 does not show incompatible packages? |
We just need to set the os_max_ver in the info file. I don't remember if that variable is exposed on the server though. |
I would like to see a least by the time DSM 7.0 becomes officially released that the Mono package gains compatibility. Sure there are other solutions to get Mono running but they are a bit less than practical for less technical users. You can compile from source or you can leverage a Mono install via a Docker container. I would prefer though to be able to continue to have the ease of a Package Center installation for Mono. I support a number of applications and I'd like to keep things as simple as possible for my users. I just hope that this is not forgotten. I greatly appreciate the work done by this Synology Community. |
That might end-up being an interesting idea to set |
I mean than when I take DSM7 branch of this repo and yes, build a arch-x64-7.0 package, I can manually install it using package center, so no reason to not to make it available? |
@favoretti Please just wait until #4395 is merged. We are getting closer. The main reason is that packages need to be tested, there have been significant changes to DSM7 some documentation needs updating. @gus70 Everyone works a bit different in open source but here is what I think: Please help out rather than ask for package releases for a beta DSM or ETA for DSM7 support. Generally I just ignore such requests. You can compile, install & report bugs for instance or help update the wiki. @hgy59 is public editing on? |
Oh just noticed, what I said above is also addressed by @hgy59 in the README too: https://github.com/SynoCommunity/spksrc#dsm-7 |
@publicarray don't get me wrong, I'm not in a rush and I can perfectly build stuff that I miss, I appreciate all the work you folks are doing here. My question was merely a statement that it "works on my machine", albeit maybe worded a bit incorrectly. If you need any help with getting DSM7 out there - I'll be happy to help. So far everything that I've tried to build in dsm7 branch just works, aside of Deluge, where boost is barfing on me. Trying to find a solution, but unsuccessful so far. |
I'm sorry that my follow-up post wording clearly says that I was requesting that packages get released for beta operating systems. That is not my intention. But my original request was not of that nature. My original request still stands and I see it as a bug report, the package is available because it shows up and and I can install it and then I get the error message about root privilege. Do with that what you will. My work here is done fellas. Thank you all for your time. I'm not personally benefiting from free work. I also offer free support for some software that requires Mono for a community of weather station software users is all. |
As an update to this, they released a release candidate today (https://www.synology.com/en-us/releaseNote/DSM#ver_41882) and have a help guide on what the package situation is:
Therefore, I think it is now required to reevaluate what packages require root access and which do not, as they are pushing in this direction hard and, as of now, almost no packages are on track to be available on the upcoming release. |
You find detailed information in #4524 about packages that require root permissions. You find detail in the linked issue. We could even make mono package for DSM7, but IMHO mono is not state of the art anymore and we should publish only packages that are migrated to .net for DSM7. |
FYI I've got mono version 6.12 running for my NAS (braswell) on DSM 7.0 |
@DigitalBox98 can you share your patch for mono, i'm on armadaxp and x64 |
@superpippo82xxx, a PR has been proposed. You can test it if needed. |
hi there, i am new to all this and just updated to DSM 7 and mono is not working, thus sonar, radarr, jacket, transmission. can you help in how to fix that? |
Unable to install Mono package running DSM 7.0.
The error received is that the Mono package only runs as root. The recommendation from Synology is to contact the package developer and tell them to change the privilege settings on the package.
See error screenshot attached:
The text was updated successfully, but these errors were encountered: