. . .There is no i386 indicated (as expected).
The first release candidate build of the 15.0-RELEASE release cycle is now available.
Note: Due to a problem affecting VM image builds, we anticipate building an expedited 15.0-RC2.
Installation images are available for:
o 15.0-RC1 amd64 GENERIC
o 15.0-RC1 powerpc64 GENERIC64
o 15.0-RC1 powerpc64le GENERIC64LE
o 15.0-RC1 armv7 GENERICSD
o 15.0-RC1 aarch64 GENERIC
o 15.0-RC1 aarch64 RPI
o 15.0-RC1 aarch64 PINE64
o 15.0-RC1 aarch64 PINE64-LTS
o 15.0-RC1 aarch64 PINEBOOK
o 15.0-RC1 aarch64 ROCK64
o 15.0-RC1 aarch64 ROCKPRO64
o 15.0-RC1 riscv64 GENERIC
o 15.0-RC1 riscv64 GENERICSD
. . .i386?
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, aarch64, and riscv64 architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
. . .i386?
=== OCI Container Images ===
OCI container images are available for the amd64, i386, aarch64, and riscv64 architectures, and can be found at
. . .i386?
=== Upgrading ===
The freebsd-update(8) utility supports binary upgrades of amd64, i386,
and aarch64 systems running earlier FreeBSD releases. Systems running
earlier FreeBSD releases can upgrade by first installing any updates for
the currently running release:
. . .
Colin Percival <cperciva_at_FreeBSD.org> wrote:
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, aarch64, and riscv64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
i386?
. . .
=== OCI Container Images ===
OCI container images are available for the amd64, i386, aarch64, and riscv64 >> architectures, and can be found at
i386?
The freebsd-update(8) utility supports binary upgrades of amd64, i386,
and aarch64 systems running earlier FreeBSD releases. Systems running
earlier FreeBSD releases can upgrade by first installing any updates for
the currently running release:
. . .
i386?
On 11/17/25 14:02, Mark Millard wrote:A type of thing that may be odd for now for folks trying to test
Colin Percival <cperciva_at_FreeBSD.org> wrote:
=== Virtual Machine Disk Images ===i386?
VM disk images are available for the amd64, i386, aarch64, and riscv64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
. . .i386?
=== OCI Container Images ===
OCI container images are available for the amd64, i386, aarch64, and riscv64
architectures, and can be found at
The freebsd-update(8) utility supports binary upgrades of amd64, i386,i386?
and aarch64 systems running earlier FreeBSD releases. Systems running
earlier FreeBSD releases can upgrade by first installing any updates for >>> the currently running release:
. . .
Editing failure. I have i386 in the template (because we do those on 14.x) and I forgot to remove it in my rush to announce 15.0-RC1.
It has been a long week...
A type of thing that may be odd for now for folks trying to test
15.0-RC1 :
# ping -4 pkgbase.freebsd.org
ping: cannot resolve pkgbase.freebsd.org: No address associated with name
# ping -6 pkgbase.freebsd.org
ping: cannot resolve pkgbase.freebsd.org: Address family for hostname not supported
$ host -t srv _https._tcp.pkgbase.freebsd.org
_https._tcp.pkgbase.freebsd.org has SRV record 1 100 443 cloudfront.aws.pkgbase.freebsd.org.
On 11/17/2025 4:12 PM CST Colin Percival <cperciva@freebsd.org> wrote:
It has been a long week...
On 11/17/25 14:48, Mark Millard wrote:
A type of thing that may be odd for now for folks trying to test
15.0-RC1 :
# ping -4 pkgbase.freebsd.org
ping: cannot resolve pkgbase.freebsd.org: No address associated with
name
# ping -6 pkgbase.freebsd.org
ping: cannot resolve pkgbase.freebsd.org: Address family for hostname
not supported
And yet pkg+https://pkgbase.freebsd.org/ works. :-)
The pkg(8) tool looks up SRV records
$ host -t srv _https._tcp.pkgbase.freebsd.org
_https._tcp.pkgbase.freebsd.org has SRV record 1 100 443
cloudfront.aws.pkgbase.freebsd.org.
and that's the real host. (Right now; we might add other endpoints in
the
future.)
From: Colin Percival <cperciva@freebsd.org>
The pkg(8) tool looks up SRV records
$ host -t srv _https._tcp.pkgbase.freebsd.org
_https._tcp.pkgbase.freebsd.org has SRV record 1 100 443
cloudfront.aws.pkgbase.freebsd.org.
and that's the real host. (Right now; we might add other endpoints in
the
future.)
It causes problem that poudriere can't create jail with pkgbase method
and repository on pkgbase.freebsd.org because poudriere regards "pkg+https://pkgbase.freebsd.org/" as invalid value of -U argument.
On 11/17/25 21:29, Yasuhiro Kimura wrote:
From: Colin Percival <cperciva@freebsd.org>
The pkg(8) tool looks up SRV recordsIt causes problem that poudriere can't create jail with pkgbase method
$ host -t srv _https._tcp.pkgbase.freebsd.org
_https._tcp.pkgbase.freebsd.org has SRV record 1 100 443
cloudfront.aws.pkgbase.freebsd.org.
and that's the real host. (Right now; we might add other endpoints in
the
future.)
and repository on pkgbase.freebsd.org because poudriere regards
"pkg+https://pkgbase.freebsd.org/" as invalid value of -U argument.
This seems like a bug which should get fixed in poudriere, but if
someone
familiar with the code can tell me how we can work around the bug on a temporary basis I'm willing to make it happen.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 12:22:40 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
2 files (2,024K bytes) |
| Messages: | 183,175 |
| Posted today: | 1 |