From: Eric Wong <normalperson@yhbt.net>
To: Peter Baumann <waste.manager@gmx.de>
Cc: "Marcus D. Hanwell" <marcus@cryos.net>, git@vger.kernel.org
Subject: Re: git-svn init from Avogadro SVN repo - deleted files showing
Date: Thu, 13 Dec 2007 08:41:34 -0800 [thread overview]
Message-ID: <20071213164134.GD18433@soma> (raw)
In-Reply-To: <20071210104235.GA7521@xp.machine.xx>
Peter Baumann <waste.manager@gmx.de> wrote:
> On Sun, Dec 09, 2007 at 07:24:40PM -0500, Marcus D. Hanwell wrote:
> > Hi,
> >
> > I am quite new to git and git-svn but have been using both for my
> > development work recently. I imported the Avogadro subversion repository
> > (hosted on Sourceforge) using the following commands,
> >
> > git svn init -t tags -b branches -T trunk
> > https://avogadro.svn.sourceforge.net/svnroot/avogadro
> >
> > git svn fetch
> >
> >
> > The files avogadro.pro and README in the trunk/ directory appear in my
> > imported git repository but not in Avogadro subversion trunk. We also had
> > trunk/src/ and all its files/subdirectories appearing in the git checkout
> > but not in subversion trunk. We deleted this using git and git svn which
> > removed it from the git checkouts too after r858.
> >
> > I have been talking to Peter who confirmed this and pointed out that the
> > repo was reorganised several times in the past. Please CC me on replies as
> > I am not on the list. There is a copy of my git repo at
> > http://platinum.cryos.net/avogadro.git/ if you would rather skip the
> > import. Other than that everything has been working great. It would be good
> > to get rid of this bug if possible. Let me know if there is anything else I
> > can do to help.
> >
>
> [ Eric Cc'ed, as the author of git-svn ]
>
> I can confirm that this looks like an import problem.
> (e.g see svn log -v -r33:78 https://avogadro.svn.sourceforge.net/svnroot/avogadro)
>
> I did my analysis on the file /trunk/avogadro.pro, because the error
> happens really early in the history so could just import up to revision 76
> to see what goes wrong. (The file gets never deleted in the import, as it
> should be!)
>
>
>
> trunk/avogadro.pro is added here:
>
> ------------------------------------------------------------------------
> r33 | dcurtis3 | 2006-08-21 07:34:10 +0200 (Mon, 21 Aug 2006) | 3 lines
> Changed paths:
> A /trunk/avogadro.pro
>
> Does a recursive build.
>
>
> Here the refactoring starts (a new directory not tracked by git is added):
> ------------------------------------------------------------------------
> r66 | dcurtis3 | 2007-01-03 06:42:45 +0100 (Wed, 03 Jan 2007) | 3 lines
> Changed paths:
> A /avogadro
>
> Making room for libavogadro.
>
>
> /branches is moved to /avogadro/branches
> ------------------------------------------------------------------------
> r67 | dcurtis3 | 2007-01-03 06:47:11 +0100 (Wed, 03 Jan 2007) | 3 lines
> Changed paths:
> A /avogadro/branches (from /branches:66)
> D /branches
>
> Making room for libavogadro
>
>
>
>
> ERROR HAPPENS HERE:
> ====================
>
> /trunk and /tags are moved, too.
> (/trunk/avogadro.pro becomes /avogadro/trunk/avogadro.pro):
> ------------------------------------------------------------------------
> r68 | dcurtis3 | 2007-01-03 06:47:34 +0100 (Wed, 03 Jan 2007) | 3 lines
> Changed paths:
> A /avogadro/tags (from /tags:66)
> A /avogadro/trunk (from /trunk:66)
> D /tags
> D /trunk
>
> Making room for libavogadro.
>
> The above delete/move of trunk isn't recorded anywhere in the git svn import.
> 'git-svn find-rev r66' doesn't produce any output!
> And later git-svn thinks that /trunk and all its files are still there, so
> e.g. /trunk/avogadro.pro stays in the repo forever.
Hi,
Thanks for the analysis, Peter.
git-svn ignores deletions to the directory we're tracking in order to
represent renames when the follow-parent case is hit.
Unfortunately, this never took into account the directory we're tracking
reappearing later in history. I'll try to have a fix later tonight or
over the weekend.
> mv /avogadro/trunk/avogadro.pro /trunk/avogadro/avogadro.pro
> ------------------------------------------------------------------------
> r75 | dcurtis3 | 2007-01-03 20:49:35 +0100 (Wed, 03 Jan 2007) | 2 lines
> Changed paths:
> D /avogadro
> D /avogadro-lib
> A /branches
> A /tags
> A /trunk
> A /trunk/avogadro (from /avogadro/trunk:74)
> A /trunk/libavogadro (from /avogadro-lib/trunk:74)
>
> Moving things around. Conforming to a more KDE-like layout in SVN.
> I'm going nuts. SOrry
Instead of handling the full delete of everything in r68, I think I'll
make it so importing r75 will clobber all the stuff in trunk/ we ignored
deleting in r68 before adding the contents of trunk/ in r75.
--
Eric Wong
next prev parent reply other threads:[~2007-12-13 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 0:24 git-svn init from Avogadro SVN repo - deleted files showing Marcus D. Hanwell
2007-12-10 10:42 ` Peter Baumann
2007-12-10 11:40 ` Peter Baumann
2007-12-13 16:41 ` Eric Wong [this message]
2007-12-13 18:13 ` Peter Baumann
2007-12-14 16:39 ` [PATCH] git-svn: handle our top-level path is deleted and later re-added Eric Wong
2007-12-14 16:43 ` Eric Wong
2007-12-15 0:24 ` cho
2007-12-15 16:35 ` Peter Baumann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071213164134.GD18433@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=marcus@cryos.net \
--cc=waste.manager@gmx.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).