This bug was fixed in the package oxide-qt - 1.3.5-0ubuntu8 --------------- oxide-qt (1.3.5-0ubuntu8) vivid; urgency=medium
* Revert back to 1.3.5-0ubuntu1 in anticipation of a workaround in click instead (LP: #1408195) -- Timo Jyrinki <timo-jyri...@ubuntu.com> Wed, 07 Jan 2015 06:36:25 +0000 ** Changed in: oxide-qt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1408195 Title: A workaround to have working vivid click chroot for SDK Status in click package in Ubuntu: New Status in oxide-qt package in Ubuntu: Fix Released Bug description: We'd need a workaround in click to overcome the endless hurdles of bug #1399597 and revert Oxide (https://launchpad.net/ubuntu/+source/oxide- qt/+changelog) back to the 1.3.5-0ubuntu1 situation without SDK related changes. Currently we've gone from breaking SDK to breaking autopkgtests (ubuntu4), desktop (ubuntu6) or image builds (ubuntu7), all dancing around the same "first install one package, then replace with it another, but apt wants to configure the first one still and fails" issue. The issue started with arch specific conflicts added that made SDK work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1408195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp