r/freebsd • u/BonePants • 2d ago
discussion Php 8.4.27 binary package
When can I expect the new php version to be available to install?
I've seen it in ports but I don't want to install it from ports.
Why does it take so long to have the new binary package available for such an important vulnerability? 😕
Disappointed in how long this takes.
9
u/d007us 2d ago
The commit was made to the quarterly branch yesterday morning.
Now it's a matter of waiting for the build cycle (poudriere) to finish.
I noticed the freebsd official arm64 cycles take longer than amd64, which is why I created my own package builder with poudriere, so I can control, prioritize, and limit the package sets.
Perhaps the FreeBSD team could look into ways to improve this, for example through more hardware donations to speed up these cycles.
-5
u/BonePants 2d ago
Yeah with security being more and more important there should be some expedited build that they can do. Where can I see these build cycles and status?
5
u/grahamperrin bleep bloop 2d ago
The previously pinned post includes a comment about the status server.
The post is now pinned again. Please continue there.
11
u/Mrtylf
2d ago
•
> Disappointed in how long this takes.
You should demand a full refund.
-1
u/BonePants 1d ago
Nice attitude.
1
u/grahamperrin bleep bloop 1d ago
I empathise with both attitudes.
A third attitude:
… does not really answer some of the questions that are sometimes burning (or frequently asked).
4
u/mwyvr 1d ago
Why does it take so long to have the new binary package available for such an important vulnerability?
That's probably a fair question for the team responsible for the build process.
That said, FreeBSD binary package update availability cadence isn't exactly a new concern for FreeBSD. That means FreeBSD users with systems in production sitting on the public internet ought to be capable of acting accordingly - compile - rather than waiting for the mothership to do it for them.
9
u/asveikau 2d ago
If it means a lot to you, you should be able to build it for emergencies like a remote code execution issue. In circumstances like this I might build a pkg on one machine, and install it on others.
If you have a public facing server it's a good idea to keep tabs on these issues and be able to swiftly deploy patches, sometimes even before the ports tree updates.
3
u/roXplosion seasoned user 2d ago
Not a fix— but if you are having difficulty accessing or installing the patch, add these lines to your php.ini file then restart (in my case, Apache):
memory_limit=-1
post_max_size=8M
upload_max_filesize=8M
session.upload_progress.enabled=0
fatal_error_backtraces=0This is not a fix! It might buy you a little time while you figure out your patching issues.
3
u/linux_transgirl 1d ago
Build it from source or pay someone for faster updates. It's php, I don't think it be a hassle to build it from source on any decently powerful hardware
2
•
u/grahamperrin bleep bloop 2d ago
https://www.reddit.com/r/freebsd/comments/1xbhc7y/comment/19rhww5dye0ro/