You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Shaw Terwilliger <st...@sourcegear.com> on 2001/11/30 15:36:07 UTC
"svn co -d" and updates
Let me first say that I really like the notion of Subversion soon replacing
CVS in most or all of its installations. I think the internal design is
simple and neat, and the team has done a good job focussing on the features
important to developers.
I've been building the svn trees for the last few weeks, and I'm trying to
determine whether the behavior I'm seeing is intended (and I just haven't
found the documentation to let me know).
I check out any tree with the -d option, and supply a name other than
the repository's last component, and svn gets confused when I later do things
like "svn update" inside that tree. The client can't seem to map its
not-quite-maching-the-repository working copy directory name with the file
info inside it.
--
Shaw Terwilliger <st...@sourcegear.com>
SourceGear Corporation
217.356.0105 x 641
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: "svn co -d" and updates
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Cool, I'm glad this got worked out so quickly.
General rule, though: when you post with a problem, it's good to list
the *exact* commands you ran, and the *exact* results you saw, and how
they differed from what you expected to see. "I'm having problems
with blah" is usually not going to be enough information. :-)
Best,
-Karl
Shaw Terwilliger <st...@sourcegear.com> writes:
> Kevin Pilch-Bisson wrote:
> > I recently changed the name from ancestor to url. If you missed the message
> > to the dev list pointing out that working copies were broken then that would
> > do it. There was a script posted at that time which would go through a
> > working copy and change it over, but its also safe to just re-checkout.
>
> Aha, was just a timing thing. All fixed! :)
>
> --
> Shaw Terwilliger <st...@sourcegear.com>
> SourceGear Corporation
> 217.356.0105 x 641
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: "svn co -d" and updates
Posted by Shaw Terwilliger <st...@sourcegear.com>.
Kevin Pilch-Bisson wrote:
> I recently changed the name from ancestor to url. If you missed the message
> to the dev list pointing out that working copies were broken then that would
> do it. There was a script posted at that time which would go through a
> working copy and change it over, but its also safe to just re-checkout.
Aha, was just a timing thing. All fixed! :)
--
Shaw Terwilliger <st...@sourcegear.com>
SourceGear Corporation
217.356.0105 x 641
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: "svn co -d" and updates
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
On Fri, Nov 30, 2001 at 09:55:38AM -0600, Shaw Terwilliger wrote:
> Kevin Pilch-Bisson wrote:
> > Could you give some more details. I always check out the subversion
> > source tree like this:
> >
> > svn co http://svn.collab.net/repos/svn/trunk -d svn.static (or svn.shared,
> > or whatever)
>
> I think I discovered my problem. My repository's .svn/entries had no
> "url" property for the top-level directory. I don't know how that happened,
> but I can check out new repositories and they all get the url prop.
>
> The entry in my broken tree looks like:
>
> <entry
> name="svn:this_dir"
> kind="dir"
> prop-time="Wed 28 Nov 2001 10:11:55.000000 (day 332, dst 0, gmt_off -21600)"
> revision="548"
> ancestor="http://svn.collab.net/repos/svn/trunk"/>
I recently changed the name from ancestor to url. If you missed the message
to the dev list pointing out that working copies were broken then that would
do it. There was a script posted at that time which would go through a
working copy and change it over, but its also safe to just re-checkout.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: "svn co -d" and updates
Posted by Shaw Terwilliger <st...@sourcegear.com>.
Kevin Pilch-Bisson wrote:
> Could you give some more details. I always check out the subversion
> source tree like this:
>
> svn co http://svn.collab.net/repos/svn/trunk -d svn.static (or svn.shared,
> or whatever)
I think I discovered my problem. My repository's .svn/entries had no
"url" property for the top-level directory. I don't know how that happened,
but I can check out new repositories and they all get the url prop.
The entry in my broken tree looks like:
<entry
name="svn:this_dir"
kind="dir"
prop-time="Wed 28 Nov 2001 10:11:55.000000 (day 332, dst 0, gmt_off -21600)"
revision="548"
ancestor="http://svn.collab.net/repos/svn/trunk"/>
--
Shaw Terwilliger <st...@sourcegear.com>
SourceGear Corporation
217.356.0105 x 641
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: "svn co -d" and updates
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
On Fri, Nov 30, 2001 at 09:36:07AM -0600, Shaw Terwilliger wrote:
> Let me first say that I really like the notion of Subversion soon replacing
> CVS in most or all of its installations. I think the internal design is
> simple and neat, and the team has done a good job focussing on the features
> important to developers.
>
> I've been building the svn trees for the last few weeks, and I'm trying to
> determine whether the behavior I'm seeing is intended (and I just haven't
> found the documentation to let me know).
>
> I check out any tree with the -d option, and supply a name other than
> the repository's last component, and svn gets confused when I later do things
> like "svn update" inside that tree. The client can't seem to map its
> not-quite-maching-the-repository working copy directory name with the file
> info inside it.
>
Could you give some more details. I always check out the subversion
source tree like this:
svn co http://svn.collab.net/repos/svn/trunk -d svn.static (or svn.shared,
or whatever)
and I have never noticed any problems.
>
> --
> Shaw Terwilliger <st...@sourcegear.com>
> SourceGear Corporation
> 217.356.0105 x 641
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~