FOG 1.5.10 officially released

[Sebastian Roth]

After a certainly too long period since the last release we finally announce the new FOG 1.5.10:

https://news.fogproject.org/fog-1-5-10-officially-released/

Thank you very much to everyone devoting time to help getting this ready!!!

Find all the details in the new release notes…

This version was re-released (re-tagged) on 31st of March 2023 to patch issues with the location plugin that would cause trouble when updating from an earlier version.

[Trev-lchs]

@Sebastian-Roth Great news, thank you Sabastian and your crew of dedicated Fog warriors, much appreciated.

[Florent]

Thank you we are happy to see FOG alive !

[qpassa]

Thank you very much!!!

[typotony]

@Sebastian-Roth Thank you fog team!!!

[Trev-lchs]

Hi all I know its very old, but, will 1.5.10 work ok on ubuntu 10.04.6 LTS Xenial Xerus

[george1421]

@Trev-lchs said in FOG 1.5.10 officially released:

Hi all I know its very old, but, will 1.5.10 work ok on ubuntu 10.04.6 LTS Xenial Xerus

I hate to say this because I know we all need to run old stuff, but 10.04 reached end of support by ubuntu in 2015. I would bet that the ubuntu repos will not have all of the required prerequisites in their distribution needed for FOG 1.5.10. The installer should fail. BUT, if you are able to get FOG installed, it will run on that old of an operating system because uses all FOSS components.

For you, unless you have a really compelling case, you will be better off in the long run to install FOG on a current supported operating system and walk away from 10.04.

[Sebastian Roth]

@george1421 I am pretty sure the number is a typo because the distro name is for 16.04 which makes a little more sense than 10.04.

@Trev-lchs Officially we 1.5.10 does not support Ubuntu 16.04 as it reached the normal end of life cycle. And we don’t have a intaller test running for 16.04 either. But on the other hand I don’t see what change should make it impossible to use 1.5.10 on Ubuntu 16.04 in case you are using PHP 7.0 at the least. So I suggest you either setup a fresh test instance and see how it goes or even better you take a snapshot of your production server and just do an update to 1.5.10. Let us know how it goes.

By the way, even 14.04 is still hast so called extended security maintainance (ESM) just as 16.04 does according to wikipedia. This is definitely too much of official OS support we can stem. Not saying you cannot install FOG 1.5.10 on 14.04. I just haven’t tried.

Something I came to think about. How does Ubuntu handle things like PHP for such old versions. Are you still using PHP 7.0 on 16.04 while even 7.4 is not being updated anymore.

[Trev-lchs]

@Sebastian-Roth Hi Sabastian. Yes you are correct 16.04.6 LTS Xenial Xerus, well I took your advice and created a snapshot of the virtual server. Installed 1.5.10 and so far all seems well, I will let you know, but …

Mod edit: moved to https://forums.fogproject.org/topic/16739/migrating-fog-1-5-10-from-old-to-new-server-old-to-new-os

[Trev-lchs]

@george1421 Hi George, sorry buddy it is a typo, its 16.04.6 LTS Xenial Xerus. Thanks for getting back to me, just for info I took Sabastian’s advice and took a snapshot of the server and installed1.5.10 and all seems ok for now. I will however look to upgrade to the latest LST version.

[plegrand]

@Sebastian-Roth
Hello,
until now I was using the “dev-branch” branch of git:

git branch -vv
* dev-branch ddb9904a7 [origin/dev-branch] Fix https build failing due to inline tests
 master 171d63724 [origin/master] FOG 1.5.9 Officially Released

For the latest update of fog: 1.5.10, is it better to switch to the master branch?
This is a production server and I don’t want to “break” it.

Once the choice of the branch is made, the update procedure is always the same?

Change the reference branch to master or dev-branch (To be done the first time)
	git checkout master or git checkout dev-branch
Initialize git :
	git init
Update the git repository:
	git pull
Install FOG
cd bin/
./installfog.sh

Thanks for your help.
Pascal

[Sebastian Roth]

@plegrand Good you are asking. Going forward is always supported. So in your particular case coming from commit ddb9904a7 (version 1.5.9.111) you can safely switch to the master branch and then follow the known update commands:

cd /path/to/fogproject
git checkout master
git pull
# Make sure this succeeds as it can fail when you have made changes to the repo files,
# e.g. compiled ipxe binaries. If this fails, then you can drop all modifications using "git reset --hard HEAD"
cd bin
./installfog.sh

[plegrand]

@Sebastian-Roth
Thank you for your answer.
I didn’t touched anything in the deposits.
I use Fog as it is, without changing anything.
So I will do the update and I will come back here to tell you if everything went well.
Thanks again.

[Oleg]

Thanks you guys for keeping this project alive. We really love that because it’s saving us so much time.
Big thanks to all developers and supporters for their time!

[Kureebow]

This seems like a dumb question but is there a way for us to “Upgrade to FOG 1.5.10” without a complete uninstallation?

Thanks.

[george1421]

@Kureebow Yes, if you installed FOG originally using the git method, just change to that directory (typically /root/fogproject) and execute the command git pull then change into the bin directory and run the installfog.sh script once again. That will update fog from a previous release to 1.5.10.

[Kureebow]

@george1421 Sorry for the late response I have been out of my office for a family emergency. This is the response I got when attempting that command. Thanks

[root@localhost fogproject]# git pull
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[root@localhost fogproject]#

[george1421]

@Kureebow It sounds like you crated the fogproject directory using the tarball and not the git clone method?

[Sebastian Roth]

@Kureebow May I please ask you to open a new topic as this issue is not really related to the initial post.

[Sebastian Roth]

FOG 1.5.10 was kind of re-released (technically just re-tagged on Github) just now to patch issues causing trouble when updating from an earlier version with the location plugin enabled.