[krbdev.mit.edu #7695] krb5-1.11.3/1.10.6 - full resync may fail and still result in ulog being updated

[Greg Hudson via RT]

At line 2925, log_ctx->iproprole is set to IPROP_NULL.  At line 2970, the 
conditional won't fire because log_ctx->iproprole is false, and the ulog 
won't be updated.

In 1.11, you do want iproprole to be IPROP_NULL during restore_dump() in 
order to avoid locking the ulog (whereas on master, any iproprole other 
than IPROP_MASTER will do).  However, you'll need to change the 
bookkeeping somehow so that the conditional at line 2970 still fires.