[GH-ISSUE #1931] LSGM Teamspeak Update Option overwrites Teamspeak Beta Installs #1520

New issue

Closed

opened 2026-02-27 02:57:34 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:57:34 +03:00

Owner

Originally created by @gOOvER on GitHub (Jul 5, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1931

I updated manually Teamspeak to the 3.3.0 beta1. If I have autoupdate enabled, 3.3.0 will be overwritten be 3.2.0.

Maybe you can add an option to use Beta Build s too order ignore if Version is greater than installed.

"ts3@web01:$ ./ts3server sp
[ OK ] Stopping ts3server: TeamSpeak 3 Server
ts3@web01:$ ./ts3server st
[ OK ] Update ts3server: Checking for update: teamspeak.com

Update available:
Current build: 3.3.0 amd64
Available build: 3.2.0 amd64

Applying update...
extracting teamspeak3-server_linux_amd64-3.2.0.tar.bz2...OK
copying to /home/ts3/serverfiles...OK
"

Originally created by @gOOvER on GitHub (Jul 5, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1931 I updated manually Teamspeak to the 3.3.0 beta1. If I have autoupdate enabled, 3.3.0 will be overwritten be 3.2.0. Maybe you can add an option to use Beta Build s too order ignore if Version is greater than installed. "ts3@web01:~$ ./ts3server sp [ OK ] Stopping ts3server: TeamSpeak 3 Server ts3@web01:~$ ./ts3server st [ OK ] Update ts3server: Checking for update: teamspeak.com Update available: Current build: 3.3.0 amd64 Available build: 3.2.0 amd64 Applying update... extracting teamspeak3-server_linux_amd64-3.2.0.tar.bz2...OK copying to /home/ts3/serverfiles...OK " See also: https://forum.teamspeak.com/threads/136231-PreRelease-TeamSpeak-3-Server-3-3-0-Beta

kerem

2026-02-27 02:57:34 +03:00

closed this issue
added the
type: feature

outcome: issue resolved

game: Teamspeak 3
labels

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jul 5, 2018):

Managing stable teamspeak versions is already a pain because they don't really have a proper structure to check versions... I think we figured a good way though.
I don't see ourselves working on adding beta repos which would probably change structure quite often and be even more of a pain to maintain. If you want to install the beta version, I would suggest downloading such version to your serverfiles directory manually and update it manually as well.

@UltimateByte commented on GitHub (Jul 5, 2018): Managing stable teamspeak versions is already a pain because they don't really have a proper structure to check versions... I think we figured a good way though. I don't see ourselves working on adding beta repos which would probably change structure quite often and be even more of a pain to maintain. If you want to install the beta version, I would suggest downloading such version to your serverfiles directory manually and update it manually as well.

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@gOOvER commented on GitHub (Jul 6, 2018):

Maybe only an option to ignore update when Version is higher than the installed one. I think this should be enough. And you will not miss an regular update :)

@gOOvER commented on GitHub (Jul 6, 2018): Maybe only an option to ignore update when Version is higher than the installed one. I think this should be enough. And you will not miss an regular update :)

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 21, 2018):

Good idea with the ignoring if the available version is higher. That way you can manually install a beta version and not overwrite it until a newer stable is released.

@dgibbs64 commented on GitHub (Jul 21, 2018): Good idea with the ignoring if the available version is higher. That way you can manually install a beta version and not overwrite it until a newer stable is released.

kerem commented

2026-02-27 02:57:35 +03:00

Author

Owner

@lock[bot] commented on GitHub (Oct 27, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Oct 27, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:11 +03:00

[PR #1520] [MERGED] Fix for issue #1517 'DOI Setup Broken' #3351