From mbzadegan at gmail.com  Mon Nov  2 18:49:12 2026
From: mbzadegan at gmail.com (Sayed Mohammad Badiezadegan)
Date: Mon, 2 Nov 2026 19:49:12 -0700
Subject: Fwd: [DragonFlyBSD/DeltaPorts] PR run failed: Build on Pull Request -
 science/quest: Add QuEST 4.3.0 (acd8415)
In-Reply-To: <DragonFlyBSD/DeltaPorts/check-suites/CS_kwDOAGJDas8AAAAXZRWW9Q/1793595760@github.com>
References: <DragonFlyBSD/DeltaPorts/check-suites/CS_kwDOAGJDas8AAAAXZRWW9Q/1793595760@github.com>
Message-ID: <CADMcpTadpDUsdbwJQYLm65sLf7PjPfQiTTBkQ9vrU7fM7X8ENQ@mail.gmail.com>

Hello maintainers,

I noticed that the GitHub Actions workflow for this PR expired while
awaiting approval.

The QuEST 4.3.0 port has already been built and tested successfully on
DragonFlyBSD 6.5-DEVELOPMENT, as documented in the PR description.

Could someone please review the contribution and restart or approve the CI
workflow when convenient?

Thank you for your time and consideration.

---------- Forwarded message ---------
From: Mohamad Badiezadegan <notifications at github.com>
Date: Sun, Nov 1, 2026 at 10:03?PM
Subject: [DragonFlyBSD/DeltaPorts] PR run failed: Build on Pull Request -
science/quest: Add QuEST 4.3.0 (acd8415)
To: DragonFlyBSD/DeltaPorts <DeltaPorts at noreply.github.com>
Cc: Ci activity <ci_activity at noreply.github.com>



[image: GitHub] [DragonFlyBSD/DeltaPorts] Build on Pull Request workflow
run

  Build on Pull Request: No jobs were run

View workflow run
<https://github.com/DragonFlyBSD/DeltaPorts/actions/runs/37094967431?email_source=notifications&email_token=ACPKTBBJHZTHILZLF7LCJSD5XAIQJA5CNFSNUACDM5UWIORPF5TWS5BNNB2WEL2DNBSWG22TOVUXIZKFOZSW45CON52GSZTJMNQXI2LPNYXTCMBQGQ4DAMJWGE2TENJFGNBDCNZZGM2TSNJXGYYKM4TFMFZW63VAUVSXMZLOOS2WG427O5XXE23GNRXXOX3SOVXF6Y3MNFRWW>




?
You are receiving this because you are subscribed to this thread.
Manage your GitHub Actions notifications
<https://github.com/settings/notifications?email_source=notifications&email_token=ACPKTBHNNYLA5LV3VB4UBXD5XAIQJA5CNFSNUACDM5UWIORPF5TWS5BNNB2WEL2DNBSWG22TOVUXIZKFOZSW45CON52GSZTJMNQXI2LPNYXTCMBQGQ4DAMJWGE2TENJFGNBDCNZZGM2TSNJXGYYKM4TFMFZW63VAUVSXMZLOOSYWG427ONSXI5DJNZTXGX3DNRUWG2Y>


GitHub, Inc. ?88 Colin P Kelly Jr Street
<https://www.google.com/maps/search/88+Colin+P+Kelly+Jr+Street++San+Francisco,+CA+94107?entry=gmail&source=g>
?San Francisco, CA 94107
<https://www.google.com/maps/search/88+Colin+P+Kelly+Jr+Street++San+Francisco,+CA+94107?entry=gmail&source=g>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20261102/01d42496/attachment-0001.htm>

From balazs at gnifanip.info  Mon Nov  2 23:11:05 2026
From: balazs at gnifanip.info (=?UTF-8?B?SsOhdm9yc3preSBCYWzDoXpz?=)
Date: Tue, 3 Nov 2026 08:11:05 +0100
Subject: PHP-upgrade
In-Reply-To: <1a08f7ab-6bc0-4102-a5de-71969c367943@gnifanip.info>
References: <1a08f7ab-6bc0-4102-a5de-71969c367943@gnifanip.info>
Message-ID: <46cb7724-13bf-4be0-a059-6b96de99beb9@gnifanip.info>

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

From fgudin+dfbsd at bsdbellule.fr  Tue Nov  3 01:36:53 2026
From: fgudin+dfbsd at bsdbellule.fr (Francis GUDIN)
Date: Tue, 03 Nov 2026 09:36:53 +0000
Subject: PHP-upgrade
In-Reply-To: <46cb7724-13bf-4be0-a059-6b96de99beb9@gnifanip.info>
References: <46cb7724-13bf-4be0-a059-6b96de99beb9@gnifanip.info>
 <1a08f7ab-6bc0-4102-a5de-71969c367943@gnifanip.info>
Message-ID: <efb31f2674e72d2d2d650be0d08c2c65@bsdbellule.fr>

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

From aly at aaronly.me  Tue Nov  3 02:00:59 2026
From: aly at aaronly.me (Aaron LI)
Date: Tue, 3 Nov 2026 18:00:59 +0800
Subject: PHP-upgrade
In-Reply-To: <efb31f2674e72d2d2d650be0d08c2c65@bsdbellule.fr>
References: <46cb7724-13bf-4be0-a059-6b96de99beb9@gnifanip.info>
 <1a08f7ab-6bc0-4102-a5de-71969c367943@gnifanip.info>
 <efb31f2674e72d2d2d650be0d08c2c65@bsdbellule.fr>
Message-ID: <ee431f37-1041-49c4-8ed7-4f21abaa7b23@aaronly.me>

Hello.

Thank you for the feedback.

We're building the latest packages for the freebsd-ports 2026Q4, for 
both v6.4 release and the master branch. The packages for master branch 
are already in good shape, but there may be more failures for 6.4 
release as it's already quite old. We're trying to make the packages 
available to the public as soon as possible; should be ready in a few days.

On the other hand, I'll try to backport a few more fixes to 6.4 release 
and we can later quickly release the v6.4.3.

The dports/packages failures have been the major blocker for releasing 
v6.6. We're really lacking the manpower and help in this regard. Once 
the dports/packages are in good shape, I believe it's time for the v6.6 
release.

Thank you all.

Bests,
Aaron


On 11/3/26 5:36 PM, Francis GUDIN wrote:
> 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,

> 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



From liweitianux at live.com  Tue Nov  3 02:05:41 2026
From: liweitianux at live.com (Weitian LI)
Date: Tue, 3 Nov 2026 18:05:41 +0800
Subject: PHP-upgrade
In-Reply-To: <efb31f2674e72d2d2d650be0d08c2c65@bsdbellule.fr>
References: <46cb7724-13bf-4be0-a059-6b96de99beb9@gnifanip.info>
 <1a08f7ab-6bc0-4102-a5de-71969c367943@gnifanip.info>
 <efb31f2674e72d2d2d650be0d08c2c65@bsdbellule.fr>
Message-ID: <OS3PR01MB10154FBED2893B97135797A5EC2692@OS3PR01MB10154.jpnprd01.prod.outlook.com>

Hello.

Thank you for the feedback.

We're building the latest packages for the freebsd-ports 2026Q4, for 
both v6.4 release and the master branch. The packages for master branch 
are already in good shape, but there may be more failures for 6.4 
release as it's already quite old. We're trying to make the packages 
available to the public as soon as possible; should be ready in a few days.

On the other hand, I'll try to backport a few more fixes to 6.4 release 
and we can later quickly release the v6.4.3.

The dports/packages failures have been the major blocker for releasing 
v6.6. We're really lacking the manpower and help in this regard. Once 
the dports/packages are in good shape, I believe it's time for the v6.6 
release.

Thank you all.

Bests,
Aaron

PS. Resend the mail because my previous mailbox was blocked by Outlook. 
Sorry for the noise.


On 11/3/26 5:36 PM, Francis GUDIN wrote:
> 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,

> 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



-- 
Weitian