Instructions on the page https://wiki.documentfoundation.org/QA/Bibisect/Linux do not describe, how to use the lo-linux-dbgutil-daily repository. I currently have a problem with 5.0 and would like to bibisect it prior to submitting a bug - I do not know how. The instruction, which are ok for other sets do not help in this case. The problems: git bisect start latest oldest does not check out anything. It looks like 'latest' is not defined. Instead, I tried git bisect start 2b392af9c8f54629e3a3a98a8c92fa5af1c6722f oldest where 2b392af9c8f54629e3a3a98a8c92fa5af1c6722f is in the output of 'git log'. I got: HEAD is now at 2b392af... 2015-05-20: source-hash-90e2dabb8d0bb5382234be776c2ad0e2d5d9e224 2b392af9c8f54629e3a3a98a8c92fa5af1c6722f was both good and bad Still no checkout git reset --hard oldest checks the stuff out. However, ./opt/program/soffice hangs. Pls, update the instruction at //wiki.documentfoundation.org/QA/Bibisect/Linux thanks m
Kendy: thought you might be interested in this one.
Robinson has been working on these - let's see if he has thoughts.
(In reply to Joel Madero from comment #2) > Robinson has been working on these - let's see if he has thoughts. Let's see... Miklos is the maintainer of the dbgutil repository (https://wiki.documentfoundation.org/QA/Bibisect/Linux#dbgutil) and should be able to answer some basic questions. I don't currently have a local copy of this repository but I'll download one this week and take a look. Sounds like a reasonable inquiry, so tossing into NEW for now.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I added a note on how to get the latest/oldest commit hashes in general when they aren't defined. The wiki page could use an overhaul/cleanup, but I don't feel being up to that. At least finding this information should be somewhat easier in the future, so closing this as fixed.