PHP packages for Ubuntu EOL releases put under paywall
1–10 of 18 posts
Re: PHP packages for Ubuntu EOL releases put under paywall
#2Bad title
Re: PHP packages for Ubuntu EOL releases put under paywall
#3I think the only way to get some people to notice an EOL is to actually make a system stop working.
This is so ingrained that I've actually heard of project managers having specific post-shutdown plans to transition users who only then notice that something happened.
Re: PHP packages for Ubuntu EOL releases put under paywall
#4This is pretty much how it's always been, LTS gets 5 years of support, then after it goes EOL you can pay Canonical for backported security updates to important packages.
What I'm not clear on is the relationship(s) between:
* Canonical's LTS lifecycle/extended support scheme,
* the linked deb.sury.org repository,
* and https://www.freexian.com/lts/php/
It sounds like deb.sury.org is voluntarily halting _their_ PHP packaging for the EOL Ubuntu release, and recommending this alternative vendor Freexian instead (why not recommend Canonical ESM, do they not do PHP?)
The claim being that "it's not possible to build the packages any more" but I'm not sure why this would be, necessarily. More a technicality because the upstream distro will be gone/paywalled so a downstream PPA can't reasonably provide support? But then how is the other vendor doing it?
(Looking closer, Freexian's PHP packager appears to be the same guy running deb.sury.org so while it _is_ turtles all the way down, none of this seems unreasonable to me)
Re: PHP packages for Ubuntu EOL releases put under paywall
#5Throwaway for obvious reasons.
I can sympathise the maintainer thoughts but only up to a certain degree. In a perfect world we would all be able to plan and upgrade accordingly on time and without any hiccups but this is not always the case.
We've actually been bitten by this and scrambling to find a solution as we are still running Ubuntu 18.04 on AWS OpsWorks (this is actually EoL and will be shut down next year).
Migrations steps are being planned but we still need to retain some services until we are done. This PPA worked just fine a couple of days ago, so paying Freexian just for the time we need for completing the migration seems kind of a stretch, for lack of a better word.
Does anyone know where to find a mirror of this (or even .deb files)? We could self host it for our own internal use until the migration is complete.
Thank you.
Re: PHP packages for Ubuntu EOL releases put under paywall
#6Throwaway for obvious reasons. I can sympathise the maintainer thoughts but only up to a certain degree. In a perfect world we would all be able to plan and upgrade accordingly on time and without any hiccups but this is not always the case. We've actually been bitten by this and scrambling to find a solution as we are still running Ubuntu 18.04 on AWS OpsWorks (this is actually EoL and will be shut down next year).…
Am I misreading this, or would you have to pay €250?
If so, why wouldn't you just pay?
I can see it being a question for the higher tiers where it's €10k or more.
Re: PHP packages for Ubuntu EOL releases put under paywall
#7Bad title
Yeah the title reeks of editorializing to ride the coattails of the rhel drama.
This is just the already known EOL policy acting as expected.
Re: PHP packages for Ubuntu EOL releases put under paywall
#8Throwaway for obvious reasons. I can sympathise the maintainer thoughts but only up to a certain degree. In a perfect world we would all be able to plan and upgrade accordingly on time and without any hiccups but this is not always the case. We've actually been bitten by this and scrambling to find a solution as we are still running Ubuntu 18.04 on AWS OpsWorks (this is actually EoL and will be shut down next year).…
If you still have running instances you may be able to pull the packages from apt's cache in /var/cache/apt/archives/*.deb.
From there you could host your own private repo. I've used Aptly to do this easily.
Re: PHP packages for Ubuntu EOL releases put under paywall
#9Throwaway for obvious reasons. I can sympathise the maintainer thoughts but only up to a certain degree. In a perfect world we would all be able to plan and upgrade accordingly on time and without any hiccups but this is not always the case. We've actually been bitten by this and scrambling to find a solution as we are still running Ubuntu 18.04 on AWS OpsWorks (this is actually EoL and will be shut down next year).…
If you still have running instances you may be able to pull the packages from apt's cache in /var/cache/apt/archives/*.deb. From there you could host your own private repo. I've used Aptly to do this easily.
Yeah, that was my original idea but that folder is actually empty on our instances.
Not sure why, my best guess is that Chef is automatically cleaning that up as a last step.
Re: PHP packages for Ubuntu EOL releases put under paywall
#10I don't understand the post title. Ondřej does this in his free time, you're not entitled to his labor. LTS only lasts 5 years, you shouldn't be building out new systems on such an out of date OS. If your business processes depend on 18.04, then paid support makes sense.