Hello fossil developers,

I am switching from git to fossil and decided to use
compiled sources from trunk (003db810a282b3ba), according
to http://www2.fossil-scm.org/fossil/doc/tip/www/build.wiki
(Aside: Is it really safe to use...)

However, the logic that "honours timezones" is plain wrong
and leads to a permanent error during the first hours after
the checkout.

The timestamps in the git exports are stored in seconds
since epoch. The timezone information is purely informational.
Thus it is plain wrong, to modify the timestamp using that information.

Please remove or change the change.
What happened:

-------------------
$ git fast-export --all | fossil import --git new-repo.fossil

$ fossil open new-repo.fossil

$ fossil status
...
checkout:     a26ddc725567348b47d558d4bfb807b60b529f31 2014-05-01 15:03:53 UTC
parent:       f1e6c85bdc0ce8cbdeca7a23d8393221e9bdc096 2014-04-30 16:18:44 UTC
leaf:         open
tags:         trunk

$ date
Thu May  1 15:44:44 CEST 2014

$ date -u
Thu May  1 13:47:29 UTC 2014

$ touch foo

$ fossil add foo
ADDED  foo

$ fossil commit -m "try to commit something"
ancestor check-in [a26ddc7255] (2014-05-01 13:52:04.031) is not older (clock 
skew?) Use --allow-older to override.
-------------------

The checkout is the result of a fresh import 
as per http://www.fossil-scm.org/fossil/doc/trunk/www/inout.wiki

Any try to check in changes will lead to an error due to timestamp checking.

Please comment, I would like to open a ticket against this change in trunk.
In the meantime I will use release 1.28.

Thanks and kind regards

Ingo Struck
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to