Philip Paeps <philip_at_freebsd.org> 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 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 > > last Monday March 30. > > > > Any idea how long it might be or how serious the issue is? It looks > > like > > all package builds were completed, though there does appear to have > > been a > > significant jump in failed builds since the previous build (14.1 > > default) > > We upgraded the package builders to recent -CURRENT last week and the > release/X build jails are no longer working. Well: The i386 builds do not crash (reach "done:"). The amd64 ones do crash. Separate issue: pkg 2.1.0 also makes the overall build sequence take much longer, especially on older/slower hardware. For example, beefy17 and beefy18 now take over twice as long. Even beefy21 and beefy22 take over 9 more hrs, over 20% longer. > If we have to reinstall > the builders with older -CURRENT, it's at least a week of work. If > someone can fix the actual bug in -CURRENT, it'll take us about an > hour-ish to upgrade all the builders. > > I don't know what the bug is. But it's easy enough to reproduce: run > poudriere in a release/X jail on -CURRENT and watch it explode. That form of testing appears to presume i386 is not the type of context. For amd64, it is not obvious to me for: Host OSVERSION: 1500035 (prior: 1500028) vs. Jail OSVERSION: 1402000 (prior: 1401000) for what might be the important part, although I'd tend to guess the Host 1500035 part. (Both parts were changed at the same time.) === Mark Millard marklmi at yahoo.com
