On 22 Apr 2016 18:11, "James Hogarth" james.hogarth@gmail.com wrote:
In the event that there are CentOS users making use of the EPEL owncloud
packages, but not following the EPEL mailing lists, please read the mail below with regards to your installations.
Thanks
James
---------- Forwarded message ---------- From: "James Hogarth" james.hogarth@gmail.com Date: 22 Apr 2016 16:21 Subject: EPEL-ANNOUNCE Re: Upcoming OwnCloud changes in EPEL To: "EPEL Development List" epel-devel@lists.fedoraproject.org Cc: epel-announce@lists.fedoraproject.org
On 5 April 2016 at 09:22, James Hogarth james.hogarth@gmail.com wrote:
Hi all,
Following on the process of bringing OwnCloud up to date in Fedora
we're turning our attention to the EPEL users.
Unfortunately EL6's use of php53 means we cannot update any further
there given the minimum requirement of php54.
As such the maintenance update of 7.0.13 that is in epel-testing now
for EPEL6 will be the final one there to be followed by the retiring of the package.
If you wish to update from that please either migrate to an EL7 base
system or switch to the OwnCloud upstream packages which make use of SCL to satisfy the php54+ requirement.
On the EPEL7 side of things 8.1.6 is due to hit testing very shortly.
This is a mandatory update as a precursor to the 8.2.3 update in due course. Once this reaches live please ensure that updates are carried out and your OwnCloud installation is fully tested prior to the 8.2.3 update.
This is due to a requirement from upstream that updates follow the
path 8.0 -> 8.1 -> 8.2 -> 9.0.
Related to this when updating the EL6 install from the 7.0 version to
an EL7 or upstream SCL version please do make sure you follow the upgrade chain correctly - it is not possible to skip a step.
Once the 8.2 goal is reached a discussion will be had then for EPEL as
to whether to provide owncloud82 and owncloud90 packages or to just stay on the current major update - but that discussion is some time away as of yet.
The reason for picking owncloud82 as the possible base for this is
that this is the first version that has no php libraries bundled so will be the easiest to provide the long term maintained base from in a clean fashion complying to guidelines as closely as possible.
Kind regards,
James
Following on from the previous message EPEL6 has it's final update with
the EOL message. Please arrange to move to the upstream SCL packages or to migrate to EL7 if you are using owncloud on EPEL6 - be aware when you do migrate off of this that it is important to follow the chain through 8.0->8.1->8.2 checking your installation at each step.
EPEL7 has had some time in testing and received a positive test so the
8.1.6 update there is being pushed today.
When that has gone stable an 8.2.3 update will be pushed to
epel-testing. Please ensure that your installation is updated to 8.1.6 and fully tested before applying the 8.2.3 update.
For any OwnCloud users on CentOS who utilise the EPEL packages please be aware of important changes this week:
The EPEL6 package has now been retired as end of life. If using the EPEL6 packaging of OwnCloud please ensure you migrate to a supported version as discussed above.
On the EPEL7 side of things 8.2.4 has just been submitted to stable. Please ensure that the previous 8.1.6 update has been applied and fully tested before carrying out the 8.2.4 update.
For those willing to do some early preliminary testing of 9.0.2 it has been uploaded to my Fedora people space, along with its dependencies.
On 5/21/2016 5:23 PM, James Hogarth wrote:
....or switch to the OwnCloud upstream packages which make use of SCL to satisfy the php54+ requirement.
i started to look at SCL and got lost pretty quickly. I'm not running OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
could someone point me at a writeup on how to setup SCL and php54 or newer on a CentOS 6 system?
On 5/21/2016 6:03 PM, John R Pierce wrote:
i started to look at SCL and got lost pretty quickly. I'm not running OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
ok, I've installed php54-1.1-5.el6.centos.alt.x86_64 ... if I run `scl enable php54`, will that connect it up to my existing apache, so it just works, or will that blow the heck out of everything on my host, or something else? I'm currently using php-5.3.3-46.el6_7.1.x86_64
On 22 May 2016 07:01, "John R Pierce" pierce@hogranch.com wrote:
On 5/21/2016 6:03 PM, John R Pierce wrote:
i started to look at SCL and got lost pretty quickly. I'm not running
OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
ok, I've installed php54-1.1-5.el6.centos.alt.x86_64 ... if I run
`scl enable php54`, will that connect it up to my existing apache, so it just works, or will that blow the heck out of everything on my host, or something else? I'm currently using php-5.3.3-46.el6_7.1.x86_64
The scl enable stuff just affects the command passed. It has no system wide level effect. This is why to get a terminal session with it in affect you use scl enable php54 bash ... then that session will show php 5.4 when running the php binary.
The documentation on how to actually use it for something like php in Apache is terrible, and the general blogs on it are awful overall. Things like doing source /opt/rh/foo/enable seem to be frequently mentioned despite not being what the RH docs say.
There's also a lot of confusion between the CentOS SIG SCL stuff, the official RHEL SCL stuff and the generic softwarecollections.org stuff.
As for mod_php from an SCL from my discussions with Remi on the topic he prefers to use php-fpm in that situation rather than mod_php since that then allows use of different php versions via passing that particular application to a different pool and also allows you to move away from the worker mpm and on top a more performant one since the thread safety issues are then bypassed.
Do keep in mind that the repos only have the base php packages IIRC and that still leaves the question of packages for all the other php libraries. For something like upstream php that bundles everything is not a big deal, but for other things it can be.
Personally I still prefer to use IUS in this use case due to the simpler set up and larger repository of php libraries built against it.
Perhaps I'll dive into a blog post soon™ negotiating through this stuff with decent examples of how to make use of the various methods, along with their pros and cons. The question comes up frequently enough on #centos that it'd be good to have a decent write up to refer to... and with a long time till C6 EOL and RH relying heavily on SCL for PHP5.4+ (rather than rebasing the php in the base distro) on it I'm sure it'll become an even more common question than it already is.
Still none of the options (RH SCL, SIG SCL, SCL.org, IUS, RemiRepo) help us EPEL since we can only depend on what's in base or EPEL for package dependencies, and all efforts to get SCL approved in the Fedora Packaging Guidelines have been rejected over the past few years.
Am 22.05.2016 um 09:00 schrieb James Hogarth james.hogarth@gmail.com:
On 22 May 2016 07:01, "John R Pierce" pierce@hogranch.com wrote:
On 5/21/2016 6:03 PM, John R Pierce wrote:
i started to look at SCL and got lost pretty quickly. I'm not running
OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
ok, I've installed php54-1.1-5.el6.centos.alt.x86_64 ... if I run
`scl enable php54`, will that connect it up to my existing apache, so it just works, or will that blow the heck out of everything on my host, or something else? I'm currently using php-5.3.3-46.el6_7.1.x86_64
The scl enable stuff just affects the command passed. It has no system wide level effect. This is why to get a terminal session with it in affect you use scl enable php54 bash ... then that session will show php 5.4 when running the php binary.
The documentation on how to actually use it for something like php in Apache is terrible, and the general blogs on it are awful overall. Things like doing source /opt/rh/foo/enable seem to be frequently mentioned despite not being what the RH docs say.
There's also a lot of confusion between the CentOS SIG SCL stuff, the official RHEL SCL stuff and the generic softwarecollections.org stuff.
As for mod_php from an SCL from my discussions with Remi on the topic he prefers to use php-fpm in that situation rather than mod_php since that then allows use of different php versions via passing that particular application to a different pool and also allows you to move away from the worker mpm and on top a more performant one since the thread safety issues are then bypassed.
Do keep in mind that the repos only have the base php packages IIRC and that still leaves the question of packages for all the other php libraries. For something like upstream php that bundles everything is not a big deal, but for other things it can be.
Personally I still prefer to use IUS in this use case due to the simpler set up and larger repository of php libraries built against it.
Perhaps I'll dive into a blog post soon™ negotiating through this stuff with decent examples of how to make use of the various methods, along with their pros and cons. The question comes up frequently enough on #centos that it'd be good to have a decent write up to refer to... and with a long time till C6 EOL and RH relying heavily on SCL for PHP5.4+ (rather than rebasing the php in the base distro) on it I'm sure it'll become an even more common question than it already is.
The retirement date for PHP54 (RH SCL) will be Oct 2016. Will the SCL SIG provide longer "support"??
Still none of the options (RH SCL, SIG SCL, SCL.org, IUS, RemiRepo) help us EPEL since we can only depend on what's in base or EPEL for package dependencies, and all efforts to get SCL approved in the Fedora Packaging Guidelines have been rejected over the past few years.
-- LF
Am 22.05.2016 um 08:00 schrieb John R Pierce pierce@hogranch.com:
On 5/21/2016 6:03 PM, John R Pierce wrote:
i started to look at SCL and got lost pretty quickly. I'm not running OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
ok, I've installed php54-1.1-5.el6.centos.alt.x86_64 ... if I run `scl enable php54`, will that connect it up to my existing apache, so it just works, or will that blow the heck out of everything on my host, or something else? I'm currently using php-5.3.3-46.el6_7.1.x86_64
just take a look under /etc/httpd/conf.d/ and move the php.conf away to allow the php-54.conf file to get the precedency ...
-- LF
On 22 May 2016 07:01, "John R Pierce" pierce@hogranch.com wrote:
On 5/21/2016 6:03 PM, John R Pierce wrote:
i started to look at SCL and got lost pretty quickly. I'm not running
OwnCloud but I've got some other php stuff thats getting increasingly unhappy about the stock c6 php...
ok, I've installed php54-1.1-5.el6.centos.alt.x86_64 ... if I run
`scl enable php54`, will that connect it up to my existing apache, so it just works, or will that blow the heck out of everything on my host, or something else? I'm currently using php-5.3.3-46.el6_7.1.x86_64
Since this is becoming a recurring topic as EL6, and now EL7, begin to show their age I did a write up on the options and how to use them today:
Am 04.06.2016 um 00:47 schrieb James Hogarth:
Since this is becoming a recurring topic as EL6, and now EL7, begin to show their age I did a write up on the options and how to use them today:
Thank you very much for this. Very useful.