Sadly it is not that simple. When upgrading from 1.24 to 1.29 years ago, the output of "fossil annotate" changed and broke all our scripts (and even some customer databases).
I expect even more incompatibilities when switching from 1.29 to 2.0 and therefore this is nothing that can be done in a few minutes. We have to check for all the output of all fossil commands we use in scripts whether they still produce the same output they did before. But ok, then we know why our automated tests do not work any more. Greetings, Stefan On Mon, 13 Mar, Richard Hipp wrote: > On 3/13/17, Stefan Bellon <sbel...@sbellon.de> wrote: > > > > Is this (old) version not able to work with current trunk anymore? > > Do we have to upgrade to 2.0 or 2.1? > > > > Correct. As of check-in > https://www.fossil-scm.org/fossil/info/7815d015f3b5a663 (2017-03-10) > the self-hosting Fossil repository now contains artifacts named by > SHA3 hashes, and Fossil version 2.0 or later is necessary to > understand those now hashes. > > The upgrade is simple. Just replace your current fossil executable > with a new one. Everything should work exactly as it did before. > There are no incompatibilities. The only difference is that Fossil > 2.1 will read and write the latest repositories whereas Fossil 1.x > will not. > > -- > D. Richard Hipp > d...@sqlite.org -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
