Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Richard Hipp
On Fri, Oct 26, 2012 at 7:13 PM, Bernd Paysan wrote: > Am Samstag, 27. Oktober 2012, 01:06:18 schrieb Bernd Paysan: > > When I do this with my local fossil version, I get the same broken > > repository. > > I downloaded the current 1.24 release, and then, I can successfully clone > it, > too. So

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Bernd Paysan
Am Samstag, 27. Oktober 2012, 01:06:18 schrieb Bernd Paysan: > When I do this with my local fossil version, I get the same broken > repository. I downloaded the current 1.24 release, and then, I can successfully clone it, too. So I think you already have fixed the bug. -- Bernd Paysan "If you

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Bernd Paysan
Am Freitag, 26. Oktober 2012, 18:36:56 schrieb Richard Hipp: > If I clone from your repo, I do indeed get a corrupt clone. But if I > download the raw repo, set up a server locally ("fossil server > vd-2012-03.fossil") then clone it locally ("fossil clone > http://localhost:8080/ vd-new.fossil") t

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Bernd Paysan
Am Freitag, 26. Oktober 2012, 18:24:07 schrieb Richard Hipp: > On Fri, Oct 26, 2012 at 6:12 PM, David Given wrote: > > On 26/10/12 23:06, Bernd Paysan wrote: > > [...] > > > > > If you have the incomplete repository, try a "fossil pull", which then > > > > will > > > > > fail with an error mess

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Richard Hipp
On Fri, Oct 26, 2012 at 5:42 PM, Bernd Paysan wrote: > We have "managed" to create a repository that can't be cloned anymore - > after > a fork and merge where some larger files have been changed (date > 2012-09-26). > The two developers who created fork and merge were able to continue to > work,

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Richard Hipp
On Fri, Oct 26, 2012 at 6:12 PM, David Given wrote: > On 26/10/12 23:06, Bernd Paysan wrote: > [...] > > If you have the incomplete repository, try a "fossil pull", which then > will > > fail with an error message. > > Yep, you're right, that dies: > > $ fossil pull -R out.fossil > Server:htt

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread David Given
On 26/10/12 23:06, Bernd Paysan wrote: [...] > If you have the incomplete repository, try a "fossil pull", which then will > fail with an error message. Yep, you're right, that dies: $ fossil pull -R out.fossil Server:http://fossil.forth-ev.de/vd-2012-03 Bytes Cards Art

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Bernd Paysan
Am Freitag, 26. Oktober 2012, 22:59:56 schrieb David Given: > On 26/10/12 22:42, Bernd Paysan wrote: > [...] > > > or try cloning it (will fail!) > > Cloning worked successfully for me, on: > > This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC > > (standard Debian version on amd6

Re: [fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread David Given
On 26/10/12 22:42, Bernd Paysan wrote: [...] > or try cloning it (will fail!) Cloning worked successfully for me, on: This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC (standard Debian version on amd64), and also on: This is fossil version 1.24 [21f8161e8e] 2012-10-23 18:20:03 UT

[fossil-users] Bug report: Out of memory when cloning a repository

2012-10-26 Thread Bernd Paysan
We have "managed" to create a repository that can't be cloned anymore - after a fork and merge where some larger files have been changed (date 2012-09-26). The two developers who created fork and merge were able to continue to work, but everybody else was excluded. Pulling or cloning (via foss

Re: [fossil-users] Wiki naming limitations

2012-10-26 Thread Carlo Miron
On Fri, Oct 26, 2012 at 4:11 PM, K wrote: > On Oct 26, 2012, Carlo Miron wrote: >> >>On Fri, Oct 26, 2012 at 1:28 AM, K wrote: >>> On Oct 24, 2012, Ron Aaron wrote: Wouldn't it be better to make this a parameter the user can adjust rather than permitting any length? >>> >>> While this i

Re: [fossil-users] Wiki naming limitations

2012-10-26 Thread K
On Oct 26, 2012, Carlo Miron wrote: > >On Fri, Oct 26, 2012 at 1:28 AM, K wrote: >> On Oct 24, 2012, Ron Aaron wrote: >>>Wouldn't it be better to make this a parameter the user can adjust >>>rather than permitting any length? >> >> While this is a more complex solution, I would support it. Per

[fossil-users] 'fossil clean' doesn't consider case-sensitivity

2012-10-26 Thread Mark Incley
Hi all, Using Fossil 1.24 on Windows, I've noticed that 'fossil clean' prompts me to delete two files that are not reported by 'fossil extras'. A cursory look at the Fossil code shows that while the 'extras' command uses the following: db_multi_exec("CREATE TEMP TABLE sfile(x TEXT PRIMARY KEY %

Re: [fossil-users] Wiki naming limitations

2012-10-26 Thread Carlo Miron
On Fri, Oct 26, 2012 at 1:28 AM, K wrote: > On Oct 24, 2012, Ron Aaron wrote: >>Wouldn't it be better to make this a parameter the user can adjust >>rather than permitting any length? > > While this is a more complex solution, I would support it. Perhaps in the > Admin area, some option to contr