touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: click (Ubuntu)
     Importance: Undecided
     Assignee: Michael Vogt (mvo)
         Status: New

** Affects: oxide-qt (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
       Status: New

-- 
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 vivid click chroot for SDK

Status in click package in Ubuntu:
  New
Status in oxide-qt package in Ubuntu:
  New

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