Sorry title cut me off: Upgrading to SP1 - beware PHP will upgrade to 7 without notice - via SUSE Manager 3.0
If you’re not ready or your application doesn’t yet support PHP7 becareful when upgrading to SLES12 SP1. The upgrade will do so without telling you.
Also found the patching will do the same as well, though I found away around that. Use the Online update tool in YAST and you can tell PHP to just upgrade rather than replace 5 with 7. Looking for a way to do this through the SP migration process in SUSE Manager.
This is a major problem in my opinion as many applications are not ready for PHP7 and PHP7 is not mature enough to have la the backward compatibilities worked out yet. Many PECLs will NOT work with PHP7 - so if you need them don’t go to PHP7 until you check to see if they were upgraded to work with PHP7.
SUSE needs to stop the automatic upgrade to PHP7. They need to release PHP5.6 to replace PHP5.5 until there is more support for PHP7.
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:
Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…
On 10/20/2016 11:54 AM, cisaksen wrote:[color=blue]
Sorry title cut me off: Upgrading to SP1 - beware PHP will upgrade to 7
without notice - via SUSE Manager 3.0
If you’re not ready or your application doesn’t yet support PHP7
becareful when upgrading to SLES12 SP1. The upgrade will do so without
telling you.[/color]
I suspect you could update the Zypper locks file on client machines that
you want to remain on a current version, though this locks the package
completely, and not just within a certain set of versions, as far as I know.
From the SUSE Manager side I would also guess you should still be able to
clone a channel, modify the packages within, and then subscribe to TAT
channel as part of your SP Migration process (if using the traditional
SUSE Manager client) which would prevent a change to versions outside of
that cloned channel.
[color=blue]
SUSE needs to stop the automatic upgrade to PHP7. They need to release
PHP5.6 to replace PHP5.5 until there is more support for PHP7.[/color]
You may want to talk to your account/sales representative as they will be
able to direct the product direction more than the forum members who, like
you, are customers, partners, and other interested parties who are
unofficially monitoring things for whatever reason (not product management
necessarily).
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…