Re: [Monotone-devel] Re: Duplicate keys

[William Uther]

On 08/03/2007, at 7:19 AM, Graydon Hoare wrote:

> William Uther wrote:
>
> > mtn: warning: ignoring bad signature by
> > 'address@hidden' on
> > 'address@hidden:YXUuY29tLm5pY3RhLmR 
> > nYw==]'  I was hoping that the bad rev would eventually be ignored  
> > once
> > evveryone moved past it, but I just checked out a new workspace, and
> > it gave that warning too.  Is there an easy way to make that revision
> > go away, or does it require 'mtn kill_rev_locally' on every db in the
> > cloud?
>
> Wait, is it a bad rev or a bad cert? Why kill the rev if you just  
> have one bad cert stuck on it?

It looked like set of bad certs - all for the one rev.  Certainly,  
the person who committed the rev could re-sign it all, but the code  
had already been moved using diff/patch somewhere else and committed  
by someone else.  So there are two reasons for killing the entire rev:

i) documentation.  It was easier to find out how to do this than to  
find out how to kill all the certs and re-sign them.  Killing the rev  
gets them all at once.

ii) The commit had already been re-made elsewhere, which means a) I  
didn't need to keep the rev, and b) if I had worked to keep it, it  
would have just lead to conflicts anyway.

Or am I confused?

Will       :-}