On Aug 5, 2015, at 12:32 PM, Kurt R. Coleman wrote:
> I am not looking for help...
>
> "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."
Ok, in that case, th
On Aug 5, 2015, at 11:08 AM, Kurt R. Coleman wrote:
>
> Hi Ryan,
>
> I was updating my source to the head revision.
>
> There were a few tree conflicts. One of which was automatically merged. I
> believe the exception came right after the merge. After clicking OK out of
> the exception dialog,
> On Aug 4, 2015, at 12:28 PM, Kurt R. Coleman
> wrote:
>
> Hi,
>
> This is the exception message:
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailin
Bert Huijben wrote on Sun, Mar 15, 2015 at 10:08:00 +:
> Yes, we probably should.
>
Looks like you just did, in r1666832. Thanks. Nominate it for backport?
% nominate.pl r1666832 "Resolves an assertion"
:-)
Daniel
>
> The problem here is an editor that drives a file or directory add in
Yes, we probably should.
The problem here is an editor that drives a file or directory add in a location
that already has a BASE (‘status normal’) node. That should never happen,
because the reporter just told the server that this node is there).
But github only uses some bits of the reporter
On 14 March 2015 at 22:57, Bert Huijben wrote:
> Hi,
>
> Thanks for noting that this is related to the github implementation.
>
> When Subversion recovers from an so called ‘incomplete’ update, it sends
> other information to the server, but the github Subversion compatibility
> co
Hi,
Thanks for noting that this is related to the github implementation.
When Subversion recovers from an so called ‘incomplete’ update, it sends other
information to the server, but the github Subversion compatibility code doesn’t
properly implement this recovery code pat
rking copy?
JM
From: Kumar Krishnamoorthy [mailto:rkrishnamoor...@seamlesscms.com]
Sent: Thursday, October 09, 2014 7:30 PM
To: John Maher
Subject: RE: Exception reporting
Oops. Sorry, I was in the middle of something when I got this error, so just
skimmed through the message and took and scree
Hello,
> On 4 Jun 2014, at 13:20, Jonathan Naumann wrote:
>
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.4\ext\subversion\subversion\libsvn_client\commit_util.c'
>
> line 211: assertion failed (repos_root_url && repos_relpath)
Try again with the latest release.
What are you
Guten Tag Geoff Hopkins,
am Donnerstag, 18. Juli 2013 um 03:02 schrieben Sie:
> svnadmin upgrade "E:\svn_respository\Projects"
This is a known issue and will be fixed in 1.8.1.
http://mail-archives.apache.org/mod_mbox/subversion-users/201306.mbox/%3C20130619093032.GB2964@lp-shahaf.local%3E
Mit
Phillip Seaver wrote on Tue, Jul 16, 2013 at 16:42:03 -0400:
> From the error dialog: "In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_ra_serf\util.c'
> line 1649: internal malfunction"
>
I believe that's fixed by http://svn.apache.org/r1503318, whi
Am 17.01.2012 16:31, schrieb Césare - Reitech TI:
Could you please help me out?
[...]
with as much information as possible about what you were trying to do.
Please consider this part.
But please first search the mailing list archives for the error message
to avoid reporting the same probl
On 2012.01.14. 5:07, Les Mikesell wrote:
2012/1/13 Balogh Péter:
I've got exactly the same exception from one of our old wc.
I'm not sure what's the reason for cleanup.
The wc was update-ed from 1.6 to 1.7
I did found some .svn directories deeper in the directory tree.
Maybe the update went wro
2012/1/13 Balogh Péter :
> I've got exactly the same exception from one of our old wc.
> I'm not sure what's the reason for cleanup.
> The wc was update-ed from 1.6 to 1.7
> I did found some .svn directories deeper in the directory tree.
> Maybe the update went wrong?
> Can I help track this bug d
y trigger different conditions (and thus bugs) in
the cleanup code.
From: "Cooke, Mark"
To: Greg Townes; "users@subversion.apache.org"
Sent: Thursday, 12 January 2012, 15:29
Subject: RE: Exception...line 673: assertion failed (checksum != NULL)
m: "Cooke, Mark"
> To: Greg Townes ; "users@subversion.apache.org"
>
> Sent: Thursday, 12 January 2012, 15:29
> Subject: RE: Exception...line 673: assertion failed (checksum != NULL)
>
> Hello,
>
>> Tried to do a cleanup on my folders and got th
this problem prior to the upgrade from 1.7.1 to 1.7.3
Regards
Greg
From: "Cooke, Mark"
To: Greg Townes ; "users@subversion.apache.org"
Sent: Thursday, 12 January 2012, 15:29
Subject: RE: Exception...line 673: assertion failed (checks
Hello,
> Tried to do a cleanup on my folders and got this message.
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.3\ext\subversion\subversion\libsvn_wc\workqueue.c'
>
> line 673: assertion failed (checksum != NULL)
Are you asking for help? In which case, what were you doing that required
Adding dev@tsvn as cc.
2011/10/14 Andreas Krey :
> On Fri, 14 Oct 2011 08:23:21 +, Cooke, Mark wrote:
> ...
>> > Subversion encountered a serious problem.
>> >
>> > Please search the mailing list archives for the error message, as
>> > a solution may already be available (this also avoids repo
I've asked Stefan Küng to change the text, cc: dev@svn bcc: users@svn,
a couple of days ago.
I like your suggested text though.
Cooke, Mark wrote on Fri, Oct 14, 2011 at 08:23:21 +0100:
> Folks,
>
> I think it might be a good idea to change this text as people are doing the
> first thing they a
On Fri, 14 Oct 2011 08:23:21 +, Cooke, Mark wrote:
...
> > Subversion encountered a serious problem.
> >
> > Please search the mailing list archives for the error message, as
> > a solution may already be available (this also avoids reporting the
> > same problem repeatedly). You can find the
Stefan --- could you make the error below clarify in bold red capital
letters the part that says "with as much information as possible about
what you were trying to do"?
There's no reason our users@ volunteers should be answering five times
a month "Read the error message" to random people who ins
Using VisualSVN 2.5 to see which files needed checking in. Visual Studio 2010.
...but below you have a backtrace that suggests the use of TortoiseSVN.
What's going on?
Subversion encountered a serious problem. Please take the time to report
> this [...] with as much information as possible
CC += dev@
Patrick Kursawe wrote on Tue, 29 Jun 2010 at 13:42 -:
> Am 6/28/2010 10:38 PM, schrieb Daniel Shahaf:
> [...]
> > Wow.
> > NICE.
> >
> > You're the first person I know of to be able to build Subversion on
> > Windows without fighting with it for days/weeks before... (and you even
>
Patrick Kursawe wrote on Tue, 29 Jun 2010 at 13:42 -:
> Am 6/28/2010 10:38 PM, schrieb Daniel Shahaf:
> [...]
> > Firstly, could you please file an issue in our tracker, so we don't
> > forget it?
> >
> >
> I did not know the correct initial assignee, so I just assigned it to you -
> #366
Am 6/28/2010 10:38 PM, schrieb Daniel Shahaf:
[...]
Wow.
NICE.
You're the first person I know of to be able to build Subversion on
Windows without fighting with it for days/weeks before... (and you even
have a working debug environment)
How did you do that?
If I had known this, I hadn't tr
Patrick Kursawe wrote on Mon, 28 Jun 2010 at 12:18 -:
> Patrick Kursawe wrote on Thu, 24 Jun 2010 at 16:03 -:
>
> > [...]
> > In file
> > 'D:\Development\SVN\Releases\TortoiseSVN-1.6.8\ext\subversion\subversion\libsvn_client\blame.c'
> > line 487: assertion failed (frb->last_filename == NU
Patrick Kursawe wrote on Thu, 24 Jun 2010 at 16:03 -:
[...]
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.6.8\ext\subversion\subversion\libsvn_client\blame.c'
line 487: assertion failed (frb->last_filename == NULL)
Am 6/25/2010 11:16 AM, schrieb Daniel Shahaf:
It would probably
It would probably help if you tell us how to reproduce the issue. That
is, tell us what command to run on some public repository to get the
assertion, or give us a script (starting with 'svnadmin create') that ends
with invoking the assertion.
I'm not sure if this was reported before.
Thanks,
29 matches
Mail list logo
