Re: Viewing the woking copy of a lock
Anton Shepelev wrote: >How can I view the working-copy path with which a >lock is associated, given the information about the >lock from `svnadmin lslocks'? you can't. The server knows nothing about the working copy and its location, only about the user. If you know the working copy, you could run "svn info" on all occurences of the file, to identify the working copy. -- Lorenz
Re: Viewing the woking copy of a lock
Lorenz to Anton Shepelev: >>How can I view the working-copy path with which a >>lock is associated, given the information about >>the lock from `svnadmin lslocks'? > >you can't. The server knows nothing about the >working copy and its location, only about the user. > >If you know the working copy, you could run "svn >info" on all occurences of the file, to identify >the working copy. I think it one of the rare cases when dear old SourceSafe was better, but of course we should reor- gaise our process to avoid situations when this functinality is desired. -- Please, do not forward replies to the list to my e-mail.
Nested groups in path based authorization?
Does svn path based authorization support nested groups? group_a = fred,jim group_b = jane,@group_a Best regards David
Re: Viewing the woking copy of a lock
Lorenz wrote on Tue, 20 Aug 2019 09:20 +00:00: > Anton Shepelev wrote: > >How can I view the working-copy path with which a > >lock is associated, given the information about the > >lock from `svnadmin lslocks'? > > you can't. > The server knows nothing about the working copy and its location, > only about the user. > > If you know the working copy, you could run "svn info" on all > occurences of the file, to identify the working copy. And for future reference, you can have your users lock files using something along the lines of «svn lock -m "$(hostname):$(pwd)"» to be able to answer your question. You could even enforce this with a pre-lock hook.
Re: Nested groups in path based authorization?
David Aldrich wrote on Tue, 20 Aug 2019 12:29 +00:00: > Does svn path based authorization support nested groups? > > group_a = fred,jim > group_b = jane,@group_a > > Best regards > David [[[ % cat authz [groups] group_a = fred,jim group_b = jane,@group_a [/] * = @group_b = r % svnauthz accessof --repository=r --path=/trunk -R --username=jane./authz r % svnauthz accessof --repository=r --path=/trunk -R --username=fred./authz r % svnauthz accessof --repository=r --path=/trunk -R --username=jrandom ./authz no % ]]] Looks like it does. Cheers, Daniel
Moving WC from one computer to another using tar?
I want to work on a project on a Raspberry Pi computer but this particular one is not networked with the svn server... I do have another RPi on the same network as the svn server so I can check out a WC to that computer via VPN access to the RPi. So I wonder if this would work: 1) Check out project on the remote RÅi accessed via VPN 2) Create a tar file of the resulting working copy 3) Transfer the tar file to my home network via FTP 4) Transfer the tar file on my local network to the target RPi 5) Unpack the wc on the target and work on the project 6) Make a tar file on the target and transfer in reverse to the RPi on the remote network 7) Commit changes from the remote RPi to teh remote svn server. Or are there some hidden tokens used to identify the client in the WC? Best Regards, Bo Berglund Sweden
Re: Moving WC from one computer to another using tar?
Bo Berglund wrote on Tue, 20 Aug 2019 17:27 +00:00: > So I wonder if this would work: Yes, with two caveats: - The versions of svn on the two RPis must use the same working copy format. All 1.8.0..1.12.x versions use the same working copy format as each other. - Recommend that you look into git-svn / hgsubversion / etc to be able to version patch series easily. Cheers, Daniel
Re: Viewing the woking copy of a lock
Daniel Shahaf: > And for future reference, you can have your users lock > files using something along the lines of `svn lock -m > "$(hostname):$(pwd)' to be able to answer your question. > You could even enforce this with a pre-lock hook. Thank you, Daniel. Since the pre-lock hook does not receive the actual working directory I can only theck the syntax of such a comment, but I will bear the option in mind. -- Please, do not forward replies to my e-mail.
