On Thu, Oct 13, 2011 at 05:02:16PM -0700, Mike Dixon wrote:
> PS. It seems kind of unfortunate that stack traces aren't included
> in the reports. I'd guess that that would help you figure out what's
> going on better than relying on users to put in a useful text
> description about what they were
On Thu, Oct 13, 2011 at 05:55:20PM -0500, Les Mikesell wrote:
> On Thu, Oct 13, 2011 at 5:04 PM, Stefan Sperling wrote:
> > The project has decided long ago to filter problem reports on the
> > users mailing list. There are several reasons for this.
> > See the big yellow box at http://subversion.
On 10/13/2011 3:55 PM, Les Mikesell wrote:
Isn't there a better place to recommend sending the error report than
a user's mail list?
The project has decided long ago to filter problem reports on the
users mailing list. There are several reasons for this.
See the big yellow box at http://subvers
On Thu, Oct 13, 2011 at 5:04 PM, Stefan Sperling wrote:
>>
>> > We've been getting this report a lot lately.
>> > Maybe it's time to add this to the FAQ?
>> >
>> > I also think we should change the assert into a proper error message.
>> >
>>
>> Isn't there a better place to recommend sending the e
On Thu, Oct 13, 2011 at 04:50:45PM -0500, Les Mikesell wrote:
> On Thu, Oct 13, 2011 at 10:02 AM, Stefan Sperling wrote:
> >
> > We've been getting this report a lot lately.
> > Maybe it's time to add this to the FAQ?
> >
> > I also think we should change the assert into a proper error message.
>
On Thu, Oct 13, 2011 at 10:02 AM, Stefan Sperling wrote:
>
> We've been getting this report a lot lately.
> Maybe it's time to add this to the FAQ?
>
> I also think we should change the assert into a proper error message.
>
Isn't there a better place to recommend sending the error report than
a u
On Thu, Oct 13, 2011 at 10:39 AM, Philip Martin
wrote:
> Hyrum K Wright writes:
>
>> Another option might be to run a pre-upgrade check to ensure this type
>> of error doesn't exist, before we irrevocably upgrade (and potentially
>> hose) the working copy.
>
> This is happening during upgrade so
On Thu, Oct 13, 2011 at 04:29:03PM +0100, Philip Martin wrote:
> In this particular case one of the checksum values in one of the
> .svn/entries files doesn't match the checksum of the corresponding file
> in .svn/text-base. The incorrect checksum won't show up as an error in
> 1.6 until an update
Hyrum K Wright writes:
> Another option might be to run a pre-upgrade check to ensure this type
> of error doesn't exist, before we irrevocably upgrade (and potentially
> hose) the working copy.
This is happening during upgrade so the working copy remains a 1.6
working copy.
--
Philip
On Thu, Oct 13, 2011 at 10:29 AM, Philip Martin
wrote:
> Stefan Sperling writes:
>
>> On Thu, Oct 13, 2011 at 04:28:21PM +0200, Daniel Sparing wrote:
>>> Dear fellow subversion users,
>>>
>>> as requested by the error message, i would like to report an error as
>>> the following:
>>>
>>> ---8<---
Stefan Sperling writes:
> On Thu, Oct 13, 2011 at 04:28:21PM +0200, Daniel Sparing wrote:
>> Dear fellow subversion users,
>>
>> as requested by the error message, i would like to report an error as
>> the following:
>>
>> ---8<---
>> In file
>>
>> 'D:\Development\SVN\Releases\TortoiseSVN-1.7
On Thu, Oct 13, 2011 at 10:02 AM, Stefan Sperling wrote:
> On Thu, Oct 13, 2011 at 04:28:21PM +0200, Daniel Sparing wrote:
>> Dear fellow subversion users,
>>
>> as requested by the error message, i would like to report an error as
>> the following:
>>
>> ---8<---
>> In file
>> 'D:\Development\SV
On Thu, Oct 13, 2011 at 04:28:21PM +0200, Daniel Sparing wrote:
> Dear fellow subversion users,
>
> as requested by the error message, i would like to report an error as
> the following:
>
> ---8<---
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_w
Dear fellow subversion users,
as requested by the error message, i would like to report an error as
the following:
---8<---
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\entries.c'
line 1935: assertion failed (svn_checksum_match(entry_md5_checksum,
14 matches
Mail list logo