Excellent! I reported on the bug here some time ago, but didn't
provide a fix. I hope this gets into trunk soon.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-us
Even when I have the versionable 'allow-symlinks' setting on, 'fossil open'
initially creates symlinks as regular files (as if
.fossil-settings/allow-symlinks did not exist or were set to 'off').
I have to first delete the symlink files and then run 'fossil update'
in order for the setting to tak
On Thu, Oct 30, 2014 at 7:45 PM, Warren Young wrote:
>
> So, how about that “fossil rebuild” tip? Is it really needed
> prophylactically on every Fossil trunk pull-and-rebuild, or will Fossil
> diagnose the condition for me?
>
It was a good idea to run rebuild in the early days (circa 2008) but
On Oct 30, 2014, at 4:08 PM, Richard Hipp wrote:
> Thank you. That was the hint I needed. The fix is now checked in.
Confirmed. Thanks!
So, how about that “fossil rebuild” tip? Is it really needed prophylactically
on every Fossil trunk pull-and-rebuild, or will Fossil diagnose the conditio
Thank you. That was the hint I needed. The fix is now checked in.
On Thu, Oct 30, 2014 at 5:45 PM, Warren Young wrote:
> On Oct 30, 2014, at 12:58 PM, Richard Hipp wrote:
>
> > On Thu, Oct 30, 2014 at 2:53 PM, Warren Young
> wrote:
> >
> > SQLITE_MISUSE: API call with NULL database connectio
On Oct 30, 2014, at 12:58 PM, Richard Hipp wrote:
> On Thu, Oct 30, 2014 at 2:53 PM, Warren Young wrote:
>
> SQLITE_MISUSE: API call with NULL database connection pointer
>
> It seems to be working fine for me. Do you have any other hints on how I
> might reproduce the problem?
These are an
If you cannot tell me how to reproduce the problem, can you catch Fossil in
a debugger when it emits the message and send me a stack trace?
On Thu, Oct 30, 2014 at 5:21 PM, Warren Young wrote:
> On Oct 30, 2014, at 12:57 PM, James Turner wrote:
>
> > Did you remember to run fossil rebuild?
>
>
On Oct 30, 2014, at 12:57 PM, James Turner wrote:
> Did you remember to run fossil rebuild?
Fossil doesn’t diagnose DB schema mismatches itself? Subversion does.
Anyway, no, that didn’t help.
___
fossil-users mailing list
fossil-users@lists.fossil-sc
I got same error msg on first web request, and then hit reload and it
worked fine.
-bch
On 10/30/14, Richard Hipp wrote:
> On Thu, Oct 30, 2014 at 2:53 PM, Warren Young wrote:
>
>> I just updated my Fossil server from version [e061a675e6] 2014-09-26
>> 21:02:03 to the tip of trunk, as of a few
On Thu, Oct 30, 2014 at 2:53 PM, Warren Young wrote:
> I just updated my Fossil server from version [e061a675e6] 2014-09-26
> 21:02:03 to the tip of trunk, as of a few minutes ago. On restarting
> “fossil server”, I got these complaints:
>
> SQLITE_MISUSE: API call with NULL database connection
Did you remember to run fossil rebuild?
On Thu, Oct 30, 2014 at 12:53:54PM -0600, Warren Young wrote:
> I just updated my Fossil server from version [e061a675e6] 2014-09-26 21:02:03
> to the tip of trunk, as of a few minutes ago. On restarting “fossil server”,
> I got these complaints:
>
> SQL
I just updated my Fossil server from version [e061a675e6] 2014-09-26 21:02:03
to the tip of trunk, as of a few minutes ago. On restarting “fossil server”, I
got these complaints:
SQLITE_MISUSE: API call with NULL database connection pointer
SQLITE_MISUSE: misuse at line 103842 of [83afe23e55]
S
12 matches
Mail list logo
