Hey dear fellow(s), I'm being quite critical down bellow, but your work is awesome. As a whole. just this message sucks to me. Ok when doing a simple update, message I got is unprecise to me : * Please remember to restart gpg-agent if a different version * of the agent is currently used. If you are unsure of the gpg * agent you are using please run 'killall gpg-agent', * and to start a fresh daemon just run 'gpg-agent --daemon'. 'killall gpg-agent' part I sure do as root user, but 'gpg-agent --daemon', I don't have the knowledge, sorry. Should I execute this for all opened sessions ? Or if it's only with root account, why not provide the complete command for copy/paste ? 'killall gpg-agent && gpg-agent --daemon' Yes I am lazy : suit me ! (but I write bug reports...and love gentoo) Well, and even though my post was intended for above part of the message, this part bellow is not so relevant to me either : * If you wish to view images emerge: * media-gfx/xloadimage, media-gfx/xli or any other viewer * Remember to use photo-viewer option in configuration file to activate * the right viewer. For people that know why you'd like to see gnupg related images (which I think I only guess); those people so, they are very likely to know how to install an image viewer. wrong ? Keep on the good work and enjoy the Sunday ! Arnaudv6 Reproducible: Always Steps to Reproduce: 1.update gnupg
Not sure, I think it depends on if the environment it returns changes; but yes, would be nice to see this clarified on how this applies to multiple sessions.
Well, it is much more complex than that. If you use gpg-agent as daemon you should know how and where it is started, there are lots of configuration options to do so. The important thing to remember is that once executed using --daemon you get the following message: GPG_AGENT_INFO=/tmp/gpg-LbxI52/S.gpg-agent:14258:1; export GPG_AGENT_INFO; This environment variable must be available for applications that are to use the agent. So although you are right that the message does not describe the entire solution, it is consider friendly reminder that daemon need to be restarted as well... If you can provide alternate phrasing that is more generic it would be great.
Marking this as CANTFIX unless some valuable input arrives.
Thanks both for answering. I am very willing to propose a message in an attempt to make it clearer. (even though not a native english speaker), I have no certitude on whether the deamon can be system-wide or session-level. Can you tell me, Alon Bar-Lev, maybe ? regards ArnaudV6
(In reply to Arnaud Vallette d'Osia from comment #4) > Thanks both for answering. > I am very willing to propose a message in an attempt to make it clearer. > (even though not a native english speaker), > I have no certitude on whether the deamon can be system-wide or > session-level. > Can you tell me, Alon Bar-Lev, maybe ? > > regards > ArnaudV6 I am unsure what you refer as 'session'... A daemon uses unix domain sockets to communicate with utilities. Unix domian sockets is accessible to uid/gid who runs the daemon. In order for utilities to know how to locate the unix domain socket, an environment variable (GPG_AGENT_INFO) should be provided. Usually this can be run at X session initialization, then the environment variable is exposed to all applications.
