From: Eric Wong <normalperson@yhbt.net>
To: Nicolas Vilz <niv@iaglans.de>
Cc: git@vger.kernel.org
Subject: Re: git-svn throwing assertion on old svn tracking branch
Date: Fri, 22 Dec 2006 22:45:31 -0800 [thread overview]
Message-ID: <20061223064531.GB10460@localdomain> (raw)
In-Reply-To: <20061222094337.GC9595@hermes>
Nicolas Vilz <niv@iaglans.de> wrote:
> On Fri, Dec 22, 2006 at 12:38:03AM -0800, Eric Wong wrote:
> > Nicolas Vilz <niv@iaglans.de> wrote:
> > > On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> > > > On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > > > > Nicolas Vilz <niv@iaglans.de> wrote:
> > > [...]
> > > > beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> > > > Subversion version 1.1.4 (r13838).
> > >
> > > i should ammend, that the same error message comes, when i want to
> > > dcommit something in this repository...
> >
> > Weird, so you have the SVN:: libraries installed? (dcommit requires it).
> > Is the repository you're tracking public? If so, I'd like to have a
> > look...
> unfortunatelly, its not public...
>
> I noticed, it is not the step of committing anything, but the step to
> fetch the revisions in the svn tree. I had a workaround last night... I
> used the documentation on Advanced Example: Tracking a Reorganized
> Repository to reorganize my tree from broken old repository to
> reorganized fresh tree that is working... that all because time was
> running out this night and i had to work something.
So the repository was reorganized? That could be it...
> I keep the old one as a souvenier... The problem lies somewhere there in
> the old branch. The history is not lost here in any case.
Good to know :)
> I backuped my repository and pruned my tree as you suggested it... I
> connected to that remote repository... and then the assertion came down
> on me. Personally i can live with that reorganized repository. If you
> are really keen on digging the error down to ground, i could try to
> setup something.
>
> Perhaps back were i worked on that repository, git-svn accessed a little
> different from now....
Some things have changed such as allowing access to repositories with
limited read permissions. I'm not sure how/if that affects you. If you
have time, can you try going back to revision
30d055aa1e45b4740edc3bfbff77fa5d65e106ff? Or try bisecting...
--
Eric Wong
next prev parent reply other threads:[~2006-12-23 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 23:55 git-svn throwing assertion on old svn tracking branch Nicolas Vilz
2006-12-21 1:05 ` Eric Wong
2006-12-22 1:35 ` Nicolas Vilz
2006-12-22 2:16 ` Nicolas Vilz
2006-12-22 8:38 ` Eric Wong
2006-12-22 9:43 ` Nicolas Vilz
2006-12-23 6:45 ` Eric Wong [this message]
2007-01-01 2:27 ` Eric Wong
2007-01-05 9:18 ` Nicolas Vilz
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=20061223064531.GB10460@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=niv@iaglans.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).