git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Errors GITtifying GCC and Binutils

From
CSChris Shoemaker <c.shoemaker@cox.net>
Date
Mar 25, 2006, 00:37 UTC
Message-ID
<20060325003712.GA32320@pe.Belkin>
In-Reply-To
<20060324075229.GH31387@lug-owl.de>
On Fri, Mar 24, 2006 at 08:52:29AM +0100, Jan-Benedict Glaw wrote:
Show 14 quoted lines
> On Thu, 2006-03-23 19:39:44 -0500, Chris Shoemaker <c.shoemaker@cox.net> wrote:
> > On Thu, Mar 23, 2006 at 09:03:06PM +0100, Jan-Benedict Glaw wrote:
> > > On Wed, 2006-03-22 17:28:23 -0800, Linus Torvalds <torvalds@osdl.org> wrote:
> > > It seems there's a patch like
> > > http://www.gelato.unsw.edu.au/archives/git/0602/16278.html is missing?
> > > ...or we need a better cvsps.  Shall I add it and try again / try to
> > > continue, or give up on it for now?  Though it would be nice to have
> > > these two large and important source trees under GIT control :-)
> > 
> > You make want to try the cvsps patch I attached to the email here:
> > 
> > http://www.gelato.unsw.edu.au/archives/git/0511/11812.html
> 
> [...]
> invalid initial_branch for file bfd/po/BLD-POTFILES.in, probably
> from old cache, run with -x.
I guess that error message wasn't quite as obvious as I intended.

That means you have old cvsps cache state hanging around. You can either run cvsps with -x or delete the cache file manually. Those are the files in ~/.cvsps.

Incidentally, I'd recommend doing this in two stages during trouble-shooting. Run cvsps first and verify that you can produce a valid ancestry tree. If it's not-quite-right you can even edit the cvsps output to reparent the incorrect branches. Then run git-cvsimport after you're satisfied with the ancestry.

-chris
Previous: Jan-Benedict GlawNext: H. Peter Anvin
Message 10 of 43 in “Errors GITtifying GCC and Binutils”
  1. Jan-Benedict GlawMar 22, 2006
  2. Linus TorvaldsMar 22, 2006
  3. Linus TorvaldsMar 23, 2006
  4. Linus TorvaldsMar 23, 2006
  5. Jan-Benedict GlawMar 23, 2006
  6. Linus TorvaldsMar 23, 2006
  7. Chris ShoemakerMar 24, 2006
  8. Keith PackardMar 24, 2006
  9. Jan-Benedict GlawMar 24, 2006
  10. Chris ShoemakerMar 25, 2006
  11. H. Peter AnvinMar 23, 2006
  12. Keith PackardMar 23, 2006
  13. Linus TorvaldsMar 23, 2006
  14. seanMar 23, 2006
  15. Linus TorvaldsMar 23, 2006
  16. Shawn PearceMar 23, 2006
  17. Ryan AndersonMar 23, 2006
  18. Junio C HamanoMar 24, 2006
  19. Junio C HamanoMar 23, 2006
  20. Johannes SchindelinMar 24, 2006
  21. Mark WoodingMar 24, 2006
  22. Andreas EricssonMar 24, 2006
  23. David S. MillerMar 23, 2006
  24. Linus TorvaldsMar 23, 2006
  25. Timo HirvonenMar 23, 2006
  26. seanMar 23, 2006
  27. Ralf BaechleMar 24, 2006
  28. Andreas EricssonMar 24, 2006
  29. Carl WorthMar 24, 2006
  30. Andreas EricssonMar 24, 2006
  31. Ryan AndersonMar 23, 2006
  32. Linus TorvaldsMar 23, 2006
  33. Junio C HamanoMar 23, 2006
  34. Ryan AndersonMar 24, 2006
  35. Junio C HamanoMar 24, 2006
  36. Ralf BaechleMar 24, 2006
  37. Jan-Benedict GlawMar 24, 2006
  38. Andreas EricssonMar 24, 2006
  39. Jan-Benedict GlawMar 25, 2006
  40. Santi BéjarMar 24, 2006
  41. Eric WongMar 25, 2006
  42. contrib/git-svn: stabilize memory usage for big fetchesEric Wong, Mar 26, 2006
  43. James CloosMar 25, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.