You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Blair Zajac <bl...@orcaware.com> on 2003/08/04 22:33:57 UTC
cvs2svn.py failure with a tiny repository
Hi Karl,
I think you'll like this bug report. This may be related to issue
1421 or 1442, but with an extremeley samll CVS repository (2 files,
14 Kbytes) with low revision number (5) that should make debugging
easier:
------- Committed revision 5 >>>
<<< Started new txn, based on original revision 6
* adding path : branches/demo-node-0 ...COPIED... done.
* deleting path : branches/demo-node-0/module/file1 ... done.
* editing path : branches/demo-node-0/module/file2 ... done.
* deleting path : branches/demo-node-0/module/file1 ...subversion/libsvn_fs/tree.c:181: (apr_err=160013)
svn: Filesystem has no item
svn: file not found: transaction `6', path `branches/demo-node-0/module/file1'
Interestingly enough, if you remove one of the two files from the
CVS repository, then you don't get a bad import file.
Do you want a new issue opened or append this onto an existing one?
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py failure with a tiny repository
Posted by Blair Zajac <bl...@orcaware.com>.
kfogel@collab.net wrote:
>
> Blair Zajac <bl...@orcaware.com> writes:
> > I think you'll like this bug report. This may be related to issue
> > 1421 or 1442, but with an extremeley samll CVS repository (2 files,
> > 14 Kbytes) with low revision number (5) that should make debugging
> > easier:
> >
> > ------- Committed revision 5 >>>
> >
> > <<< Started new txn, based on original revision 6
> > * adding path : branches/demo-node-0 ...COPIED... done.
> > * deleting path : branches/demo-node-0/module/file1 ... done.
> > * editing path : branches/demo-node-0/module/file2 ... done.
> > * deleting path : branches/demo-node-0/module/file1 ...subversion/libsvn_fs/tree.c:181: (apr_err=160013)
> > svn: Filesystem has no item
> > svn: file not found: transaction `6', path `branches/demo-node-0/module/file1'
> >
> > Do you want a new issue opened or append this onto an existing one?
>
> Thanks, Blair!
>
> Just append to #1421 please. Fortunately the cause of the bug is
> well-understood now, but this may still save us some time constructing
> a regression test.
Done. Attached a tiny tar.gz to 1421.
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py failure with a tiny repository
Posted by kf...@collab.net.
Blair Zajac <bl...@orcaware.com> writes:
> I think you'll like this bug report. This may be related to issue
> 1421 or 1442, but with an extremeley samll CVS repository (2 files,
> 14 Kbytes) with low revision number (5) that should make debugging
> easier:
>
> ------- Committed revision 5 >>>
>
> <<< Started new txn, based on original revision 6
> * adding path : branches/demo-node-0 ...COPIED... done.
> * deleting path : branches/demo-node-0/module/file1 ... done.
> * editing path : branches/demo-node-0/module/file2 ... done.
> * deleting path : branches/demo-node-0/module/file1 ...subversion/libsvn_fs/tree.c:181: (apr_err=160013)
> svn: Filesystem has no item
> svn: file not found: transaction `6', path `branches/demo-node-0/module/file1'
>
> Do you want a new issue opened or append this onto an existing one?
Thanks, Blair!
Just append to #1421 please. Fortunately the cause of the bug is
well-understood now, but this may still save us some time constructing
a regression test.
> Interestingly enough, if you remove one of the two files from the
> CVS repository, then you don't get a bad import file.
That's consistent with the cause of the bug, yes.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org