Could please someone explain what "Exp builds", "Package builds" and "Qat builds" means on this site?On https://pkg-status.freebsd.org/builds?jailname=144amd64 I can see the quarterly build was started Wed, 21 Oct 2026 19:31:46 GMT
My impression: it dependsIf one is interested in the security of the pkgs, and not the latest updates of the pkgs, should one use quarterly or latest?
For me it seems to be random, which builds are started first and therefore finish first. Could anybody clarify?That seems to be the current focus of the FreeBSD team regarding security for the 14 branch.
Only look at the package builds, those are the ones that will end up in the various repositories. You don't need to worry about the others.Could please someone explain what "Exp builds", "Package builds" and "Qat builds" means on this site?
Yeah, it's gone beyond embarrassing. I mean, FreeBSD was always lagging behind with security patches compared to most Linux distributions, but it's been days now.Nothing for 15.1-RELEASE quarterly...
I’m starting to get worried. Three days, and nothing. I no longer know what to say at work to explain the time taken.
Most of the servers I manage that are on FreeBSD and run PHP are still down because they're far from critical. There's one where after a day I couldn't justify waiting any longer, I've gone the ports route: checked out ports from git on the quarterly branch and installed all PHP packages I have installed on that server from ports. It should be OK since I'm using both the quarterly branch from the ports repo and the quarterly package repo for binary packages, so as soon as the packages are available in the pkg repository I'll just reinstall the lot from there.Should I change the servers in production to "latest"?
What do you recommend doing?
P.D.:
I started a Poudriere build yesterday to try and generate the binaries... I’ll check in a few hours to see if the build has finished.
Linux doesn't take care of their distributions as a whole like FreeBSD does. Linux only takes care of their kernel. FreeBSD is a cohesive, complete system that all works together. When someone else screws things up, they don't rely on some outsiders to guarantee their work.FreeBSD was always lagging behind with security patches compared to most Linux distributions
We suggest you set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector. This setting was already listed as a mitigation in the GHSA-6wmf-4rv5-p3rp advisory for CVE-2026-109619 published on Oct 21st, 2026.
I would imagine that to be correct if one is staying on the same base (quarterly vs latest). If you have been pulling quarterly and switch to latest I think the pkg update -f is almost mandatory.And as it works for me as written in the docs: No, you don't have to run apkg updateprior to apkg upgrade.
Of the three servers I manage, on one that is for testing, I made the change from quarterly to latest like this:I would imagine that to be correct if one is staying on the same base (quarterly vs latest). If you have been pulling quarterly and switch to latest I think the pkg update -f is almost mandatory.
# mkdir -p /usr/local/etc/pkg/repos
# cat << 'EOF' > /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD-ports: {
url: "pkg+https://pkg.freebsd.org/${ABI}/latest"
}
EOF
# pkg upgrade
# pkg info | grep 'php8[2-5]-[0-9].*'
mod_php85-8.5.12 PHP Scripting Language (8.5.X branch)
php85-8.5.12 PHP Scripting Language (8.5.X branch)
Cool. I wonder if pkg upgrade pulls in the "latest" catalogs based on the current config. As in when configured for quarterly, pkg upgrade pulls in that catalog, then if user switches to latest, the next pkg upgrade pulls in the "latest catalog for latest" before running upgrade.Of the three servers I manage, on one that is for testing, I made the change from quarterly to latest like this:
# mkdir -p /usr/local/etc/pkg/repos
# cat << 'EOF' > /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD-ports: {
url: "pkg+https://pkg.freebsd.org/${ABI}/latest"
}
EOF
# pkg upgrade
# pkg info | grep 'php8[2-5]-[0-9].*'
Code:mod_php85-8.5.12 PHP Scripting Language (8.5.X branch) php85-8.5.12 PHP Scripting Language (8.5.X branch)
After running the 'pkg upgrade' command, the new packages were immediately displayed; the 'pkg update' command was not required.