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!
 
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.
 
You must log in or register to reply here.
Back
Top