On 7/29/07, Kai P Ford <fordkp@lnx5e023.enp.aramco.com.sa> wrote:
> Recently I noticed that all commits have the same Last Change Author of the repository owner, regardless of the person commiting. This only happens when commiting via the subclipse plug-in; commiting using the svn command line client does not exhibit the problem. Even newly created files have the wrong Last Change Author, not just modified ones.
>
> I believe this is related to a power outage and subsequent NFS file system problems that occurred a couple of weeks ago (while I was on vacation; there was no problem before I left). However, I have no clue how to diagnose and fix the problem. Any suggestions?
How are you determining this? When you run the Show History option
you see the wrong authors?
There is no such thing as a repository owner. I imagine you are
referring to the owner of the files in the filesystem but that is not
a value that is visible to Subversion or that it cares about other
than that it has the privileges it needs to access the files.
The key piece of info is the repository access method. file://,
https:// svn:// svn+ssh:// etc. I suspect you are using svn+ssh. It
is not uncommon in that scenario to have all users connect as a common
user, but there is a way to still provide a unique author. It is all
done in the SSH setup though. In Subclipse, if you use the SVNKit
client adapter option in your preferences, then it will prompt for all
of this info on the fly. Otherwise, Subclipse shares the SSH
configuration used by the command line client.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Jul 29 14:04:21 2007