Rok Mandeljc

> Could be that issue is that one lib is bundled and the other is not. Yep, that seems to be the case on my system; the `libssl.so.1.1.so` is pulled...

Is there a `/usr/lib64/python3.11/lib-dynload/_blake2.cpython-311-x86_64-linux-gnu.so` file on your system? Is it collected into `_internal/lib-dynload`? If it is, what is it linked against (`ldd `)? If I try importing it in python...

Aha, then it's different in your python version vs. mine. In my case, it is linked against ssl and crypto: ``` $ ldd /usr/lib64/python3.11/lib-dynload/_blake2.cpython-311-x86_64-linux-gnu.so linux-vdso.so.1 (0x00007ffeec929000) libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007fcd8e911000)...

Hmmm, that confuses situation somewhat. Can you check the `build//Analysis-00.toc` and find out where `_blake2` was collected from? Or if you run ``` import _blake2 print(_blake2.__file__) ``` in interpreter?

Do you have two python 3.11 installations on that system? RPM-installed (python3.11, python3.11-libs) in `/usr` and something manually installed in `/usr/local`?

So I take it if you try to import `_blake2` using `/usr/bin/python3.11`, it will raise an error?

> Yep XD > > I guess we need to uninstall all instances of Python 3.11.5 from our system? Nah, don't, because then we might lose the chance to debug...

So aside this detour with different python versions, the OpenSSL case is clear: if we collect ssl or crypto shared lib and there are accompanying hmac files, we need to...

> * `uuid` is a built-in, so I expect this problem to occur for plenty of users. Most users don't build with UPX enabled. > Is there a responsible way...

>> Is there a reliable way for pyinstaller to detect modules not compatible with UPX and short-circuit the call to UPX so that this warning does not occur? > We...