2021-11-29Utility : C2IdentityDockerMgmtTool ✎ : 1.0.1-00010 ⇩ ✱
Package : C2IdentityLDAPAgent ✎ : 1.0.0-0021 ⇩ ✱
Changes posted as they get added in the Synology archive webpages. Alphabetically would just mean posting all the packages every time, regardless of updates.Changes listed alphabetically, if you prefer this way.
Package Center should be alerting to updates but often, for me, it takes weeks or months for it to tell me. Sometimes CMS finds updates well ahead of Package Center.
Thanks...the "after some time" lag certainly feels lengthy. I'm not anxious to update for the sake of updating, but I am interested in getting security update/patches sooner than later.After some time the new packages are available on Package Center. If someone don't want to wait, can install the update manually.
As posted in the other thread, Synology will inevitably replace the patch with one with the same build number, leaving you no simple ability to install the lastest "fix".Disconcerting that Synology has yet again posted a DSM update to their ftp site, and then taken it back down. I need to learn to stop installing these things as soon as they're released
ICBW, but I recall that a mode 2 reset, will then enable you to reinstall all update patches. You may also be able to "trick" DSM by editing the patch file to make it appear as the next numerical update... Though I've not tried that.Lovely...damned if you do, damned if you don't.
Yabbut as you say, not incrementing the build number is a complete foobar and just hard to comprehend why they would do that, other than internal laziness/fear of retribution (e.g., new build number kicks off new testing requirements and/or notification of management that they screwed up again and had to re-release a patch, etc.).ICBW, but I recall that a mode 2 reset, will then enable you to reinstall all update patches. You may also be able to "trick" DSM by editing the patch file to make it appear as the next numerical update... Though I've not tried that.