On 02/11/2018 04:48 PM, Eli Schwartz via arch-general wrote: > There > have been numerous forum posts, mailing list threads, IRC discussions, > Reddit discussions, Twitter discussions, and for all I know Linux User > Group conventions discussing the issue ad nauseam -- and by this I mean > to say that this raft of discussion across all forms of social media, > happens on an individual level for each new Trusted User, every single > time. Without fail. Thank you for not hacking me :) If there have been social media discussion on it, then I would never see them. I'm 51, not a bird, I don't tweet, etc... When faced with a "this looks like an Arch problem" (or any other distro problem), after 20 years of experience the resounding proper place to address it is to the distros mailing list - to determining if it can be confirmed and a bug is needed, or, for answer, since there will be no other social whatever that knows more about Arch, than Arch. When things that are supposed to be seamless and take place under the hood without user intervention -- don't, for whatever reason, I like to understand why if I'm going to rely on my system. I have never created any key for the keyring so there is no possibility I match the key with a future date problem. I'll search again through the forums to see how to completely dump and restore my arch keyring because --init --updatedb --refresh-key don't work. And, no, I'm certainly not going to trust and social media "Hey, try this..." to fix the problem. -- David C. Rankin, J.D.,P.E.
Attachment:
signature.asc
Description: OpenPGP digital signature
