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 2002/04/17 06:56:21 UTC
svn commit failure
I'm trying to import a package of mine into svn and I'm getting a
commit failure.
<aside>
I think we need another public repository on svn.collab.net so that people
can mess around with a test server and not have to bother setting up their
own server to try to debug stuff. Do we have one available?
</aside>
Here's what I did. Create the following directory structure and import it
into the svn root. I have this up at http://svn.orcaware.com:8000/repos
orca
orca/branches
orca/tags
orca/trunk
% cd /tmp
% svn co http://svn.orcaware.com:8000/repos
% cd repos/orca/trunk
% wget http://www.orcaware.com/orca/pub/orca-0.18.tar.gz
% zcat orca-0.18.tar.gz | tar xf -
% mv orca-0.18/* .
% rm -fr orca-0.18 orca-0.18.tar.gz
% find `/bin/ls -1` | xargs svn add # this to skip the .svn
% svn commit
Adding ARCHITECTURE
Adding CHANGES
Adding INSTALL
Adding Makefile.in
Adding README
Adding REQUIREMENTS
Adding TODO
Adding config
Adding configure
Adding configure.in
svn_error: #21088 : <RA layer request failed>
Commit failed (details follow):
svn_error: #21088 : <RA layer request failed>
PROPFIND of /repos/orca/trunk/config: 404 Not Found
config is a directory.
Now you may wonder why I'm doing an add instead of an import, but that's
because I have a Perl script that I'll be checking into the tree soon that
add any number of tar.gz files and creates the tags for them. Right now
the same logic that checks for files and directories to add and delete
to an existing trunk uses add and there's no point in using import (or
there shouldn't be).
Best,
Blair
--
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - 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: svn commit failure
Posted by Roland Lammel <ro...@atc.co.at>.
Are those features allready on the wishlist somewhere (issuezilla) are should
enter a "reminder"?
Now I'm really looking forward to subversion 1.1 ;-)
Cheers
+rl
Ben Collins-Sussman wrote:
>
> Alexis Huxley <ah...@gmx.net> writes:
>
> > > Yes, many people want what you're talking about. We've discussed this
> > > feature before... we essentially need to implement the equivalent of
> > > soft-links within the svn repository filesystem. In past discussions,
> > > we've called them 'vnodes'. I don't think this feature will be part
> > > of svn 1.0, but probably will come soon thereafter.
> >
> > Will support for real symlinks be in 1.0?
> >
> > I tried archiving a tree with some in and though svn didn't complain,
> > they weren't there when I took it out again.
>
> Really, these are two totally different features:
>
> 1. detect/preserve symlinks in a working copy
> 2. implement symlinks *within* the repository filesystem.
>
> It's easy to get them confused. But yes, we plan to have both
> features eventually. I'm not sure if either feature is going to make
> it into 1.0 though. Trying to get 1.0 to match CVS's featureset is a
> big challenge as it is. After 1.0, there are a zillion ways to make
> SVN better. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit failure
Posted by Ben Collins-Sussman <su...@collab.net>.
Alexis Huxley <ah...@gmx.net> writes:
> > Yes, many people want what you're talking about. We've discussed this
> > feature before... we essentially need to implement the equivalent of
> > soft-links within the svn repository filesystem. In past discussions,
> > we've called them 'vnodes'. I don't think this feature will be part
> > of svn 1.0, but probably will come soon thereafter.
>
> Will support for real symlinks be in 1.0?
>
> I tried archiving a tree with some in and though svn didn't complain,
> they weren't there when I took it out again.
Really, these are two totally different features:
1. detect/preserve symlinks in a working copy
2. implement symlinks *within* the repository filesystem.
It's easy to get them confused. But yes, we plan to have both
features eventually. I'm not sure if either feature is going to make
it into 1.0 though. Trying to get 1.0 to match CVS's featureset is a
big challenge as it is. After 1.0, there are a zillion ways to make
SVN better. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit failure
Posted by Alexis Huxley <ah...@gmx.net>.
> Yes, many people want what you're talking about. We've discussed this
> feature before... we essentially need to implement the equivalent of
> soft-links within the svn repository filesystem. In past discussions,
> we've called them 'vnodes'. I don't think this feature will be part
> of svn 1.0, but probably will come soon thereafter.
Will support for real symlinks be in 1.0?
I tried archiving a tree with some in and though svn didn't complain,
they weren't there when I took it out again.
Alexis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit failure
Posted by Ben Collins-Sussman <su...@collab.net>.
Roland Lammel <ro...@atc.co.at> writes:
> So when changing something in the subproject during development of any
> subproject these changes (HEAD) are available to all other mainprojects
> as well (for allready checked out copies only cvs upd is requried)
Hi Roland,
Yes, many people want what you're talking about. We've discussed this
feature before... we essentially need to implement the equivalent of
soft-links within the svn repository filesystem. In past discussions,
we've called them 'vnodes'. I don't think this feature will be part
of svn 1.0, but probably will come soon thereafter.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit failure
Posted by Roland Lammel <ro...@atc.co.at>.
Hi Folks,
I stumbled across subversion a few weeks ago and tried to find some information
on how subprojects can be reused within the repository, but haven't found my
answer in the archives or the design docs (or just haven't interpreted what I
read correctly, if so, just put my nose on it).
We are using some shared subprojects mostly deailing with some basic stuff or
common database routines, which shoud act as libs (currently everything is perl)
for other projects. As these subprojects should not be copied to all our main
projects, we instead created links in the cvs repository on the server, so
on each checkout/checkin the same set of files is checked out/checked in.
So when changing something in the subproject during development of any
subproject these changes (HEAD) are available to all other mainprojects
as well (for allready checked out copies only cvs upd is requried)
The small picture:
cvs/lib/DBLib
cvs/Project1
cvs/Project1/lib/DBLib
cvs/Project2
cvs/Project2/lib/DBLib
cvs/Project2/lib/OtherLib
As in the repository all DBLib dirs are (manually) linked to that of the common cvs/lib/DBLib
it does not matter for which project we check out DBLib as it always is updated (on HEAD)
and tags are set for all main projects. So DBLib will have tags of Project1 and Project2
Any info would be appreciated
Cheers
+rl
-------------------------------------
Roland Lammel
-------------------------------------
Services / Technical Assistance / PPA
Kapsch CarrierCom
Triesterstr. 70a, 1102 Wien
-------------------------------------
mailto:roland.lammel@kapsch.net
Tel: +43 1 60501 - 3456 (ESN 572 3456)
Fax: +43 1 60501 - 3405
Mobil: +43 664 628 - 3456
-------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit failure
Posted by Blair Zajac <bl...@orcaware.com>.
Blair Zajac wrote:
>
> I'm trying to import a package of mine into svn and I'm getting a
> commit failure.
>
> <aside>
> I think we need another public repository on svn.collab.net so that people
> can mess around with a test server and not have to bother setting up their
> own server to try to debug stuff. Do we have one available?
> </aside>
>
> Here's what I did. Create the following directory structure and import it
> into the svn root. I have this up at http://svn.orcaware.com:8000/repos
>
> orca
> orca/branches
> orca/tags
> orca/trunk
>
> % cd /tmp
> % svn co http://svn.orcaware.com:8000/repos
> % cd repos/orca/trunk
> % wget http://www.orcaware.com/orca/pub/orca-0.18.tar.gz
> % zcat orca-0.18.tar.gz | tar xf -
> % mv orca-0.18/* .
> % rm -fr orca-0.18 orca-0.18.tar.gz
> % find `/bin/ls -1` | xargs svn add # this to skip the .svn
> % svn commit
>
> Adding ARCHITECTURE
> Adding CHANGES
> Adding INSTALL
> Adding Makefile.in
> Adding README
> Adding REQUIREMENTS
> Adding TODO
> Adding config
> Adding configure
> Adding configure.in
>
> svn_error: #21088 : <RA layer request failed>
> Commit failed (details follow):
>
> svn_error: #21088 : <RA layer request failed>
> PROPFIND of /repos/orca/trunk/config: 404 Not Found
>
> config is a directory.
Michael,
Now I can check in all my code into svn.
Thanks!
Blair
PS Noting that revision 1739 fixed this in case anybody needs this.
--
Blair Zajac <bl...@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org