Re: svn:global-ignores limited to workspace dirs?
On Wed, Jul 23, 2014 at 05:50:00PM +0200, Stefan Sperling wrote: > On Wed, Jul 23, 2014 at 02:02:39PM +0200, Matthias Vorwerk wrote: > > Hi, > > > > setting the svn property svn:global-ignores to the repository root (or some > > higher level directory in the repository) - it obviously does not get > > inherited > > if I only checkout and work in some lower-level directory (until > > subversion-1.8.9) . > > > > It looks like the parent directory containing the svn:global-ignores > > property > > must be present in the workspace. This seems to be in contrast to e.g. the > > svn:auto-props property which may not be present in the workspace - it > > seems to > > be looked for also on the server - which is what I expect. > > > > So the effect of the current svn:global-ignores handling is that the client > > behavior depends on the hierarchy which is checked out in the workspace. > > > > Can you reproduce this bahvior? > > > > Regards, > > Matthias > > Yes, this is a bug. > > The function filter_unwanted_props() in libsvn_wc/wc_db.c seems filters out > the cached global-ignores prop because the property names it compares are > different (one is qualified with "svn:" and the other isn't), even though > they should be the same: > > 10240 if (strcmp(ipropname, propname) != 0) > (gdb) p ipropname > $5 = 0x21281cfda20 "global-ignores" > (gdb) p propname > $6 = 0x211f750bba6 "svn:global-ignores" > > I'm not sure off-hand how to fix this. > I've filed http://subversion.tigris.org/issues/show_bug.cgi?id=4515 > > Thanks for your report. I tried to look into this today but I cannot reproduce this bug anymore. I should have written a reproduction script. Matthias, do you have a way of reliably triggering this bug? Thanks.
RE: svnadmin pack vs hotcopy --incremental
> If you don't pack and hotcopy concurrently, it's perfectly safe. > > If you pack and hotcopy concurrently, it's almost safe. > There is a known problem with concurrent hotcopy and pack, the fix for which > isn't released yet, I believe. Details here: http://svn.apache.org/r1605633 What about the --incremental option? Any problems using it in conjunction with pack? My basic plan for the nightly housekeeping script is: svnadmin verify %repopath% svnadmin pack %repopath% svnadmin hotcopy %repopath% %backupdir% --incremental I should end up with a properly packed hotcopy at the end, right? Sincerely, Myron A. Semack
Re: svnadmin pack vs hotcopy --incremental
On Mon, Aug 04, 2014 at 12:46:06PM -0400, Myron A. Semack wrote: > > If you don't pack and hotcopy concurrently, it's perfectly safe. > > > > If you pack and hotcopy concurrently, it's almost safe. > > There is a known problem with concurrent hotcopy and pack, the fix for which > > isn't released yet, I believe. Details here: http://svn.apache.org/r1605633 > > What about the --incremental option? Any problems using it in conjunction > with pack? > > My basic plan for the nightly housekeeping script is: > > svnadmin verify %repopath% > svnadmin pack %repopath% > svnadmin hotcopy %repopath% %backupdir% --incremental > > I should end up with a properly packed hotcopy at the end, right? Yes, this should work. The incremental copy notices if the source was packed since the last incremental copy, creates corresponding packs in the destination repository and removes individual revision files from the destination afterwards. Just make sure not to run the last two commands in your list concurrently (i.e. pack the source while a hotcopy is in progress) until the change made in http://svn.apache.org/r1605633 is available in a released version of Subversion. With the fix, the hotcopy command will error out if a pack is in progress. Without it, the hotcopy will succeed but could create a destination repository which is not packed consistently, which will cause problems.
RE: Unable to load svn module from python2.6
Can you update please ? _ From: Muniyappan, Sasikumar (CWM-NR) Sent: 2014, August, 04 9:53 PM To: 'users@subversion.apache.org' Subject:Unable to load svn module from python2.6 Hi Team, >We have installed two python version. > > Python 2.6 > Python 2.4 > > We are able load the svn module from python2.4 and not able to do it from > python2.6. === python2.4 Python 2.4.6 (#1, Mar 23 2010, 12:41:43) [GCC 4.4.3 20100226 (Red Hat 4.4.3-8)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from svn import fs, repos, core >>> === > But subversion is binding python 2.6. can you tell me how to change the > subversion binding from pytton2.6 to python2.4 > > Thanks & Regards > Sasikumar M __ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive this e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Emails are monitored by supervisory personnel in jurisdictions where monitoring is permitted. Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information.
