pijul_org / pijul

#57 Any feedback on the last history reboot?

Opened by lthms, on April 20, 2017
Closed
lthms commented on April 20, 2017

Is every pijul repo impacted?

pmeunier commented on April 20, 2017

There's no way to tell. A patch (I couldn't tell which) was incorrectly recorded, and was causing a conflict that was impossible to resolve.

I identified a bug in the patch application code, which might have caused this. I could reproduce the bug on a minimal example, and it's now fixed.

lthms commented on April 20, 2017

Okay, thanks! If I am understanding this correctly, as long as I do not have any conflict I can’t explain, I should be okay?

FlorentBecker commented on April 20, 2017

Yes, this time pijul is able to interoperate between versions 0.4 and 0.5, but some 0.4 repositories might be "poisonned" with bad patches. It's not certain if / how this poisonning can be recovered from, and for pijul itself, we have opted for a history reboot, as it seemed to be the best use of our energy.

lthms commented on April 23, 2017

Thanks for the feedback. I think we can close this.