libgcrypt | Libgcrypt bindings for Rust | Wrapper library

Your dask and distributed versions have gone out of sync, 2021.4.0 versus 2021.4.1. Updating dask should fix this. Note that you need to ensure that the exact same versions are also in the environment you are using for YARN.

Since you've installed this using brew you are trying to link against libraries built for the Mac. You need to build those libraries for iOS. Note this will typically involve making a fat binary of the different architectures you'll need per library. You can easily test this for fftw and see if the linker errors disappear. Here are some references to build or download a pre-built version.

https://github.com/godock/fftw-build

In theory once you link up against the iOS version, you should see errors like

In my personal setup I have added the signingkey to the user section.

This is normal behavior in CMake. When compiling you binaries the rpath to the dependencies is set in the binary, but stripped when installing it.

By default if you don't change any RPATH related settings, CMake will link the executables and shared libraries with full RPATH to all used libraries in the build tree. When installing, it will clear the RPATH of these targets so they are installed with an empty RPATH. Source

When looking up runtime dependencies the rpath is preferred over the default directories (see https://stackoverflow.com/a/33520976/4181011). But since the rpath was removed from your library it doesn't know about you "out-of-default-directories"-dependencies.

You can manipulate the lookup with LD_LIBRARY_PATH, LD_PRELOAD or by adding the additional path to the lookup directories using ldconfig.

Thanks to advice from marlam I found out that this issue is due to an overly restrictive AppArmor profile for msmtp. I am led to assume that my new OS version is more stringent with regards to usage of msmtp (good thing I guess). Unfortunately this often happens on Debian and Ubuntu and it confuses many users. The commands I've used to solve it are

When we enter npm install puppeteer it installs the latest version which is 3.1.0. It seems something wrong with the latest version.

This is almost certainly a permissions error.

Make sure that whatever file is readable: chmod a+r /opt/gitlab/embedded/service/gitlab-rails/config/database.yml (according to the comments you already did this) AND

Make sure that all the directories are executable, which for directories allows cd'ing into that directory:

Use gcc to link and use -Wl,-Bstatic to tell the linker to prefer linking against static libraries rather than shared ones. Example:

I figured this out (after a little bit of experimentation and luck).

The whole issue smelled like a problem with ld and the linking process of the C libssl library needed by git to use SSH connections.

Pop!_OS is known for including a lot of "development needed" things, so I was positive I had all that (I did).

I looked at the /etc/ld.so.conf.d/ directory. There are a few ".conf" files there. x86_64-linux-gnu.conf pointed at /usr/lib/x86_64-linux-gnu, so I went there to see which libraries matched libssh*.

I found this: