I recently tried to upgrade to PHP 7.3 using the deb.sury.org repo, following all the proper guides and installing all of the packages, as well as keeping the stable Debian 7.0 release. When I did this and changed to php7.3, I got a 500 server error, even after restarting the entire server. I tried then to go back to 7.0 and was still receiving the error.
I run Nginx, and not Apache, and would love if someone posted a guide to upgrade for Nginx, because a2dismod and enmod do not work for Nginx (as im sure most know). I have not been able to find a guide for anything other than Apache2.
Just hold off on adding secondary repositories. It just creates problems down the road and opens up vulnerabilities. Debian 10 will be out soon and the issue will be solved.
Agree the issue will just come up again with Debian. Not just here either, but with other software. Still sticking with Debian stable on servers though.
As to those concerned about the security of old Debian softwareā¦Debian issues their own security fixes for software in stable almost as fast as Arch.
Not sure my 2 cents will matter, but I agree with schnappi, I stick with Debian 9 stable which has been serving me well over the years ā¦ each attempt at upgrading PHP lead at some points to issues ā¦ web servers by essence hosts many different things and a PHP upgrade can break stuff that you discover way later because you didnāt take the time to check each and every page of the 150 websites hosted on the machine.
I wonāt say Iād prefer Debian to update more frequently, of course, but Iām more annoyed by PHP updating their product at such a high pace and outdating very recent products ā¦ I see still thousands of websites running PHP 5 ā¦
Anyway, that was not the reason for my message: I just saw that I am suddenly offered to update NC to 16.0.3 (from 15.0.10), and I am still (as you might have guessed) on Debian 9 stable, ie PHP 7.0.33. Is there a place where I can check this, a place where it would be clearly stated that now NC 16 supports PHP 7.0.33 ? Updating to 16 was not an option as of a few days ago unless I am mistaken.
Sorry but I perfectly know about all this (requirements and warnings about running 7.0.33 and I already went to the documentation, thank you) and maybe my question was not phrased properly (english is not my main language)
I am suddenly et very recently proposed with upgrading to 16.0.3 (I was not before until I would say a week ago), so Iām wondering if something changed (and that could explain the doc not being updated).
And if nothing changed I think itās kind of dangerous to propose the upgrade, I know many people who will try and ā¦ ooops. I guess that there are some limits and minimum requirements that have to be met for an installation to propose an upgrade, so I think itās curious that I can now launch that upgrade ā¦ maybe I will get some warnings later during the process (hopefully soon enough
Anyway, maybe Iāll try on a test install to see by myself.
Thanks.
i guess 16.0.3 is the āproductionā release of nc16. so if you set your update channel to production it is offered to you. and yes, thatās a bad bug.
tooltip:
my playbook could be helpfull. just install php 7.0 and nextcloud 15 and do the update manually.
Iām just removing a Nextcloud from Debian because of the ācrusty and oldā PHP issues. Mine is Debian 8 so Iām in even more of a pinchā¦Iāve given up on Linux for old and stable. It stays stable, but way too old unless you backport or upgrade your OS. Save yourself some headache and learn FreeBSD. They have PHP 7.1, 7.2, and 7.3 in their ports and it actually isnāt a death march to upgrade between major and minor releases. Not a direct resolution to the problem, but once you go FreeBSD you donāt wanna go back.
Late answer, sorry.
Iām on the āstableā channel and each time there is a v15 update (letās say 15.0.11 to 15.0.12), that update is offered to me, fine. But as soon as it is applied, I am again offered with a 16.0.4 update ā¦ which gives me the impression that it is possible ā¦ I know itās not possible for me (still being PHP 7.0.33) but Iām afraid somebody will do it ā¦ anyway, moving soon onto Debian 10
There may be good reasons to use FreeBSD (including but not limited to being a U.S. citizen). However, there are good reasons to use Linux (including but not limited to being a EU citizen).
Unfortunately, one cannot ignore tribal aspects and any community effort can degrade into lost debates or other complex issues. Naturally, technical and deployment aspects should always matter most and you are free to choose.
Please be aware of the Unattended Upgrades to keep the computer current with the latest security (and other) updates automatically.
IMHO there was never heard of a ādeath march to upgradeā from the more conservative subset of the several Linux distributions or prove me wrong. Please note for a lasting time the consecutive updates and several migration to quite a bunch of machines (iron and/or VM) from Debian 8 and Debian 9 to the recent Debian 10 gave one no true hassle ever, if I may.
Which is why I recommend FreeBSD, because after 8 years of using Linux, I learned that in many ways, FreeBSD is technically more superior. And if you want to still stick with Linux, still abandon Debian for Devuanā¦but you still fall into Linux pitfalls whether you agree or not. But, it all comes down to your use case. I personally will not recommend Linux for many use cases, some I most certainly will. For *EMP/*AMP stacks, I find FreeBSD the easiest to carry along over longer periods of time without having to deal with dangerous upgrades and difficult rollbacks. Plus the *EMP/*AMP stack has more current software than Debian. Also benchmarks have shown better performance on FreeBSD by large numbers because of how the CPU scheduler works.
Also disable Unattended Upgrades. Bad idea. Iāve had it remove software and enable daemons quietly without my knowledge. Horrible for production environments.
That said, Iāve been using Debian 10 since before its release and, apt, unattended upgrades, and systemd aside, itās a good OS. CentOS is an even better alternative to Debian
Death march: Iāve upgraded Linux from major release to major release enough times to have enough papercuts to conclude that you either fresh install or suffer with unintended consequences somewhere.
@stratacast Ceterum censeo carthaginem esse delendam
This āsuperiorā attitude could screw you, I presume.
Ad infinitum
You are free to choose. However, one has to pay for the lessons learned.
No offense but IMHO one should not fall into the easy trap of blaming others and certainly should not attack a sustainable open and free professional effort for the utter lessons of oneās own apparently failed personal excercises, if I may. Learning is acknowledging oneās failure to improve oneās skills for the next endeavours, I presume.
The NextCloudPi rationale could be worth a reading, although only deducted from Debian and not a standard system, I presume. Some background info and discussion were provided by the two posts of the same thread as was: