Re: UserName in SVN Update
Guten Tag Mahdi Pakzad, am Samstag, 26. Oktober 2013 um 11:45 schrieben Sie: > (tortoisesvn version: 1.83) TorotiseSVN has it's own support mailing list and besides that, you won't get any help there, too, if you don't describe your error much more detailed. http://tortoisesvn.net/support.html Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Subversion Exception!
--- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list archives for the error message to avoid reporting the same problem repeatedly. You can find the mailing list archives at http://subversion.apache.org/mailing-lists.html Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.2\ext\subversion\subversion\libsvn_client\commit_util.c' line 211: assertion failed (repos_root_url && repos_relpath) --- OK --- I had two folders with the same name one inside the other (for example: c:\temp\temp), I wanted to delete one of them: 1. I have renamed with subversion the first folder to another name (C:\temp2\temp) 2. I have moved the versioned items to the parent folder (C:\temp2 and C:\temp) 3. I have deleted the old parent folder (C:\temp)
Re: Limiting access to a subtree when using svn+ssh:// access
On Oct 25, 2013, at 22:28, Branko Čibej wrote: > On 25.10.2013 22:23, Alfred von Campe wrote: >> Everything is working as expected so far. Users in each group can only >> access their respective projects, and users in both groups can access both >> projects. But now we want to prevent a subset of users in GroupB from >> accessing certain subtrees of ProjectB. Can this be done when using >> svn+ssh:// access? If so, how? > > http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.serverconfig.svnserve.auth.general Excellent, thanks for that pointer. Don't know how I missed that, but I guess it's a feature we have not used before. All our svnserve.conf files are unmodified from when they were created with svnadmin. Alfred
RE: Subversion Exception!
Hi 'Casual Trash', (Sorry, got that from your e-mail address; not sure if this is going to you :)) I'm looking into this problem and it appears the move recipe at the bottom of your mail is a nice way to get the Subversion working copy in an inconsistent state in 1.8.3, 1.8.4 (to be released soon) and trunk. I hope I can get this fixed soon. Can you tell me how you invoke the commit? (I can reproduce the database inconsistency, but not the exception when committing) Bert From: Casual Trash [mailto:casualtr...@hotmail.com] Sent: maandag 28 oktober 2013 10:02 To: users@subversion.apache.org Subject: Subversion Exception! --- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list archives for the error message to avoid reporting the same problem repeatedly. You can find the mailing list archives at http://subversion.apache.org/mailing-lists.html Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.2\ext\subversion\subversion\lib svn_client\commit_util.c' line 211: assertion failed (repos_root_url && repos_relpath) --- OK --- I had two folders with the same name one inside the other (for example: c:\temp\temp), I wanted to delete one of them: 1. I have renamed with subversion the first folder to another name (C:\temp2\temp) 2. I have moved the versioned items to the parent folder (C:\temp2 and C:\temp) 3. I have deleted the old parent folder (C:\temp)
Preserve timestamps while creating tag with SVN copy
I would like to be able to create a tag using the SVN copy command so that the timestamps on the files in the destination are the same as those in the source. Is this possible?
Re: Preserve timestamps while creating tag with SVN copy
Guten Tag Steve Cohen, am Montag, 28. Oktober 2013 um 22:27 schrieben Sie: > I would like to be able to create a tag using the SVN copy command so > that the timestamps on the files in the destination are the same as > those in the source. > Is this possible? Not with svn commands alone, you would need to tag and afterwards copy the source files again with preservation of timestamps. Something like cp -rp xy z Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
How to revert a --record-only svn merge before a commit
Hi All We use SVN 1.6 How do we perform a svn merge "revert" of a revision number that is --record-only in linux shell before a svn commit ? We perform svn merge --record-only -c 1234 http://testsomething.com We like to revert that step. Thank you Sincerely
Re: Preserve timestamps while creating tag with SVN copy
Steve Cohen wrote:
>I would like to be able to create a tag using the SVN copy command so
>that the timestamps on the files in the destination are the same as
>those in the source.
there are no individual timestamps on files in the repository, only
one timestamp on the revision as a whole.
If you are talking about the timestamp of the commit / tag though ...
That can easyly be changed to match the tag source using "svn propset
svn:date --revprop -r ".
Be aware that the "svn -r {date} ..." syntax will no longer work
properly if you do so (because it relies on the revision timestamps to
be ordered).
And you will need a pre-revprop-change hook to allows revprop changes.
--
Lorenz
