-
-
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
DSM 7 - Packages reporting error due to high privileges #4170
Comments
WarningCurrently none of the community packages can be installed - neither through package center nor manually. Packages already installed before installation of DSM 7 prerelease stay installed. |
Can we help? Does Synology about this issue? |
Just found the DSM 7 Preview forum on synology and posted about missing an updated development guide. Findings so far:
Without the knowledge whether third party apps will need the new spk format - or this new format is for official packages only and the traditional format is only temporary disabled in the preview version - it is not possible to solve this. |
As you can see in the DSM 7 community forum (for previewers only) there is no public information available yet. Conclusion: At the moment there is no way to use 3rd party packages with DSM 7 preview. |
While I have not installed DSM 7.0 yet, I assume |
You must not install DSM 7 preview when you want to use 3rd party packages. |
Thanks @hgy59 I'm aware, I've even posed an |
@publicarray as you have access to the DSM 7 preview forum you can see the answer for my question about updated developer documentation here: |
Any update on this? Does anybody had contact with Synology? |
My position is clear - users choosing Synology devices often consider SynoCommunity packages as part of "the offer" (even if it is not commercial - as an example, we heards here about guys returning properly working device to choose another one where packages of interest are already available) and I find Synology does not play fair with us, asking guaranties with NDA but provides no help nor even at least documentation for us to port (any) packages to DMS 7 "earlier" (because we would find a way "one day"). They seem only interested in porting current package list from their marketplace they consider a priority to get available on DSM 7. |
And personally, I have a single Synology device I will not upgrade to DSM 7 until packages I run there have been ported and tested at least on an xpenology VM. Docker may be an option to avoid such dependency but its support is limited to most expensive devices not targeting individuals like most of SynoCommunity users. |
From @baya44 at SynoCommunity/spkrepo#55 |
Good news, the DSM 7 Preview Toolchains are published at sf.net: |
This is great news... no kernel branch yet with build id but if your ok with this I volunteer myself to do the initial work to include this into the framework like I did with the previous, post PR #4200. |
@th0ma7 DSM 7 will need a lot of investigation and I propose to use a development branch for this and not touch the master until we reach a (more or less) stable stage. The same approach was used when DSM 6 was introduced. I have the DSM 7 Preview Version installed on a DS218+ and my first experience was frustrating (I built the example package but it failed to install). |
Just wondering wether synology will create Diskstations with AMD Ryzen™ Embedded V1000 processors (as there is a toolchain called Intel x86 Linux 4.4.59 (V1000)) |
Interesting finding... :) |
The new Archs purley, geminilake and v1000 where added to the github repo of Synology DSM6.0 package toolkit framework just three days ago. |
The secret is revealed: it's the new DS1621+ (without 'xs')
|
What's the status of this issue? I see there is some information right now: https://community.synology.com/enu/forum/19/post/137228 |
Current DMS7 support is: Work in progress. Although this particular issue (Packages reporting error due to high privileges) is mostly solved in my DSM7 branch. It needs testing and some scripts need a rewrite. I still expect to see more subtle permission problems depending on the package. |
@publicarray I've been trying to get some packages to be installed but I am still hitting the high privileges error. What do you mean by "it's been mostly solved on your DSM7 branch"? Have you managed to install a package successfully without seeing that error on install? Can you share the privilege file and/or other files? I've actually cloned your dsm7 branch to work with but it doesn't really matter how I modify the privileges file, I still get the same error. EDIT: Spoke too early, after checking the synopkg log I was able to see exactly what I was doing wrong. Package has been installed but it's not working but it's progress! |
Hi there, Good to see more people trying out DSM7 👍 "Mostly Solved" means that one instance of the specific privilege problem is solved. Package can now be installed without the error message but since a few packages and scripts assume they have root access now fail silently. This is like the symptoms you have described. Some packages may work and while some start up scripts need to be adjusted. I've tried to fix another instance in the generic service startup script but I've only tested 3 working packages. (I've only compiled 3 due to lack of time) Hope this clears that up. As @tmm1 alluded to, the developer documentation is the best place to learn more about the changes to DSM7 and develop your own package. |
Thansk, @tmm1 and @publicarray . |
This particular issue is solved on the DSM7 branch. Some packages still have custom scripts that fail. Please see issue #4215 for further discussion. |
Taking info from several sources, it seems like the AMD Ryzen V1500B is a X86_64 processor. - SynoCommunity/spksrc#4170 - eizedev/AirConnect-Synology@80f7c87
Taking info from several sources, it seems like the AMD Ryzen V1500B is a X86_64 processor. - SynoCommunity/spksrc#4170 - eizedev/AirConnect-Synology@80f7c87
As the DSM 7 preview release is out, there are several synocommunity packages that fail installation with error due to high privileges.
Unfortunatly the development guide page about Lower Privilege does not solve this issue. The developer guide is outdated (last update was 2016/01/14).
Until an official solution is available, let's collect the affected packages here (instead of creating an issue for each).As there is no Information available on how to build spk packages compatible with DSM 7, there is no way to build 3rd party packages and the list of incompatible packages is obsolete for now.
Packages reporting error due to high privilegesRemarks
Third party packages are currently not supported by DSM 7 Preview.
See installation notes:
The text was updated successfully, but these errors were encountered: