Broken FreeBSD

[Washington Odhiambo]

Looks like I am in big trouble..

root@gw:/home/wash # pkg upgrade
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
All repositories are up to date.
Checking for upgrades (27 candidates): 100%
Processing candidates (27 candidates): 100%
Checking integrity... done (2 conflicting)
  - gnupg-2.5.20_1 [FreeBSD-ports] conflicts with gnupg1-1.4.23_4 [installed] on /usr/local/bin/gpg
  - gnupg-2.5.20_1 [FreeBSD-ports] conflicts with gnupg1-1.4.23_5 [FreeBSD-ports] on /usr/local/bin/gpg
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
The following 29 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        libdisplay-info: 0.3.0 [FreeBSD-ports]
        ruby33: 3.3.11_1,1 [FreeBSD-ports]
        spirv-llvm-translator-llvm19: 19.1.19 [FreeBSD-ports]

Installed packages to be UPGRADED:
        erlang: 26.2.5.21,4 -> 28.5.0.2,4 [FreeBSD-ports]
        frei0r: 2.5.1 -> 3.2.1 [FreeBSD-ports]
        gnupg: 2.4.9 -> 2.5.20_1 [FreeBSD-ports]
        hwdata: 0.407,1 -> 0.408,1 [FreeBSD-ports]
        libobjc2: 2.2.1 -> 2.3 [FreeBSD-ports]
        lighttpd: 1.4.82 -> 1.4.83 [FreeBSD-ports]
        mesa-libs: 24.1.7_1 -> 26.0.6 [FreeBSD-ports]
        meson: 1.10.2 -> 1.10.2_1,1 [FreeBSD-ports]
        mlmmj: 2.0.1_1 -> 2.1.0 [FreeBSD-ports]
        mutt: 2.3.2 -> 2.3.3 [FreeBSD-ports]
        nginx: 1.30.2_2,3 -> 1.30.2_3,3 [FreeBSD-ports]
        nss: 3.124 -> 3.125 [FreeBSD-ports]
        openssl: 3.0.20,1 -> 3.0.21,1 [FreeBSD-ports]
        p5-CryptX: 0.087 -> 0.089 [FreeBSD-ports]
        p5-Template-Toolkit: 3.102 -> 3.106 [FreeBSD-ports]
        pango: 1.56.4_1 -> 1.57.1 [FreeBSD-ports]
        py311-maturin: 1.13.3_1 -> 1.14.0 [FreeBSD-ports]
        py311-numpy: 2.4.6,1 -> 2.4.6_1,1 [FreeBSD-ports]
        python311: 3.11.15_2 -> 3.11.15_3 [FreeBSD-ports]
        ruby: 3.4.9_1,1 -> 3.4.9_2,1 [FreeBSD-ports]
        spamassassin: 4.0.2_2 -> 4.0.2_3 [FreeBSD-ports]
        vim: 9.2.0461 -> 9.2.0611 [FreeBSD-ports]
        vulkan-headers: 1.4.350.0 -> 1.4.354 [FreeBSD-ports]
        vulkan-loader: 1.4.350.0 -> 1.4.354 [FreeBSD-ports]
        xxd: 9.2.0461 -> 9.2.0611 [FreeBSD-ports]

Installed packages to be REMOVED:
        gnupg1: 1.4.23_4

Number of packages to be removed: 1
Number of packages to be installed: 3
Number of packages to be upgraded: 25

The process will require 96 MiB more space.

Proceed with this action? [y/N]: y
[ 1/29] Upgrading erlang from 26.2.5.21,4 to 28.5.0.2,4...
===> Creating groups
Creating group 'beam' with gid '372'
/bin/sh: /usr/sbin/pw: Exec format error
pkg: PRE-INSTALL script failed

root@gw:/home/wash # uname -Kr
15.0-RELEASE-p10 1500068
root@gw:/home/wash #

--

Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223

 In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

[How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

[Edward Sanford Sutton, III]

On 6/20/26 03:22, Washington Odhiambo wrote:
> Looks like I am in big trouble..
>
>
> root@gw:/home/wash # pkg upgrade
> Updating FreeBSD-ports repository catalogue...
> FreeBSD-ports repository is up to date.
> Updating FreeBSD-ports-kmods repository catalogue...
> FreeBSD-ports-kmods repository is up to date.
> Updating FreeBSD-base repository catalogue...
> FreeBSD-base repository is up to date.
> All repositories are up to date.
> Checking for upgrades (27 candidates): 100%
> Processing candidates (27 candidates): 100%
> Checking integrity... done (2 conflicting)
>   - gnupg-2.5.20_1 [FreeBSD-ports] conflicts with gnupg1-1.4.23_4

gnupg 2.5 and gnupg1 are no longer able to be installed side by side
per upstream changes as explained in `pkg updating|grep -A11 20260616`.
It is good practice to review output of `pkg updating` as it contains
things to know and actions to take for upgrade steps. It is a pruned
list of what you find when reading /usr/ports/UPDATING; human error and
entry complication could lead to pkg not giving all relevant results so
it may be better to read that file instead.
Not sure if you can get by with putting gnupg1 inside a jail if you
need both at the same time or if passing different parameters when
building the port could help but it might work if few to no things
depend on gnupg1. Long ago I used to build+install as my user into a
folder in my user's directory with something like:

mkdir ~/tmp/`make -V PKGNAME`;mtree -U -f `make -V MTREE_FILE` -d -e -p
~/tmp/`make -V PKGNAME`;make depends PREFIX=~/tmp/`make -V PKGNAME`

followed by:

make install PREFIX=~/tmp/`make -V PKGNAME`

and then a step that you won't care about for a workaround case but was
used when porting to build up a pkg-plist without doing it manually:

/usr/ports/Tools/scripts/plist -Md -m `make -V MTREE_FILE` ~/tmp/`make
-V PKGNAME` > pkg-plist

to setup an isolated install into my user's directory when trying to
work on a port. This was all ran as my normal user if memory serves but
I haven't done it in a long time and these notes likely predate
poudriere, let alone workflows I use now.

> questions.html <http://www.catb.org/~esr/faqs/smart-questions.html>]