How to revert a directory to a previous revision
Hi, I want to revert 2 directories in my repos to a previous revision. In the repos view, when I right-click on the folder I want to revert I see an option "revert to previous version" or the like. Right-clicking the local directory to replace it with a previous version does not give me the option to revert to a specific version - just "Base revision", "Latest from repository" and "Base revision" What is the best way to do this? I have Subversion 1.6.17 I use the Subclipse (v1.6.18) Subversion plugin in Eclipse. I use Tortoise 1.6.16 (b 21511) Windows 7
How to create a tag from multiple revisions?
Hello, As the subject says, I want to create a tag consisting of at least 2 different revisions in the trunk. All revisions concern the same project. Reason is, I have several revisions in the trunk and I want to exclude some revisions from the tag because the code in those is not yet production ready. For example the trunk consists of this: trunk/ rev333 rev331 rev330 rev229 rev228 I want to create a tag based on rev333 and rev330 but not rev 331 since that code is not finished yet. Am I able to do this - using subclipse or tortoise? Thanks, Marc
1.7.0-rc2: abnormal program termination on Windows
With the pre-built CollabNet binaries from https://ctf.open.collab.net/sf/go/rel2972, I get an abnormal program termination, if the URL is not valid: D:\temp>svn --version svn, version 1.7.0-rc2 (Release Candidate 2) compiled Aug 26 2011, 11:47:28 D:\temp>"C:\program files (x86)\Subversion\svn.exe" checkout file://d:\temp\test\repo.svn d:\temp\wc.svn svn: E235000: In file '..\..\..\subversion\libsvn_client\checkout.c' line 94: assertion failed (svn_uri_is_canonical(url , pool)) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. -- Best regards, Marc Strapetz = syntevo GmbH http://www.syntevo.com http://blog.syntevo.com
Re: 1.7.0-rc2: abnormal program termination on Windows
On 07.09.2011 17:02, Bert Huijben wrote: > > >> -Original Message----- >> From: Marc Strapetz [mailto:marc.strap...@syntevo.com] >> Sent: woensdag 7 september 2011 14:40 >> To: users@subversion.apache.org >> Subject: 1.7.0-rc2: abnormal program termination on Windows >> >> With the pre-built CollabNet binaries from >> https://ctf.open.collab.net/sf/go/rel2972, I get an abnormal program >> termination, if the URL is not valid: >> >> D:\temp>svn --version >> svn, version 1.7.0-rc2 (Release Candidate 2) >>compiled Aug 26 2011, 11:47:28 >> >> D:\temp>"C:\program files (x86)\Subversion\svn.exe" checkout >> file://d:\temp\test\repo.svn d:\temp\wc.svn >> svn: E235000: In file '..\..\..\subversion\libsvn_client\checkout.c' >> line 94: assertion failed (svn_uri_is_canonical(url >> , pool)) >> >> This application has requested the Runtime to terminate it in an unusual >> way. >> Please contact the application's support team for more information. > > I can reproduce this problem and will look into fixing this. > > There are two problems with your URL that will probably make it fail even > after this assertion is fixed. > > The correct url format is file:///d:/temp/test/repo.svn with three slashes > after file:. > file://server/share/ would translate to \\server\share, so your path points > to \\d:\temp\test\repo.svn. Thanks, Bert. I've fixed my URL and RC 2 works well so far. -- Best regards, Marc Strapetz = syntevo GmbH http://www.syntevo.com http://blog.syntevo.com
Exception: Assertion failed wc_db.c line 9465
Hi there, I just got the following error using svn 1.7 (build TortoiseSVN-1.7.0): D:\Foo>svn status R + C lib\ExternalLib > local edit, incoming replace upon update [...] D lib\ExternalLib\ServiceLocation.pdb M bat\environment.build ! src\Project1 svn: E235000: In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\wc_db.c' line 9 465: assertion failed (work_presence == svn_wc__db_status_normal || work_presence == svn_wc__db_status_not_present || wo rk_presence == svn_wc__db_status_base_deleted) What I did: Last week I upgraded from an 1.6.something to 1.7 without doing a cleanup with the 1.6 version. The WC upgrade went well. It is possible, that there were uncommited changes at that time. Today some operations on ExternalLib caused a tree conflict on that folder. I deleted the lib folder in the file system and updated the working copy (restoring the deleted folder). Today I was wondering if I had uncommited changes and called svn status. The result is shown above. Deleting and updating src\Project1 didn't fix the problem. It is still marked as modified and causes the exception. Calling svn status in the Project1 folder causes the problem as well. Best Regards, Marc Messing Rheinmetall Defence Electronics GmbH Software Architect C4I Brüggeweg 54 28309 Bremen Germany Tel +49 421 457-1017 Fax +49 421 457-1028 marc.mess...@rheinmetall.com Rheinmetall Defence Electronics GmbH Brüggeweg 54 - D-28309 Bremen - Tel +49 421 457-01 - Fax +49 421 457-2900 - Sitz der Gesellschaft: Bremen - Register: Amtsgericht Bremen, HRB 9659 Commerzbank AG, Bremen (BLZ 290 400 90) 102213600 Aufsichtsratsvorsitzender: Heinz Dresia - Geschäftsführung: Luitjen Ennenga, Georg Morawitz, Ulrich Sasse, Thorsten Quade - www.rheinmetall-defence.com
Assertion on updated
I just got following assertion on "svn update": Fetching external item into 'ext-normal': ... svn: E235000: In file '..\..\..\subversion\libsvn_wc\update_editor.c' line 1582: assertion failed (action == svn_wc_conflict_action_edit || action == svn_wc_conflict_action_delete || action == svn_wc_conflict_action_replace) D:\svntest\small-1.7-1>svn --version svn, version 1.7.0 (r1176462) compiled Oct 12 2011, 16:57:34 -- Best regards, Marc Strapetz = syntevo GmbH http://www.syntevo.com http://blog.syntevo.com
Python-subversion
Hello,
I'm using subversion and python-subversion on a debian squeeze system.
The package version is 1.6.12dfsg-4.
I'm trying to modify the behavior of the changed command of the
svnlook.py file provided by python-subversion.
I'm want to show that a directory was copied by adding a "+" to the
output - the way genuine svnlook command do.
I've modified the add_directory method of the ChangedEditor as follow:
def add_directory(self, path, parent_baton,
copyfrom_path, copyfrom_revision, dir_pool):
print('A %s %s/' % ("+" if copyfrom_path else " ", path))
return [ 0, path ]
but the copyfrom_path always equals to None.
Is there a way to have this parameter set?
Thanks,
Marc Schlinger.
This message has been scanned for viruses by BlackSpider MailControl. -
www.blackspider.com
Re: Python-subversion
Le jeudi 08 décembre 2011 à 15:20 +0200, Daniel Shahaf a écrit :
> Marc Schlinger wrote on Thu, Dec 08, 2011 at 14:07:06 +0100:
> > Hello,
> >
> > I'm using subversion and python-subversion on a debian squeeze system.
> > The package version is 1.6.12dfsg-4.
> >
> > I'm trying to modify the behavior of the changed command of the
> > svnlook.py file provided by python-subversion.
> >
> > I'm want to show that a directory was copied by adding a "+" to the
> > output - the way genuine svnlook command do.
> >
> > I've modified the add_directory method of the ChangedEditor as follow:
> >
> > def add_directory(self, path, parent_baton,
> > copyfrom_path, copyfrom_revision, dir_pool):
> >
> > print('A %s %s/' % ("+" if copyfrom_path else " ", path))
> > return [ 0, path ]
> >
> > but the copyfrom_path always equals to None.
> >
> > Is there a way to have this parameter set?
> >
>
> What does viewvc do to cause
> http://svn.apache.org/viewvc?view=revision&revision=1207555
> to show "(Copied from
> subversion/trunk/contrib/server-side/mod_dontdothat, r1207550)"
> ?
Thanks for pointing out this project. I didn't even notice it was
written in python.
To answer your question.
They call the svn.fs.copied_from(rev_root, path) method to get the
copyfrom_path information.
They don't seem to implement the "editor" interface, so I still don't
know how to get the copyfrom_info directly in add_directory.
>
> > Thanks,
> >
> > Marc Schlinger.
> >
> >
This message has been scanned for viruses by BlackSpider MailControl. -
www.blackspider.com
Re: Python-subversion
Le jeudi 08 décembre 2011 à 19:39 +0200, Daniel Shahaf a écrit :
> Marc Schlinger wrote on Thu, Dec 08, 2011 at 16:00:03 +0100:
> > Le jeudi 08 décembre 2011 à 15:20 +0200, Daniel Shahaf a écrit :
> > > Marc Schlinger wrote on Thu, Dec 08, 2011 at 14:07:06 +0100:
> > > > Hello,
> > > >
> > > > I'm using subversion and python-subversion on a debian squeeze system.
> > > > The package version is 1.6.12dfsg-4.
> > > >
> > > > I'm trying to modify the behavior of the changed command of the
> > > > svnlook.py file provided by python-subversion.
> > > >
> > > > I'm want to show that a directory was copied by adding a "+" to the
> > > > output - the way genuine svnlook command do.
> > > >
> > > > I've modified the add_directory method of the ChangedEditor as follow:
> > > >
> > > > def add_directory(self, path, parent_baton,
> > > > copyfrom_path, copyfrom_revision, dir_pool):
> > > >
> > > > print('A %s %s/' % ("+" if copyfrom_path else " ", path))
> > > > return [ 0, path ]
> > > >
> > > > but the copyfrom_path always equals to None.
> > > >
> > > > Is there a way to have this parameter set?
> > > >
> > >
> > > What does viewvc do to cause
> > > http://svn.apache.org/viewvc?view=revision&revision=1207555
> > > to show "(Copied from
> > > subversion/trunk/contrib/server-side/mod_dontdothat, r1207550)"
> > > ?
> >
> > Thanks for pointing out this project. I didn't even notice it was
> > written in python.
> >
> > To answer your question.
> > They call the svn.fs.copied_from(rev_root, path) method to get the
> > copyfrom_path information.
> >
> > They don't seem to implement the "editor" interface, so I still don't
> > know how to get the copyfrom_info directly in add_directory.
>
> Perhaps you should use svn_repos_replay() to drive your editor?
>
That's excatly what I've found in svnlook::main.c . They use
svn_repos_replay2.
In python it's in the subpackage repos of package svn.
The right method to use is svn.repos.replay2 because the api have
changed.
http://subversion.apache.org/docs/api/1.6/svn__repos_8h.html#aef0fa3335d10b603cfbae5efc7a5d016
Since python subversion is an "dummy" binding of the subversion C api I
think this is the right place to look at.
Thank you for your help.
> A quick look into the source of svn_repos_dir_delta2() (which is what
> 'svnlook.py changed' uses) suggests that it always passes '(NULL,
> SVN_INVALID_REVNUM)' for the copyfrom.
>
>
> Click https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== to report
> this email as spam.
This message has been scanned for viruses by BlackSpider MailControl. -
www.blackspider.com
log -g reports revisions in wrong order
One of our users encounters a strange order of log revisions. When invoking an: svn log -v -g the top-level revision r1605930 is reported before top-level revision r2571860. In my understanding, this should not be possible. For a log without merged revisions included, the order is fine. How can we investigate that further? CollabNet Subversion Edge 2.1.0 hosted on Linux (RedHat Enterprise Linux WS 3, 32-bit). CollabNet Subversion Client 1.7.2, 32-bit Windows version, running on Windows 7 64-bit. -Marc
Undocumented: ssl-pkcs11-provider - What is a «Security Provider»?
Hi I got a proprietary PKCS#11 library (for Post SuisseID smartcard) in /usr/lib/libcvP11.so. There is a configuration option «ssl-pkcs11-provider» in ~/.subversion/servers. But it is absolutely undocumented what this option is, even google doesn't find anything useful. The only documentation is: «Name of PKCS#11 provider to use». How is the «Name of PKCS#11 provider» defined? It is *not* the name of the PKCS#11 library, so what is it? Everytthing I tried results in «unable to load PKCS#11 provider», e.g.: user@host:~/svn/project$ LANG= svn up svn: Invalid config: unable to load PKCS#11 provider '/usr/lib/libcvP11.so' user@host:~/svn/project$ ls -l /usr/lib/libcvP11.so -rwxr-xr-x 1 root root 5279688 Jul 6 14:30 /usr/lib/libcvP11.so So: - What is the missing link? - How to get a PKCS#11 /usr/lib/libcvP11.so library into svn? - Could you please add some understandable documentation? Thank you Regards Marc
How to use SVN and PKCS#11? [Re: Undocumented: ssl-pkcs11-provider - What is a «Security Provider»?]
Am Samstag, 25. August 2012, 17.35:50 schrieben Sie: > += dev@, please drop users@ from replies It's not a developper question, it's a usage question. I am asking this as a user. Sorry, but I don't understand your answer. I build nothing, I install the packages from the ubuntu repository. > If you build svn against neon 0.28 or greater, the value of that option > is passed is passed to ne_ssl_pkcs11_provider_init(): > https://svn.apache.org/repos/asf/subversion/branches/1.7.x/subversion/libsvn > _ra_neon/session.c I absolutely do not understand. You have to specify what at compile time? That's absurd; how should the package builder know what the users will need? And PKCS#11 libraries are commonly loaded at runtime using dlopen, so there must surely be a way to specify a library at runtime?!? > However, current trunk no longer uses the ssl-pkcs11-provider option, > but still generates a config file that documents it. (The option was > originally added in r869495(r29421) by jorton for libsvn_ra_neon. > (Marc: libsvn_ra_neon is no longer supported in trunk/1.8-to-be; only > libsvn_ra_serf will be available for http/https access.)) So how is PKCS#11 specified now? > We should at least update the config file that trunk generates. We > might want to teach libsvn_ra_serf to support that config option (for > compatibility reasons). Again, the question is: How to specify /usr/lib/libcvP11.so (or any other arbitray library) as PKCS#11 provider? Does SVN work with PKCS#11 token? If yes: How? (I mean at runtime.) Thank you Regards
modifyng symlinks
Hello, I'm using : svn, version 1.7.7 (r1393599) compiled Nov 7 2012, 19:23:31 on a debian host. I am trying to create and apply a patch on a repos with the new svn commands: svn diff and svn patch. The commit is, for what matters, changing the target of a symlink. The patch section related to my symlink looks like this: Modified: folder/symlink === --- folder/symlink 2012-10-18 10:56:32 UTC (rev 76023) +++ folder/symlink 2012-10-18 11:25:32 UTC (rev 76024) @@ -1 +1 @@ -link file \ No newline at end of file +link other_file \ No newline at end of file Since I'm on a linux host my symlink file is really a symlink. This way "svn patch" is actually trying to modify "folder/file" instead of editing file pointed by "folder/symlink". Is this a known behaviour ? Regards, Marc Schlinger
Subversion/Dreamweaver, Error #175002
Hi, I'm not certain what version of Subversion we're using at work, but I ran into an issue after the IT team changed the port from a custom to the default port. I'm unable to commit any of my files using Dreamweaver CS4 and the IT team says their servers are fine (great!). I do have access to "TortoiseSVN" so I see the files in the repo, but I'd really like to get this feature working with Dreamweaver again. I tried to commit this file /foodsafety/@09/about.html and I got this error: SVN: #175002, Commit failed (details follow): MKCOL of '/svn/foodsafety/!svn/wrk/06507cd4-1619-a24a-afdb-6b76fbd45c66/trunk/@09': 405 Method Not Allowed Thank you for any help. -- Marc Ferguson www.fergytech.com www.digitalalias.net "When life gives me lemons... I make Linuxaide, hmm good stuff!"
how to identify the version of mod_dav_svn installed
Although we have installed SVN 1.6.6, the web-page delivered reports 1.4.6 Could someone advise how to identify the version of mod_dav_svn apache-module that is installed? Ty.
Re: how to identify the version of mod_dav_svn installed
thanks for the hint. Can I just grab the mod_dav_svn.so and mod_authz.so files from Collabnet's 1.6.6-rpm distribution and replace the existing modules with it? Or will it result in compatibility issues with the Apache-server? Am 12.01.2010 um 16:43 schrieb Ryan Schmidt: > Quoting Marc Lustig: > >> Although we have installed SVN 1.6.6, the web-page delivered reports 1.4.6 >> >> Could someone advise how to identify the version of mod_dav_svn >> apache-module that is installed? > > I think you've already discovered how: look on the web page. It says 1.4.6. > You have mod_dav_svn from Subversion 1.4.6. Or at least, you did when Apache > started. If you've since then updated mod_dav_svn, restart Apache to see this > change. > > >
Subversion 1.9 working copy compatibility
From my experiments with Subversion 1.9 binaries and the listed changes in the release notes, Subversion 1.9 seems to be backwards compatible with Subversion 1.8 working copies. Is that correct? If so, it makes sense to update the "Upgrading the Working Copy" section: https://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade At least I was initially reluctant to try Subversion 1.9 on my real-world working copies to avoid troubles when switching back to 1.8. -Marc
Re: Subversion 1.9 working copy compatibility
On 16.03.2015 16:34, Branko Čibej wrote:> On 16.03.2015 15:58, Marc Strapetz wrote: From my experiments with Subversion 1.9 binaries and the listed changes in the release notes, Subversion 1.9 seems to be backwards compatible with Subversion 1.8 working copies. Is that correct? There are no schema changes, but 1.9 is faster at many working copy operations due to more optimized queries. Does that mean than an "svn upgrade" should still be invoked to get these optimized queries? -Marc On 16.03.2015 16:34, Branko Čibej wrote: On 16.03.2015 15:58, Marc Strapetz wrote: From my experiments with Subversion 1.9 binaries and the listed changes in the release notes, Subversion 1.9 seems to be backwards compatible with Subversion 1.8 working copies. Is that correct? There are no schema changes, but 1.9 is faster at many working copy operations due to more optimized queries. If so, it makes sense to update the "Upgrading the Working Copy" section: https://subversion.apache.org/docs/release-notes/1.9.html#wc-upgrade At least I was initially reluctant to try Subversion 1.9 on my real-world working copies to avoid troubles when switching back to 1.8. Absolutely; the release notes are not final until 1.9.0 is released; that's why they're not published on our site (i.e., there's no link to the 1.9 release notes on the site). We'll be updating them until the last minute. -- Brane
Subversion 1.8.13 on Cygwin: E170000 or E180001: Unable to connect to a repository at URL , Unable to open an ra_local session to URL
Hi, I've been using subversion on my Windows 7 PC with Cygwin with a repository on a Linux server accessed via file://. I installed a brand new Cygwin version yesterday. My local workspace lost its connection to the repository. I can no longer access via svn the repository which I was previously using on the same PC. % svn status -u svn: E17: Unable to connect to a repository at URL 'file://server/path/repository/trunk' svn: E17: Unable to open an ra_local session to URL svn: E17: Local URL 'file://server/path/repository/trunk'contains unsupported hostname % svn ls file:server/path/repository svn: E180001: Unable to connect to a repository at URL 'file:///server/path/repository' svn: E180001: Unable to open an ra_local session to URL svn: E180001: Unable to open repository 'file:///server/path/repository' % ls //server/path/repository conf dav db format hooks locks README.txt The new svn version is 1.8.13 (r1667537) on i686-pc-cygwin. The previous svn version I was using is 1.6.17. With file:// I get the E17 error. With file:/// or file: I get the E180001 error. The repository directory is technically on another computer but is seen as local on my PC (I guess it's NFS or SAMBA) when accessed with the // prefix from the shell. I tried touch-ing a new file in the repository's directory and that worked, with correct owner, group and file permissions when checked from the Linux server. If I copy the repository folder to my local /tmp, I can access it correctly via svn. But that's obviously not my goal. If I access the repository via the URL svn+ssh://somelinuxcomputer/nfspath/repository, that works. But my experience with the SSH tunnel is that it tends to slow down access. Has anyone experienced this problem before? Any suggestions? Thanks in advance
RE: Subversion 1.8.13 on Cygwin: E170000 or E180001: Unable to connect to a repository at URL , Unable to open an ra_local session to URL
Hi Bert, Thanks for your reply. 1) Are you suggesting that Cygwin executables are cross-compiled for Cygwin under Linux? Are you sure of this? I’ve never come across a Linux environment for cross-compiling code for Cygwin execution. Do you have more information about this? 2) Access to the same repository worked fine with the previous svn on Cygwin on the same Windows computer, same Linux server, same network. Are you suggesting that someone removed the path mapping capability from svn between versions 1.6 and 1.8? Marc From: Bert Huijben [mailto:b...@qqmail.nl] Sent: vendredi 26 juin 2015 05:17 To: MORGAN Marc; users@subversion.apache.org Subject: Re: Subversion 1.8.13 on Cygwin: E17 or E180001: Unable to connect to a repository at URL , Unable to open an ra_local session to URL The cygwin version of Subversion is a unix compilation of subversion running on Windows, via the cygwin libraries. As such it doesn't understand special Windoes paths. If you would use a normal windows client (compiled for windows; not cygwin) it would understand that it should transform file://myserver/share/path to \\myserver\share\path. If you would like to use the cygwin version, you should probably map the network share and then relocate your working copy. Bert Sent from Surface From: MORGAN Marc<mailto:marc.mor...@csem.ch> Sent: Thursday, June 25, 2015 3:47 PM To: users@subversion.apache.org<mailto:users@subversion.apache.org> Cc: MORGAN Marc<mailto:marc.mor...@csem.ch> Hi, I’ve been using subversion on my Windows 7 PC with Cygwin with a repository on a Linux server accessed via file://. I installed a brand new Cygwin version yesterday. My local workspace lost its connection to the repository. I can no longer access via svn the repository which I was previously using on the same PC. % svn status -u svn: E17: Unable to connect to a repository at URL 'file://server/path/repository/trunk' svn: E17: Unable to open an ra_local session to URL svn: E17: Local URL 'file://server/path/repository/trunk'contains unsupported hostname % svn ls file:server/path/repository svn: E180001: Unable to connect to a repository at URL 'file:///server/path/repository' svn: E180001: Unable to open an ra_local session to URL svn: E180001: Unable to open repository 'file:///server/path/repository' % ls //server/path/repository conf dav db format hooks locks README.txt The new svn version is 1.8.13 (r1667537) on i686-pc-cygwin. The previous svn version I was using is 1.6.17. With file:// I get the E17 error. With file:/// or file: I get the E180001 error. The repository directory is technically on another computer but is seen as local on my PC (I guess it’s NFS or SAMBA) when accessed with the // prefix from the shell. I tried touch-ing a new file in the repository’s directory and that worked, with correct owner, group and file permissions when checked from the Linux server. If I copy the repository folder to my local /tmp, I can access it correctly via svn. But that’s obviously not my goal. If I access the repository via the URL svn+ssh://somelinuxcomputer/nfspath/repository, that works. But my experience with the SSH tunnel is that it tends to slow down access. Has anyone experienced this problem before? Any suggestions? Thanks in advance
Re: 1 updated user can't commit
On 27.01.2016 09:35, Johan Corveleyn wrote: On Tue, Jan 26, 2016 at 8:26 PM, Corey Meyer wrote: Howdy, I have a repository that I have multi-users updating and committing to and from. Sadly my machine can’t commit. Since updating from SmartSVN7 to SmartSVN9 I get a number of errors depending on circumstances. If i’m trying to commit over the internet (which is normal, the server lives in Seattle and I’m near Tacoma and half my other users are in New Jersey) I most likely get an error were SVN just crashes or from the command line I get svn: E120105: Commit failed (details follow): svn: E120105: Error running context: The server sent an improper HTTP response I was in the office yesterday on the same network and got a lot less crashes but many of the same errors. After many attempts to rectify the commits I started getting this error instead libsvn: Out of memory - terminating application. Abort trap: 6 Now i know my other users are not having any issue updating or committing, i’m not having any issue updating but I am the only one who can’t commit. I also know I’m the only one who has updated subversion to 1.9.3 and SmartSVN9. As the IT guy i probably should have done this on a test box but I wasn’t really expecting there to be any issues, haha jokes on me. Any help would be fantastically welcomed and I’m happy to answer any questions that will help me resolve this! Hi Corey, Some users on this list might have experience with SmartSVN, but most of us don't. The lingua franca around here is "command line usage of the native client" (i.e. a binary that's been built from officially released sources by the Apache Subversion project). The problem which Corey has reported is reproducible with command line client (he just discovered it using SmartSVN). Now, I have some vague recollection that SmartSVN7 still used SVNKit inside (which is a pure Java re-implementation of svn, not supported by the Apache Subversion project, having its own mailinglist etc). For SmartSVN 7, this is correct. > And SmartSVN9 probably uses a native svn client (svnkit has not made a 1.9 release yet). SmartSVN 9 is using the official SVN binaries (just we are using a custom build process). There might be some leftover working copy corruption, This was my first suspect also, but the problem is reproducible with a clean Check Out, even for different repositories (URLs). -Marc
Slow SSL handshake/authentication
One of our Subversion 1.9 users is encountering a slow SSL handshake (or maybe even subsequent connection) to a Jetty 7.6.16.v20140903 server. This happens on Windows and OSX. Interestingly, when using Subversion 1.7, access works fast as expected. Also, accessing the same URL using curl or from the browser works fast. Any ideas what could cause this? I'm also able to reproduce the problem and I can provide credentials for a test repository on the affected server. -Marc
Feature Request: svn upgrade [--check][--check-current]
There is a lot of effort and hacks on determining what SVN database version is being used on the working copy. Usually resorting to examining the internal contents of a .svn/* file. For future releases it would be nice if there was a command to display if the current working copy is at the same level as the svn version being used, and if not if it is upgradable. The use case is to be able to detect early on in a build process if the wrong version of SVN was used. Examples: svn upgrade --check . CURRENT: yes UPGRADABLE: yes VERSION: 20 exit code 0 to indicate upgradable, which should be a no-op svn upgrade --check . CURRENT: no UPGRADABLE: yes VERSION: 19 exit code 0 to indicate upgradable svn upgrade --check . CURRENT: no UPGRADABLE: no VERSION: unknown exit code non-zero to indicate not upgradable svn upgrade --check-current . CURRENT: yes UPGRADABLE: yes VERSION: 20 exit code 0 to indicate no upgrade is needed svn upgrade --check-current . CURRENT: NO UPGRADABLE: yes VERSION: 19 exit code 1 to indicate upgrade is needed svn upgrade --check-current . CURRENT: NO UPGRADABLE: no VERSION: unknown exit code 2 to indicate upgrade cannot be performed
Re: Feature Request: svn upgrade [--check][--check-current]
I had found some of the magic formulas before, which was how I was aware of looking into the .svn directory. Thank you for the detailed responses which I can wrap into local commands, and should be sufficient for my needs. However I believe a supported, documented, and forward compatible way is preferable; given the volume of questions that come up when googling it seems to be a popular item. The problem I am working on is to have a bash script exit early with a clear error message if: - the script was checked out in a svn workspace version that is not expected, older or newer. - the script is executed on a host that has an old version of svn that cannot work with the workspace. - the script is executed on a host that has a newer version of svn, such that the workspace would have to be upgraded. It is an issue when there are manual operations in a distributed environment with a shared file system. It is a common error to accidentally perform manual operations on a host that has the wrong svn version. Especially since the old versions have to be retained on some workstations. Thanks for the quick response Marc On Dec 2, 2016 12:13 PM, "Daniel Shahaf" wrote: > Marc Pawlowsky wrote on Fri, Dec 02, 2016 at 11:50:14 -0500: > > There is a lot of effort and hacks on determining what SVN database > > version is being used on the working copy. Usually resorting to > > examining the internal contents of a .svn/* file. > > The incantation is: > > format_number=`head -n1 .svn/format` > if [ "$format_number" -eq 12 ]; then > format_number=`sqlite3 .svn/wc.db 'pragma user_version;'` > fi > > This inspects .svn directly, and as such is *not* guaranteed to be > forward compatible. (We don't anticipate breaking it, but we may.) > > See SVN_WC__VERSION (in wc.h) for the format-number-to-minor-version map. > > > For future releases it would be nice if there was a command to display > > if the current working copy is at the same level as the svn version > > being used, and if not if it is upgradable. > > > > The use case is to be able to detect early on in a build process if > > the wrong version of SVN was used. > > > > Couldn't you run, say, 'svn info >/dev/null' and see whether it gives > error E155036 or not? > > % ./tools/dev/which-error.py E155036 > 00155036 SVN_ERR_WC_UPGRADE_REQUIRED > > Going through your scenarios: > > > svn upgrade --check-current . > > CURRENT: yes > > UPGRADABLE: yes > > VERSION: 20 > > exit code 0 to indicate no upgrade is needed > > 'svn info' will exit 0. > > > svn upgrade --check-current . > > CURRENT: NO > > UPGRADABLE: yes > > VERSION: 19 > > exit code 1 to indicate upgrade is needed > > 'svn info' will report E155036 (and 'svn upgrade' will succeed). > > > svn upgrade --check-current . > > CURRENT: NO > > UPGRADABLE: no > > VERSION: unknown > > exit code 2 to indicate upgrade cannot be performed > > Only happens in corner cases (e.g., > <https://subversion.apache.org/docs/release-notes/1.8.html#wc-upgrade>). > 'svn info' will report E155036 and 'svn upgrade' will error out. > > I'm not sure whether we have today a way to distinguish "non-current, > non-upgradeable" from "non-current, upgradeable", without actually > running 'svn upgrade'. Perhaps others can speak to that. > > > > > To be clear, I'm not opposed to adding such functionality; I'm simply > trying to understand why the use-case can't be addressed with existing > features. > > Cheers, > > Daniel >
Feature Request: svn update --accept failure
Sometimes failure is an option. I am working inside a complex scripting environment. It would be better if when svn update detects a conflict that the update did not occur and that the command would fail. The versioned versions of the file could still be crated and maybe another one that would have the standard conflict markers, but the original file should be unchanged versus copied into the .mine. The exit code should be non-zero, so it is easy to detect. This new behaviour would only occur with a new option to --accept, I like "--accept failure". Another addition that work with "--accept failure" is if svn update also had --dry-run. Thanks for your considering this feature. Marc Pawlowsky
Question about subversion
Hi there. I have a question about subversion. I have a theory on what files should not be on SVN and I would like you to tell me if you agree. If you dont agree can you tell me why please. If you see more files that should not be there, tell me and why. Files who should not be on SVN : * files automatically generated * files containing specific information about my development environment (so properties files for example) * executable files PS: I am conscious that we can put anything to subversion but I am looking for Best practices Thank you so much * "Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire. Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel." **
Re: Question about subversion
Thank you for your answers... all of you @Andrew Thank you, the answers you gave were exactly what I thought about (I was a little bit too general when I asked the question) - concerning answer number 2 (specific files) Let's say I have a parameter file with paths for my dev environement. Typically I would not put it on svn because everybody has different ones... but how to I version the param file (without it the application does not work) Message original Sujet: Re: Question about subversion De : Andrew Reedick Pour : Marc Davenne , users@subversion.apache.org Date : 26/06/2013 18:39 From: Marc Davenne [mailto:marc.dave...@cramif.cnamts.fr] Sent: Wednesday, June 26, 2013 10:37 AM To: users@subversion.apache.org Subject: Question about subversion Hi there. I have a question about subversion. I have a theory on what files should not be on SVN and I would like you to tell me if you agree. If you dont agree can you tell me why please. If you see more files that should not be there, tell me and why. Files who should not be on SVN : * files automatically generated * files containing specific information about my development environment (so properties files for example) * executable files PS: I am conscious that we can put anything to subversion but I am looking for Best practices Thank you so much Wrong question. The correct question is: Do I have what I need to reproduce the build? Generally speaking: * The reasons to avoid checking in generated files are: - they can be re-created automatically, - checking them in results in duplicate data which - takes up space unnecessarily - leads to data synchronization issues, i.e. are the generated files I checked in, the same as the files the build generates? And before you say that's a stupid thing to worry about, ask yourself what happens when a checked in generated file is no longer generated by the build? (Someone will have to manually delete the no longer needed generated file from the repo.) * The reason to avoid checking in dev environment files is because they're different between everyone's work environment and provide no value to the build process. * The reasons to avoid checking in executable files are: - they're big - they can't be merged, and/or - the executable is generated by the build and thus can be re-built from code if necessary. However, as others have noted, there are times when you want to check in such files. They're guidelines, not hard and fast rules. Guidelines/Rules exist to support your goals. Your goals are build reproducibility, accurate deployments, and other SCM-ish things that allow your organization to deliver a product that customers will pay money for so that your company can pay your salary. Craft your guidelines/rules in that context and you'll be fine. * "Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire. Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel." **
Re: Question about subversion
I am not sure I understand it very well. When you say it is ignored, does it mean it is on svn ? And what is this script that would trigger on checkout ? Can you explain it again ? Message original Sujet: Re: Question about subversion De : Cooke, Mark Pour : Marc Davenne , Andrew Reedick Copie à : "users@subversion.apache.org" Date : 27/06/2013 11:40 -Original Message----- From: Marc Davenne [mailto:marc.dave...@cramif.cnamts.fr] Sent: 27 June 2013 10:25 To: Andrew Reedick Cc: users@subversion.apache.org Subject: Re: Question about subversion Thank you for your answers... all of you @Andrew Thank you, the answers you gave were exactly what I thought about (I was a little bit too general when I asked the question) - concerning answer number 2 (specific files) Let's say I have a parameter file with paths for my dev environement. Typically I would not put it on svn because everybody has different ones... but how to I version the param file (without it the application does not work) I think it was BOb who gave an answer for that one... What I do is to svn:ignore the file itself, then check in a default version with a different filename (e.g. extra `.tmpl` extension) and provide some sort of `initialisation` script that can be used on fresh checkout to copy the template file(s) to the right name(s) for use. For exmaple, I have several .ini files to target different servers (development, test, site1, site2 etc) all checked in with the actual .ini file name ignored. I then copy the right one for what I want to the right name. The different ini fils are then versioned in the repo. ~ mark c * "Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire. Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel." **
wc.db: corruption after move?
We are encountering working copies with nodes.presence = moved and nodes.moved_to = As far as I have been told, this has already been fixed and backported to 1.8.5. Still, for those users which already have this corruption, is there a way to recover their working copies with standard Subversion functionality? Could a Revert work? And if it currently does not, could the Revert be more tolerant, so it could handle such cases? -Marc
Re: wc.db: corruption after move?
On 26.11.2013 18:27, Branko Čibej wrote: > On 26.11.2013 18:08, Philip Martin wrote: >> Marc Strapetz writes: >> >>> We are encountering working copies with >>> >>> nodes.presence = moved and nodes.moved_to = >> What does "nodes.presence = moved" mean? There has never been a moved >> presence. Sorry, actually in the underlying wc.db, it should be: presence = normal and op_depth > 0 and moved_here > 0 >> Do you mean rows with nodes.moved_here=1 no corresponding rows with >> non-null nodes.moved_to? Exactly, that seems to be the case. >> Or something else? >>> As far as I have been told, this has already been fixed and backported >>> to 1.8.5. Still, for those users which already have this corruption, is >>> there a way to recover their working copies with standard Subversion >>> functionality? Could a Revert work? And if it currently does not, could >>> the Revert be more tolerant, so it could handle such cases? >> What operation is failing? Are you getting some error? I can't tell whether an operation fails, because an assertion when reading the wc.db is hit before. I'd expect some operations (in the GUI) to fail later, because we are assuming at various places that a moved file must have a move-source. Is this assumption correct? > Marc is looking at some code that converts wc.db info to some internal > structure ... > > Marc, can you please explain how the wc.db itself looks like? Hint: we > don't support SmartSVN or SVNKit here. :) Unfortunately I haven't seen such a wc.db until now, but when tracing back the conversions we do, the resulting problematic wc.db *should* look like as described above. -- Best regards, Marc Strapetz = syntevo GmbH http://www.syntevo.com
Re: wc.db: corruption after move?
On 26.11.2013 21:38, Philip Martin wrote: > Marc Strapetz writes: > >>>>> As far as I have been told, this has already been fixed and backported >>>>> to 1.8.5. Still, for those users which already have this corruption, is >>>>> there a way to recover their working copies with standard Subversion >>>>> functionality? Could a Revert work? And if it currently does not, could >>>>> the Revert be more tolerant, so it could handle such cases? >>>> What operation is failing? Are you getting some error? >> >> I can't tell whether an operation fails, because an assertion when >> reading the wc.db is hit before. I'd expect some operations (in the GUI) >> to fail later, because we are assuming at various places that a moved >> file must have a move-source. Is this assumption correct? > > Is that Subversion that is asserting? It would help if you showed the > exact error or assertion. It's an assertion in SmartSVN which directly reads wc.db. > If moved_to is missing Subversion usually falls back to copy and delete: OK, so it's a valid wc.db state? I think that answers my question and I will fix/remove SmartSVN's assertion accordingly. > $ svnadmin create repo > $ svn import -mm repo/format file://`pwd`/repo/A/f > $ svn co file://`pwd`/repo wc > $ svn wc/A wc/B > $ svn mv wc/B/f wc/B/g > > $ svn st wc > D wc/A > > moved to wc/B > D wc/A/f > A +wc/B > > moved from wc/A > D +wc/B/f > > moved to wc/B/g > A +wc/B/g > > moved from wc/B/f > > $ sqlite3 wc/.svn/wc.db "update nodes set moved_to = null" > $ svn st wc > D wc/A > D wc/A/f > A +wc/B > D +wc/B/f > A +wc/B/g -Marc
Re: wc.db: corruption after move?
On 27.11.2013 11:32, Bert Huijben wrote: > > >> -Original Message----- >> From: Marc Strapetz [mailto:marc.strap...@syntevo.com] >> Sent: woensdag 27 november 2013 09:30 >> To: Philip Martin >> Cc: Branko Čibej; users@subversion.apache.org >> Subject: Re: wc.db: corruption after move? >> >> On 26.11.2013 21:38, Philip Martin wrote: >>> Marc Strapetz writes: >>> >>>>>>> As far as I have been told, this has already been fixed and backported >>>>>>> to 1.8.5. Still, for those users which already have this corruption, is >>>>>>> there a way to recover their working copies with standard Subversion >>>>>>> functionality? Could a Revert work? And if it currently does not, could >>>>>>> the Revert be more tolerant, so it could handle such cases? >>>>>> What operation is failing? Are you getting some error? >>>> >>>> I can't tell whether an operation fails, because an assertion when >>>> reading the wc.db is hit before. I'd expect some operations (in the GUI) >>>> to fail later, because we are assuming at various places that a moved >>>> file must have a move-source. Is this assumption correct? >>> >>> Is that Subversion that is asserting? It would help if you showed the >>> exact error or assertion. >> >> It's an assertion in SmartSVN which directly reads wc.db. >> >>> If moved_to is missing Subversion usually falls back to copy and delete: >> >> OK, so it's a valid wc.db state? I think that answers my question and I >> will fix/remove SmartSVN's assertion accordingly. > > No, this is not a valid state. But we prefer to fix the problem how you got > there, over updating Subversion to cope with invalid states everywhere. Unfortunately the user who has encountered this problem doesn't know (anymore) how he came into that state. -Marc
New svn client format (1.7+) breaks when checkout crosses filesystems
Howdy, On my personal system, I got a new svn and as prompted by "your repo is too old", upgraded it to the new format (svn 1.7.13). And now I'm very hosed. legolas:/var/local/scr# svn update svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted legolas:/var/local/scr# svn cleanup svn: E18: Can't move '/.svn/tmp/svn-1FyLjO' to '/var/local/scr/btrfs-subvolume-backup': Invalid cross-device link Indeed, I use svn across my entire system to keep track of changed files, and this goes across filesystems. Been doing this for years, well until now I guess. / is my root /var/local/scr is 2 levels of filesystems mounted on top svn now keeps everything in /.svn it seems and naively assumes it can rename files across locations I don't really want to rebuild my entire svn checkout in 7 different ones (one per filesystem), not counting that I'd have to manually fix what svn state that isn't synced on each of my client checkouts. What are my options? 1) revert to svn 1.6 but I don't think I can revert my svn repo state without going back to backups, I'm assuming it's a one way upgrade. 2) split my repo in 7 pieces, which sucks as explaine above (going to be hours of manual work and checking over multiple systems) and reverting/rolling this out. 3) other :) Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/
Re: New svn client format (1.7+) breaks when checkout crosses filesystems
First, thanks for your answer, and sorry my late answer On Mon, Feb 03, 2014 at 03:05:28PM -0800, Ben Reser wrote: > On 2/3/14, 2:26 PM, Marc MERLIN wrote: > > On my personal system, I got a new svn and as prompted by "your repo is > > too old", upgraded it to the new format (svn 1.7.13). > > You mean working copy, there is no such message about repositories. We > support > repositories all the way back to 1.0. Yes, I did. After working with svn, p4, and git, I tend to confuse the terms a bit, sorry. > It's no longer supported for a working copy to cross file systems. > Unfortunately, doesn't look like we documented that fact in our release notes: > http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng So be it. Maybe it would be good for svn upgrade to notice this and fail, or at least print a warning? > This has caused some issues on Windows as well where permissions become > problematic because the files are not made under the same directory as their > destination. So it's possible we might change this in the future. But that > does nothing to help you right now. Indeed :) but I appreciate the info nonetheless. > > I don't really want to rebuild my entire svn checkout in 7 different ones > > (one > > per filesystem), not counting that I'd have to manually fix what svn state > > that > > isn't synced on each of my client checkouts. > > > > What are my options? > > 1) revert to svn 1.6 but I don't think I can revert my svn repo state > > without going back to backups, I'm assuming it's a one way upgrade. > > Before starting it would be a good idea to take a backup of the files if you > have concerns about local modifications. Sound advise. > Note what revision you're at in your working copy with svnversion (I'll assume > $WC is your $WC root from here on out) > svnversion $WC Good idea, but: legolas:/var/local/scr# svnversion svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted legolas:/var/local/scr# svnversion / svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted > Hopefully that's not a mixed revision range, if it is you may have some issues > with the following. If it's locally modified that should be ok. > > Remove the .svn working copy metadata directory: > rm -rf $WC/.svn > > Run the checkout again with 1.6 client where $REV is the revision you got from > svnversion and $URL is the $URL to your repo: > svn-1.6 checkout --force -r $REV $URL $WC > > You'll get a lot of E lines (which is the client saying the file already > exists). It'll still have your local modifications. Thanks for the tip. I'll try some of that on one client, but on the others I probably > However, we no longer support 1.6, so you probably want to upgrade to 1.7/1.8 > at some point or you're going to be stuck in the past. I know, I lose, I'll have to rebuild my entire system. Maybe I'll just switch away from svn considering how much work it'll be anyway. > This (splitting your working copy) is probably your best bet. However, to be > honest with you this was never a task to which Subversion was made for. I'm Apparently not. I used to do this with cvs, then upgraded to svn, now maybe to something else. I understand that my use case is clearly not a majority so I'll deal. > guessing you're already using some sort of wrapper to deal with permissions. actually I don't because I only check config files and scripts that do not need special owners or permissions. > So it seems to me you need to extend the wrapper to deal with multiple working > copies on each file system and keeping them in sync. More than likely you > need > to request the latest revision from the server (1.7/1.8: use svn info $URL and > pull out the Revision: field; 1.9 will have svn youngest for this purpose). > Then run svn up -r $REV on each working copy. > > > 3) other :) > > I don't see any other choices. Thanks for laying down the options, it definitely helps me plan about what I should do next. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
svn file compatibility 1.6, 1.8 on Fedora 20
I am on two different hosts with different SVN versions. Host1 is using svn client 1.6.18 and checks out all the files. Host2 is using svn client 1.8.8 and using NFS works on the same files as Host1. e.g. The actual files are shared across machines, not copies. I cannot upgrade the files with svn upgrade, since the files must irk on host1. Can someone please confirm that svn 1.8.8 cannot work on the files that were checked out with the older version. host2$ svn info libs svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at 'xxx/libs' is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy. My expectation would be that the newer client would be able to work with the older files without having to upgrade them, just not supporting the newer features. Failing that, how do I install svn 1.6.8 on Fedora 2? I tried to install subversion-1.6.17-5.fc16.x86_64.rpm, and I tried building from rpm source but there are too many incompatible libraries. Thanks in advance, Marc
subversion - svnsync synchronize hangs - how to debug?
Hi: I’ve been trying to get an SVN repository to synchronize to a target server. When I run the svnsync synchronize [target-http-url] [target-svn+ssh-url] I get the following output: Transmitting file data . It just hangs there. I managed to get some logging on the svnserve source side switched on and the last entry I see in the log is: 32272 2014-12-01T18:28:35.638273Z - [uid] [repo-name] replay / r108 Would love some suggestions about how to debug this. I've checked out revisions 107, 108 and 109 successfully. Thanks!
Re: subversion - svnsync synchronize hangs - how to debug?
+Mailing list > On Dec 1, 2014, at 4:30 PM, Marc Breslow wrote: > > Hi Andreas. Thanks so much for your quick reply. Please find my responses > inline: > —Marc > >> On Dec 1, 2014, at 4:06 PM, Andreas Stieger wrote: >> >> Hi, >> >>> On 1 Dec 2014, at 18:40, Marc Breslow wrote: >>> >>> I’ve been trying to get an SVN repository to synchronize to a target >>> server. When I run the >>> svnsync synchronize [target-http-url] [target-svn+ssh-url] I get the >>> following output: >>> >>> Transmitting file data . >> >> Why are you specifying the target twice? > > I’m not. I just wrote it wrong in the email. Sorry about that. Corrected > to this > >svnsync synchronize [target-http-url] [source-svn+ssh-url] > >> >>> It just hangs there. I managed to get some logging on the svnserve source >>> side switched on and the last entry I see in the log is: >>> >>> 32272 2014-12-01T18:28:35.638273Z - [uid] [repo-name] replay / r108 >> >> Does the target repository start a transaction, is there network traffic and >> is the in-progress transaction changing on disk? > > I don’t have direct access to the target svn server. I will need to work > with someone tomorrow to find this out. > svn info [target-url] shows > Revision: 0 > Node Kind: directory > Last Changed Rev: 0 > >> >>> >>> Would love some suggestions about how to debug this. I've checked out >>> revisions 107, 108 and 109 successfully. >> >> Does "svnadmin dump" and "svnrdump dump" finish giving dumps for these >> revisions? > > svnrdump dump [source-svn+ssh-url] -r [rev] —incremental succeeds for revs > 107, 108 and 109 > svnadmin dump [local-path-to-repo] -r [rev] —incremental succeeds for revs > 107, 108 and 109 > >> >> Does syncing from a file:// source (on source host) to destination work? > > There is no route to target from source host. One of the reasons why I am > doing this sync. > >> >> Andreas >> >
Re: subversion - svnsync synchronize hangs - how to debug?
Did some more testing here and still stuck. In one test I changed the sync source to be a different repository on a different server and sync worked. So pretty sure it is an issue with the source repo now. There was also a question: > Does the target repository start a transaction, is there network traffic > and is the in-progress transaction changing on disk? We see the timestamp on the db/txn-current file being updated when svnsync synchronize starts but we don't see the content of that file changing from 'a' Any other thoughts on what the issue might be? On Tue, Dec 2, 2014 at 10:12 AM, Marc Breslow wrote: > +Mailing list > > > On Dec 1, 2014, at 4:30 PM, Marc Breslow wrote: > > > > Hi Andreas. Thanks so much for your quick reply. Please find my > responses inline: > > —Marc > > > >> On Dec 1, 2014, at 4:06 PM, Andreas Stieger > wrote: > >> > >> Hi, > >> > >>> On 1 Dec 2014, at 18:40, Marc Breslow wrote: > >>> > >>> I’ve been trying to get an SVN repository to synchronize to a target > server. When I run the > >>> svnsync synchronize [target-http-url] [target-svn+ssh-url] I get the > following output: > >>> > >>> Transmitting file data . > >> > >> Why are you specifying the target twice? > > > > I’m not. I just wrote it wrong in the email. Sorry about that. > Corrected to this > > > >svnsync synchronize [target-http-url] [source-svn+ssh-url] > > > >> > >>> It just hangs there. I managed to get some logging on the svnserve > source side switched on and the last entry I see in the log is: > >>> > >>> 32272 2014-12-01T18:28:35.638273Z - [uid] [repo-name] replay / r108 > >> > >> Does the target repository start a transaction, is there network > traffic and is the in-progress transaction changing on disk? > > > > I don’t have direct access to the target svn server. I will need to > work with someone tomorrow to find this out. > > svn info [target-url] shows > > Revision: 0 > > Node Kind: directory > > Last Changed Rev: 0 > > > >> > >>> > >>> Would love some suggestions about how to debug this. I've checked out > revisions 107, 108 and 109 successfully. > >> > >> Does "svnadmin dump" and "svnrdump dump" finish giving dumps for these > revisions? > > > > svnrdump dump [source-svn+ssh-url] -r [rev] —incremental succeeds for > revs 107, 108 and 109 > > svnadmin dump [local-path-to-repo] -r [rev] —incremental succeeds for > revs 107, 108 and 109 > > > >> > >> Does syncing from a file:// source (on source host) to destination work? > > > > There is no route to target from source host. One of the reasons why I > am doing this sync. > > > >> > >> Andreas > >> > > > >
svnsync/diff zlib - trying to understand/figure out an error
Hello, While creating a replica of an existing repository using svnsync, I bumped into a problem that I'm trying to figure out. In short, I don't think SVN is to blame but that we've got a corrupted transaction/file somewhere. I'm just trying to figure out the options and next steps to fix this. This is what happens: we create an empty repository and start syncing it with a remote one. At a certain transaction, we get the error 'Decompression of svndiff data failed' and the syncing stops. If I look at the files in that transaction (using svn log --verbose) I only see two files with a .java_ extension. I suspect that these are text files, maybe leftovers of a text editor. I've done some investigations on internet and had a look at the subversion files, especially subversion/libsvn_delta/svndiff.c. The error is linked to the 'uncompress' function of zlib. As I understand it, svnsync is replaying all the transactions from the original repository - or at least as much as possible giving the properties of the revision, etc. My questions: - I suspect this error is related to a corrupted (or missing) file. Is this correct? - Is zlib used for some other purpose within svn that I don't know about (except for zip/unzip of a file)? - is there any way to figure out which file in that transaction is giving this error? Or see the 'contents' of the transaction in full? svnsync doesn't seem to have a verbose mode that tells what exactly it is doing - Can I trust the output of 'svn diff --summarize? Since that invokes the same file/library (svndiff.c) as svnsync. Thanks for your ideas. Regards, Marc Verwerft
Cannot load mod_dav_svn.so into server: libsvn_subr-1.so.0: undefined symbol: apr_memcache_add_server
Hi, I am trying to set up SVN 1.6.9 to use Apache 2.2.4. I am using APR and APR-UTIL 1.3.9, NEON 0.29.3, SQLite-3.6.22 After "configure, make, make install" all compononents, i did the same for svn. httpd -l returns: Compiled in modules: core.c mod_authn_file.c mod_authn_default.c mod_authz_host.c mod_authz_groupfile.c mod_authz_user.c mod_authz_default.c mod_auth_basic.c mod_cache.c mod_disk_cache.c mod_mem_cache.c mod_include.c mod_filter.c mod_log_config.c mod_env.c mod_setenvif.c mod_ssl.c prefork.c http_core.c mod_mime.c mod_dav.c mod_status.c mod_autoindex.c mod_asis.c mod_cgi.c mod_dav_fs.c mod_negotiation.c mod_dir.c mod_actions.c mod_userdir.c mod_alias.c mod_rewrite.c mod_so.c All is fine, up untill the second I try to restart apache which returns this error message:Cannot load mod_dav_svn.so into server: libsvn_subr-1.so.0: undefined symbol: apr_memcache_add_server. I have no idea what is happening. I could resume normal operations on my server by commenting out the LoadModule clauses in httpd.conf. Any idea, input would be greatly appreciated. Cordially,JM _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969
Re: Is there a simple log/diff frontend (like gitk)?
yes, the guys are right, you probably need to update your WC. this is feature, not a bug. some svn clients do not behave this way, like ms-windows tortoise. for mac, i recommended a friend of mine smartsvn, he quite enjoyed it. works for windows too, it is probably written in java. my friend was quite comfortable with it. he is not a developer but quite keen with computers. 2010/4/14 Lorenz : > Ryan Schmidt wrote: >>On Apr 13, 2010, at 12:32, Thomas Allen wrote: >> >>> Maybe I have not yet >>> mastered the "log" command, but I find the output of the following >>> two commands to be confusing: >>> >>> $ svn log -r HEAD >>> >>> r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line >>> >>> full comments + jslint fixes >>> >>> $ svn log | grep tallen # outputs nothing >> >>Probably your working is not up to date. "svn up" before running "svn log" >>would probably work. > > because "svn log" on a working copy without "-r" defaults to "-r BASE" > which is the last checked-out/updated-to revision. > -- > > Lorenz > >
Embedding a working copy in a vendor branch
Hi, Over the years I have been using (T)SVN for lots of different projects, but this is something new. I want to start my own development (private repository) of some components/plugins for Joomla!. However, the folder structure of Joomla! is such that the files for these components/plugins must be spread across the source tree of Joomla! itself. So, on the one hand I have a need for a working copy (develop/test setup) that contains the Joomla! source as an svn:external, but that has regular folders/files for my personal additions. In a way I need my working copy to reside inside a vendor branch. Are there some other (T)SVN users with experience who could give some hints on how to proceed? Is is best to create a separate WC and add some 'build' step to copy the code into the Joomla! WC (or export) prior to testing (a bit of a PITA compared to just saving the files and hitting f5 in the browser). -- Regards, Jean-Marc -- . ___ . @@ // \\ "De Chelonian Mobile" . (_,\/ \_/ \ TortoiseSVN . \ \_/_\_/>The coolest Interface to (Sub)Version Control . /_/ \_\ http://tortoisesvn.net
