On Thu, Jun 18, 2015 at 01:45:24PM -0400, Ron W wrote:
On Wed, Jun 17, 2015 at 3:17 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
On Wed, Jun 17, 2015 at 12:10:36PM -0400, Richard Hipp wrote:
On 6/17/15, Jan Danielsson jan.m.daniels...@gmail.com wrote:
Out of curiosity;
On Wed, Jun 17, 2015 at 3:17 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
On Wed, Jun 17, 2015 at 12:10:36PM -0400, Richard Hipp wrote:
On 6/17/15, Jan Danielsson jan.m.daniels...@gmail.com wrote:
Out of curiosity; why aren't pulls 100% read-only on the server?
The
On Thu, Jun 18, 2015 at 1:51 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
I'm aware of the sync protocol. My point is that all clusters should
already exist on the public master repository as part of other sync
operations and I would strongly argue that this is the case that should
On Wed, Jun 17, 2015 at 12:10:36PM -0400, Richard Hipp wrote:
On 6/17/15, Jan Danielsson jan.m.daniels...@gmail.com wrote:
On 17/06/15 11:38, Joerg Sonnenberger wrote:
[---]
Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding
such problems.
Out of curiosity; why
On Tue, Jun 16, 2015 at 11:04:07PM -0700, Matt Welland wrote:
We see these (or similar) occasionally when the filesystem gets slow. The
problem is exacerbated with large repos.
It's possible to hit one of the hidden master - public repo pushes,
they can take a bit as the disks are generally
On 17/06/15 11:38, Joerg Sonnenberger wrote:
[---]
Sadly, a plain pull is not 100% read-only, so WAL doesn't help avoiding
such problems.
Out of curiosity; why aren't pulls 100% read-only on the server?
--
Kind Regards,
Jan
___
fossil-users
I've occasionally (rarely) seen errors like the following -- anybody
have an idea what might be going on ? Anything I can do to help
troubleshoot ?
===
(syncing NetBSD pkgsrc (http://pkgsrc.sonnenberger.org)):
[...]
SHA1 (test-unit-3.1.2.gem) = be7ec72f81bbfeebeaf757de3295cd2f282d4ee6
(sorry about my other message ending up in another thread, was not meant
that way)
While playing for the first time with Fossil (open, close, delete etc.) I
ended up with the message:
C:\Windows\fossil.exe: no such file: d:/test/source/monkey.txt
C:\Windows\fossil.exe: SQLITE_BUSY: statement
On Fri, Aug 12, 2011 at 10:36:13AM +0200, Jos Groot Lipman wrote:
fossil open ../monkey.fossil
fossil add monkey.txt
del monkey.txt
echo Y|fossil commit -m Versie 2010 --tag v2010 --branch v2010
What do you intend to do with this?
Maybe you should run fossil rm monkey.txt after the del?
the transaction was indeed rolled back.
-Original Message-
From: fossil-users-boun...@lists.fossil-scm.org
[mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Lluís Batlle
i Rossell
Sent: vrijdag 12 augustus 2011 11:02
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users
augustus 2011 11:02
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] SQLITE_BUSY: statement aborts at 2: [ROLLBACK]
On Fri, Aug 12, 2011 at 10:36:13AM +0200, Jos Groot Lipman wrote:
fossil open ../monkey.fossil
fossil add monkey.txt
del monkey.txt
echo Y|fossil commit -m
11 matches
Mail list logo