* I'm not sure we can, or want to, expose this over dbus.
* Assuming that's true, the best way to support this seems to be to add a --force-channel option on system-image-cli which would override the channel coming from /etc/system-image/channel.ini. Then we do normal update resolution, forcing a full update as per LP: #1208909 (i.e. --force-channel would imply --force-full, caveat other comments in that latter bug).
* The channel switch would be permanent as long as the channel.ini file laid down by the newly installed image names the new channel, which it should.
As far as developer-mode reset, that will probably be handled by LP: #1192577. LP: #1207860 might also be related.
I'll take a look at the interactions of all these bugs and come up with a plan.
A few additional thoughts:
* I'm not sure we can, or want to, expose this over dbus.
* Assuming that's true, the best way to support this seems to be to add a --force-channel option on system-image-cli which would override the channel coming from /etc/system- image/channel. ini. Then we do normal update resolution, forcing a full update as per LP: #1208909 (i.e. --force-channel would imply --force-full, caveat other comments in that latter bug).
* The channel switch would be permanent as long as the channel.ini file laid down by the newly installed image names the new channel, which it should.
As far as developer-mode reset, that will probably be handled by LP: #1192577. LP: #1207860 might also be related.
I'll take a look at the interactions of all these bugs and come up with a plan.