switch error
I received the following error while trying to use switch: Matthew Hoffman Software Engineer ZK Celltest, Inc m...@zk.com --- 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.7\ext\subversion\subversion\libsvn_wc\wc_db.c' line 8713: assertion failed (svn_dirent_is_absolute(local_abspath)) --- OK ---
Re: switch error
On Thu, Aug 14, 2014 at 03:25:57PM -0700, Matt Hoffman wrote: I received the following error while trying to use switch: Matthew Hoffman Software Engineer ZK Celltest, Inc m...@zk.com Hi Matt, this looks like invalid input is being passed to SVN libraries. Please report this to the tortoisesvn project: http://tortoisesvn.net Thanks! --- 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.7\ext\subversion\subversion\libsvn_wc\wc_db.c' line 8713: assertion failed (svn_dirent_is_absolute(local_abspath)) --- OK ---
Re: Apache Subversion 1.7.18 released
On Mon, Aug 11, 2014 at 11:52 AM, Ben Reser bre...@apache.org wrote: I'm happy to announce the release of Apache Subversion 1.7.18. This release addresses two security issues: CVE-2014-3522: ra_serf improper validation of wildcards in SSL certs. CVE-2014-3528: credentials cached with svn may be sent to wrong server. For RHEL 6 users, or CentOS or Scientific Linux users, I've updated my hooks for building Subversion 1.7 RPM.s at https://github.com/nkadel/subversion-1.7.x-srpm. Look for tag v1.7.18-0.1 for the 1.7.18 build. Nico Kadel-Garcia nka...@gmail.com
Re: Apache Subversion 1.8.10 released
On Mon, Aug 11, 2014 at 11:52 AM, Ben Reser bre...@apache.org wrote: I'm happy to announce the release of Apache Subversion 1.8.10. This release addresses two security issues: CVE-2014-3522: ra_serf improper validation of wildcards in SSL certs. CVE-2014-3528: credentials cached with svn may be sent to wrong server. Please choose the mirror closest to you by visiting: http://subversion.apache.org/download/#recommended-release For RHEL 6 users, or CentOS or Scientific Linux users, I've updated my hooks for building Subversion 1.8 RPM.s at https://github.com/nkadel/subversion-1.8.x-srpm. Look for tag v1.8.10-0.1. Note that these include only patches and spec files, not binary tarballs. Get those from the relevant Apache repository. Repoforge seems to be mildly active again, I'll take another shot at getting these updates available there. Nico Kadel-Garcia nka...@gmail.com
Creating a pre-commit hook for copy operations
We're using Subversion 1.8.3 and need to create a pre-commit hook that checks copy operations (specifically branch creation) for certain conditions. Specifically, we want to be able to prevent users from creating branches in the wrong locations and similar errors. To accomplish this, we need to know the source and destination paths of the copy operation. Our current pre-commit hook (written in Python) uses a delta.Editor subclass to check other things. We tried overriding the add_directory method, which has a copyfrom_path argument -- this would have been perfect, but this argument is always empty. We also tried using the repos.Changecollector and repos.replay2, but this doesn't seem to give us information about the pending commit -- perhaps we are doing it wrong. Any suggestion would be much appreciated. Thanks
Re: Creating a pre-commit hook for copy operations
I had a similar problem of needing to look for copies. Rather than deal with the complexity of the API, I simply relied on the svnlook command output. Specifically, I used svnlook --transaction ${tx_id} changed --copy-info, and parsed the result. Eric On Fri, Aug 15, 2014 at 7:15 AM, Keath Milligan ke...@keathmilligan.net wrote: We're using Subversion 1.8.3 and need to create a pre-commit hook that checks copy operations (specifically branch creation) for certain conditions. Specifically, we want to be able to prevent users from creating branches in the wrong locations and similar errors. To accomplish this, we need to know the source and destination paths of the copy operation. Our current pre-commit hook (written in Python) uses a delta.Editor subclass to check other things. We tried overriding the add_directory method, which has a copyfrom_path argument -- this would have been perfect, but this argument is always empty. We also tried using the repos.Changecollector and repos.replay2, but this doesn't seem to give us information about the pending commit -- perhaps we are doing it wrong. Any suggestion would be much appreciated. Thanks
Re: Creating a pre-commit hook for copy operations
Thanks, Eric. svnlook gave me the clue I needed. I look at its source and found that I had been on the right track using ChangeCollector and replay2, but there was an error in my code. Once I got that fixed, my hook worked. On Fri, Aug 15, 2014 at 12:59 PM, Eric Johnson e...@tibco.com wrote: I had a similar problem of needing to look for copies. Rather than deal with the complexity of the API, I simply relied on the svnlook command output. Specifically, I used svnlook --transaction ${tx_id} changed --copy-info, and parsed the result. Eric On Fri, Aug 15, 2014 at 7:15 AM, Keath Milligan ke...@keathmilligan.net wrote: We're using Subversion 1.8.3 and need to create a pre-commit hook that checks copy operations (specifically branch creation) for certain conditions. Specifically, we want to be able to prevent users from creating branches in the wrong locations and similar errors. To accomplish this, we need to know the source and destination paths of the copy operation. Our current pre-commit hook (written in Python) uses a delta.Editor subclass to check other things. We tried overriding the add_directory method, which has a copyfrom_path argument -- this would have been perfect, but this argument is always empty. We also tried using the repos.Changecollector and repos.replay2, but this doesn't seem to give us information about the pending commit -- perhaps we are doing it wrong. Any suggestion would be much appreciated. Thanks
Re: Creating a pre-commit hook for copy operations
Another (and possibly easier) way is to use fs.paths_changed2 - the entries in that hash have copyfrom_path/copyfrom_rev fields indicating the source of the copy. Regards, Alexey. On Friday, August 15, 2014 11:24:18 am Keath Milligan wrote: Thanks, Eric. svnlook gave me the clue I needed. I look at its source and found that I had been on the right track using ChangeCollector and replay2, but there was an error in my code. Once I got that fixed, my hook worked. On Fri, Aug 15, 2014 at 12:59 PM, Eric Johnson e...@tibco.com wrote: I had a similar problem of needing to look for copies. Rather than deal with the complexity of the API, I simply relied on the svnlook command output. Specifically, I used svnlook --transaction ${tx_id} changed --copy-info, and parsed the result. Eric On Fri, Aug 15, 2014 at 7:15 AM, Keath Milligan ke...@keathmilligan.net wrote: We're using Subversion 1.8.3 and need to create a pre-commit hook that checks copy operations (specifically branch creation) for certain conditions. Specifically, we want to be able to prevent users from creating branches in the wrong locations and similar errors. To accomplish this, we need to know the source and destination paths of the copy operation. Our current pre-commit hook (written in Python) uses a delta.Editor subclass to check other things. We tried overriding the add_directory method, which has a copyfrom_path argument -- this would have been perfect, but this argument is always empty. We also tried using the repos.Changecollector and repos.replay2, but this doesn't seem to give us information about the pending commit -- perhaps we are doing it wrong. Any suggestion would be much appreciated. Thanks