← Back to team overview

touch-packages team mailing list archive

[Bug 1387537] [NEW] online-accounts should not use private Qt headers

 

Public bug reported:

There's a critical bug that is being fixed with the following MP:

https://code.launchpad.net/~abreu-alexandre/ubuntu-system-settings-
online-accounts/use-hw-compositiing-oxide-rtm-1409/+merge/239999

This bug is about removing the need for that, since using private
headers causes extra pain for Qt migrations and we should minimize their
usage.

Could Oxide provide this somehow else, so that only Oxide would use the
private headers (like it already does)?

** Affects: oxide
     Importance: Undecided
         Status: New

** Affects: ubuntu-system-settings-online-accounts
     Importance: Undecided
         Status: New

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

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- Should not use private Qt headers
+ online-accounts should not use private Qt headers

** Also affects: oxide
   Importance: Undecided
       Status: New

** Also affects: ubuntu-system-settings-online-accounts (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 ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1387537

Title:
  online-accounts should not use private Qt headers

Status in Oxide Webview:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in “oxide-qt” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New

Bug description:
  There's a critical bug that is being fixed with the following MP:

  https://code.launchpad.net/~abreu-alexandre/ubuntu-system-settings-
  online-accounts/use-hw-compositiing-oxide-rtm-1409/+merge/239999

  This bug is about removing the need for that, since using private
  headers causes extra pain for Qt migrations and we should minimize
  their usage.

  Could Oxide provide this somehow else, so that only Oxide would use
  the private headers (like it already does)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1387537/+subscriptions


Follow ups

References