Ethan Blanton wrote:
> I have pulled down usher on pidgin.im, because we have a bad revision.
> I need EVERYONE who can write to im.pidgin.pidgin to run the following
> command on their databases, if they have pulled at all recently:
>> mtn db kill_rev_locally 4a9bc00413fc26e292eab242a535ba3569a2d760
>> If it says it doesn't know that revision, that's fine -- it just means
> your database isn't tainted. If we don't eradicate this from every
> database which has it, it will just keep cropping up forever more,
> making any operation which works on im.pidgin.pidgin issue a warning,
> so make sure you get all of your databases.
>> I'll bring usher up after a while, when we have hope that this
> revision has died out.
>> Ethan
It would probably be advisable for anyone who developers pull revisions from,
such as Gabriel, to do this as well as an additional measure of protection so
that this revision can't get back into any of our databases.
John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20071103/84d083de/attachment.sig>