I track the the development of the Fossil version control system quite
closely on one system (oker.escape.de
). I do this for
three reasons:
git
usage on the LKML.)The fossil sources are of course maintained with fossil.
I usually do at least one update per week, and very often a few.
The systems is very stable on the trunk
development branch.
Hower, I was missing any update for the last two weeks, and that was quite unusual. Also, the last changes related to the syncing of repositories, so was a bit suspicous. Checking out out the project site, there were indeed ongoing changes which I was missing. I was just sticking on my 2020-04-13 version.
The easy fix was to check out some version beginning of April, compile that and use it to sync to the current (April 29th) version, jumping over the hump.
This was the first time ever I had a problem with the fossil bleeding edge, and I track it for several years now.