Wed Apr 29 13:13:13 CEST 2020

fossil unwedged

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:

  1. I want to see how stable or instable this system is "on its bleeding edge",
  2. I wanted to check how good older or event ancient fossil versions I have in use on other hosts interact with the latest fossil,
  3. I want to see how the inventors/developers of fossil use fossil themselves. (Just like I monitor Linus Torvarld's comment on wrong or correct 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.


Posted by neitzel | Permanent link | File under: done