You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Florin Avram <av...@yahoo.com> on 2010/11/03 10:54:49 UTC
Log problem
Hi,
I've run over a strange situation and want to know if this is OK to happen (in
my opinion it shouldn't). These are the details:
- one of our servers has a repository with Subversion 1.4 format
- I have a working copy from a given repository path, let it be
"http://R/svn/repos/userguide"
- in my working copy, one of the folders has an external folder X, pointing to
"http://R/svn/repos/branches/rel/doc"
- I modify a file from the external folder X and commit it
- when looking over the log information of the root of my working copy, there is
no entry for the commit which I've just made (this is OK, I've committed to an
external resource)
- after, I look over the log information of the folder at which my working copy
external folder targets. There is no information about my commit there either,
which is strange, I've committed from my external folder which is pointing to
this one.
- the folder to which my working copy external folder is pointing was copied
from another branch, and if I do a log on that branch (the original one), then I
can see my commit, which again is strange: why the commit goes there and not to
the HEAD of the branch to which my external folder is pointing.
I don't know if the above information helps you somehow, but I would like to
know if this would be possible and if this is a repository side problem, taking
into account that the repository has an old version (1.4).
Thank you.
Best Regards,
Florin
Re: Log problem
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 5, 2010, at 05:05, Johan Corveleyn wrote:
> Just a wild guess: the syntax for the svn:externals property has
> changed (in 1.5 I believe): the order of the URL and the target were
> reversed (among other things). See
> http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html. Could
> it be that your problem is caused because the externals definition is
> now interpreted differently than before (by a 1.5+ client, as opposed
> to a 1.4 client previously)?
The old externals syntax is still supported, but as of 1.5 an additional syntax is supported as well with the order reversed.
Re: Log problem
Posted by Johan Corveleyn <jc...@gmail.com>.
[small nit: please don't top-post on this list, i.e. put your reply at
the bottom, or inline.]
On Fri, Nov 5, 2010 at 9:22 AM, Florin Avram <av...@yahoo.com> wrote:
> Hi,
>
> Thank you for your reply.
> My folders are up to date in my working copy, but the log information is the
> same either when requested on working copy resources or when using the
> repository URLs. Is strange that there is a long time since I work with this
> working copy structure and suddenly something which worked fine seems to be
> broken.
>
> Have any idea about what else could trigger this behavior ?!
>
> Best Regards,
> Florin
>
>
> ________________________________
> From: Ryan Schmidt <su...@ryandesign.com>
> To: Florin Avram <av...@yahoo.com>
> Cc: users@subversion.apache.org
> Sent: Wed, November 3, 2010 4:10:52 PM
> Subject: Re: Log problem
>
>
> On Nov 3, 2010, at 05:54, Florin Avram wrote:
>
>> I've run over a strange situation and want to know if this is OK to happen
>> (in my opinion it shouldn't). These are the details:
>> - one of our servers has a repository with Subversion 1.4 format
>> - I have a working copy from a given repository path, let it be
>> "http://R/svn/repos/userguide"
>> - in my working copy, one of the folders has an external folder X,
>> pointing to "http://R/svn/repos/branches/rel/doc"
>> - I modify a file from the external folder X and commit it
>> - when looking over the log information of the root of my working copy,
>> there is no entry for the commit which I've just made (this is OK, I've
>> committed to an external resource)
>> - after, I look over the log information of the folder at which my working
>> copy external folder targets. There is no information about my commit there
>> either, which is strange, I've committed from my external folder which is
>> pointing to this one.
>
> Is the folder up to date? Use "svn up" and try again.
>
>> - the folder to which my working copy external folder is pointing was
>> copied from another branch, and if I do a log on that branch (the original
>> one), then I can see my commit, which again is strange: why the commit goes
>> there and not to the HEAD of the branch to which my external folder is
>> pointing.
This seems very strange. If you commit a change into an external, it
should go exactly to that external, not to some other location of
which your external location is a copy. Are you sure that the external
property is set correctly?
Can you provide more details? Maybe give the exact contents of the
svn:externals property, and an overview of the repository structure
(feel free to obfuscate any paths or other information that may be
confidential)?
Just a wild guess: the syntax for the svn:externals property has
changed (in 1.5 I believe): the order of the URL and the target were
reversed (among other things). See
http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html. Could
it be that your problem is caused because the externals definition is
now interpreted differently than before (by a 1.5+ client, as opposed
to a 1.4 client previously)?
Cheers,
--
Johan
Re: Log problem
Posted by Florin Avram <av...@yahoo.com>.
Hi,
Thank you for your reply.
My folders are up to date in my working copy, but the log information is the
same either when requested on working copy resources or when using the
repository URLs. Is strange that there is a long time since I work with this
working copy structure and suddenly something which worked fine seems to be
broken.
Have any idea about what else could trigger this behavior ?!
Best Regards,
Florin
________________________________
From: Ryan Schmidt <su...@ryandesign.com>
To: Florin Avram <av...@yahoo.com>
Cc: users@subversion.apache.org
Sent: Wed, November 3, 2010 4:10:52 PM
Subject: Re: Log problem
On Nov 3, 2010, at 05:54, Florin Avram wrote:
> I've run over a strange situation and want to know if this is OK to happen (in
>my opinion it shouldn't). These are the details:
> - one of our servers has a repository with Subversion 1.4 format
> - I have a working copy from a given repository path, let it be
>"http://R/svn/repos/userguide"
> - in my working copy, one of the folders has an external folder X, pointing to
>"http://R/svn/repos/branches/rel/doc"
> - I modify a file from the external folder X and commit it
> - when looking over the log information of the root of my working copy, there
>is no entry for the commit which I've just made (this is OK, I've committed to
>an external resource)
> - after, I look over the log information of the folder at which my working copy
>external folder targets. There is no information about my commit there either,
>which is strange, I've committed from my external folder which is pointing to
>this one.
Is the folder up to date? Use "svn up" and try again.
> - the folder to which my working copy external folder is pointing was copied
>from another branch, and if I do a log on that branch (the original one), then I
>can see my commit, which again is strange: why the commit goes there and not to
>the HEAD of the branch to which my external folder is pointing.
>
> I don't know if the above information helps you somehow, but I would like to
>know if this would be possible and if this is a repository side problem, taking
>into account that the repository has an old version (1.4).
I doubt any problem exists.
Re: Log problem
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 3, 2010, at 05:54, Florin Avram wrote:
> I've run over a strange situation and want to know if this is OK to happen (in my opinion it shouldn't). These are the details:
> - one of our servers has a repository with Subversion 1.4 format
> - I have a working copy from a given repository path, let it be "http://R/svn/repos/userguide"
> - in my working copy, one of the folders has an external folder X, pointing to "http://R/svn/repos/branches/rel/doc"
> - I modify a file from the external folder X and commit it
> - when looking over the log information of the root of my working copy, there is no entry for the commit which I've just made (this is OK, I've committed to an external resource)
> - after, I look over the log information of the folder at which my working copy external folder targets. There is no information about my commit there either, which is strange, I've committed from my external folder which is pointing to this one.
Is the folder up to date? Use "svn up" and try again.
> - the folder to which my working copy external folder is pointing was copied from another branch, and if I do a log on that branch (the original one), then I can see my commit, which again is strange: why the commit goes there and not to the HEAD of the branch to which my external folder is pointing.
>
> I don't know if the above information helps you somehow, but I would like to know if this would be possible and if this is a repository side problem, taking into account that the repository has an old version (1.4).
I doubt any problem exists.