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

Re: [BUG] git-svn not following svn moves

From
PBPeter Baumann <waste.manager@gmx.de>
Date
Oct 18, 2007, 12:13 UTC
Message-ID
<20071018121328.GA5358@xp.machine.xx>
In-Reply-To
<ff7fhg$2eu$1@ger.gmane.org>
On Thu, Oct 18, 2007 at 11:20:16AM +0000, cho wrote:
Show 21 quoted lines
> Hello,
> 
> I have a git-svn checkout that apparently did not follow a move correctly.
> The files are not present in an svn checkout, but are in a git svn clone.
> 
> According to a trac browser, some of the files that appear in my git 
> checkout had in fact been moved to their separate branch before doing git-
> svn clone. I noticed this when trying to commit changes to those files, 
> getting the error message:
> > Le système de fichiers ne contient pas cet élément: Fichier non 
> trouvé : transaction '3926-1', chemin '.../composants.py' at /home/marc/
> bin/git-svn line 2960
> It's a standard subversion error, "Filesystem has no item"
> 
> I've made a clean checkout (with today's 1.5.3.4.206.g58ba4), and I still 
> have the moved files present.
> The clone command is just:
> git svn clone --stdlayout svn+ssh://host/srv/subversion/proj/appli/proj
> 
> Tell me if I can give more info (the repository isn't public).
> 

Any chance you could provide a testcase which is similar to what happened in your private repo so that the problem could be reproduced here?

-Peter
Previous: choNext: cho
Message 2 of 7 in “[BUG] git-svn not following svn moves”
  1. choOct 18, 2007
  2. Peter BaumannOct 18, 2007
  3. choOct 18, 2007
  4. Sam VilainOct 18, 2007
  5. choOct 19, 2007
  6. choOct 19, 2007
  7. choOct 19, 2007

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.