FOG 1.5.10 officially released

[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.

[Squanchy2112]

Thank you all for the hard work we all truly appreciate it, for updating can we just install this on to of 1.5.9?

[Sebastian Roth]

@Squanchy2112 Yes sure, you can Update from 1.5.9 by simply running the 1.5.10 FOG installer.

[lebrun78]

Hello and thank you for your very useful job !

The installation instructions in https://news.fogproject.org/fog-1-5-10-officially-released/ link seams not good.
The link drives me to installer archive

Arnaud

[Tom Elliott]

@lebrun78 I’m not seeing any issues.

[Sebastian Roth]

@lebrun78 said in FOG 1.5.10 officially released:

The installation instructions in https://news.fogproject.org/fog-1-5-10-officially-released/ link seams not good.

The link changed over time as we are working on the docs as well. This should be fixed now.

@JJ-Fullmer Will the links change again in the future you reckon?

[Dyego Sales]

Thank you so much FOG team!!!

[JJ Fullmer]

@Sebastian-Roth I have a work in progress concept for permanent links. But things have gotten busy and I haven’t had much free time to get it working in full.
Short version is that we’ll be able to create uuids for all pages and that can be used as a permanent link even if it moves elsewhere in the doc.

[milsondc]

After upgrade 1.5.9.110 to 1.5.10 fog stopped sending email, i can still send through terminal with sendmail -v , is this a know bug ?

[Tom Elliott]

@milsondc Fog doesn’t send email period.

[oaslanmetu]

Will there be a new version of Fog Server soon?

[tedlaur]

@Sebastian-Roth Thank you for this update. I’m curious … do you know the release schedule (or if there is one)? I’ve been doing some test installs and it looks like php 5 is a dependency that seems to be problematic for me. I’ve found I can get past it using Debian 11 but would rather use something a little more current. I’m grateful for all the FOG team has done on this project. Its a life saver!

[Tom Elliott]

@tedlaur FOG does not require using php 5 anylonger.

The “minimum” version expected in more modern versions of FOG I believe is at least 7. In the past it used to be 5.6 at least, but with the large differences in php 7/8 I believe it’s normal now to expect at least 7 or >

[tedlaur]

@Tom-Elliott Thanks for the reply. I noticed PHP 8 support in the release notes so I’m guessing that the comment in the source code of the management page is just out of date. No worries. It seems like I should not have a problem using Debian 12.5 but for some reason I get a blank page when I click on /fog/management webpage during the install. I’ll try again with debian 12.5 standard … maybe Lynx would work?

[Tom Elliott]

@tedlaur You can provide your error log from the install, but sometimes more fruitful is the actual php-fpm error (or on debian it may just be in the http error logs)

I don’t recall, and it has been a while since I did direct troubleshooting with fog. I can still read of course and probabaly help in that way, but my systems are limited as of late and as such harder for me to troubleshoot issues to try to replicate.