package testing made easy by conary rollback

Some time ago I came into a bug of foresight, FL-2639 - fails to boot due to libata-migrate. Then our lead developer António committed an updated recipe. But before new packages are made, I was asked to build the recipe and test it locally.

So I checked out the recipe, and 'cooked' it on my system.

cvc cook mkinitrd.recipe

The package was built and I installed it.

sudo conary update mkinitrd-6.0.93.ccs

But something seemed wrong, as you might guess from the libata-migrate warnings in the above screenshot.

So I asked António and confirmed the problem.

I didn't panic. As António said, I ran a single command and brought my system back to safety :)

sudo conary rollback 1

That's a typical scenario during foresight development, and part of what makes it a fun to work with conary.