PHP-upgrade

[Francis GUDIN]

Hi all,

i can only add my voice to Jávorszky's.
We all know this is volunteer work and thankfully use your craft (in my case, since a few months after you announced your fork, Matt).

Living with years old software is ok in my personal setting (i moved my wife's laptop to OpenBSD years ago and i rely on it for tasks that mandate a tiny bit of security, like banking or shopping on the web).
Matters are different in the enterprise. At my job, i've been promoting Dragonfly and running 2 VMs for about 6 years. They host LibreNMS, Zabbix and assume a few other functions where a UNIX host is a handy fit.

This morning i was asked whether they were up to date regarding the PHP vulnerabilities. I could only say that packages weren't available **yet**.
I might be asked in a near future to just rip them off and reinstall my stuff on a loonix.

Sad but true.

Keep up the great work! But perhaps keep in mind that an OS is there first of all to run applications.

Regards,
-- 
Francis GUDIN


3 novembre 2026 08:11 "Jávorszky Balázs" <balazs at gnifanip.info> a écrit:

> Hi Maintainers,
> 
> Unfortunately, we have to use PHP in our production server but php84 is still stuck at 8.4.8.
> FreeBSD upgraded it almost immediately (to 8.4.27, the patchlevel that fixes the infamous
> vulnerability). Furthermore, as per below, the latest change in Avalon (already almost a year old)
> has some inconsistencies in the dependencies graph.
> 
> It looks like as if the development of DragonFlyBSD got stuck or at least the fervor that was
> characteristic even a few years before is gone. I think DragonFly is a sane alternative to FreeBSD
> and, in general, to most unix-like systems and it would be painful now to change it. Can we count
> on it?
> 
> Regards,
> 
> Jávorszky Balázs
> 
> On 8/9/26 16:53, Jávorszky Balázs wrote:
> 
>> Hi,
>> 
>> This is not new but I couldn't use the solutions suggested. The symptom:
>> 
>> root at whateverhost /h/whateveruser# pkg upgrade
>> Updating Avalon repository catalogue...
>> Avalon repository is up to date.
>> All repositories are up to date.
>> Checking for upgrades (340 candidates): 100%
>> Processing candidates (340 candidates): 100%
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> Cannot solve problem using SAT solver, trying another plan
>> pkg: Cannot solve problem using SAT solver
>> upgrade rule: upgrade local libXft-2.3.8 to remote libXft-2.3.8
>> cannot install package libXft, remove it from request? [Y/n]:
>> 
>> This is a production system... What should I do? I don't want to break > the system. I don't even
>> know what "remove it from request" is > supposed to mean.
>> 
>> BTW for us one of the reasons for choosing DragonFLY was the ease of > upgrading the system (as
>> opposed to FreeBSD), together with the very > mature pkg system of from FreeBSD.
>> 
>> Thanks for any help,
>> 
>> Regards
>> 
>> Jávorszky Balázs