You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by LIRA Olavo <Ol...@gemalto.com> on 2006/12/13 23:08:04 UTC
svn 1.4.2 tells me the it is 1.2.3
Hi,
I'm a newbie in this list and I have installed the svn-win32
1.4.2 but when I run the svn --version it shows me:
svn, version 1.2.3 (r15833)
compiled Sep 13 2005, 22:45:22
...
Does any one have a clue of what am I doing wrong?
Thanks a lot,
========================================
Olavo Lira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals problem in checkout
Posted by Bob Hiestand <bo...@gmail.com>.
On 12/14/06, LIRA Olavo <Ol...@gemalto.com> wrote:
> Fetching external item into 'EEBXXX_YYYZZZ\Dev'
> svn: 'EEBXXX_YYYZZZ\Dev' is already a working copy for a
> different URL
> -----------
>
> My svn:externals is: "Dev/ https://repository/trunk/toto"
>
> Where directory Dev already exist in project A, but when I
> change the value to:
> "Dev/temp https://repository/trunk/toto"
> Where temp is not under SVN control, then it works fine.
>
> Is it normal? Is there another way to avoid this kind of
> problem? Should I use something else than svn:externals for this
> situation?
Yes, the directory named by the external directive should not exist in
the current directory. Remove the 'Dev' directory and commit, then
set the external property and update.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals problem in checkout
Posted by Mark Clements <gm...@kennel17.co.uk>.
"LIRA Olavo" <Ol...@gemalto.com> wrote in message
news:C851EA3075DC8341BD2A66E40EDF971C01CBDD9D@VGEEXC02.CORP.DS.GEMPLUS.COM..
.
> Yes, I think that it is normal.
> You should not have a directory Dev in >your project A.
> It will be created at checkout time by the svn:externals.
> Just remove your Dev directory from A and it should be OK
Thank you Christophe,
But in my case I also have the Dev directory in both projects,
is there another way to do the link the directories and avoid this kind
of problem?
------------------END QUOTE
Yes - use a different name for the externals directory. Externals can only
point to directories, and those directories musn't exist in the repository.
- Mark Clements
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: svn:externals problem in checkout
Posted by LIRA Olavo <Ol...@gemalto.com>.
Ahhhhh, sure... cool! (How stupid of me not testing this before...)
Thanks a lot! ;-)
Olavo Lira
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006d@ryandesign.com]
Sent: Monday, December 18, 2006 2:26 PM
To: LIRA Olavo
Cc: users@subversion.tigris.org
Subject: Re: svn:externals problem in checkout
On Dec 18, 2006, at 12:18, LIRA Olavo wrote:
>> I'm not sure that I realy understand.
>> Your question seems to be "Can I have two directories
>> with the same name at the same place ?".
>> What would you like subversion to do exactly
>> when you checkout your project A ?
>>
>> EEBXXX_YYYZZZ (From Project A)
>> Dev (From Project A)
>> ??? (From Project B svn:externals), it can not be also Dev...
>
> Hi Christophe,
>
> Sorry if I didn't explain may self correctly. Here is another
> try:
>
> EEBXXX_YYYZZZ (From Project A)
> Dev/
> Tools (From Project A)
> Applet (From Project B svn:externals)
> OS (From Project B svn:externals)
> Ext (From Project A)
> Plugin (From Project C svn:externals)
>
> So in order to have the picture above my svn:externals should be:
>
> Dev/ https://svnrepository/ProjectB/Applet
> Dev/ https://svnrepository/ProjectB/OS
> Dev/ https://svnrepository/ProjectC/Plugin
>
> But then I have the error I've shown you because I Project A has
> already the Dev directory.
>
> If svn:externals cannot handle this, do you know another way to
> link directories from different projects?
svn:externals can handle this just fine. But you need to set
svn:externals on the Dev directory of Project A then, not its parent
directory, and the contents of the svn:externals property on the Dev
directory should be as follows:
Applet https://svnrepository/ProjectB/Applet
OS https://svnrepository/ProjectB/OS
Plugin https://svnrepository/ProjectC/Plugin
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals problem in checkout
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 18, 2006, at 12:18, LIRA Olavo wrote:
>> I'm not sure that I realy understand.
>> Your question seems to be "Can I have two directories
>> with the same name at the same place ?".
>> What would you like subversion to do exactly
>> when you checkout your project A ?
>>
>> EEBXXX_YYYZZZ (From Project A)
>> Dev (From Project A)
>> ??? (From Project B svn:externals), it can not be also Dev...
>
> Hi Christophe,
>
> Sorry if I didn't explain may self correctly. Here is another
> try:
>
> EEBXXX_YYYZZZ (From Project A)
> Dev/
> Tools (From Project A)
> Applet (From Project B svn:externals)
> OS (From Project B svn:externals)
> Ext (From Project A)
> Plugin (From Project C svn:externals)
>
> So in order to have the picture above my svn:externals should be:
>
> Dev/ https://svnrepository/ProjectB/Applet
> Dev/ https://svnrepository/ProjectB/OS
> Dev/ https://svnrepository/ProjectC/Plugin
>
> But then I have the error I've shown you because I Project A has
> already the Dev directory.
>
> If svn:externals cannot handle this, do you know another way to
> link directories from different projects?
svn:externals can handle this just fine. But you need to set
svn:externals on the Dev directory of Project A then, not its parent
directory, and the contents of the svn:externals property on the Dev
directory should be as follows:
Applet https://svnrepository/ProjectB/Applet
OS https://svnrepository/ProjectB/OS
Plugin https://svnrepository/ProjectC/Plugin
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: svn:externals problem in checkout
Posted by LIRA Olavo <Ol...@gemalto.com>.
> I'm not sure that I realy understand.
> Your question seems to be "Can I have two directories
> with the same name at the same place ?".
> What would you like subversion to do exactly
> when you checkout your project A ?
>
> EEBXXX_YYYZZZ (From Project A)
> Dev (From Project A)
> ??? (From Project B svn:externals), it can not be also Dev...
Hi Christophe,
Sorry if I didn't explain may self correctly. Here is another
try:
EEBXXX_YYYZZZ (From Project A)
Dev/
Tools (From Project A)
Applet (From Project B svn:externals)
OS (From Project B svn:externals)
Ext (From Project A)
Plugin (From Project C svn:externals)
So in order to have the picture above my svn:externals should be:
Dev/ https://svnrepository/ProjectB/Applet
Dev/ https://svnrepository/ProjectB/OS
Dev/ https://svnrepository/ProjectC/Plugin
But then I have the error I've shown you because I Project A has
already the Dev directory.
If svn:externals cannot handle this, do you know another way to
link directories from different projects?
Thanks a lot,
Olavo Lira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: RE: RE: RE: svn:externals problem in checkout
Posted by Méresse Christophe <ch...@nagra.com>.
> > Yes, I think that it is normal.
> > You should not have a directory Dev in >your project A.
> > It will be created at checkout time by the svn:externals.
> > Just remove your Dev directory from A and it should be OK
>
> Thank you Christophe,
>
> But in my case I also have the Dev directory in both projects,
> is there another way to do the link the directories and avoid
> this kind
> of problem?
I'm not sure that I realy understand. Your question seems to be "Can I have two directories with the same name at the same place ?".
What would you like subversion to do exactly when you checkout your project A ?
EEBXXX_YYYZZZ (From Project A)
Dev (From Project A)
??? (From Project B svn:externals), it can not be also Dev...
Regards,
Christophe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: RE: RE: svn:externals problem in checkout
Posted by LIRA Olavo <Ol...@gemalto.com>.
> Yes, I think that it is normal.
> You should not have a directory Dev in >your project A.
> It will be created at checkout time by the svn:externals.
> Just remove your Dev directory from A and it should be OK
Thank you Christophe,
But in my case I also have the Dev directory in both projects,
is there another way to do the link the directories and avoid this kind
of problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: RE: svn:externals problem in checkout
Posted by Méresse Christophe <ch...@nagra.com>.
> My svn:externals is: "Dev/ https://repository/trunk/toto"
>
> Where directory Dev already exist in project A, but when I
> change the value to:
> "Dev/temp https://repository/trunk/toto"
> Where temp is not under SVN control, then it works fine.
>
> Is it normal? Is there another way to avoid this kind of
> problem? Should I use something else than svn:externals for this
> situation?
Yes, I think that it is normal. You should not have a directory Dev in your project A.
It will be created at checkout time by the svn:externals.
Just remove your Dev directory from A and it should be OK
Regards
Christophe Méresse
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: svn:externals problem in checkout
Posted by LIRA Olavo <Ol...@gemalto.com>.
I'm sorry to ask again, but does someone have any idea to help me with
this? Thanks!
========================================
Olavo Lira
-----Original Message-----
From: LIRA Olavo [mailto:Olavo.LIRA@gemalto.com]
Sent: Thursday, December 14, 2006 12:02 PM
To: users@subversion.tigris.org
Subject: svn:externals problem in checkout
Hello,
I need some help in my design structure in SVN server. I have
project that is composed by other projects, so I have started to use
svn:externals property as the link between projects.
But the problem comes when I try to do a checkout of folders
that belong from project B into an existing folder in project A. It
gives me the following error:
-----------
Fetching external item into 'EEBXXX_YYYZZZ\Dev'
svn: 'EEBXXX_YYYZZZ\Dev' is already a working copy for a
different URL
-----------
My svn:externals is: "Dev/ https://repository/trunk/toto"
Where directory Dev already exist in project A, but when I
change the value to:
"Dev/temp https://repository/trunk/toto"
Where temp is not under SVN control, then it works fine.
Is it normal? Is there another way to avoid this kind of
problem? Should I use something else than svn:externals for this
situation?
Thanks in advance,
==========
Olavo Lira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
svn:externals problem in checkout
Posted by LIRA Olavo <Ol...@gemalto.com>.
Hello,
I need some help in my design structure in SVN server. I have
project that is composed by other projects, so I have started to use
svn:externals property as the link between projects.
But the problem comes when I try to do a checkout of folders
that belong from project B into an existing folder in project A. It
gives me the following error:
-----------
Fetching external item into 'EEBXXX_YYYZZZ\Dev'
svn: 'EEBXXX_YYYZZZ\Dev' is already a working copy for a
different URL
-----------
My svn:externals is: "Dev/ https://repository/trunk/toto"
Where directory Dev already exist in project A, but when I
change the value to:
"Dev/temp https://repository/trunk/toto"
Where temp is not under SVN control, then it works fine.
Is it normal? Is there another way to avoid this kind of
problem? Should I use something else than svn:externals for this
situation?
Thanks in advance,
==========
Olavo Lira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn 1.4.2 tells me the it is 1.2.3
Posted by Theo Van Dinter <fe...@kluge.net>.
On Thu, Dec 14, 2006 at 12:08:04AM +0100, LIRA Olavo wrote:
> I'm a newbie in this list and I have installed the svn-win32
> 1.4.2 but when I run the svn --version it shows me:
>
> svn, version 1.2.3 (r15833)
>
> Does any one have a clue of what am I doing wrong?
My guess is that you have multiple versions of SVN installed, likely in
different areas.
--
Randomly Selected Tagline:
"A computer is a stupid machine with the ability to do incredibly smart
things, while computer programmers are smart people with the ability to
do incredibly stupid things. They are, in short, a dangerously perfect
match." - Bill Bryson.