Date: Fri, 22 Sep 2023 22:55:31 +0000 From: Glen Barber <gjb@freebsd.org> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Cc: FreeBSD Release Engineering Team <re@freebsd.org> Subject: Update on 14.0-RELEASE Message-ID: <20230922225531.GT1219@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
--A/2QVx3Okwt4+LIK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline We will likely need at minimum a fourth BETA build for the 14.0-RELEASE cycle. As was just announced, BETA3 is now available. There are some known outstanding issues: 1) freebsd-update(8) has previously failed to upgrade from 13.x and earlier due to a file name that had been replaced with a directory of the same name. A patch for this is under testing. 2) FreeBSD arm64/aarch64 EC2 AMIs have been failing to build properly, presumably due to lang/rust build failures leading to the ec2-scripts package from being prevented to be available. The last 15.0-CURRENT snapshots seem to have this resolved, so hopefully it is also resolved for what will eventually be the 'release_0' package set for 14.0-RELEASE, but that is still over a week away. 3) There are no "official" FreeBSD base packages available. I have been occupied with external factors preventing me from having cycles available to look into this without interruption, but I think I am going to err on the side of caution and have a manual package set run available via https://download.freebsd.org/ somewhere within the version, architecture, and machine type namespace. 4) Vagrant images fail to upload due to an incorrect target following the addition of ZFS images. This is another issue where I have personally been blocked/blocking progress. 5) The 'ftp-stage' target does not currently account for ZFS virtual machine images. I again have this in my queue. I do not know if I necessarily care too much about this for 14.0-RELEASE, since all virtual machine images are within the 'Latest/' directory namespace for all builds, but I am intent on fixing it. 6) The ZFS-root EC2 AMIs panic a few seconds after booting, apparently due to memory corruption in ZFS. Note regarding (3) above: this is not yet done, but the datasets in which the builds were done are preserved. I hope to have at least a few hours this weekend to try to get binary packages for the FreeBSD base system in place, wherever that ends up being. Glen On behalf of: re --A/2QVx3Okwt4+LIK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmUOG2MACgkQAxRYpUeP 4pOPCw/+K8Lod6s+bzgmP08Ata8Ag1VNqpVMhiiMQfhBplChUT3kahJuA9Pbucxq 7w6CEemCJOYm2xeQ7RsesnAl3qvrxOVT9P4/z6zBw737/DMyMy0VgAwNNua9Rn4m iFJrqfohMjPyoiq76N6MM6fN8LzXE8GWo/qAmY/2Z5IA4h78NdUAvT4TieqQl8bB X8exhMMlE0C+C0cA5CXC35urNYsZFDIvrdSF3ps5NORard41md0p+EL8lL/Tsd9N FgtPjeX4fhpuoMaNtXPLSPz2DnMfnzkvvmgC+pQrBJS4CoA7gQ3ibT6x11Ams+gC /qBBwP69i252J7EEHfrpSKOfK9iedMW9x54Ay7MlLUc6n03z8d1dSfptNuTKUBuw RsfCbpCO9HxkyXJGJWQc8Z7dmFhy5l1qYL7djA8B7APQag2kH+BwY+x9lE/Rsk2W Wf9OAFTifMsJKLrYd//HRgRwr9Ldf0zywXIuCqFo8NVwNI7WmcL9rx7avfJ4gqB0 y5GGhK5UaVANe6D4FXqvFa7270T0CL+J51jI7HnY9FmJ3MevhvjRhptr7pcmMpty Lw1HYAcYhTuBEcOWmE00t6syONLfDzlqgbJbIKbOWjm2aBE+GmBcoOW2WckQ7kHr yEpsE5hdrtjSAjWw7EV+5LHwbxpu7Adf16ubodTDCHPPIw4X67U= =967b -----END PGP SIGNATURE----- --A/2QVx3Okwt4+LIK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230922225531.GT1219>