Created attachment 235096 [details] pkg bad output Bug happened in a test environment where the pkgbase is from 02/2022, afterwards from this set was upgraded from 1.16.3 to 1.17.99.10 and afterwards 1.18.3 to solve the bug with the @config files in pkgbase. Following pkg versions were tested: 1.16.3 OK 1.17.4 OK 1.17.5 OK (i this same as 1.17.99.9?) 1.17.99.10 NOT OK 1.18.3 NOT OK When installing for example FreeBSD-runtime with the newer pkg in a fresh pkgbase jail, pkg uses lib32 for most libraries instead of lib. For example libfetch-lib32 is used instead of libfetch is used, resulting in pkg in this jail been unusable. Many things are affected, grep was not working, df, ifconfig and so on. for testing i created a empty zfs dataset and used pkg -r ${dataset} ins FreeBSD-runtime with different pkg versions.
Created attachment 235097 [details] pkg good output
I would need the output of pkg -o DEBUG_DEVEL=4 ... (it will be huge)
(In reply to Baptiste Daroussin from comment #2) hmmm Option DEBUG_DEVEL=4 is not working as expected: === root@dssweb02 (pts/3) /home/rosenke 64(2) -> pkg -o DEBUG_DEVEL=4 -r /jail/j9/ ins -f FreeBSD-runtime Updating P10EOL_j12p64-server repository catalogue... P10EOL_j12p64-server repository is up to date. Updating j12p64-pkgbase repository catalogue... j12p64-pkgbase repository is up to date. All repositories are up to date. The following 74 package(s) will be affected (of 0 checked): But i created a output with -dddd is this the same? yes its sadly to huge to upload is as a text file, tried uploading it on a website. pkg.bad.debug_4_v1.17.99.10 https://textbin.net/ozknxkbafk pkg.good.debug_4_v1.17.5 https://textbin.net/91a1zd69vl
pkg -dddd is the same yes, I saved both files it will take time for me to analyse and see what should be fixed.