02:11:19 I know r38 is no longer LTS, but I just started seeing python3.9 showing "ld.so.1: python3.9: fatal: libc.so.1: version 'ILLUMOS_0.39' not found (required by file /usr/lib/amd64/libpython3.9.so.1.0)". any idea how that could be fixed? 07:21:16 <|cos|> oninoshiko: with least pain, by upgrading? there seem to be no 'ILLUMOS_0.xx' in libc.so.1 on my r38 either, but python-39 still works. later releases has heaps of 'ILLUMOS_0.xx' in libc. dunno more than that, sorry. 07:55:35 oninoshiko - the easiest way is to go back to the old boot environment and `pkg update -f` 16:03:59 Hello hadfl, I logged this issue with zadm, let me know if there is more information I can add :  https://github.com/omniosorg/zadm/issues/140 16:24:03 unfortunately, this is doing this on fresh installs for me. 16:25:17 it might be something off with my private repo... but I don't see how that could happen. it doesn't provide libc or python. 16:40:05 There was a change in r38 a while ago, where python started to require the memrchr() function from libc, and I think that is what you are hitting. 16:41:18 It sounds like you have a newer python and an older libc, which should not be possible - there are some dependencies in place that should stop it happening, although the way it was done was not the best, it should work. 16:44:11 hrm... I'm running a local mirror of the r38 repo. maybe the last time I updated it something didn't make it 16:45:14 It would be interesting to list the versions of `system/library` and `python-39` that are in there 16:47:12 I'll check it in a bit, right now it's running a verify 16:47:56 With local access `pkgrepo -s /path/ list python-39 library` should work 16:48:08 You want omnios system/library 0.5.11-151038.0:20220407T165903Z 18:57:09 omnios runtime/python-39 3.9.17-151038.0:20230614T205750Z 18:57:37 omnios system/library 0.5.11-151038.0:20210427T213425Z 19:06:36 those look consistant with what's on the main repo 19:32:13 there should be a bunch of ILLUMOS_* revs, whether python needs them depends on which symbols in libc it actually uses 19:32:18 you can use pvs(1) to look at stuff like this 19:33:30 so `pvs -sd libc.so.1` will show you which versions exist, and which symbols are within them, `pvs -s python` will tell you what it wants, though deeply unbelievably 19:33:34 (perhaps you linked python with gld?) 19:33:52 or perhaps because it's all in libpython really. 19:34:14 yes, pvs -s libpython3.11.so is more useful 19:34:22 hopefully that brain dump gets you someplace? 20:04:07 oninoshiko, your system/library definitely seems outdated. this is what i get when i query the r38 repo 20:04:15 hadfl@nemesis:~$ pkg list -H -avf -g https://pkg.omnios.org/r151038/core system/library | head -1 20:04:16 pkg://omnios/system/library⊙0:20220407T165903Z --- 22:48:36 whoops, 5.11-151038.0:20220407T165903Z 22:49:58 I did a diff ` 22:50:18 I did a diff `/usr/bin/pkgrepo -s https://pkg.omnios.org/r151038/core/ list | diff -u - <(pfexec /usr/bin/pkgrepo -s /Array-0/pkg/r151038/core/ list)` to check it