Mercurial > hgsubversion
view tests/fixtures/binaryfiles.sh @ 981:82bbb3428684
pull: save the last pulled revision *after* converting revisions
Otherwise, a KeyboardInterrupt may lead to an unpulled revision being
incorrectly saved as pulled in the lastpulled file. This will lead to
the interrupted revision being incorrectly skipped at the next pull,
leading to an incorrect conversion -- one might even say corrupt.
Due to it's nature of requiring a manual interrupt, this bug is
difficult to test.
author | Dan Villiom Podlaski Christiansen <danchr@gmail.com> |
---|---|
date | Sun, 11 Nov 2012 15:31:19 +0100 |
parents | f1919e1c35bf |
children |
line wrap: on
line source
#!/bin/sh # # Generate binaryfiles.svndump # mkdir temp cd temp mkdir project-orig cd project-orig mkdir trunk cd .. svnadmin create testrepo svnurl=file://`pwd`/testrepo svn import project-orig $svnurl -m "init project" svn co $svnurl project cd project/trunk # Add a regular binary file, and an unflagged one python -c "file('binary1', 'wb').write('a\0\0\nb\0b')" python -c "file('binary2', 'wb').write('b\0\0\nc\0d')" svn add binary1 binary2 svn propset svn:mime-type application/octet-stream binary1 svn propdel svn:mime-type binary2 svn ci -m 'add binaries' # Update them python -c "file('binary1', 'wb').write('a\0\0\nc\0d')" python -c "file('binary2', 'wb').write('b\0\0\0\nd\0e')" svn ci -m 'change binaries' # Remove them svn rm binary1 binary2 svn ci -m 'remove binaries' cd ../.. svnadmin dump testrepo > ../binaryfiles.svndump