upgrade to pkg-1.19.1_3 fails

M

markb

Good evening!
FreeBSD Current 14.0 'pkg' fails. My 'update' file:
Code: 
  pkg update -f
  pkg upgrade
  pkg audit -F
  pkg prime-list
When I run the above, I DO get a kernel mismatch (would love to address this also!):
Code: 
Newer FreeBSD version for package zycore-c:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1400092
- running kernel: 1400088
Ignore the mismatch and continue? [y/N]: N
(NOTE: even though I specify N, the update proceeds)

Installed packages to be UPGRADED:
    pkg: 1.19.1_1 -> 1.19.1_3
I then re-run 'update' and get the following errors:
# ./update
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
I run the following to repair 'pkg.'
# portmaster ports-mgmt/pkg
===>>> Upgrade of pkg-1.19.1_3 to pkg-1.19.1_1 complete
Guidance please, and thanks!
MarkB
 
Last edited by a moderator:
One of many reasons why running -CURRENT is not recommended unless you do actual development.

Background here is the import of OpenSSL 3 in -CURRENT. Your installation still has OpenSSL 1.1.1, but the pkg package you download is already built on a newer version and therefore links OpenSSL 3 (which is not found on your host). Funnily, I had the exact opposite issue, after upgrading my -CURRENT shortly after import of OpenSSL 3, the package repositories still had packages linking 1.1.1

There are a few options:
  • Recommended: Install 13.2-RELEASE instead.
  • If you really NEED -CURRENT, upgrade it (this must be done from source)
  • You could also build all ports locally instead of using pkg
 
Good afternoon!
I'm headed to 13.2-RELEASE as per your recommendation.
Sincere thanks!
MarkB
 
Addendum....I'd ALSO appreciate guidance in order to have my AX-210 WiFi to work in 13.2-RELEASE; it did work in 14-Current.
Thanks!
MarkB
 
Hint: this should be a separate thread, it's an entirely different topic. Just for some first info, it seems iwlwifi(4) is the driver needed for this, which is available since 13.1-RELEASE and should auto-load on boot, so first step could be to check whether it is loaded.
 
zirias@ said:
There are a few options:
  • Recommended: Install 13.2-RELEASE instead.
  • If you really NEED -CURRENT, upgrade it (this must be done from source)
  • You could also build all ports locally instead of using pkg
Click to expand...
What is the better way in case that I have some installed packages (nginx, etc…) with a lot of configs, and need to save that configs (but have no dedicated sh script for this…)?

Also shifting to 14.0 - RELEASE would be nice.
 
markb said:
I'm headed to 13.2-RELEASE …
Click to expand...

Alternatively, continue with CURRENT:
  • use pkgbase for minor updates and major upgrades (building from source is no longer required)
  • create, activate then boot a new ZFS boot environment before each update (quite fearless).
You've been using FreeBSD longer than me. CURRENT or STABLE could be fine for someone with your experience.
 
Sergei_Shablovsky said:
What is the better way in case that I have some installed packages (nginx, etc…) with a lot of configs, and need to save that configs (but have no dedicated sh script for this…)?

Also shifting to 14.0 - RELEASE would be nice.
Click to expand...
Do I understand that correctly that you're on 15.0-CURRENT right now? If there's no hard technical reason to keep -CURRENT, I'd indeed recommend to move to a -RELEASE, and 14.0-RELEASE would be the obvious choice, as it's not too far away right now.

Downgrades are not supported, but can be attempted from source. Just checkout the releng/14.0 branch of src and do the typical "upgrade" process (buildworld, buildkernel, installkernel, installworld, etcupdate, delete-old, delete-old-libs, re-build/-install all ports/packages). I can't guarantee an in-place downgrade that way will work, but it's somewhat likely. So, if you're on ZFS, I really recommend creating a new boot environment before attempting this.
 
zirias@ said:
Do I understand that correctly that you're on 15.0-CURRENT right now? If there's no hard technical reason to keep -CURRENT, I'd indeed recommend to move to a -RELEASE, and 14.0-RELEASE would be the obvious choice, as it's not too far away right now.
Click to expand...
Code: 
# freebss-version
14.0-CURRENT

And my question mostly about flawless upgrade to 14.0-RELEASE with NOT TO LOST CONFIGS.

Thank You for kind help!
 
Sergei_Shablovsky said:
And my question mostly about flawless upgrade to 14.0-RELEASE with NOT TO LOST CONFIGS.
Click to expand...
14.0-CURRENT is older than 14.0-RELEASE (and doesn't exist any more, -CURRENT moved to 15 when the 14.0-RELEASE was created) .... therefore, this will be a straight forward upgrade.

All you have to do is switch your src branch to releng/14.0 and then follow the handbook for "upgrading from source".
 
Sergei_Shablovsky said:
And all configs of all other packages would be untouched during the upgrade procedure?
Click to expand...
Upgrading base will never touch anything about ports/packages, they live in /usr/local (with their configs in /usr/local/etc).

Depending on how old your 14-CURRENT installation is, you might have to rebuild/reinstall all your ports/packages (when using binary packages, pkg upgrade -f after the base upgrade is enough). I recommend to do that anyways, just to be sure. Upgrading and/or reinstalling packages also never fiddles with existing configuration files.

Finally, I'd again recommend to create a boot environment first (IF you're using ZFS), so you have a simple rollback in case anything does go wrong ... although that's unlikely.
 
zirias@ said:
Upgrading base will never touch anything about ports/packages, they live in /usr/local (with their configs in /usr/local/etc).
Click to expand...
1.
Thank You for patience and friendly reply!

2.
What if some packages NOT stick to BSD standards and keep some configs OUTSIDE the /usr/local and /usr/local/etc ? This configs files (or CERTAIN STRINGS in system configs files) would be lost during upgrade?
 
zirias@ said:
Finally, I'd again recommend to create a boot environment first (IF you're using ZFS), so you have a simple rollback in case anything does go wrong ... although that's unlikely.
Click to expand...
Please point me on the step-by-step instruction (may be official 26.6 from here https://docs.freebsd.org/en/books/handbook/cutting-edge/ ?) how to make upgrade from -CURRENT to -RELEASE in my CERTAIN CASE.

And how to create boot environment as You recommend.

(Sorry again one time for newbie’s question…)
 
Sergei_Shablovsky said:
So, how to upgrade to 14.0-RELEASE in my certain case?
Click to expand...
Still the same answer: from source. And yes, you will need git to fetch the source in the first place... as of now, you'll probably have to build it from ports, the @tiny flavor is enough.

Once you're on a RELEASE version, you can switch to binary upgrades using freebsd-update(8) if you want, but as long as you're on CURRENT, source is the only way.
 
You must log in or register to reply here.
Back
Top