Jani-
Could you please post the URL for that info?
As for the fact that OGR-24 is NOT complete, I think that I can shed some light on that.
As all OGR crunchers know, the OGR-25 stubs are bigger, and there is much more of them. When OGR-24 stubs had been issued, OGR-25 stubs started to be issued. The order in which stubs were crunched came into play. Since I use option 3 to keep my in-buffers filled, and my out-buffers flushed, I have been able to find out the order.
I had started each client with the default of 0, which is 25 stubs. Theoretically with the default settings you would complete 24, and then update with the keyserver while the 25th was working. No stubs would be caught in your in-buffer with new work added to them.
Realizing that it would take several weeks for some of these clients to complete these 25 WUs, I cut down the number. As they munched down and flushed this stale work, OGR-24 work started appearing. As I found out, the munch order is the lowest number of the stub, NOT whether the work is OGR-24 or 25 as a precedence.
That is why OGR-24 blocks continue to trickle in, as their turn comes up in the machines whose in-buffers had OGR-25 stubs dumped on top of OGR-24.
viz
BTW, Hi Jani and Nukefarmer. I haven't seen you around much lately.