Subject: CI device tests

From: Christopher James Halse Rogers <[email-masked]>
Date: Fri, 18 Jul 2014 14:46:13 +1000

So, I think the cause of much of the heartache in the packaging in
https://code.launchpad.net/~mir-team/mir/libmircommon/+merge/226704
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.

---

From: Alan Griffiths <[email-masked]>
Date: Fri, 18 Jul 2014 09:06:40 +0100

On 18/07/14 05:46, Christopher James Halse Rogers wrote:
> 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.
>

Anyone know which project to report the bug against?

---

From: Michał Sawicz <[email-masked]>
Date: Fri, 18 Jul 2014 11:03:19 +0200

> Anyone know which project to report the bug against?

https://bugs.launchpad.net/ubuntu-ci-services-itself/

Should be a good place.

-- 
Sq