On Jan 28, 2017, at 1:57 PM, Richard Hipp wrote:
> On 1/28/17, Joe Mistachkin wrote:
>>
>> Lonnie Abelbeck wrote:
>>>
>>> BTW, this also segfaults in Fossil 1.35, only discovered it by
>>> randomly clicking, testing 1.37.
>>>
>>
>> Thanks for the report. The issue should now be fixed on tr
On 1/28/17, Joe Mistachkin wrote:
>
> Lonnie Abelbeck wrote:
>>
>> BTW, this also segfaults in Fossil 1.35, only discovered it by
>> randomly clicking, testing 1.37.
>>
>
> Thanks for the report. The issue should now be fixed on trunk.
x-ed
the reason I had trouble reproducing the problem is be
On 1/28/17, Lonnie Abelbeck wrote:
> I recently upgraded fossil to 1.37 for our project (cross-compiled from
> source).
>
> In our case the "nobody" user has "a" Capabilities. This is desired since
> fossil (listening on 127.0.0.1) is accessed via an authenticated HTTPS proxy
> using lighttpd.
>
Lonnie Abelbeck wrote:
>
> BTW, this also segfaults in Fossil 1.35, only discovered it by
> randomly clicking, testing 1.37.
>
Thanks for the report. The issue should now be fixed on trunk.
--
Joe Mistachkin @ https://urn.to/r/mistachkin
___
fossil-
BTW, this also segfaults in Fossil 1.35, only discovered it by randomly
clicking, testing 1.37.
Lonnie
On Jan 28, 2017, at 11:47 AM, Lonnie Abelbeck wrote:
> I recently upgraded fossil to 1.37 for our project (cross-compiled from
> source).
>
> In our case the "nobody" user has "a" Capabilit
I recently upgraded fossil to 1.37 for our project (cross-compiled from source).
In our case the "nobody" user has "a" Capabilities. This is desired since
fossil (listening on 127.0.0.1) is accessed via an authenticated HTTPS proxy
using lighttpd.
In the web interface, click on "Login" and whi
6 matches
Mail list logo
