> On 31/07/2018, at 12:47 AM, Eric S. Raymond <e...@thyrsus.com> wrote: > > Richard Biener <richard.guent...@gmail.com>: >> Ok, so let me ask whether you can currently convert trunk and >> gcc-{6,7,8}-branch >> successfully, ignoring "merges" into them (shouldn't have happened). All >> other >> branches can in theory be converted later if required, right? > > Trunk conversionm is currently broken. That's what makes this serious > problem; > it was working before.
Didn’t you mention the trunk conversion issue was due to a bug introduced into reposurgeon at some date recently as a fix for some other conversion? Can you not roll back to a version of reposurgeon used for the last successful conversion? Assuming you know the date of the last successful conversion, then you can use the reposurgeon version from that date. What were the problems in the last “successful” conversion that led to the subsequent changes in reposurgeon? Were the conversion problems in the last successful conversion major enough that the resultant tree was not usable for trunk and the major development branches: gcc6, gcc7 and gcc8 branches? Or were the issues on older branches? If you are bisecting reposurgeon then would you not search for the date of the message when you had reported successful conversion here on this list (with whatever remaining issues that version had), and use the version of reposurgeon from that date for your next trial conversion? Last known good version of reposurgeon is the problem right? (with whatever outstanding issues that version had with the conversion).