commit | d3715fd4e336da85b1bb08e4677d43e1d98bfc22 | [log] [tgz] |
---|---|---|
author | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | Mon Apr 23 12:45:17 2018 -0400 |
committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | Mon Apr 23 12:45:17 2018 -0400 |
tree | cfaf551993246570731eb3f17b5fcbf9b17fe915 | |
parent | 191d6bc3733ae13eab6ff8bccac87cb323fccbd2 [diff] |
Do lock the repos during fsck/repack Looks like if a repo that is pulled with --mirror is updated in the middle of fsck, it reports scary corruption errors that are false-positive. Lock the repo before repack/fsck and unlock right after to avoid those. Also, a few cleanups and further py3 compatibility. Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>