Joseph Myers <jos...@codesourcery.com>:
> I think we currently have the following reposurgeon issues open for cases
> where the present code results in incorrect tree contents and we're hoping
> the new code will fix that (or make it much easier to find and fix the
> bugs). These are the issues that are most critical for being able to use
> reposurgeon for the conversion.
>
> https://gitlab.com/esr/reposurgeon/issues/167
> https://gitlab.com/esr/reposurgeon/issues/171
> https://gitlab.com/esr/reposurgeon/issues/172
> https://gitlab.com/esr/reposurgeon/issues/178
I'm aware these are the real blockers.
I was much more worried about the conversion before we figured out
that most of the remaining content mismatches seem to radiate out from
something weird that happened at r14877. That's early enough that a
leading-segment load including it doesn't take forever. Which means
it's practical to do detailed forensics on the defect even if you don't
have handy an EC12 instance with ridiculo-humongous amonts of RAM.
Now I'm pretty certain we can finish this. A matter of when, not if.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
