Upgrade to 15.1 Doesn't Proceed

J

jcw

I am following the official instructions for the upgrade to 15.1. pkg upgrade seems to think we are already up to date.

Code: 
# pkg -oABI=FreeBSD:15:$(uname -p) -oOSVERSION=1501000 upgrade -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
FreeBSD-base is up to date.
Checking for upgrades (218 candidates): 100%
Processing candidates (218 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
[root@l1 ~/system.notes]# freebsd-version -kru
15.0-RELEASE-p2
15.0-RELEASE-p2
15.0-RELEASE-p1
[root@l1 ~/system.notes]#

But 15.0 is obviously not 15.1. Seems like this should be trivially easy. Did I miss something?

I did deviate from the instructions in that I upgraded pkg itself before getting started. I had started looking at some older RC instructions before I happened upon the post release date instructions.
 
Don't you need to run freebsd-update to get freebsd-version -kru to the same levels first?

If you don't you are likely to encounter some problems sooner or later.

Once all at the same level you can proceed to upgrade to 15.1-RELEASE and then you can run pkg upgrade.
 
What is the output of pkg repos?
And the content of any file in /usr/local/etc/pkg/repos/?
And, as we are there, the content of /etc/pkg/FreeBSD.conf?
 
Balanga is right here, your safest bet is to use freebsd-update(8). The thing is... pkgbase is still in development (as also mentioned in the handbook) so... there might still be some quirks here and there. Not to mention that as far as I can tell freebsd-update will eventually also support pkgbase, so there's really no need for manual tinkering.
 
ShelLuser said:
Balanga is right here, your safest bet is to use freebsd-update(8). The thing is... pkgbase is still in development (as also mentioned in the handbook) so... there might still be some quirks here and there. Not to mention that as far as I can tell freebsd-update will eventually also support pkgbase, so there's really no need for manual tinkering.
Click to expand...
He uses pkgbase, freebsd-update should refuse to run. And if it run anyway, it will damage the system.
 
jcw
From the instructions page
Before upgrading to a new release, ensure the installed system is up to date
Click to expand...
jcw said:
[root@l1 ~/system.notes]# freebsd-version -kru
15.0-RELEASE-p2
15.0-RELEASE-p2
15.0-RELEASE-p1
Click to expand...
Your system has not been updated for a long time.
Don't know if it will help but it's a start.
In case it doesn't do anything, reinstall all packages pkg upgrade -f, then try again to upgrade to 15.1.

ShelLuser said:
so there's really no need for manual tinkering
Click to expand...
That's the thing with the actual form of pkgbase, it's a bit of tinkering this tinkering that. The user experience will be better with 16 and 17 for sure but for now it is what it is until freebsd-update comes to cover everything for us :)
 
SirDice said:
Yes, OP used the commands to upgrade a pkgbase system, but as it says nothing is installed I'm doubtful it's actually a pkgbase installation.
Click to expand...
I think that there is a problem with pkgbase conversion here. But, if pkgbase had been never used, pkg with -r FreeBSD-base had answered that this repo doesn't exist or something like that. Here, it's enabled.

Maybe, it's time to let the Op answer?
 
Emrion said:
But, if pkgbase never used, pkg with -r FreeBSD-base had answered that this repo doesn't exist or something like that. Here, it's enabled.
Click to expand...
You can enable it, even if you don't actually use it.

jcw what does pkg info -x FreeBSD show?
 
Ok, I mention it in this post. https://forums.freebsd.org/threads/good-news-today.102946/post-763983, but the post was more about Nvidia.
In my case, I had more than one machine, one updated properly the other didn't. The one that didn't had a /usr/local/etc/pkg/repos/FreeBSD-base.conf as well as /usr/local/etc/pkg/repos/FreeBSD.conf and that FreeBSD.conf had the line
Code: 
FreeBSD-base: { enabled: yes }

Renaming the FreeBSD-base.conf file to conf.orig fixed the problem for me. So, if you do have two files in /usr/local/etc/pkg/repos and one is FreeBSD-base.conf, you can try removing or renaming it and seeing if that helps.
 
You must log in or register to reply here.
Back
Top