On Thu, Oct 24, 2013 at 8:41 AM, Mirosław Zalewski <mini...@poczta.onet.pl> wrote: > I decided to use violence and removed my binrepo directory and then > extracted bibisect.tar.lzma content again.
:-) > After following these guides step-by-step: > https://wiki.documentfoundation.org/QA/HowToBibisect > http://flosmind.wordpress.com/libreoffice-bisecting/ > http://www.youtube.com/watch?v=SA88flop4MM > > Bibisected LibreOffice is starting as it should be and I have managed > to track down commit I was looking for. Good, good. > > I am not sure why it did not work before and does work now. > It might be that git checkout command is neccessary, and Florian's blog > post does not mention it. > Or maybe I have messed up my repo to the state that git tracking > mechanism and source tree were out of sync. That's possible. IIRC, Joren said that he had a problem with his git tree being stuck in a weird state. Joren -- did you ever figured out what went wrong with your bibisect repo, and have you managed to repair it? I wonder if it would be possible to wipe out local changes in the git repo just using zsync commands? (I'm not so familiar with the way that zsync works) > > If anyone knows why it might have happened, please share - it might be > useful information for future bibisecters. Bjoern might have some insight here, but it might just be gremlins in the repo. It's unfortunate that the repo is such a large re-download if/when it breaks. --R _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/