Kurt Roeckx dijo [Sat, Aug 08, 2026 at 03:53:48PM +0200]:
Devotee uses the keyring as provided by the keyring maintainers. As far as
I know after you upload it to the keyserver, they have to process it. Once
they have done that, it's available on ftp-master and devotee. I guess
that's also when you can get it from the keyserver. There is a cron job to
copy the files.
Thanks, Kurt. You are correct, we (keyring-maint) do our work on an
approximately monthly basis, trying to be predictable (on the 24th/25th
each month), as “pushing a keyring” is a somewhat-artisanal process that
takes between one and two hours — and we want to pay attention to what
happens, to avoid errors as much as possible.
Now, a question to better understand devotee's end of the issue: I had
understood that devotee checks on the currently active keyring _as each
vote is cast_, is this correct? That means that we could get the following
chain of events:
1. I (being “I” a random DD) send my vote on the 20th
2. My vote is rejected, as my key has expired. I get a rejection mail
almost-immediately.
3. On the 24th, keyring-maint pushes a new keyring
4. On the 25th, I send my vote again (maybe even resend the same mail I
sent originally)
5. Devotee checks the vote against the active keyring, and succeeds
6. I get my positive vote acknowledgement
Is my understanding right? What is the time resolution of the cron job you
mention?
