How about another angle, we drop the ancient webkit2gtk build from
webkitgtk source (since both are built from the same source package, but
are essentially independent builds) and add webkit2gtk to main (which
doesnt include webkit1 at all)? thats gotta be better than the current
situation, and
This bug was fixed in the package gnome-online-accounts -
3.18.2.1-1ubuntu1
---
gnome-online-accounts (3.18.2.1-1ubuntu1) xenial; urgency=medium
* debian/patches/0001-Revert-back-to-webkit1.patch: Revert back to webkit1;
we don't have a sufficient version of webkit2 in main. :(
gnome-online-accounts is tangled up in many packages in main, and while
it might be possible to split out the bits that require webkit2 into
another source package and build those in universe, that seems like a
horribly messy idea.
So I guess the only way forward is to revert patches in g-c-c
yes your probably right, the webkit2gtk binaries would need to be in
main for building purposes, but the binaries that built against those
could be demoted to universe. Maybe that becomes too confusing? but not
sure what else can be done, its incredibly unlikely that a full
webkit2gtk transition
It would be confusing because people will think they are supported when
they are not, which is no different than the current situation with the
existing webkit (which we must not carry forward).
Ultimately (and I've said this before-- indeed it is part of the MIR
team review process), I think
3. update to 3.16 but demote to main
Obviously I mean, 3. update to 3.16 but demote to universe
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1466290
Title:
Having the binaries that depend on webkit2gtk be in universe with
webkitgtk2 source only in main is fine (so long as later we don't allow
its binaries to be promoted-- note the MainINclusionRequests page has
this to say New binary packages from existing source packages, where
the source package is
mterry, yes that is correct.
gnome-online-accounts needs to stay in main, but the binaries that
depend on webkit2gtk do not as they are only seeded in ubuntu-gnome.
gnome-control-center also needs to stay in main, since gnome-control-
center-shared-data is used by unity-control-center, the
promote webkit2gtk (source only for the time being) to main
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1466290
Title:
Update to 3.16
Status in
What action is needed from the MIR team here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1466290
Title:
Update to 3.16
Status in gnome-online-accounts
But in comment 8, Jamie says It sounds like Tim is working on a
solution which will obviate the need for g-c-c parts that need to be in
main to depend on webkit, which is fantastic.
Which made me think we didn't need webkit2gtk in main.
--
You received this bug notification because you are a
I guess I read it now as no binary bits in main. But you still want the
source in main for building the universe binaries.
Jamie, how OK is webkit2gtk in main as source-only?
** Changed in: gnome-online-accounts (Ubuntu)
Assignee: MIR approval team (ubuntu-mir) = Jamie Strandboge
The g-c-c changes are ready and included in the branch in bug 1466245.
deja-dup has been uploaded, which just leaves compiz, that should just
be able to change the build-dep to unity-control-center-dev.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Dropping webkit dependencies is an important goal because we cannot
current provide proper maintenance for webkit. It sounds like Tim is
working on a solution which will obviate the need for g-c-c parts that
need to be in main to depend on webkit, which is fantastic.
** Changed in:
and that first means that libgnome-control-center1/-dev will go away
completely.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1466290
Title:
Update to
mterry, I have actaully been meaning to drop support for external panels
from gnome-control-center, since deja-dup is the only remaining panel
that uses it, and the patches we have in g-c-c to allow that are a pain
to maintain. I'll sift through the patches over the weekend and then the
g-c-c
Jamie, can you comment on this from a MIR/security POV? I don't think
we can simply demote the non-shared-binaries because most of them are
depended on by at least something:
libgnome-control-center-dev = deja-dup build-dep
libgnome-control-center1 = deja-dup dep
gnome-control-center-dev =
** Changed in: gnome-online-accounts (Ubuntu)
Status: Fix Released = In Progress
** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
easier option seems to be keep g-c-c source in main, but demote all
binary packges except the shared one. are the MIR team ok with this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
This is stuck in proposed due to the webkit2gtk-4.0 dependency. Bug
1469221 is tracking this transition, but there is quite some porting to
be done.
Laney suggested it might be possible to move webkit3get-4.0 into main
for building purposes only and demote the resulting binary packages
This bug was fixed in the package gnome-online-accounts - 3.16.3-1
---
gnome-online-accounts (3.16.3-1) unstable; urgency=medium
* New upstream release.
* Add Upstream-Name and Upstream-Contact to debian/copyright.
-- Michael Biebl bi...@debian.org Mon, 15 Jun 2015 20:31:35
21 matches
Mail list logo
