I was able to track the spawning down to calls to gpg done from add-apt-repository.
Simplified - that spawns one: gpg --keyserver hkp://keyserver.ubuntu.com:80/ --recv 04450970750A7228C042CD4442C3EB37B6832E30
There already is our "oneshot" in the form of "--no-use-agent" So that does not spawn, but still work as intended.
gpg --no-use-agent --keyserver hkp://keyserver.ubuntu.com:80/ --recv 04450970750A7228C042CD4442C3EB37B6832E30
Need to make the mode and check if other calls later on still spawn it.
Unfortunately that option is a dummy in newer gpg, so I opened a discussion upstream as https://bugs.gnupg.org/gnupg/issue2858.
I was able to track the spawning down to calls to gpg done from add-apt-repository.
Simplified - that spawns one: .ubuntu. com:80/ --recv 04450970750A722 8C042CD4442C3EB 37B6832E30
gpg --keyserver hkp://keyserver
There already is our "oneshot" in the form of "--no-use-agent"
So that does not spawn, but still work as intended.
gpg --no-use-agent --keyserver hkp://keyserver .ubuntu. com:80/ --recv 04450970750A722 8C042CD4442C3EB 37B6832E30
Need to make the mode and check if other calls later on still spawn it.
Unfortunately that option is a dummy in newer gpg, so I opened a discussion upstream as https:/ /bugs.gnupg. org/gnupg/ issue2858.