cvs-fast-export: internal error - branch cycle

Good day,

Would you have an opportunity to check this kind of error? Why this happens? I'm a bit confused what it means and also from the below description is not that clear.

   internal error - branch cycle
       cvs-fast-export found a cycle while topologically sorting commits
       by parent link. This should never happen and probably indicates a
       serious internal error: please file a bug report.

Thanks

I don't know why it happens either. It probably indicates a serious malformation in the CVS metadata somehere.

There are instructions in the distribution for producing a siimplestr possible stripped-down version of your repo and shipping it to me: bug-repoerting.asc.

I'll try to find the problem, but I make no promises. CVS is a toxic swamp; there may not be a fix.

Im also trying to debug what went wrong or what branch has an issue. But tried to announce the r-> refname it will have a memory core dump .

Will you please help me list the git_branches? My c programming is a bit rusty now and would like to check if it was an issue on a branch so i can do a cleanup of the cvs

Thanks

"Will you please help me list the git_branches?"

Sorry, I don''t understand this request.

Hi Eric,

Apologies for the confusion, the git_branches is located in the merge.c

rev_ref_tsort ... . . . . .

while (git_branches) { /* search the remaining input list */ for (prev = &git_branches; (r = *prev); prev = &(prev)->next) { / * Find a branch where we've already sorted its parents. * Toposorting with this relation will put the (parentless) trunk first, * and child branches after their respective parent branches. / if (parents_in_revlist(r->ref_name, sorted_git_branches, masters, nmasters)) { break; } } if (!r) { announce("internal error - branch cycle\n"); return NULL; } / * Remove the found branch from the input list and * append it to the output list */ *prev = r->next; *sorted_tail = r; r->next = NULL; sorted_tail = &r->next;

If you succeed in understanding that code, you'll be the first person to do so since Keith Packard forgot what he knew when he wrote it. I've been studying it for years and don't completely understand it.

hmm that's to bad, is there an instruction or requirement for a branch name. i'm still debugging the code, and its very hard pinpointing if there is any issue with the branch.

I don't understand this --> There are instructions in the distribution for producing a siimplestr possible stripped-down version of your repo and shipping it to me: bug-repoerting.asc.

Thanks

Look in the file "reporting-bugs.asc". Sorry, I mis-remembered the name.

Saw it, but it requires python, i'm not a system administrator of the unix box, and won't be able to generate the bug report.

Thanks

Hi Eric,

Already saw the branch cycle. Is it possible to migrate only specific branches from cvs to avoid the branch cycle? Just the latest branch created.

Thanks