Current version for RHEL 9 (etc) systems

[aristotle]

I am currently running openlitespeed 1.7.19-5.el9 from the OpenLiteSpeed repo, but expected v1.8.0 (at least) to be available by now.
Have I overlooked something?

 

[Cold-Egg]

1.8.x is not on the stable tier yet, once it is ready, we will build a package and push it to the repository.
https://rpms.litespeedtech.com/centos/9/update/x86_64/RPMS/

 

[aristotle]

I just noticed that my Rocky 9 servers have been updated to LiteSpeed/1.8.2 Open (BUILD built: Sat Oct 26 04:05:54 UTC 2024).

I am not sure when it happened, but have not noticed any changes.

 

[Cold-Egg]

That is good, isn't it?
Here’s the release log if you’d like to see what has changed.

 

[aristotle]

Yes it is good. An announcement somewhere here when the RPMs are updated would be even nicer.

On the subject of RPMs, litespeed-update repo may need an update, lsphp74-mysqlnd.x86_64 is at version 7.4.32-2.el9 but 7.4.33-2.el9 has been released for around 1 year in the Remi repo I think.

 

[Cold-Egg]

There's no plan for updating end-of-life PHP packages.

 

[aristotle]

But if it is an EOL package why is it a dependency of the v1.8.2-1.el9 openlitespeed rpm?

I would be much happier if the dependencies were for the generic packages such as php-litespeed provided by the remi repos.

I run PHP v8.2 or 8.3 on my sites, why should Litespeed insist I install 7.4?

 

[Cold-Egg]

That is for the OpenLiteSpeed Web Admin, we have upgraded the PHP version for Debian, and it should be soon for the rpm system.

 

[aristotle]

Today I am offered v1.8.2-2.el9

Does this address the issues discussed here, or something else?

It would be much nicer if we got an announcement when package updates are released.

 

[aristotle]

Installation not so successful:

Last metadata expiration check: 1:24:58 ago on Sat Dec 28 18:11:08 2024.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Upgrading:
openlitespeed x86_64 1.8.2-2.el9 litespeed-update 18 M

Transaction Summary
================================================================================
Upgrade 1 Package

Total download size: 18 M
Downloading Packages:
openlitespeed-1.8.2-2.el9.x86_64.rpm 17 MB/s | 18 MB 00:01
--------------------------------------------------------------------------------
Total 17 MB/s | 18 MB 00:01
Package openlitespeed-1.8.2-2.el9.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

 

[Cold-Egg]

Not yet. Implementing the newer PHP version may take a little bit longer. The GPG key issue should have been fixed; let us know if it is still not working.

 

[aristotle]

The update package now installs successfully. Thank you.

 

[technotic]

Not yet. Implementing the newer PHP version may take a little bit longer. The GPG key issue should have been fixed; let us know if it is still not working.

Are you referring to updating the admin console to PHP 8? It would be nice. Btw I have a bug report I need to file too re: a dependency for lsphp74 (oniguruma5php, libxcrypt-compat, even libc-client has trouble after removal using repo packages).

It'll be nice to see the admin console updated though. I want to possibly submit a couple patches/PRs for detection/correction of a couple basic things, like permissions. But it'd be best to wait for the update I think.

Regarding openlitespeed repo, I believe it has a dependency on remi's repo too? And is 1.8.2 only on the litespeed-update repo then? If the update repo is like a next or testing repo, wouldn't it make more sense to rename it that? Or to put 1.8.2 on openlitespeed-edge for EL9? Just thinking outloud