Comment 9 for bug 1421230

Removing calico-origin is easy enough, though it feels a bit unfortunate. The better thing to do, as you say, would be to re-run install during config-changed. That should be do-able (there's a fixed set of packages that the calico-origin provides, so we can hardcode them and simply force a reinstall). It'll lead to a fair bit of code churn because I'lll have to re-add every file that needs updating.

The alternative would be a complex script that scans through all installed packages to see if they came from calico-origin and then reinstall all of those: that would be complete, but much more open to bugs and errors than simply hard-coding the list.

Do you have a preference, Kevin?