Thanks Tontyna! I was going to do what you tried, today, but I really appreciate you confirming it.
It is certainly possible that the students would do a "fossil rebuild" if fossil told them to. The odds of 20 of them doing that if not told are very low. ../Dave On 12 March 2015 at 06:40, Tontyna <tont...@ultrareal.de> wrote: > Am 11.03.2015 um 18:48 schrieb David Mason: >> >> The problem was that the version of fossil that apt-get used was >> version 1.27 (I think... maybe 1.29) and I created the fossils with >> 1.30[a507dc7cf5] (and use 1.30[cf49528e5c] to look at them). This is >> the resource page I point them at: > > > Can't imagine how your students were able to work with 1.27 on a repository > created with 1.30 without doing a "fossil rebuild" > > With 1.29 I'm not even able to open the 1.30 repo. > With 1.27 I can open the cloned repo but cannot add files. > > Managed to reproduce your corrupted timeline: > > 1. Created a repo with Fossil 1.30 > 2. Switched to Fossil 1.27 > 3. clone/open worked without warning > BTW: open produced a _FOSSIL_ but the local reposirory was empty, > i.e no checked-out files at all > 4. created a new file > 5. `fossil add` warned me about the wrong schema version > 6. did what I was told: `fossil rebuild` > 7. Now `add .` worked fine > 8. `commit` warned me about "autosync not working" > I ignored that an continued. > 9. fossil ui/timeline -- see attached picture > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
