My original guess at the problem was long and misleading as I didn't know exactly what caused the build failure. Basically all I did was point it out. Have finally figured it out.

Question: Should I delete most of my original guess or add a new comment about what is really happening and leave the old guess there?

Are there any rules for changing comments? Unlike this forum, it seem GitHub allows for a lot more editing

Without knowing for certain which issue you're talking about, it's hard to advise. Why not at least post the issue number here, in your question?

From what you've actually said, I'd say:

Leave the problem that you first encountered visible, for others to read.
Remove all the guesses that turned out to be false trails.
Write a clear statement about what the true solution was. Possibly make that the first thing that people will read, below the initial statement of the problem.

Tell us - here, if you like - if any documentation needs updating, to avoid other people wasting their time as you appear to have done.

And where possible use strikeout to show that text is no longer current

---

Without knowing for certain which issue you're talking about, it's hard to advise. Why not at least post the issue number here, in your question?

From what you've actually said, I'd say:

Leave the problem that you first encountered visible, for others to read.
Remove all the guesses that turned out to be false trails.
Write a clear statement about what the true solution was. Possibly make that the first thing that people will read, below the initial statement of the problem.

I do not normally contribute to issues on GitHub concerning Boinc and was concerned that making a lot or even a few changes in an issue or a comment might be unwelcome. Your advice was what I was looking for: It is OK to remove the false trails and restate the problem clearly.

Tell us - here, if you like - if any documentation needs updating, to avoid other people wasting their time as you appear to have done.

As far as I know, no documentation needs to updating. I am retired and have plenty of time available but am not wasting it. I am sorry if I am wasting your time by asking for advice here. I thought it was appropriate to ask here and not at GitHub.

As far as I know, no documentation needs to updating. I am retired and have plenty of time available but am not wasting it. I am sorry if I am wasting your time by asking for advice here. I thought it was appropriate to ask here and not at GitHub.

I'm in the same boat - retired, and with time on my hands. It's absolutely fine to ask questions here, or at any of the multiple other places where BOINCers hang out - but if you refer in one place to a problem described in another place, it's helpful to tie the two together with a link or a reference number.

As far as I know, no documentation needs to updating. I am retired and have plenty of time available but am not wasting it. I am sorry if I am wasting your time by asking for advice here. I thought it was appropriate to ask here and not at GitHub.

I'm in the same boat - retired, and with time on my hands. It's absolutely fine to ask questions here, or at any of the multiple other places where BOINCers hang out - but if you refer in one place to a problem described in another place, it's helpful to tie the two together with a link or a reference number.

Sent private message about the problem with issue 3347 and just posted an update there