TL;DR: I found that I needed to (manually) reinstall
        bind-tools-9.18.28.pkg & bind918-9.18.28.pkg.

For my small installation at home (2 "production" machines; 1 "build"
machine, and some laptops that are (along with the build machine)
treated as "development" machines), I build my own packages and update
the production machines (weekly) -- a process I just completed for this
weekend.

That process was rather more ... eventful ... than usual this time.

On one of the production machines, "pkg upgrade" informed me of the
following:

| The following 5 package(s) will be affected (of 0 checked):
| 
| Installed packages to be UPGRADED:
|         abseil: 20230125.3 -> 20240722.0
|         cpu-microcode-amd: 20240116 -> 20240810
|         curl: 8.9.0 -> 8.9.1
|         protobuf: 24.4,1 -> 24.4_1,1
| 
| Installed packages to be REINSTALLED:
|         protobuf-c-1.4.1_2 (required shared library changed)
| 
| Number of packages to be upgraded: 4
| Number of packages to be reinstalled: 1
| 
| Proceed with this action? [y/N]: y

which seemed reasonable, so I went ahead with it (as shown).

(The other production machine was similar, though not identical.
Saliently, each mentioned that protobuf-c-1.4.1_2 had a "required shared
library changed" and neither mentioned either bind918 or bind-tools.
The latter point I learned was "of interest" in hindsight.)

I then rebooted the production machines; usually (just about every
weekend since July 2015), this is uneventful.

Today, nothing worked; cutting to the chase: named wasn't running,
because named-checkconf failed because a required shared library for
part of bind-tools was missing.

I ended up using scp to copy the *.pkg files from bind918 & bind-tools
from the build machine to the production machines, then running

        pkg add -f /tmp/bind*

on the production machines (& rebooting).  And things seem to be OK once
again.

Peace,
david
-- 
David H. Wolfskill                              da...@catwhisker.org
Someone isn't exactly courting the "childless cat lady" vote.

See https://www.catwhisker.org/~david/publickey.gpg for my public key.

Attachment: signature.asc
Description: PGP signature

Reply via email to