Correction, aside from the case where Fossil doesn’t build at all because I’m
trying to link it against a from source statically built copy of libtcl, all
other scenarios I’ve outlined use Tcl obtained from running:
sudo apt-get install libtcl8.6
> On Mar 16, 2017, at 7:55 PM, Ryan Dingman wr
> On Mar 16, 2017, at 7:03 PM, Joe Mistachkin wrote:
>
>
> How was the Tcl library built?
In the case where Fossil builds successfully as a statically linked binary and
then crashes, the Tcl library used is one that gets installed via:
sudo apt-get install libtcl8.6
So, I don’t know precise
How was the Tcl library built? Are you able to step through Fossil in gdb to
see why tclInvoke is not getting added to the TH1 interpreter?
Sent from my iPhone
https://urn.to/r/mistachkin
___
fossil-users mailing list
fossil-users@lists.fossil-scm.o
> On Mar 16, 2017, at 6:34 PM, Joe Mistachkin wrote:
>
>
> That's really odd. I've run Tcl-enabled Fossil on multiple flavors of Linux,
> both statically and dynamically linked to Tcl and never seen this crash or
> failure.
>
> It should be noted that simply using "fossil version --verbose"
That's really odd. I've run Tcl-enabled Fossil on multiple flavors of Linux,
both statically and dynamically linked to Tcl and never seen this crash or
failure.
It should be noted that simply using "fossil version --verbose" actually loads
and uses Tcl from TH1 (and that appears to work on yo
I’m having trouble with Fossil and Tcl integration. At a high level, I have two
main problems:
Problem 1. When I configure Fossil to build as a dynamically linked binary, the
build succeeds and loads the Tcl library. However, when I run a TH1 script that
uses a command requiring Tcl integration
On Mar 16, 2017, at 3:04 PM, Dan Raymond wrote:
>
> Whats not clear in the docs is which password.
That’s because it depends. :)
If you use an ssh:// URL, you give the OS user password because the local
Fossil logs into the remote system and schleps the data back through the SSH
connection.
Thank you. Whats not clear in the docs is which password. I had interpreted
as the site user not the fossil user password. Also nowhere is it mentioned
you need a running instance of fossil on the server.
All sorted now though and working.
Thanks to all for help
On 16 Mar 2017 22:32, "Warren Youn
On Thu, Mar 16, 2017 at 2:01 PM,
wrote:
>
> Date: Thu, 16 Mar 2017 14:31:00 +0100
> From: Richard Bukovansky
> Subject: Re: [fossil-users] Conflicting edits of ticket
>
> Some kind of “comparer” where I would be able to decide which values are
> correct.
>
When you are viewing a ticket, there is
On Thu, 16 Mar 2017 17:14:33 +
Pietro Cerutti wrote:
> On 2017-Mar-16, 17:54, Manfred Lotz wrote:
> > Hi there,
> > Newest fossil binary just downloaded. This is a Fedora 25 system.
> >
> > $ fossil version:(
> > This is fossil version 2.1 [83e
On 2017-Mar-16, 17:54, Manfred Lotz wrote:
> Hi there,
> Newest fossil binary just downloaded. This is a Fedora 25 system.
>
> $ fossil version:(
> This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UTC
>
> $ fossil set 'mv-rm-files' 1
Hi there,
Newest fossil binary just downloaded. This is a Fedora 25 system.
$ fossil version:(
This is fossil version 2.1 [83e3445f67] 2017-03-10 17:07:08 UTC
$ fossil set 'mv-rm-files' 1
no such setting: mv-rm-files
I thought it should wor
Some kind of “comparer” where I would be able to decide which values are
correct.
Example situation:
_Step1: Initial state_
*Common Repository*
Ticket: #1
Status: Open
*Dev Repository*
Ticket: #1
Status: Open
*My Repository*
Ticket: #1
Status: Open
_Step2: Dev resolves ticket and pushes to Co
On 3/16/17, Richard Bukovansky wrote:
>> If two edits change the same field, the last edit wins.
>
> I see. Not exactly what I was expecting, but OK.
What were you expecting? Is there a better way?
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users
On Mar 16, 2017, at 6:32 AM, Warren Young wrote:
>
> On Mar 15, 2017, at 1:55 AM, Dan Raymond wrote:
>>
>> whenever I try to autosync back the other way I get a "not authorized to
>> write" error?
>
> That’s because you didn’t give your remote Fossil user name in the clone URL.
> Hence, you
On Mar 15, 2017, at 1:55 AM, Dan Raymond wrote:
>
> whenever I try to autosync back the other way I get a "not authorized to
> write" error?
That’s because you didn’t give your remote Fossil user name in the clone URL.
Hence, you’re anonymous, hence you can’t write. Say:
fossil clone ht
> If two edits change the same field, the last edit wins.
I see. Not exactly what I was expecting, but OK.
Thank you very much.
--
Richard Bukovansky
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi
On 3/16/17, Richard Bukovansky wrote:
> HI,
> I’m new to Fossil, but I would like to ask you, how Fossil handles
> conflicting edits to tickets?
> In my company we are currently looking for distributed scm&ticketing system,
> but about this we are not sure.
Every edit has a timestamp. The edits
HI,
I’m new to Fossil, but I would like to ask you, how Fossil handles conflicting
edits to tickets?
In my company we are currently looking for distributed scm&ticketing system,
but about this we are not sure.
Thank you.
Regards,
Richard Bukovansky
19 matches
Mail list logo
