2014-05-02 4:27 GMT+02:00 Andy Bradford amb-fos...@bradfords.org:
I did some testing and it looks like fossil already had the correct
timestamps. Perhaps whatever method you were using to get the data out
of git was providing fossil incorrect timestamps?
If 2 people (Ingo and Andy)
On Thu, Apr 17, 2014 at 10:12 AM, Rich Neswold rich.nesw...@gmail.com wrote:
On Wed, Apr 16, 2014 at 3:40 PM, Rich Neswold rich.nesw...@gmail.com wrote:
It would be nice if fossil would break the pull into smaller
transactions which contain valid timeline commits so, if there's a
database
On Fri, May 2, 2014 at 10:10 AM, Rich Neswold rich.nesw...@gmail.com wrote:
That's right, my write-ahead file is 177 GB (16x the expected size of
the final repository!)
I'm doing a fossil sqlite and it's slowly trying to apply the
transaction, but I really don't have any hope it will succeed
On 18/04/14 17:52, Matt Welland wrote:
Just FYI, I'm seeing this kind of message quite often. This is due to
overlapping clone operations on large fossils on relatively slow disk.
[---]
Artifacts sent: 0 received: 895 Error: Database error: database is locked:
{UPDATE event SET mtime=(SELECT
Thus said Jan Danielsson on Fri, 02 May 2014 17:39:20 +0200:
Artifacts sent: 0 received: 895 Error: Database error: database is locked:
{UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE
objid IN (SELECT mid FROM time_fudge);} #key_3_2
[...]
As you say, it is
5 matches
Mail list logo
