Kevin Oberman wrote on
Date: Sat, 05 Apr 2025 04:34:21 UTC :
> On Fri, Apr 4, 2025 at 8:11 PM Philip Paeps wrote:
>
> > On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote:
> > > There appear to have been no successful package updates for FreeBSD
> > > since
> > > EOL for 14.1-AMD64. The only b
On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote:
There appear to have been no successful package updates for FreeBSD
since
EOL for 14.1-AMD64. The only build for 142amd64-default that one
appears to
have crashed. As a result, I am seeing a growing list of packages that
are
not getting updat
On Apr 4, 2025, at 09:04, Mark Millard wrote:
> Longest ever prior bulk build of main-arm64-default (HHH:MM:SS): 171:50:51
> (Host OSVERSION: 1500019)
>
> On going bulk build: Built 11348 Remaining 23676(HHH:MM:SS): 85:57:28
>
> This suggests possibly more like 230+ Hrs for the completed
Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this po
[Note: The new main-amd64 (beefy18) example reported is
still building but has taken over 72 hrs longer than any
other prior example. There is a major performance change
involved compared to builds started before April. Slower
hardware makes that more obvious than the fastest
hardware does.]
On Ap
On Fri, Apr 4, 2025 at 8:11 PM Philip Paeps wrote:
> On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote:
> > There appear to have been no successful package updates for FreeBSD
> > since
> > EOL for 14.1-AMD64. The only build for 142amd64-default that one
> > appears to
> > have crashed. As a re
[This is an update of earlier notes, now that I've noticed what
is different for the contexts that not seeing larger time frames
in the Mar-29/Apr-01 bulk build starts of official package builds.]
The context here is the official bulk builds started
2025-Mar-29 (beefy 17 and beefy18) or 2025-Apr-0
Philip Paeps wrote on
Date: Sat, 05 Apr 2025 03:10:26 UTC :
> On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote:
> > There appear to have been no successful package updates for FreeBSD
> > since
> > EOL for 14.1-AMD64. The only build for 142amd64-default that one
> > appears to
> > have crash
Longest ever prior bulk build of main-arm64-default (HHH:MM:SS): 171:50:51
(Host OSVERSION: 1500019)
On going bulk build: Built 11348 Remaining 23676(HHH:MM:SS): 85:57:28
This suggests possibly more like 230+ Hrs for the completed build.
Now (0n going bulk build, first such):
Host OSV
On Mar 21, 2025, at 03:17, Matthias Fechner wrote:
> Dear Mark,
>
> Am 21.03.2025 um 07:06 schrieb Mark Millard:
>> The conflict was created at "Security related update to 0.14.0.":
>>
>> Commit db5b5f1
>> on Mar 6, 2021.
>>
>> mfechner_at_freebsd.org shows on the commit.
>>
>> It added the f
There appear to have been no successful package updates for FreeBSD since
EOL for 14.1-AMD64. The only build for 142amd64-default that one appears to
have crashed. As a result, I am seeing a growing list of packages that are
not getting updated. The last successful build was the final build on 14.1
Kevin Oberman wrote on
Date: Fri, 04 Apr 2025 16:37:47 UTC :
> There appear to have been no successful package updates for FreeBSD since
> EOL for 14.1-AMD64. The only build for 142amd64-default that one appears to
> have crashed. As a result, I am seeing a growing list of packages that are
> not
12 matches
Mail list logo
