After upgrade to gnupg 2.3.3 on multiple systems I started to experience issues of connecting to gpg-agent. While gpg-agent is running, when I attempt to send gpg-connect-agent KILLAGENT /bye I run into issue where one of the processes get stuck. In addition to this, when running any gnupg command, I see error message gpg: error reading symlink '/proc/curproc/file': No such file or directory I understand that there is not a lot of information, but I don't see a way to troubleshoot this further. Fixed this by reverting to 2.3.2 sudo pkg install /var/cache/pkg/gnupg-2.3.2.pkg
Looks like issue with /proc is discussed upstream at https://dev.gnupg.org/T5656
There is a commit that seems to fix it: https://dev.gnupg.org/rG4cb44914b57a8db9d2f0d24e11d2b5e6fedc0a87 Maybe we can patch the port until 2.3.4 is released?
Yes please.
Created attachment 229040 [details] Patch for common/homedir.c, bump PORTREVISION in Makefile I tried to make a patch for the port that also bumps the PORTREVISION in Makefile. Tests seem to work okay. With the patch applied, gpg now doesn't complain about missing procfs.
Committed in 7b6ca19a8048. Sorry, forgot to link the PR in the commit message. Thanks for doing the work on this!