Latest version on the website is 1.32.5.7516, but this follows (in my case) 1.32.6.7371 which is installed on my Synology NAS. Therefore the update won’t install.
The build number suggests an issue on versioning with the website downloads as I would have expected 1.32.7.7516. This “wrong” version number seems to be in place for all technologies, not only Synology.
Or am I missing something?
1 Like
This is like deja vu all over again (Lower build numbers in newer releases (NERD ALERT)) 
Only this time around it’s reversed, in that the version number went down, but the build number went up. Just not good practice…
Why didn’t you guys just increase the build number of today’s release by one (or a few), since there were no changes since 1.32.5.7349? For those of us who upgraded to 1.32.7.7484 without any issues (Windows), there is no reason to downgrade. Yet, now we have a higher build number in an older version overall. Confusing to users and the PMS upgrade process alike 
What bothers me is if the automatic update actually downgrades my install. I have never once done that since I know that the database can become messed up in some situations by downgrading.
I think this has been a huge disaster, and honestly @ChuckPa this has happened before when you have built PMS packages.
Further, the handling of the beta->public situation has been weird. The beta for the offending version was in beta for almost a month, why was this caught just after the public version was out?
Chuck, I just saw your post in the other thread and was gonna post something about that 7515 here
Yes, this was a disaster.
This time, we got HAMMERED by losing a whole bunch of the team.
MOST IMPORANTLY, we lost the team members who made the changes!
We think we just found it. (I’ve got success on 3 different configurations) so I’m sharing with everyone.
I work part time and I’ve already used up my month’s allotment of time
2 Likes
But can you explain how the beta was out for like a month, and then litterally the next day the public went out (so everyone got updated), this was found?
That’s very odd. I have trusted this beta->public release schedule very much, trusting that this could not happen. I am on public releases exactly for moments like these.
It happened because of what went on BEHIND the scenes.
I am not at liberty to disclose any of it but it was a upheaval and NOT pretty.
This is the gross exception.
We essentially lost about 20% of our team.
I don’t know if you work in software but when you lose 20% – AND – it’s a critical part – THAT S*** HURTS
This is where we’re at. Take it or leave it.
We’re doing the best we can with what we have.
We have a working (seemingly) build to put in beta
1 Like
Look, all I’m saying is you guys should not have released it as stable/public.
It sounds like a bad time inside the company, but this has nothing to do with the fact that someone decided to release the build as stable without properly testing it. Why not just keep it in beta until the dust settles?
That happened with the version before it also, btw. It was known that the beta had subtitle issues, and the release stayed in beta for like a full month. Then without any fix, it was just released to public. That was also very confusing. Why even have such a system if you are just going to release the stable version with known serious bugs?
Sure, that would have been the right decision but somehow not what happened.
Monday morning quarterbacking is always 20/20 vision.
With this. I am exiting this thread. I have more testing to do.
1 Like
Before you bow out, I also want to say that if this actually downgrades my install tonight, then that is just highly incompetent.
That is simply not a 100 percent safe manuever, and we both know that.
If your install script does something other than what Synology allows – That’s on you and your script.
- We have not updated Package Center
- DSM Package Center does not allow downgrade. It requires
– Uninstall Package
– Install Lower version package - Downgrading is a manual action -OR- performed by 3rd party script.
(I am the Syno packaging dev here)
I am on Windows and not even affected by the bug. Which is why I obviously don’t want to be downgraded, with the risks that comes with it.
i cannot speak to windows. I don’t have anything to do with it.
This is a Synology thread.
I do two things when it comes to windows; Wash or Break .
That’s it.
I don’t even have a Windows VM
You don’t get downgraded on Windows either, unless the downgrade version is overall newer in version numbers (not builds).
…and as long as you have “Server version updates” set to " Ask me", nothing happens anyway.
1 Like
I guess that makes sense. I hope so at least.
I do not have it set to ask me.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
