Comment 4 for bug 1293733

Hi Kent,

Unfortunately the 0.17.8.1 appears to have "cut" some of our components (checkbox-ng and friends) in a bad place, where some parts (plainbox maybe?) were already using id but others (checkbox-ng) hadn't been yet updated. Latest python3-checkbox-ng, checkbox-ng and plainbox-provider-certification-server all use job.id consistently in place of job.name, and thus they don't crash, plus they also have the correct provider names which fix https://bugs.launchpad.net/checkbox/+bug/1293644.

I've also noticed that canonical-certification-server is conflicting with checkbox-ng, I'll have this sorted out by the time the next stable release is out in about 10 days.

For now I suggest using 0.17.6 if possible, it should be stable and the components fit well together.

The other alternative is tracking the daily builds in the ppa:checkbox-dev/ppa repository, though those are known not to work entirely at the moment (they also don't crash, which is a plus).

I'll leave this bug open until we have a combination that actually works, hopefully in the next couple of days.