A fresh checkout of pijul doesn’t build, because it’s full of conflicts.
I installed a fresh version of pijul with cargo install pijul and then I closed the repository with pijul clone https://nest.pijul.com/pijul_org/pijul. The result was a bunch of conflicts. For example, the first few lines of libpijul/Cargo.toml are:
[package]
name = "libpijul"
description = "A patch-based distributed version control system, easy to use and fast."
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
version = "0.9.0-beta1"
================================
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
version = "0.9.1"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Yes, Pijul 0.9 simplified the algorithm a lot, and our converter had to use libpijul in unusual ways, making many bugs visible. While this is great news in the long run, it’s temporarily a disaster, especially as it happened at the same time as “devops” mistakes I made while managing the Nest.
I believe I’ve fixed those conflicts in a local version, I’ll update pijul on crates.io today.
Wow, it’s been two weeks already! I’ve been pretty busy with other things (such as setting up an AFM microscope for my starting experimental project), but I still found some time to improve the test coverage (as measured by kcov) to almost 80%, which helped fix a large number of bugs which I think were responsible for this situation.
I know I’ve promised a new version several times for “today” and “really soon”, so I prefer not to commit to any date, but libpijul is now quite well covered by tests, so I think we’re starting to see the end of the tunnel.