The package discussed in this thread is entirely unrelated to SynoCommunity builds.
@acolomb Can you tell us anything about why there are that differences between the packages?
Again I outline this negativ concept of SynoCommunity package which make internal updates possible and is a very important positiv concept of Kastelo package, that each installation and update package is a closed one. Internal updates are not possible.
This thread is still not about the SynoCommunity package. But regarding your comments about internal updates: Please bear in mind that in contrast to Kastelo, SynoCommunity is a community project offered by volunteers.
Yes, the different packaging approach has its downsides, witnessed by several reported issues in the past. But until someone steps up to work around that, or the publishing process for spksrc gets fully automated (with all associated infrastructure costs), having Syncthing internal updates is much better than none at all. I personally am not sure which approach to prefer, but certainly having to log into each Synology box’s DSM regularly to install package updates would be a much worse situation. The internal updater works perfectly fine as long as the package is left untouched.
Since around v1.5.1, Syncthing’s update routine is much more robust because it still has a chance to run even after finding a database schema “from the future”. So hopefully with v1.7.1 now published at least the symptoms should become mure more rare.
2 Likes
Is also a Syncthing v1.8.0 package for Synology available?
Yes, at the same time as the other release packages, automatically. However it seems the package server can get confused when there are too many versions lying around or something like that, I made it clean away older versions now.
Is now clarified for Geminilake? A further platform would be “rtd1296”.
What is the status of the syncthing package for rtd1296? It looks like I can install the Synology provided package (version 1.3.4.1) but I cannot receive updates via https://synology.kastelo.net/ on this device (DS218play).
Love the software, thanks for providing these packages.
If is a package from Saphire you could install and update internally. But that is no good solution. Better would be the closed Kastello package.
rtd1296 is a supported platform.
geminilake is not, because the latest version of Synology’s package scripts don’t acknowledge its existence and hence packages are not tagged as compatible.
Those were last updated in 2018. I encourage interested parties to discuss this with Synology support.
I sought a response from Synology regarding Geminilake. I find this a bit strange. The answer is:
Dear customer, Thank you for choosing Synology Customer Service. See the list below to find the type of processor that is used for each model.
DS920 + Intel Celeron J4125 Quad Core 4 Geminilake DDR4 4GB
ApolloLake (Intel64)
More information can be found here:
At the end, I´m sure is a to the others similar 64-bit system
You got a nonsense answer which misses the point entirely, which was my point, unfortunately.
I know, is simply strange. Maybe you can formulate your question for that, I will send and see what comes back, its also interessting by me.
Regarding the process with Geminilake, the regular support could not make any further statements and referred me to the development in Taiwan. As follows, the answer:
History Log
________________________________________
Staff replied on 2020-09-03 06:20:17:
Hi Andreas,
I apologise for the unclear information, but yes, Geminilake is under the x86_64 family, and packages built for x86_64 will work with Geminilake.
Thank you for your support.
Best regards,
Charles Shih
Product Specialist
+886-2-2955-1814 #8802
Synology Inc.
________________________________________
Customer replied on 2020-08-28 09:38:35:
Hallo,
vielen Dank, dass Sie sich an Synology wenden. Wir melden uns schnellstmöglich bei Ihnen. Vielen Dank für Ihre Geduld. Unten sehen Sie eine Kopie der Nachricht, die wir gerade von Ihnen erhalten haben.
Firmenname
Webseite
Nachricht In order to be able to develop APPs, the exact description in the current version of the Synology package scripts is required, otherwise their "existence" is not officially and also not exactly defined.
There are no documents available for "Geminilake" as a processor platform, it is only known that this is a 64-bit platform and can probably be assigned to the "amd64" or "x86_64" family. Documentation would be required for this. At the moment it looks like the current package scripts "Geminilake" are not assigned to a more general family, so for example an available x86_64 package could be loaded. Each of the platforms has an affiliation for APP development. Example family="x86_64":
x86 | bromolow | cedarview | avoton | braswell | broadwell | denverton | apollolake
Produktname Syncthing
Produktkategorie Sonstiges
Produktinformationen Peer-to-Peer Software Syncthing
Special Notes
• Um Fehler bei der Kommunikation aufgrund der Filterregeln Ihres E-Mail-Anbieters zu vermeiden, empfehlen wir, die Domain synology.com zu Ihrer E-Mail-Whitelist hinzuzufügen. Nutzen Sie bitte hierzu das Hilfe-Handbuch Ihres E-Mail-Anbieters.
• Um Missverständnisse zu vermeiden, formulieren Sie Ihre Anfrage auf Deutsch oder Englisch.
Synology Inc. http://www.synology.comThis should be solved in a recent PR and package 1.8.0.1.
The newest statement of Synology to DSM 7:
Thanks for your continuing interest in developing with Synology.
We are planning for a major version update to DSM7.0 Beta soon.
Due to DSM 7.0 having quite a few adjustments to the framework, current version of third-party packages would be incompatible with the new DSM 7.0 version.
Hence, we are providing you with a new set of Developer's Guide, Toolkit and relevant resources, so that your future package can be compatible with our upcoming DSM release.
**DSM 7.0 Package:**
Please provide us with your Synology Account (E-mail) before we can send you the portal url for downloading DSM7.0 Beta to your device.
If you don’t have a Synology Account, please create one here: https://account.synology.com/
The part “current version of third-party packages would be incompatible” is not so transparent for me, maybe is for you more transparent with the attached Developer’s Guide.
DSM7_developer-guide.pdf (1.8 MB)
Let me briefly introduce to you the upcoming changes:
1. Adjustment to lower the privilege level for third-party packages to run as a user rather than root. Package installation would fail if its privilege setting differs from our new requirement.
2. To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology.
In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center.
To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation.
If you wish to continue running as root rather than user, please follow the instructions below:
i) Log in to the DSM of NAS device(s) that you want to develop / test on
ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat”
iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.)
iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/
v) You are all set to develop the new version using your current privilege level setting.
3. It is anticipated that a lot of Synology users will be upgrading to DSM 7.0 Beta after its public release. In order to make it in time with our DSM 7.0 Beta’s release, please submit your new version by the end of October 2020. For which, our package verification process will begin in October.
4. Although you can continue to support the current DSM version, it is recommended that your package supports DSM 7.0 as a priority.
5. Please refer to the package review items stated in Appendix C of the Developer’s Guide for an idea on the things to look out for to expedite the verification process.
Thank you!Regarding the confusion of the DSM 7 permissions (root/user) during the installation process I got today the follow message from Synology:
Start
Yes, you may continue using root privilege ONLY if you apply a token from us to bypass the lower privilege setting this time round, without which, your package installation would fail in DSM7.0 Beta.
As mentioned in point 2 in my previous email:
To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology.
In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center.
To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation.
If you wish to continue running as root rather than user, please follow the instructions below:
i) Log in to the DSM of NAS device(s) that you want to develop / test on
ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat”
iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.)
iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/
v) You are all set to develop the new version using your current privilege level setting.
Our ultimate goal is still hoping for all of our package developers to be able to abide by our new privilege setting in future versions.
End
I don’t think either mine nor the SynoCommunity package runs as root so none of this is a breaking change. Or looks like it, who knows what happens when it lands.
I use VMM on a DS and Virtual DSM 7.0 Preview.
There is a change in the installation process in the new DSM 7.0, which usually runs in the future no longer as root, instead as user in the new lower privilege framework.
In DSM 7.0 in the package center both packages are available:
If I try to install the Safihre package (SynoCommunity),
I got the follow message (sorry for the german):
This means:
If I try to install the Kastelo package, no package is found:
With the result:
I Just installed Syncthing using the instructions here. I’m running a DS416 and the version installed shows as v1.3.4, Linux (ARM).
Will the package update to the latest release or is this where I’ll stay?
Your platform is listed, so normally the current version is installed, v1.9.0. Please check, if your package is surely from Kastelo and not from Safihre (SynoCommunity) or further.
If you have installed Kastelo at the end, then a internal update is not possible.
1 Like