Debian Based (Mint, Ubuntu, Debian), Redhat Based (Redhat, Rocky, Alma, Fedora).

The versions, dev-branch is more likely going to be in line with latest/greatest. Some what of a delay of course, but there’s no list that clearly spells out what version of specific OS is supported.

In my opinion, Redhat based OS’s are the best as we don’t have to continually update the installer code to support future versions. Most will just work right out of the box.

Migration process? No, if you’re moving one machine to another that’s one thing of a migration and there is a process for that, but if you’re meaning “I’m on bookworm and without moving anything, I’m going to do an in place upgrade?” I don’t believe there will be problems but what I would suggest is re-installing FOG once the upgrade is complete as any services or config files that got changed would need to be rebuilt for the new OS. It’s not hard and I don’t think there will be any issues. If there are, please let us know.

Also is there a migration process, how to upgrade from bookworm without creating a new server ?

On latest Debian Trixie, dev-branch installer gives :

Setting up fogproject user…/lib/common/functions.sh: ligne 1476: lastlog : commande introuvable

Please, for now, switch to the dev-branch and install where this should be resolved.

@jaumeramos Would you be willing to test:

diff --git a/lib/common/functions.sh b/lib/common/functions.sh
index b20b0e482..05f40d08c 100755
--- a/lib/common/functions.sh
+++ b/lib/common/functions.sh
@@ -725,6 +725,9 @@ installPackages() {
                     if [[ $OSVersion -gt 17 ]]; then
                         packages="${packages// libcurl3 / libcurl4 }">>$error_log 2>&1
                     fi
+                    if [[ $OSVersion -ge 22 ]]; then
+                        packages="${packages// libcurl4 / libcurl4t64 }">>$error_log 2>&1
+                    fi
                     if [[ $linuxReleaseName_lower == +(*ubuntu*) && $OSVersion -ge 18 ]]; then
                         # Fix missing universe section for Ubuntu 18.04 LIVE
                         LANG='en_US.UTF-8' LC_ALL='en_US.UTF-8' add-apt-repository -y universe >>$error_log 2>&1

Changing the functions to this code?

I’m hoping to catch as 17-21 worked fine with lubcurl4, but 22 needs libcurl4t64

It’s ugly, I have pushed if you just want to pull from dev-branch

Hi,
The dev-branch worked well for me, thanks!

Ubuntu MATE 24.04
6.8.0-31-generic
All packages fully updated before running the FOG installer (for better or worse, haha)

Thanks again for all the work on this project, it has been great to see it continue on over the years,
Dave

diff --git a/lib/common/functions.sh b/lib/common/functions.sh
index b20b0e482..05f40d08c 100755
--- a/lib/common/functions.sh
+++ b/lib/common/functions.sh
@@ -725,6 +725,9 @@ installPackages() {
                     if [[ $OSVersion -gt 17 ]]; then
                         packages="${packages// libcurl3 / libcurl4 }">>$error_log 2>&1
                     fi
+                    if [[ $OSVersion -ge 22 ]]; then
+                        packages="${packages// libcurl4 / libcurl4t64 }">>$error_log 2>&1
+                    fi
                     if [[ $linuxReleaseName_lower == +(*ubuntu*) && $OSVersion -ge 18 ]]; then
                         # Fix missing universe section for Ubuntu 18.04 LIVE
                         LANG='en_US.UTF-8' LC_ALL='en_US.UTF-8' add-apt-repository -y universe >>$error_log 2>&1

Changing the functions to this code?

I’m hoping to catch as 17-21 worked fine with lubcurl4, but 22 needs libcurl4t64

It’s ugly, I have pushed if you just want to pull from dev-branch

The issue is that the libcurl4 in ubuntu 22.04 is now libcurl4t64 so the check fails.

Changing the name of the package in lib/common/funcions.sh solves the problem and the installation works smoolthly.

For example, libcurl4 might simply be provided in default curl now but since past versions need the specific libcurl4 call out, it causes errors. So we have to maintain libcurl4 of version ubuntu <x:y> while allowing “new” ubuntu <latest>.

Ubuntu is personally one OS i’m not a fan of for FOG’s installer since the package list is consistently fragmented.

Appreciate the feedback.

Mike

While sometimes it may work just fine, in a large majority of cases they will not because changes ubuntu has made to available packages changes just as frequently as Ubuntu updates.

From what I can see Ubuntu 24.04 was released sometime yesterday. FOG 1.5.10 was released sometime in 2023. So there’s nothing for us to fix currently because we haven’t had enough time to even look at the new version of ubuntu and see IF we could even update the installer cleanly enough to get it installed on Ubuntu 24.04