Re: [Jython-dev] GitHub Jython repo broken

[Jeff A. <ja...@fa...>]

My second attempt at migrating to GitHub is now posted at: 
https://github.com/jeff5/jython-whinchat .

This does not have the broken history problem afflicting the current 
official repository. It would be useful to know if anything else is 
still wrong. I'll examine during the week how I can get from this to a 
fresh repo at the project home, and if possible, called jython/jython.

Jeff Allen

On 19/07/2020 15:29, Jeff Allen wrote:
>
> I have made a valid (I think) git repo from hg by migrating it using 
> https://github.com/frej/fast-export . It does not have the false root 
> problem seen in the current official repo (or multiple heads per 
> branch). It may not yet be attributing correctly to GitHub user names.
>
> I will repeat this (so I can do it repeatably!) in such a way that I 
> end up with a repo on my personal account, and check that it looks 
> right from GitHub, both history and attribution. Then I'll see if I 
> can make it appear at https://github.com/jython/jython, which is by no 
> means certain.
>
> Jeff
>
> Jeff Allen
> On 18/07/2020 08:27, Jeff Allen wrote:
>>
>> The master repository at https://github.com/jython/jython, recently 
>> migrated from Mercurial, has suffered some corruption in the process. 
>> Please do not use it until we work out how to fix it (or decide to 
>> live with it).
>>
>> Ernest: please keep https://hg.python.org/jython/ safe: it's the most 
>> solid foundation we have at present.
>>
>> Here and there, the translation process has lost the parent link from 
>> the first change set on a "topic branch". The effect is to make it 
>> look like the entire content of the repository is new at that change 
>> set. If you scroll back in the history of almost any file it stops 
>> (or rather begins) at the latest of these false roots. For 
>> information, we did this with a straightforward use of GitHub's 
>> migration tool, which produced no message that it was failing. (There 
>> were messages about linking contributor identities, which we addressed.)
>>
>> We're sorry not to have noticed this sooner. If there is a way of 
>> fixing this it may involve a fresh start or some history-rewriting in 
>> situ. This will break forks you may have made. We will try to fix as 
>> much of this as we can from our side, but that won't be free of 
>> downstream annoyances.
>>
>> -- 
>> Jeff Allen
>>
>