Hi,
Apologies for poluting the list, but,
Scheduling sync on osx can be done much the same way.
http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
Label
myclone-sync.fossil.agent
ProgramArguments
/usr/bin/fossil
sync
-R
/Users/spdegabrielle/fossil-loca
I should add I have not tested tested this much, so I may still have
something wrong.
Feedback appreciated.
S.
On Tue, Jan 25, 2011 at 7:15 PM, Stephen De Gabrielle <
stephen.degabrie...@acm.org> wrote:
> Hi,
>
> I've only just work this out, whith some kind help from lynxman at
> serverfaul
Hi,
I've only just work this out, whith some kind help from lynxman at
serverfault.com.
To run fossil on osx (10.5 or later) as an 'run on demand' Daemon or Agent
as an 'on demand' service, where fossil is only launched to respond to
requests, you have a couple of options.
$ launchctl load ~/Li
Hello,
I updated the fossil version I had in one computer from 2010-11-17 to
2011-01-13. I run the fossil rebuild (Btw, it said 100.1% completed at the end),
and synched to the main repository.
I noticed that the timeline was showing all the changes until today at ~15:00 in
trunk, but was not sho
Dmitry,
Here is how I have my fossil repository setup. The following
configuration is in /etc/xinetd.d/fossil-myproject
service fossil-myproject
{
flags= REUSE
socket_type= stream
wait= no
user= fossil
server
2011/1/25 Lluís Batlle i Rossell
> Hello,
>
> On a "fossil update trunk", I got this output:
> $ fossil update trunk
> Autosync: http://blabla@blabla/blabla
> Bytes Cards Artifacts Deltas
> Sent: 130 1 0 0
> Received:4494 97
On Tue, Jan 25, 2011 at 10:20:06AM -0500, Bill Whiting wrote:
> Dmitry,
> I checked the permissions. I am not running this from apache, fossil is
> launched from xinetd, so the fossil process is owned by the same user
> that owns the fossil repository file.
I don't think this is generally true.
Richard,
That's it (sort of). The /var file system is full. I thought I had
verified that all of the file systems had some free space, but
overlooked /var. I extended the file system and the push succeeded.
Thanks!
//Bill
On 01/25/2011 10:19 AM, Richard Hipp wrote:
>
>
> On Tue, Jan 25, 201
Hello,
On a "fossil update trunk", I got this output:
$ fossil update trunk
Autosync: http://blabla@blabla/blabla
Bytes Cards Artifacts Deltas
Sent: 130 1 0 0
Received:4494 97 0 0
Sent:1540 31
On Tue, Jan 25, 2011 at 10:09 AM, Dmitry Chestnykh
wrote:
> > Error: Database error: unable to open database file
> > CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
>
> Check permissions and ownership of fossil repository file. Are your web
> process allowed to write to this file?
>
Dmitry,
I checked the permissions. I am not running this from apache, fossil is
launched from xinetd, so the fossil process is owned by the same user
that owns the fossil repository file.
Thanks,
//Bill
On 01/25/2011 10:09 AM, Dmitry Chestnykh wrote:
>> Error: Database error: unable to op
> Error: Database error: unable to open database file
> CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
Check permissions and ownership of fossil repository file. Are your web process
allowed to write to this file?
--
Dmitry Chestnykh
___
I'm trying to push changes to a central fossil repository and I get the
following error:
Error: Database error: unable to open database file
CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
The fossil server is running with xinetd. The user that runs the fossil
process owns the r
Hello,
I think fossil handles bad the conflicts on binary files. Basically, it
overwrites the file in case of conflict, expecting the user to do "undo" for
planing a later conflict resolution. I think this can end up in lost changes in
the working directory too easily.
What about the approach of
14 matches
Mail list logo
