at least not over an existing system: root@builder:~ # pkg install FreeBSD-clibs-dev Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: FreeBSD-clibs-dev: 13.snap20230605162509 [FreeBSD-base] Number of packages to be installed: 1 The process will require 101 MiB more space. Proceed with this action? [y/N]: y [builder] [1/1] Installing FreeBSD-clibs-dev-13.snap20230605162509... [builder] [1/1] Extracting FreeBSD-clibs-dev-13.snap20230605162509: 100% pkg: Fail to rename /usr/include/c++/v1/.pkgtemp.__string.h9UvBQARenW2 -> /usr/include/c++/v1/__string:Not a directory root@builder:~ #
I think it's related to how we creates the -dev package. Since FreeBSD-clibs doesn't have anything in this directory it's not listed in the manifest, and we don't add directories for the -dev packages it seems.
perhaps the question should boil down to: will this trip up people upgrading from 13.2 to 13.3? or only people bootstrapping? if not, we can close it (for bootstrappers: i worked around it, but `rm -rf /usr/include` before making another attempt at pkg install)