On Mon, Apr 21, 2014 at 12:38 AM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Thus said Matt Welland on Wed, 16 Apr 2014 09:01:28 -0700:
>
> > Autosync: ssh://host/path/project.fossil
> > Round-trips: 1 Artifacts sent: 0 received: 0
> > 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);}
>
> Have you tried running the latest from trunk on your fossil server?
Yes! This is fixed on latest! Any idea which commit fixes the problem?
I guess we should switch to this not-officially-released version but what
other issues am I likely to run into?
Strictly speaking I'd feel more comfortable with a version 1.28 patched
with whatever fixes the bug rather than taking on the myriad of changes
made since 1.28 was released.
What do people advise?
> You
> can test this easily without impacting existing users via SSH by
> installing the new version to a different location on the server and
> then cloning with a URL of:
>
> fossil clone ssh://host/path/project.fossil?fossil=/path/to/new/fossil
> clone.fossil
>
> I tried the latest from trunk and I don't see this particular error
> anymore. If this also goes away for you, then you simply need to update
> your servers (no client updates should be necessary).
>
> Andy
> --
> TAI64 timestamp: 400000005354cb1b
>
>
>
--
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
