Re: [fossil-users] Amended check-in time
Thus said Richard Hipp on Mon, 25 Sep 2017 16:04:32 -0400: > It does work sometimes, at least: https://fossil-scm.org/fossil/info/1f378f9e3 I've seen it work before too, so I'm not sure why it would be different with the steps Andy Goth provided. Guess it will take some investigation... Andy -- TAI64 timestamp: 400059c9d935 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 9/25/17, Andy Bradfordwrote: > Thus said Andy Goth on Mon, 25 Sep 2017 10:45:23 -0500: > >> Has anyone tried running these commands yet? I want to see if anyone >> else can replicate my problem. > > I just tried and was able to reproduce the problem. It happens on > rebuild whether one does it via the ``fossil amend'' command or using > the ``fossil ui'' to edit the checkin. It does work sometimes, at least: https://fossil-scm.org/fossil/info/1f378f9e3 I did a rebuild after entering the change above. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
Thus said Andy Goth on Mon, 25 Sep 2017 10:45:23 -0500: > Has anyone tried running these commands yet? I want to see if anyone > else can replicate my problem. I just tried and was able to reproduce the problem. It happens on rebuild whether one does it via the ``fossil amend'' command or using the ``fossil ui'' to edit the checkin. Andy -- TAI64 timestamp: 400059c95c75 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
Thus said Andy Goth on Mon, 25 Sep 2017 10:45:23 -0500: > Has anyone tried running these commands yet? I want to see if anyone > else can replicate my problem. Sorry, I misinterpreted your comment about having a bad timezone (except in Narnia) as a retraction of your original problem. And now you've issued a correction... Guess I'll have to try it now. Andy -- TAI64 timestamp: 400059c9590e ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 09/21/17 20:48, Andy Goth wrote: On 09/21/17 19:51, Richard Hipp wrote: I don't have any idea [why] the tags are not working for you. Try this sequence: f new repo.fossil mkdir ckout cd ckout f open ../repo.fossil touch xxx f add xxx f commit -date-override 2018-01-01 -m 'add xxx' sleep 5 TIME=$(date +%FT%T) sleep 5 f rm -hard xxx f commit -allow-older -m 'remove xxx' f timeline f amend -date "$TIME" prev f timeline f rebuild f timeline Has anyone tried running these commands yet? I want to see if anyone else can replicate my problem. Correction: Replace "date +%FT%T" with "date -u +%FT%T" to avoid timezone problems. -- Andy Goth | ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 09/21/17 20:48, Andy Goth wrote: The second timeline has the corrected time: === 2017-09-22 === 01:47:20 [03d8e85285] Edit [447719afb096a7d3|447719afb0]: Timestamp 2017-09-21T20:47:15. (user: andy) 01:47:20 [7196e2f3c2] *CURRENT* remove xxx (user: andy tags: trunk) 01:47:10 [602cd20f89] initial empty check-in (user: andy tags: trunk) === 2017-09-21 === 20:47:15 [447719afb0] add xxx (user: andy tags: trunk) +++ no more data (4) +++ Oops, I didn't look very closely at this. Time zone issues, ugh. Did you know that Narnia doesn't have time zones? A round earth was not a very good idea. -- Andy Goth | ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 09/21/17 19:51, Richard Hipp wrote: I don't have any idea [why] the tags are not working for you. Try this sequence: f new repo.fossil mkdir ckout cd ckout f open ../repo.fossil touch xxx f add xxx f commit -date-override 2018-01-01 -m 'add xxx' sleep 5 TIME=$(date +%FT%T) sleep 5 f rm -hard xxx f commit -allow-older -m 'remove xxx' f timeline f amend -date "$TIME" prev f timeline f rebuild f timeline The first timeline has a time warp, as expected: === 2018-01-01 === 00:00:00 [447719afb0] add xxx (user: andy tags: trunk) === 2017-09-22 === 01:47:20 [7196e2f3c2] *CURRENT* remove xxx (user: andy tags: trunk) 01:47:10 [602cd20f89] initial empty check-in (user: andy tags: trunk) +++ no more data (3) +++ The second timeline has the corrected time: === 2017-09-22 === 01:47:20 [03d8e85285] Edit [447719afb096a7d3|447719afb0]: Timestamp 2017-09-21T20:47:15. (user: andy) 01:47:20 [7196e2f3c2] *CURRENT* remove xxx (user: andy tags: trunk) 01:47:10 [602cd20f89] initial empty check-in (user: andy tags: trunk) === 2017-09-21 === 20:47:15 [447719afb0] add xxx (user: andy tags: trunk) +++ no more data (4) +++ The third timeline, after the rebuild, has the original time warp again despite also showing the correction tag: === 2018-01-01 === 00:00:00 [447719afb0] add xxx (user: andy tags: trunk) === 2017-09-22 === 01:47:20 [03d8e85285] Edit [447719afb096a7d3|447719afb0]: Timestamp 2017-09-21T20:47:15. (user: andy) 01:47:20 [7196e2f3c2] *CURRENT* remove xxx (user: andy tags: trunk) 01:47:10 [602cd20f89] initial empty check-in (user: andy tags: trunk) +++ no more data (4) +++ This is fossil version 2.4 [493e3bade9] 2017-09-21 21:49:02 UTC -- Andy Goth | ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 9/21/17, Andy Gothwrote: > On 9/21/2017 4:36 PM, Andy Goth wrote: >> I'm having trouble changing the time of a check-in using the Web >> interface or the amend command. Either way I get a good result in the >> repository I amended, but it doesn't seem to sync right. When viewing >> on other sync'ed repositories, the amended time isn't always there. > > The corrected time is lost when I rebuild the repository. > >> Many months ago I also had trouble with the reparent tag being >> unreliable in the same way > > I remember the reparent tags also not surviving a rebuild. I don't know what that is about. One of several examples is the working date tag is attached to this check-in: https://www.sqlite.org/src/info/1cc4be7ebc463921 The date tag itself is here: https://www.sqlite.org/src/info/12d1067fa974bf12 You can clearly see that the check-in time was shifted by 7 hours. That date change has survived countless rebuilds. I don't have any idea what the tags are not working for you. Can you see the tag artifacts in your artifact list? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Amended check-in time
On 9/21/2017 4:36 PM, Andy Goth wrote: > I'm having trouble changing the time of a check-in using the Web > interface or the amend command. Either way I get a good result in the > repository I amended, but it doesn't seem to sync right. When viewing > on other sync'ed repositories, the amended time isn't always there. The corrected time is lost when I rebuild the repository. > Many months ago I also had trouble with the reparent tag being > unreliable in the same way I remember the reparent tags also not surviving a rebuild. -- Andy Goth | signature.asc Description: OpenPGP digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Amended check-in time
I'm having trouble changing the time of a check-in using the Web interface or the amend command. Either way I get a good result in the repository I amended, but it doesn't seem to sync right. When viewing on other sync'ed repositories, the amended time isn't always there. With the test I just did, the corrected time showed up in the repository I edited and the one to which I directly sync'ed, but it did not show up in the repository to which the second repository sync'ed. Many months ago I also had trouble with the reparent tag being unreliable in the same way, to the point where I was forced to laboriously reconstruct my history without the use of reparent. I wonder if any of the other amendment tags have the same issue. In case you're wondering, my topology is a patchwork of always-available network connections, intermittent VPN connections, temporary network cables, and disgustingly manual sneakernet. I'm immensely grateful that Fossil is able to negotiate this environment at all; that's one of the features that makes it a necessity I continue to fight for even despite significant pushback. No alternative exists, so I'll keep using it. -- Andy Goth | signature.asc Description: OpenPGP digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users