On Mon Mar 4, 2024 at 9:13 AM CET, Werner Koch wrote:
> Because all components of gnupg will start gpg-agent and the other
> daemons oin the fly and make sure that only one is started.
Do I understand it correctly that gnupg contains smaller version
of systemd (dependency activation) inside of
On Mon, 4 Mar 2024 14:19, Matěj Cepl said:
> Do I understand it correctly that gnupg contains smaller version
> of systemd (dependency activation) inside of itself and that
No. It is not required. Just don't let systemd start gpg-agent or
dirmngr with option --supervised. If you use ssh just
On Sun, 3 Mar 2024 20:38, Matěj Cepl said:
> 1. Could you please explain why it is racy? Why from all services
Because all components of gnupg will start gpg-agent and the other
daemons oin the fly and make sure that only one is started. Systemd
does not know about this specific start
On Sun Mar 3, 2024 at 10:05 AM CET, Werner Koch wrote:
> > am running it on host with systemd --user services (configuration
>
> Take care, the use of systemd is racy and support will be removed in
> 2.6.
1. Could you please explain why it is racy? Why from all services
only gpg is unsuitable
On Sun Mar 3, 2024 at 10:05 AM CET, Werner Koch wrote:
> > am running it on host with systemd --user services (configuration
>
> Take care, the use of systemd is racy and support will be removed in
> 2.6.
1. Could you please explain why it is racy? Why from all services
only gpg is unsuitable
Hi!
On Sat, 2 Mar 2024 20:54, mc...@cepl.eu said:
> am running it on host with systemd --user services (configuration
Take care, the use of systemd is racy and support will be removed in
2.6.
> gpg: all values passed to '--default-key' ignored
> gpg: keydb_search failed: IPC syntax error
