You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Himanshu Raina <ra...@yahoo.com> on 2009/07/15 08:22:58 UTC
svn update error !!
Hi,
Since the data size is couple of GB's we are using checkout as opposed to svn export. The issue I'm facing is given below
When I run svn update on my working copy in case a project of the same name already exists the update stops. Later when I remove the conflicting project (i.e rm project) and run svn update keeps running i.e. it doesn't return to the prompt. I tried cleanup and ran svn update again but no result.
Morever what I have observed is usually svn update on working copy gives the following output
[designer@myserver current]$ svn status
? himanshu
Now suppose I commit project1 to my repo and run svn update on my wc
svn: Failed to add directory 'himanshu': object of the same name already exists
command finished
On working copy the svn status gives
[designer@myserver current]$ svn status
? himanshu
! . (! means item is missing (removed by non-svn command) or incomplete).
Now how do I get rid of this??
Regards
Himanshu Raina
See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371414
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: AuthzSVNAccessFile per project?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 16, 2009, at 03:12, 张宇 wrote:
> As our team grows up, we have to divide the big team into small
> ones, and each of the new team has its own configuration manager,
> who will manage the svn authz for his/her own team/project, but
> currently we have one AuthzSVNAccessFile, and the policy in our
> company did not allow the manager to see and modify the authz of
> other team. For example:
>
> Our SVN structure is :
>
> /svn/proj1
> /svn/proj2
> /svn/proj3
>
> Now if we have 2 team: t1 and t2,
>
> So, t1’s manager will see and manage proj1 & proj2, and t2’s
> manager will see and manage proj3, and admin could see and manage
> all of the projects.
>
> The problem is, in our current practice, manage authz requires
> editing an authz file, but if there is only one file, all manager
> will see all projects.
>
> How to setup multiple authz file?
Either split your single repository into multiple repositories - this
will be a pain, but would give you one authz file per repository
Or invent some kind of Makefile or script which glues multiple authz
fragments into a single combined authz file. Give each manager access
to just their authz snippet file, and have a way for the combined
authz file to be regenerated when changes are made to the snippets.
For example, you could host the authz snippets in a repository of
their own (or in a directory in your existing repository) and have a
post-commit hook which uses these to generate the final authz file
after every commit to those files.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371702
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
AuthzSVNAccessFile per project?
Posted by 张宇 <zh...@vancl.cn>.
Hi,
As our team grows up, we have to divide the big team into small ones, and each of the new team has its own configuration manager, who will manage the svn authz for his/her own team/project, but currently we have one AuthzSVNAccessFile, and the policy in our company did not allow the manager to see and modify the authz of other team. For example:
Our SVN structure is :
/svn/proj1
/svn/proj2
/svn/proj3
Now if we have 2 team: t1 and t2,
So, t1’s manager will see and manage proj1 & proj2, and t2’s manager will see and manage proj3, and admin could see and manage all of the projects.
The problem is, in our current practice, manage authz requires editing an authz file, but if there is only one file, all manager will see all projects.
How to setup multiple authz file?
Richard
_____
凡客诚品 技术部 张宇
分机：8127 MSN：pootow@msn.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371694
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: svn update error !!
Posted by Himanshu Raina <ra...@yahoo.com>.
Guess I wasn't clear with the requirement. Anyways I got it working with svn update --force. The requirement is explained below
I have a working copy of my repo on my webserver . This working copy contains both versioned and unversioned projects (I can't commit all, as some of these projects aren't active basis subscription but are still needed). Tomorrow if I want to make changes to one of these unversioned projects (say if the customer wants to get some content changed) I'll copy/move this code to my SVN and commit it. Now when I used to run svn update on my working copy it used to fail as it already had a version copy. In order to fix this I used to remove the unversioned copy from my wc and ideally on running svn update it should have checked out the versioned copy of that project. The problem started here as on running svn update for the second time the update used to hang or used to give error code 400 etc..
Hope this clarifies everything. Initially I thought it could be because I am using capistrano for release management but even without it (i.e by manually running svn update on working copy I got this error).
Regards
Himanshu Raina
--- On Thu, 16/7/09, Ryan Schmidt <su...@ryandesign.com> wrote:
From: Ryan Schmidt <su...@ryandesign.com>
Subject: Re: svn update error !!
To: "Himanshu Raina" <ra...@yahoo.com>
Cc: users@subversion.tigris.org
Date: Thursday, 16 July, 2009, 5:49 AM
On Jul 15, 2009, at 03:22, Himanshu Raina wrote:
> Since the data size is couple of GB's we are using checkout as
> opposed to svn export. The issue I'm facing is given below
>
> When I run svn update on my working copy in case a project of the
> same name already exists the update stops. Later when I remove the
> conflicting project (i.e rm project) and run svn update keeps
> running i.e. it doesn't return to the prompt. I tried cleanup and
> ran svn update again but no result.
>
> Morever what I have observed is usually svn update on working copy
> gives the following output
>
> [designer@myserver current]$ svn status
> ? himanshu
>
> Now suppose I commit project1 to my repo and run svn update on my wc
>
> svn: Failed to add directory 'himanshu': object of the same name
> already exists
> command finished
>
> On working copy the svn status gives
> [designer@myserver current]$ svn status
> ? himanshu
> ! . (! means item is missing (removed by non-svn command)
> or incomplete).
>
>
> Now how do I get rid of this??
Like Jochen, I'm unclear on exactly what commands you ran, what
happened, what you expected, or what you were actually trying to do.
But taking a guess: is it perhaps that you have a working copy of
your entire repository, and to create a new project, you create (with
your OS, not with Subversion) a new directory and start adding files
to it, and when you want to import it into Subversion you use "svn
import", and then you find when you "svn update" your working copy
that it complains that the project's directory already exists?
If so, there are a number of issues going on. Foremost is that "svn
import" imports an unversioned directory into the repository. It does
not transform that unversioned directory into a working copy, and the
intended workflow is that you then remove the directory and check it
out from the repository, or in your case, update the existing whole-
repository working copy that you already have. You may find it easier
to do a so-called "in-place import" instead of using "svn import".
The "in-place import" does transform an unversioned directory into a
working copy and you just continue using it, rather than having to
throw it away and get a new one, and is described here:
http://subversion.tigris.org/faq.html#in-place-import
Finally, it is unusual to have a working copy of the entire
repository, because most repositories contain not only the trunk of a
project (or of multiple projects), but also branches and tags, and
there's almost no reason why you would want to check out the trunk
and all branches and all tags. Instead, it's usual to check out a
working copy of just the trunk or branch or tag of just the project
you're interested in.
If you want to continue using the single monolithic working copy of
everything, then you don't need "svn import" or the "in-place import"
to add a new directory; all you need to do is "svn add" and "svn
commit" it.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371648
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371678
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: svn update error !!
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 15, 2009, at 03:22, Himanshu Raina wrote:
> Since the data size is couple of GB's we are using checkout as
> opposed to svn export. The issue I'm facing is given below
>
> When I run svn update on my working copy in case a project of the
> same name already exists the update stops. Later when I remove the
> conflicting project (i.e rm project) and run svn update keeps
> running i.e. it doesn't return to the prompt. I tried cleanup and
> ran svn update again but no result.
>
> Morever what I have observed is usually svn update on working copy
> gives the following output
>
> [designer@myserver current]$ svn status
> ? himanshu
>
> Now suppose I commit project1 to my repo and run svn update on my wc
>
> svn: Failed to add directory 'himanshu': object of the same name
> already exists
> command finished
>
> On working copy the svn status gives
> [designer@myserver current]$ svn status
> ? himanshu
> ! . (! means item is missing (removed by non-svn command)
> or incomplete).
>
>
> Now how do I get rid of this??
Like Jochen, I'm unclear on exactly what commands you ran, what
happened, what you expected, or what you were actually trying to do.
But taking a guess: is it perhaps that you have a working copy of
your entire repository, and to create a new project, you create (with
your OS, not with Subversion) a new directory and start adding files
to it, and when you want to import it into Subversion you use "svn
import", and then you find when you "svn update" your working copy
that it complains that the project's directory already exists?
If so, there are a number of issues going on. Foremost is that "svn
import" imports an unversioned directory into the repository. It does
not transform that unversioned directory into a working copy, and the
intended workflow is that you then remove the directory and check it
out from the repository, or in your case, update the existing whole-
repository working copy that you already have. You may find it easier
to do a so-called "in-place import" instead of using "svn import".
The "in-place import" does transform an unversioned directory into a
working copy and you just continue using it, rather than having to
throw it away and get a new one, and is described here:
http://subversion.tigris.org/faq.html#in-place-import
Finally, it is unusual to have a working copy of the entire
repository, because most repositories contain not only the trunk of a
project (or of multiple projects), but also branches and tags, and
there's almost no reason why you would want to check out the trunk
and all branches and all tags. Instead, it's usual to check out a
working copy of just the trunk or branch or tag of just the project
you're interested in.
If you want to continue using the single monolithic working copy of
everything, then you don't need "svn import" or the "in-place import"
to add a new directory; all you need to do is "svn add" and "svn
commit" it.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371648
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: svn update error !!
Posted by Jochen Wuttke <wu...@lu.unisi.ch>.
Hi,
your problem is not clear from your mail. However, it appears that you
are confusing fundamental concepts. Maybe you want to carefully read
the book first: http://svnbook.red-bean.com/nightly/en/svn.tour.html
On Jul 15, 2009, at 10:22 AM, Himanshu Raina wrote:
> Hi,
>
> Since the data size is couple of GB's we are using checkout as
> opposed to svn export. The issue I'm facing is given below
If you want to talk about working copies, svn checkout is the only way
to go. So why do you mention export here? Does it have any relevance
to your problem?
>
> When I run svn update on my working copy in case a project of the
> same name already exists the update stops. Later when I remove the
> conflicting project (i.e rm project) and run svn update keeps
> running i.e. it doesn't return to the prompt. I tried cleanup and
> ran svn update again but no result.
What is in your repository, and what is in your working copy?
How do you end up with the same project name in the repository and in
your working copy without those being synchronized somehow?
Maybe you want to show your repository layout, WC layout and the
actual command you run and its output.
> Morever what I have observed is usually svn update on working copy
> gives the following output
>
> [designer@myserver current]$ svn status
> ? himanshu
You are showing the ouput for 'status', not for 'update'. And what is
surprising about this output?
>
> Now suppose I commit project1 to my repo and run svn update on my wc
>
> svn: Failed to add directory 'himanshu': object of the same name
> already exists
> command finished
This is the output of 'commit' or 'update' ?
> On working copy the svn status gives
> [designer@myserver current]$ svn status
> ? himanshu
> ! . (! means item is missing (removed by non-svn command)
> or incomplete).
Overall, it is not clear what you are trying to do. Without this
information it is hard to help you. Try explain what you want to
achieve, how your data looks like, which command you run and what
their output is. Then maybe we can work something out for you.
Jochen
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2371419
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].