Cannot install FOG 1.5.9 in Ubuntu 16.04 because cannot install php7.1 (Is Ondrej repository empty??)

[***Redbob]

Hi!

I tried update FOG from 1.5.7 to 1.5.9 in my servers. We have 7 fog servers spreading across our State, two running Fedora and others running Ubuntu 16.04. The last two servers (16.04) I couldn’t update because the installer cannot install php7.1 at all.
The error is this:

dpkg-query: no packages found matching php7.1
dpkg-query: no packages found matching php7.1-bcmath
dpkg-query: no packages found matching php7.1-cli
dpkg-query: no packages found matching php7.1-curl
dpkg-query: no packages found matching php7.1-fpm
dpkg-query: no packages found matching php7.1-gd
dpkg-query: no packages found matching php7.1-json
dpkg-query: no packages found matching php7.1-ldap
dpkg-query: no packages found matching php7.1-mbstring
dpkg-query: no packages found matching php7.1-mysql
dpkg-query: no packages found matching php-gettext
php-gettext

It’s funny, because I connected to Ondrej repository properly. Look:

gpg: keyring `/tmp/tmph5l8tm4m/secring.gpg' created
gpg: keyring `/tmp/tmph5l8tm4m/pubring.gpg' created
gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
gpg: /tmp/tmph5l8tm4m/trustdb.gpg: trustdb created
gpg: key E5267A6C: public key "Launchpad PPA for Ondřej Surý" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
gpg: keyring `/tmp/tmpcfmwjn32/secring.gpg' created
gpg: keyring `/tmp/tmpcfmwjn32/pubring.gpg' created
gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpcfmwjn32/trustdb.gpg: trustdb created
gpg: key E5267A6C: public key "Launchpad PPA for Ondřej Surý" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

It doesn’t matter if the server is newer or just an update. I didn’t installed at all. It seems Ondrej has thrown off these packages, because I added Apt key successfully, as you can see in the attached fog_error_1.5.9 and foginstall logfiles here. You can check, the installer installed php7.0, instead. But the installation ended unsuccessfully.

Any ideas? May I wait for Ondrej to fix his repository?

[Sebastian Roth]

@Redbob Yeah the wiki is really dated. We really need people from the community help us sort through it and move it all to the new documentation platform: https://docs.fogproject.org/en/latest/

Would you be keen to help us?

[***Redbob]

@sebastian-roth I successfully installed 1.5.9 in Ubuntu 18.04! It installed php7.2 on it. Thanks!.. It’s interesting to update installation wiki, because there is written 16.04 as high Ubuntu release that support FOG.

[Sebastian Roth]

@Redbob FOG works on Ubuntu 22.04 but you’ll need to use dev-branch instead of the last official 1.5.9 release - or wait a little longer till 1.5.10 is out.

[***Redbob]

@sebastian-roth I’m not interested in keep Ubuntu 16.04 in these machines. I’ll try in 18.04, for example, but I tried installing a fresh in Ubuntu 22.04, and the error was exactly the same!! But I think this release is too new for this test, ok? I’ll be back with the results about upgrading my server to 18.04

[Sebastian Roth]

@Redbob I don’t think there is much of a chance anyone is going to fix that issue. Ubuntu 16.04 reached the end of standard support and updates are only available through Extended Security Maintenance (ESM). I guess Ondrej removed the packages for that reason.

Are you subscribed to the ESM program? Ok, from the installer log I figured you are using ESM. Still I might ask you on what’s your plan to step forward from Ubuntu 16.04?

Now if you want to stick with Ubuntu 16.04, either you can get the extended support for those PHP packages by using the paid service (see information here) or we would need to find a way to switch back to the official PHP packages used by Ubuntu.

We are trying to support a wide range of Linux distros and versions and it’s hard to keep up with those really old versions as well. So this will be a step by step thing I can provide you here rather than changing the installer I suppose.

Update: Scrolling through the whole log file I found this:

*The following packages could receive security updates with UA Infra: ESM service enabled:

Somehow sounds like you’re not using the full ESM service?!