Live data from Hacker News

PHP packages for Ubuntu EOL releases put under paywall

github.com

11–18 of 18 posts

Re: PHP packages for Ubuntu EOL releases put under paywall

#11

Throwaway 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).…

Same boat here. OpsWorks had been communciating with us that support for 20.04 was being worked on up until the entire service was EOL’d.

We have long had working builds for 20.04 but can’t run them on OpsWorks, and now we can’t build OpsWorks images.

This will get interesting. Any idea what service you’re transitioning to?

Re: PHP packages for Ubuntu EOL releases put under paywall

#12
post #6

Throwaway 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.

We are actually considering to pay them but we still need to justify the expense and ask for approval to our finance team. It might take a while (both our side and probably theirs too).

Setting up a mirror would be trivial instead. I'm not asking by any means any support or time from him, even a ZIP file hosted on GitHub Releases (where bandwidth is "free") would've worked.

Re: PHP packages for Ubuntu EOL releases put under paywall

#13

Throwaway 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).…

Same boat here. OpsWorks had been communciating with us that support for 20.04 was being worked on up until the entire service was EOL’d. We have long had working builds for 20.04 but can’t run them on OpsWorks, and now we can’t build OpsWorks images. This will get interesting. Any idea what service you’re transitioning to?

There's actually a guide for migrating to SSM Application Manager but I'm not a fan of that (or Chef at all anyway): https://docs.aws.amazon.com/opsworks/latest/userguide/migrat...

We're just working on containerizing everything and then migrate to ECS or EKS.

Re: PHP packages for Ubuntu EOL releases put under paywall

#16
post #6

Earlier quoted context omitted.

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.

We are actually considering to pay them but we still need to justify the expense and ask for approval to our finance team. It might take a while (both our side and probably theirs too). Setting up a mirror would be trivial instead. I'm not asking by any means any support or time from him, even a ZIP file hosted on GitHub Releases (where bandwidth is "free") would've worked.

Paying the €250 is surely cheaper than any amount of you or your teams time to set up your own mirror of the old files? And would be done in a few minutes compared to multiple hours or days.

Re: PHP packages for Ubuntu EOL releases put under paywall

#17
post #10

I 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.

No one is entitled to his labor. But they are entitled to complain about a dick move. After doing his labor, he's choosing to do extra labor (going out of his way to delete old packages) for the sole reason of preventing people from accessing the packages he already built and deployed previously. This would be like Python foundation deleting the download links for Python 2.7 from python.org, or npm unpublishing old packages. Why?

And FYI, not everyone has a need to stay on a supported distro. We don't all run public-facing web services. A system on a secure LAN could run for the next 200 years and it wouldn't matter that Canonical or PHP stopped releasing security updates.

Unless there's a size limit to his Launchpad repos I'm not aware of, he simply has no excuse other than being an arrogant authoritarian.

Re: PHP packages for Ubuntu EOL releases put under paywall

#18
post #7
post #2

Bad 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.

No it's not editorialized. When something goes EOL, you're not supposed to delete the existing packages to force people to pay for new ones, as this guy did.

If people could still access the already-released free packages, then you'd have a point.

Post reply on HN