[Python-Dev] Buildbots have trouble checking out the repository due to recent changes. (original) (raw)

Alexandre Vassalotti alexandre at peadrop.com
Mon May 12 15🔞46 CEST 2008

On Mon, May 12, 2008 at 3:49 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:

> Well, I guess I really messed up on that one. So, do you have any idea > on how to revert the changes?

If the changes where in a single revision N, do svn merge -rN:N-1 . svn commit -m "revert rN" If they span over several subsequent revisions, use N-k instead. If they span over several revisions with intermediate revisions that you don't want to revert, try multiple merge commands before a single commit; if that fails, revert and commit each range of changes separately.

Yes. That is exactly what I did to revert the changes.

P.S. If you want to get the buildbots back in shape (in case they aren't), build a non-existing branch through the UI (which will cause a recursive removal of the entire checkout), then either wait for the next regular commit, or force a build of the respective branch (branches/py3k or trunk). On Windows, if there is still a python.exe process holding onto its binary, that fails, and we need support from the slave admin.

Thanks for the tip. Now, I just hope that I will never have to use it. ;-)

-- Alexandre

More information about the Python-Dev mailing list