Some amendments don't consistently survive rebuilds and syncs. I've
noticed this with date changes and reparenting. Possibly it affects
other types of amendments as well, but those are the two I've spotted.
This has been plaguing me for years, but finally I have a repeatable
test case.
Repository before rebuild:
https://drive.google.com/open?id=1-Ahs91NVigBX7uMk88wIBjClQj1yxGnm
Repository after rebuild:
https://drive.google.com/open?id=1CFzc9JyNQ5piSIO4YUqjSpqmmjPxmCsg
I constructed a repository full of time warps, much like in my previous
email about the stray riser. Then I used a bunch of amendments to
straighten everything out. But once I rebuilt, the dates got jumbled
again, and not in the same configuration as when I started. Some
amendments survived, others didn't.
Here are the commands I used to create the repository:
f new test.fossil -admin-user username -date-override 2018-05-31
mkdir test
cd test
f open ../test.fossil
f user default username
id=1; for day in 15 13 16 12 17 11 18 10 19 09 20 08 21 07 22 06 23 05
24 04 25 03 26 02 27 01; do f commit -f -m "$id" -tag "$id"
-date-override "2018-06-$day"; ((++id)); done
for id in $(seq 1 26); do f amend -date "$(printf 2018-06-%02d "$id")"
"$id"; done
And then, to mess it up again:
f rebuild
I could also have sync'ed to another repository, but here I'm just
showing the simplest way I know to trigger the problem. I wonder if the
order in which artifacts are visited is impacting the outcome.
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
