Hi Mark, I can't speak to 1) but let me explain the cause of your second problem. Mark Grant <m.grant.prg@gmail.com> writes:
2) This is the second problem. I established that the key had been refreshed on opensuse.org and now had a mid-2023 expiry date so I thought re-downloading it using the curl command in the instructions should do the trick. The command worked OK but the curl command had changed from using a target keyring of "home:m-grant-prg.gpg" to "home_m-grant-prg.gpg". So the curl command did not overwrite the old keyring. The end result was that the old expired key was still found and repository actions still errored out. The solution I have suggested to the user community is to remove the offending keyring.
This change was done in [1] due to the following GitHub Issue[2]. Apparently the old keyring file names would break GPG in some way. When I accepted this PR I did not think of your use-case (updating the keyring) and I'm sorry for causing the trouble. The question is how to go from here. Rolling back the change would not only cause the issue mentioned above again, it would also cause the same problem you just experienced in the other direction. Maybe it's better to document this somewhere and suggest what you did: removing any old keyring file for the repo. What do you think about that? Best, Alex 1: https://github.com/openSUSE/software-o-o/issues/842 2: https://github.com/openSUSE/software-o-o/pull/843