CI device tests

Christopher James Halse Rogers chris at
Fri Jul 18 04:46:13 UTC 2014

So, I think the cause of much of the heartache in the packaging in
is because the CI test is using our tools in a way that doesn't match 
standard practice.

The Breaks/Replaces pair *should* work, using apt to install those 
packages will correctly remove mircommon-dev and replace it with 
libmircommon-dev. This is not implemented in the dpkg layer, though, so 
when the device test calls dpkg --install $ALL_THE_THINGS this handling 
is not done.

It would probably be fixed by the test passing --auto-deconfigure to 
dpkg, or (better) creating a repository apt can pull from and using apt.

More information about the Mir-devel mailing list