Re: Troubleshooting Gnome keyring

2012-12-20 Thread Nico Kadel-Garcia
On Wed, Dec 19, 2012 at 12:25 PM, Mark Phippard wrote: > On Tue, Dec 18, 2012 at 10:42 PM, Nico Kadel-Garcia wrote: >> On Tue, Dec 18, 2012 at 11:09 AM, Mark Phippard wrote: >>> On Mon, Dec 17, 2012 at 8:17 PM, Aubrey Barnard wrote: >>> I am having trouble getting Subversion to work with t

Re: subversion Exception

2012-12-20 Thread Andy Levy
On Thu, Dec 20, 2012 at 1:56 AM, Ravi Kant Sahu wrote: > I'm also facing same problem even in latest version (v1.7.10) of Tortoise > SVN : > > Same problem as who? Please quote context. > > --- > Subversion Exception! > --

problem when upgrading my working copy

2012-12-20 Thread Pia Unte
Hi, I keep having problems when upgrading my working copy. This keeps popping up when I try upgrading. I'm not sure what additional information you may need. Just tell me what you need. I'm not subscribed and would appreciate being explicitly Cc:ed in any responses. Thanks. Pia ---

Re: problem when upgrading my working copy

2012-12-20 Thread Philip Martin
Pia Unte writes: > In file > > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.10\ext\subversion\subversion\libsvn_wc\entries.c' > line 1666: assertion failed (parent_node || entry->schedule == > svn_wc_schedule_normal) I think that's a new one. Can you describe your working copy? Can you use

RE: problem when upgrading my working copy

2012-12-20 Thread Bert Huijben
> -Original Message- > From: MARTIN PHILIP [mailto:codematt...@ntlworld.com] On Behalf Of > Philip Martin > Sent: donderdag 20 december 2012 16:20 > To: Pia Unte > Cc: users@subversion.apache.org > Subject: Re: problem when upgrading my working copy > > Pia Unte writes: > > > In file >

Re: problem when upgrading my working copy

2012-12-20 Thread Philip Martin
"Bert Huijben" writes: > This is caused by upgrading an added directory without its parent directory. > Most likely caused by moving a single working copy directory. > > This state (added to a parent that does not exist) is not supported by the > new working copy database introduced in 1.7. The d

Subversion 1.7.8 released

2012-12-20 Thread Ben Reser
I'm happy to announce the release of Apache Subversion 1.7.8. Please choose the mirror closest to you by visiting: http://subversion.apache.org/download/#recommended-release The SHA1 checksums are: 12c7d8d5414bba74c9777c4d1dae74f152df63c2 subversion-1.7.8.tar.bz2 1e298368cc2a73337eaa

Re: problem when upgrading my working copy

2012-12-20 Thread Stefan Sperling
On Thu, Dec 20, 2012 at 04:07:11PM +, Philip Martin wrote: > "Bert Huijben" writes: > > > This is caused by upgrading an added directory without its parent directory. > > Most likely caused by moving a single working copy directory. > > > > This state (added to a parent that does not exist) i

SOLVED: Re: Merge after looking at eligible revs w/ merginfo command erroneously merging from branch base

2012-12-20 Thread Eric Malkowski
After looking at this some more, we had some svn:mergeinfo properties that were set at one layer below the branch / trunk levels from some developers simply working at the wrong level. It spread like a virus through various branches taken since so I used: svn propget svn:mergeinfo -R -v svn:

non-canonical list addresses Re: Restoring a single numbered file into revs directory

2012-12-20 Thread Daniel Shahaf
I've replied (tldr: yes, but probably hardware problems involved), and my reply bounced since the list address used wasn't the canonical one. So, I'm one bounce message richer, and my reply didn't get delivered to list members. Any reason we shouldn't just ban emails that don't use the correct lis

Re: For a large post-commit failed

2012-12-20 Thread Thorsten Schöning
Guten Tag dhanushka ranasinghe, am Freitag, 21. Dezember 2012 um 05:10 schrieben Sie: > I got the following error when doing large commit , but the commit > was successful , is there any reason for that. ? Post commits run after commits and therefore can't stop those or what is the reason of your