Ubuntu
click package

A workaround to have working vivid click chroot for SDK

Bug #1408195 reported by Timo Jyrinki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
click (Ubuntu)
New
Undecided
Michael Vogt
oxide-qt (Ubuntu)
Fix Released
Undecided
Unassigned

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.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Landing silo 012 has Oxide revert building.

summary: - A workaround to have vivid click chroot for SDK
+ A workaround to have working vivid click chroot for SDK
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 07 Jan 2015 06:36:25 +0000

Changed in oxide-qt (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.