installing FreeBSD 15 from within FreeBSD 14.2-RELEASE

T

tOsYZYny

I downloaded and extracted the distributions base and kernel to my new disk. After copying my /etc/resolv.conf to the new root, mounting devfs, and chrooting, I'm having issues with pkg. I can ping google.com, so network connectivity is there. I normally was able to run pkg update and then do my normal pkg install stuff. This is after attempting to install gsed:

pkg install gsed
Code: 
Updating FreeBSD-ports repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Sandboxed process pid=37154 terminated abnormally by signal: 12
pkg: No signature found
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .. done
Sandboxed process pid=37659 terminated abnormally by signal: 12
pkg: No signature found
FreeBSD-ports-kmods repository is up to date.
All repositories are up to date.
pkg: Repository FreeBSD-ports cannot be opened. 'pkg update' required
pkg: Repository FreeBSD-ports-kmods cannot be opened. 'pkg update' required
pkg: No packages available to install matching 'gsed' have been found in the repositories

I tried:

pkg bootstrap -fy

Code: 
Installing pkg-2.4.2...
package pkg is already installed, forced install
Extracting pkg-2.4.2: .......... done
Bootstrapping pkg from pkg+[URL]https://pkg.freebsd.org/FreeBSD:15:amd64/quarterly[/URL], please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done

But still:
Code: 
pkg update -f
Updating FreeBSD-ports repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Sandboxed process pid=18722 terminated abnormally by signal: 12
pkg: No signature found
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .. done
Sandboxed process pid=19071 terminated abnormally by signal: 12
pkg: No signature found
FreeBSD-ports-kmods repository is up to date.
All repositories are up to date.

I'm scratching my head, it must be something simple.
 
T-Daemon said:
Do not chroot(8), try instead all pkg operations from 14.2 with the pkg(8) -c option:
Rich (BB code): 
     -c ⟨chroot path⟩, --chroot ⟨chroot path⟩
             pkg will chroot in the ⟨chroot path⟩ environment.
Example: pkg -c /chroot_env <pkg_commands>

If there are are still issues, try to build the latest ports-mgmt/pkg from ports for 14.2.
Click to expand...
Hmm, but why? Wouldn't I want to use pkg from the chroot because it'd be targeting the same OS version?
 
Wow, magic, that worked, but why? Wouldn't it be mixing 14.2-RELEASE with 15.0-RELEASE?

NOTE: Once I did that, I could run pkg cmds as expected in the chroot env.
 
tOsYZYny said:
Wouldn't it be mixing 14.2-RELEASE with 15.0-RELEASE?
Click to expand...
No, packages are fetched from the right repository and installed according to their ABI (e.g. FreeBSD:15:amd64, FreeBSD:14:amd64), there won't be any mixing, unless specifically overridden.

/etc/pkg/FreeBSD.conf
Rich (BB code): 
FreeBSD-ports: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",

tOsYZYny said:
NOTE: Once I did that, I could run pkg cmds as expected in the chroot env.
Click to expand...
Hard to tell what happened, perhaps all necessarily parts have settled in their places.
 
It isn't supported afaik, you're meant to update to the latest minor version AND the latest patch version on 14.x before attempting an upgrade. They have been very clear about this being a hard requirement.
 
Even in a chroot? It isn't really an "upgrade" because I'm not using an existing install other than avoiding rebooting to the USB installer. It is a new install.
 
Hmm, another oddity with this setup is, I've been getting "bad system call" errors. I seem to be getting that for a variety of cmds - I used packages and not ports generally. I should note that while my system is old, ~ 2013, it is 64-bit of course.
 
tOsYZYny said:
I downloaded and extracted the distributions base and kernel to my new disk. After copying my /etc/resolv.conf to the new root, mounting devfs, and chrooting
Click to expand...
Ehm, you end up running a 15.0 userland (in the chroot), on a 14.2 kernel this way.
 
You must log in or register to reply here.
Back
Top