Upgrading to 15.0-RELEASE , the good, the bad, the ugly

free-and-bsd said:
Why doesn't anybody mention the fact, that after freebsd-update install & reboot you get error "can't find libsys.so.7
Click to expand...
Code: 
We've already done what we could (fix the bug and put out an EN).  We've also
clearly documented that you should update your existing system to the latest
patch level before upgrading (this isn't new, because it's not the first time a bug
in freebsd-update broke an upgrade).  But you refuse to read that documentation,
preferring instead to read /usr/src/UPDATING which is intended for people who
update from source, i.e. not you.

So the only problem here is your refusal to read the documentation and follow the
procedure it recommends.  There is no patch for that.
 
free-and-bsd said:
Why doesn't anybody mention the fact, that after freebsd-update install & reboot you get error "can't find libsys.so.7
" and a completely unusable system?
Click to expand...
What version of freebsd did you upgrade from? Since you have root on zfs, you could've (and should've) used boot environment assuming bectl was available.
 
🤣
I used to have 14.2-RELEASE on my Lenovo laptop. Instead of doing the finicky and error-prone freebsd-upgrade(8), for which I've seen more horror stories than I care to link to, I just made a backup of stuff I don't wanna lose, and went for a fresh install of 15.0-RELEASE. Now I'm enjoying it all, it's all up to date, and no version conflicts :P Oh, I even have Plasma Wayland!
 
bakul said:
freebsd-update needs to be made more bullet-proof.
Click to expand...
It seems pretty bullet proof to me, if people read the documentation before using it. We (as a FreeBSD community) should not waste time and effort for those people that don't want to read the documentation.
 
Indeed. But my experience compile and install from source. Don't rely on automated things. Everything works fine. At least on freebsd.
Had some or more linux installs dying. Not knowing what to do.
 
ralphbsz said:
It seems pretty bullet proof to me, if people read the documentation before using it. We (as a FreeBSD community) should not waste time and effort for those people that don't want to read the documentation.
Click to expand...
I am all for it but in my experience most people don't read documentation until *after* they get in trouble! Also, good documentation is hard to write. This is why initial install and upgrade paths should be as idiot-proof as possible. When I upgrade MacOS I don't read documentation (I just make sure there is a backup). Now granted that the upgrade path is easier for a closed system like MacOS. And it is always much harder in a volunteer driven project + the fact there are far too many different hardware setups where things can go wrong. So this is more a wish than anything else!
 
In fairness. the documentation isn't always right. For example, the current handbook explanation of using pkgbase to upgrade won't work. It leaves out a few essential points. They may be covered in other places--for example, the handbook has the wrong location for keys which is covered the release notes, but one also has to add pkg-bootstrap for 15, and I'm not sure where that's covered in official documentation. I would say to bakul, Hi bakul, how are you today? (I believe in starting dialogs with politeness.) Seriously I would say that freebsd-update has been, if not bullet proof, pretty trouble free for quite awhile. I think since 11 or so (the release, not my age, nor the time of day), I've been using it without trouble.
However, I would say to ralphbsz, (again after greeting them and asking how they are), that 14.3 to 15, even using FreeBSD update was problematic on at least one machine, being, I suppose the exception to the rule, though I did, following the upgrade instructions for freebsd-update successfully update my main workstation.
 
scottro said:
In fairness. the documentation isn't always right. For example, the current handbook explanation of using pkgbase to upgrade won't work. It leaves out a few essential points. They may be covered in other places--for example, the handbook has the wrong location for keys which is covered the release notes, but one also has to add pkg-bootstrap for 15, and I'm not sure where that's covered in official documentation. I would say to bakul, Hi bakul, how are you today? (I believe in starting dialogs with politeness.) Seriously I would say that freebsd-update has been, if not bullet proof, pretty trouble free for quite awhile. I think since 11 or so (the release, not my age, nor the time of day), I've been using it without trouble.
However, I would say to ralphbsz, (again after greeting them and asking how they are), that 14.3 to 15, even using FreeBSD update was problematic on at least one machine, being, I suppose the exception to the rule, though I did, following the upgrade instructions for freebsd-update successfully update my main workstation.
Click to expand...
Hello scottro,
How do you do today?
In regards to pkgbase, despite the handbook suggesting to lock packages as a workaround an issue, it at least warns that it's experimental.
And warnings are essential points to know.

26.7.2.1. Major Upgrades​

As pkgbase with FreeBSD 14 is experimental, so is a pkgbase major upgrade to 15. At the time of this writing in some edge-cases the major upgrade removes pkg and therefore segfaults. This is considered a (known issue) for 15.0-RELEASE. To work around this issue, lock pkg before upgrading.
 
I guess this is a place to spam my own page on it, https://srobb.net/fbsd14_15.html, where I cover the steps. Most of them were given me by other people after it wasn't working for me. Once I had the extras figured out, updating with pkgbase turned out to be pretty simple. I don't know if it's a saying or just something I made up, but many things become pretty easy once you know how to do them.

And, Domecq, I'm fine thanks, how about yourself?
 
Charlie_ said:
Code: 
We've already done what we could (fix the bug and put out an EN).  We've also
clearly documented that you should update your existing system to the latest
patch level before upgrading (this isn't new, because it's not the first time a bug
in freebsd-update broke an upgrade).  But you refuse to read that documentation,
preferring instead to read /usr/src/UPDATING which is intended for people who
update from source, i.e. not you.

So the only problem here is your refusal to read the documentation and follow the
procedure it recommends.  There is no patch for that.
Click to expand...
Well I read the errata afterwards. It says, among other things:
Code: 
IV.  Workaround

No workaround is available, but this misbehaviour only applies to using
freebsd-update(8) to upgrade to FreeBSD 15.0; applying security and errata
updates (including this one) within a release branch is unaffected.

V.   Solution

Upgrade your system to a supported FreeBSD stable or release / security
branch (releng) dated after the correction date.

Perform one of the following:
Perform one of the following:

1) To update your system via a binary patch:

Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms,
or the i386 platform on FreeBSD 13, can be updated via the freebsd-update(8)
utility:

# freebsd-update fetch
# freebsd-update install
So which one is ture? Workaround: No workaround available etc?
Or this one: Solution: ...
So yes, my fault of not reading the docs BEFORE, yet... this description looks confusing.

BTW, I did upgrade to the latest patch of 14.3. Because I didn't even realize first that 15.0 was out (didn't read that one either LOL)
 
Here the upgrade went without problems, but after the final reboot X refuses to start (libmd.so.6 not found), and pkg can't find libutil.so.9.

Trying to use my CLI programs reveals a lot more libs missing.

Anyone has an idea how to fix this?
 
meine said:
Anyone has an idea how to fix this?
Click to expand...
Check for inconsistencies with command pkg check -ad.
Find the port that installs a given shared object (.so) with for instance find /usr/ports -iname pkg-plist -exec grep libmd.so {} +. Then upgrade casu quo reinstall that port.
 
Tieks said:
Check for inconsistencies with command pkg check -ad.
Find the port that installs a given shared object (.so) with for instance find /usr/ports -iname pkg-plist -exec grep libmd.so {} +. Then upgrade casu quo reinstall that port.
Click to expand...
ld-elf.so.1: Shared object libutil.so.9 not found, required by "pkg"
 
Code: 
$ cd /tmp
$ fetch  https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/compat14x-amd64-14.2.1402000.20251120_1.pkg
$ tar xzf compat14x-amd64-14.2.1402000.20251120_1.pkg
$ mv -i usr/local/lib/compat/* /usr/local/lib/compat/
What does this output?
elfdump -n /usr/sbin/pkg | grep ABI
 
I think pkg-static is a statically linked version of pkg. If so, it shouldn't need any dynamic libraries like the pkg command does. It may support enough to install the dynamic version of pkg as Alain De Vos pointed out
 
I have bad experience of not having any problem with freebsd-update fetch install , reboot and install again. I think if the install and related system is clean there may not be any problem as the base system is same for all users and not related to packages at all.
 
You must log in or register to reply here.
Back
Top