From: Chris Packham <firstname.lastname@example.org> To: Bagas Sanjaya <email@example.com> Cc: GIT <firstname.lastname@example.org> Subject: Re: [BUG] gitk error - can't read "arcnos()": no such element in array Date: Tue, 1 Jun 2021 12:29:42 +1200 [thread overview] Message-ID: <CAFOYHZAjzS+fizM+wadgFq3F6tSYu35CJOFuCWPFc5TH6Fq8vg@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Mon, May 31, 2021 at 7:53 PM Bagas Sanjaya <firstname.lastname@example.org> wrote: > > On 31/05/21 14.38, Chris Packham wrote: > >> Is your problematic repo public? If so, we can test against that. > >> > > > > Unfortunately not. It's actually an internal kernel tree which has a > > different root to upstream (hence using git replace to attach upstream). > > All of which make the history a bit funky. > > > > I don't know if the problem will survive anonymisation but I can try. > > > > Did you mean vendor kernel tree based on Linux kernel? Kind of. A repo that was created in 2007 before we were using git properly by extracting the kernel tarballs and adding our code. So although it's a kernel tree it shares no common history with Linus' tree. git fast-export/fast-import doesn't seem to like the affected repo so I'm not having much luck with making anything publicly available. > I think you can > try reproducing the issue with either Linus' tree  (mainline only) or > Greg's stable tree  (mainline + release branches and tags). > > : https://github.com/torvalds/linux > : https://github.com/gregkh/linux > I've tried a few experiments - cloning the "bad" repo -> no problem seen in clone - cloning the "bad" repo with --mirror -> no problem seen in clone - copying the "bad" repo -> same problem seen in copy So now that I have a copy that shows the problem I can do a few more things. - copy repo, remove replace refs (git replace -l | xargs git replace -d) -> problem remains - copy repo, remove replace refs and all remotes except origin -> problem remains - copy repo, run git gc -> no problem So the git gc seems to have done the trick. I'm happy enough to leave it there and hope that this thread is useful for future mailing list searchers. I'll keep a copy of the affected repo around if there is anything someone wants me to try.
prev parent reply other threads:[~2021-06-01 0:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 21:16 Chris Packham 2021-05-31 3:11 ` Chris Packham 2021-05-31 3:24 ` Bagas Sanjaya [not found] ` <CAFOYHZA4xbnWc1d1zK-fjoDHZntQj7weDZk1r=SOJxVtKD4aOA@mail.gmail.com> 2021-05-31 7:53 ` Bagas Sanjaya 2021-06-01 0:29 ` Chris Packham [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAFOYHZAjzS+fizM+wadgFq3F6tSYu35CJOFuCWPFc5TH6Fq8vg@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [BUG] gitk error - can'\''t read "arcnos()": no such element in array' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).