On Tue, Apr 09, 2019 at 10:19:10AM +0200, Mathias Behrle wrote: > Hi all, > > I have set up an expiry on my GPG key: > - originally set to 2019-04-07 > - updated on 2019-04-08 to 2021-04-06 and pushed to various keyservers > including keyring.debian.org. > > But nevertheless my ballot is rejected, because obviously the old key is used > (s. the error report below). > > What can I do to get my ballot tested against my actual updated key? > > Do I have to wait for a keyring sync of the DD Keyring? When will it happen? > Do > I have to get in touch with someone to get the key synced?
So as already explain, I get a keyring from the keyring maintainers. This is not the same as the one in the archive, but their current working version. If they update it, it also gets updated on things like ftp-master and vote, but that might take a few hours. I think most of this is documented somewhere, but I currently can't find it. In my expierence, they do update the keyring during the voting period because each year some people run into this problem. I suggest you that you send the updated key to keyring.debian.org and contact them in case you have this problem. There can be various reason why people that have the right to vote are not able to do so. If that reason can't be resolved, I'm willing to manually add the vote. I prefer not to do this, and have never done so before. If it really can't be resolved, you can contact the secretary. I will have at least the following rules for such vote casts: - The vote needs to be cast during the voting period. - You should have a good reason why the normal procedure doesn't work for you - I need some way to authenticate you Kurt
