phpswitcher: Add recent version for PHP 7.4

Hello,

use the Patch in the attachmend.

Viktor

[ERROR] main: An error occurred while executing MAKE(1) target(s) for PHP 7.4.14: W: --override-config is not set; not updating apt.conf Read the manpage for details.

gpg: key 4F4EA0AAE5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur▒" imported

gpg: Total number processed: 1

gpg: imported: 1

Starting pkgProblemResolver with broken count: 0

Starting 2 pkgProblemResolver with broken count: 0

Done

Starting pkgProblemResolver with broken count: 0

Starting 2 pkgProblemResolver with broken count: 0

Done

make: [unprepared] Error 1 (ignored)

No patch removed

make: *** [patch-stamp] Error 1

Sorry, I have similar error after use the 0029-php-5.4.9-fixheader.patch

Applying patch 0029-php-5.4.9-fixheader.patch

patching file configure.ac

Hunk #1 FAILED at 1331.

1 out of 1 hunk FAILED -- rejects in file configure.ac

Patch 0029-php-5.4.9-fixheader.patch does not apply (enforce with -f)

/var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/Makefile:230: recipe for target 'patch-stamp' failed

make: Leaving directory '/usr/local/src/phpswitcher/php-7.4.6'

I: Copying back the cached apt archive contents

I: unmounting /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler filesystem

I: unmounting /usr/local/src/phpswitcher/php-7.4.6 filesystem

I: unmounting /opt/phpswitcher/20220302 filesystem

I: unmounting dev/ptmx filesystem

I: unmounting dev/pts filesystem

I: unmounting dev/shm filesystem

I: unmounting proc filesystem

I: unmounting sys filesystem

I: Cleaning COW directory

I: forking: rm -rf /var/cache/pbuilder/build/cow.13766

[DEBUG] iMSCP::LockFile::release: Releasing exclusive lock on /var/lock/psw-php-compiler.lock

[ERROR] main: An error occurred while executing MAKE(1) target(s) for PHP 7.4.6: W: --override-config is not set; not updating apt.conf Read the manpage for details.

gpg: key 4F4EA0AAE5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur▒" imported

gpg: Total number processed: 1

gpg: imported: 1

Starting pkgProblemResolver with broken count: 0

Starting 2 pkgProblemResolver with broken count: 0

Done

Starting pkgProblemResolver with broken count: 0

Starting 2 pkgProblemResolver with broken count: 0

Done

make: [unprepared] Error 1 (ignored)

No patch removed

make: *** [patch-stamp] Error 1

Use the packaged version, don't try to build your own.

Doing so, you'll just get a lot of headache.

To know how to use the packaged version, read the doc... (an create your own post if you still have issue, following the posting rules).

Thank you for reply.

I have tested all 7.4.X version if php version large than php 7.4.7. Then, it will have error.

So, using php 7.4.7 work perfectly. This version is enough for me. Thank you

Just edit /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl accordingly

# Map PHP version names to tiny PHP versions (last known tiny PHP versions)

my %VERSION_NAME_TO_VERSION_TINY_MAP = (

'5.3' => '5.3.29', # End of life: 14 August 2014 - Reached

#'5.4' => '5.4.45', # End of life: 3 September 2015 - Reached

#'5.5' => '5.5.38', # End of life: 21 July 2016 - Reached

'5.6' => '5.6.40', # End of life: 31 December 2018 - Reached

'7.0' => '7.0.33', # End of life: 01 December 2018 - Reached

'7.1' => '7.1.33', # End of life: 01 December 2019

'7.2' => '7.2.24', # End of life: 30 November 2020

'7.3' => '7.3.11', # End of life: 06 December 2021

'7.4' => '7.4.7'

);

Hum.... will try to do a "Nuxwin" like answer... (well, will not be at all)

So you ask for help but doesn't care of the answer ?

Worst, you prefer to run a version which is behind 21 releases prior the latest one (where in those, there are 11 marked as "security" updates).

7.4.7 was released on 11th of June... 2020.

Well, you still seems to use pretty old released like the 5.3/5.6, so maybe you like the risk of it after all.

Latest release in the 7.4.x branch is the build 28, out on 17th February of this year.

Latest security update for this specific branch will get over at the end of November 2022 (more or less, 8 months).

On my own experience, keeping really old site is never a good idea, but at the end, everyone choose what they want, and accept the risk of it, I guess...