Re: [Sugar-devel] [SoaS] The plan moving forward for SoaS with Fedora 31 and Fedora 32
On Fri, Aug 30, 2019 at 07:48:26AM +0100, Peter Robinson wrote:
> On Fri, Aug 30, 2019 at 12:02 AM James Cameron wrote:
> >
> > On Thu, Aug 29, 2019 at 08:41:32AM -0700, Alex Perez wrote:
> > > Forwarding an abridged version of Peter's response to the SoaS ML for
> > > completeness, and so we can continue the conversation there.
> >
> > Thanks. Interesting.
> >
> > > Forwarded Message
> > > Subject: Re: Packages in Fedora
> > >Date: Thu, 29 Aug 2019 10:02:59 +0100
> > >From: Peter Robinson
> > > To: Alex Perez
> > > Hi Alex,
> > >
> > > > Thanks for reaching out. I am working on Telepathy-salut and
> > > > telepathy-gabble buildability tomorrow evening.
> > >
> > > Reach out on IRC or email if you need help there.
> > >
> > > With this update I think we're over the line for Beta and hence out of
> > > the woods for the moment.
> > >
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-dd8c4e8c66
> >
> > Paraphrasing, gnome-python2 did fail to build and has been fixed.
> > My comment; the dependency should disappear with 0.115.
>
> Yes, and in fact I believe, although may well be wrong here, it's
> purely a dependency of the old gtk2 sugar-toolkit and associated
> Activities and will basically disappear when we decide to drop any
> that haven't moved to gtk3.
>
> > > If you could test and provide karma on it that would be great, it's
> > > basically approved as a freeze exception so once that is ACKed we
> > > should have images. I also updated to the 0.114 release as part of
> > > that update.
> > >
> > > F-31 has branched off Rawhide now and I
> > > think we get that working as a compose, which should happen in the
> > > next day or so. It has 0.114 so we test and basically call that one
> > > done.
> > >
> > > Rawhide is open now for F-32 development for a May release next year
> > > and we aim that one for python3. We have working images as of today
> > > for that with basically the same contents as F-31.
> > >
> > > The following bug has all the other python2 bugs attached to it so I'm
> > > using it as a general tracker:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1737929
> > >
> > > The way I see it what we need to do is as follows:
> > >
> > > 1) Move as many Activities over sugar-toolkit-gtk3 as possible, kill
> > > off the rest and retire sugar-toolkit (and I think we can retire
> > > sugar-base then too). See details below around some of this below.
> > > There was a thread a number of months ago where a bunch of these were
> > > discussed. There doesn't appear to have been much movement, some just
> > > need a release tagged.
> >
> > Yes, please. We have a checklist for this;
> > https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
>
> Who from the Sugar community is going to take the lead on this?
...
> > > 2) Build a version of sugar-toolkit-gtk3 that supports both python2
> > > and python3 Basically sugar-activity3. I believe this should actually
> > > be possible with 0.114 to some degree but a new release would likely
> > > be better. This allows Activities move over independently. Once the
> > > migration is complete we disable the python2 build.
> >
> > Using 0.114 is doable if you can keep the Python 2 Telepathy static
> > binding. If you can't, then use TelepathyGLib, with 88ea8e1 ("Port to
> > TelepathyGLib").
> >
> > You'll also hit porting bugs found after 0.114, especially when you
> > begin to package activities; 381c9b1 ("Fix install TypeError").
> >
> > You may also need ed46c21 ("Port to six") and the two others following.
> >
> > I'm working toward 0.115 but there are critical bugs yet to fix, so
> > attention on these would be welcome. Please get involved.
>
> Can we have a 0.114.9x series of RCs done as we go towards that
> release tagged? That would make it easier to get it into Rawhide and
> people can then just grab nightly composes to test against which in
> turn will assist in finding critical issues.
There's no need for that. You can grab from GitHub.
I've released 0.115 for three modules. That should get you started.
> > https://github.com/orgs/sugarlabs/projects/1
> >
> > None of them are on the toolkit.
> >
> > > 3) Move the core sugar UX to python3. I believe we should be able
> > > sugar UX and datastore over independently as I believe the Activities
> > > communicate with the later via dbus.
> >
> > Yes, you can keep sugar on Python 2, if you can keep the Python 2
> > Telepathy static binding. If you can't, you'll need sugar:f8f506b
> > ("Port to TelepathyGLib").
>
> I've got python-telepathy on the list of py2 packages we currently
> depend on. Ultimately if we can move the core sugar UX, datastore and
> any Activities to py3 while keeping a sugar-toolkit-gtk3 that's py2
> compatible I would prefer moving as much as possible to py3.
0.115 does not depend on the Python 2 Telepathy static binding.
sugar-toolkit-gtk3 can be built for Python 3 and Python 2.
>
Re: [Sugar-devel] [SoaS] The plan moving forward for SoaS with Fedora 31 and Fedora 32
On Fri, Aug 30, 2019 at 12:02 AM James Cameron wrote:
>
> On Thu, Aug 29, 2019 at 08:41:32AM -0700, Alex Perez wrote:
> > Forwarding an abridged version of Peter's response to the SoaS ML for
> > completeness, and so we can continue the conversation there.
>
> Thanks. Interesting.
>
> > Forwarded Message
> > Subject: Re: Packages in Fedora
> >Date: Thu, 29 Aug 2019 10:02:59 +0100
> >From: Peter Robinson
> > To: Alex Perez
> > Hi Alex,
> >
> > > Thanks for reaching out. I am working on Telepathy-salut and
> > > telepathy-gabble buildability tomorrow evening.
> >
> > Reach out on IRC or email if you need help there.
> >
> > With this update I think we're over the line for Beta and hence out of
> > the woods for the moment.
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2019-dd8c4e8c66
>
> Paraphrasing, gnome-python2 did fail to build and has been fixed.
> My comment; the dependency should disappear with 0.115.
Yes, and in fact I believe, although may well be wrong here, it's
purely a dependency of the old gtk2 sugar-toolkit and associated
Activities and will basically disappear when we decide to drop any
that haven't moved to gtk3.
> > If you could test and provide karma on it that would be great, it's
> > basically approved as a freeze exception so once that is ACKed we
> > should have images. I also updated to the 0.114 release as part of
> > that update.
> >
> > F-31 has branched off Rawhide now and I
> > think we get that working as a compose, which should happen in the
> > next day or so. It has 0.114 so we test and basically call that one
> > done.
> >
> > Rawhide is open now for F-32 development for a May release next year
> > and we aim that one for python3. We have working images as of today
> > for that with basically the same contents as F-31.
> >
> > The following bug has all the other python2 bugs attached to it so I'm
> > using it as a general tracker:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1737929
> >
> > The way I see it what we need to do is as follows:
> >
> > 1) Move as many Activities over sugar-toolkit-gtk3 as possible, kill
> > off the rest and retire sugar-toolkit (and I think we can retire
> > sugar-base then too). See details below around some of this below.
> > There was a thread a number of months ago where a bunch of these were
> > discussed. There doesn't appear to have been much movement, some just
> > need a release tagged.
>
> Yes, please. We have a checklist for this;
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---maintainer
Who from the Sugar community is going to take the lead on this?
> > 2) Build a version of sugar-toolkit-gtk3 that supports both python2
> > and python3 Basically sugar-activity3. I believe this should actually
> > be possible with 0.114 to some degree but a new release would likely
> > be better. This allows Activities move over independently. Once the
> > migration is complete we disable the python2 build.
>
> Using 0.114 is doable if you can keep the Python 2 Telepathy static
> binding. If you can't, then use TelepathyGLib, with 88ea8e1 ("Port to
> TelepathyGLib").
>
> You'll also hit porting bugs found after 0.114, especially when you
> begin to package activities; 381c9b1 ("Fix install TypeError").
>
> You may also need ed46c21 ("Port to six") and the two others following.
>
> I'm working toward 0.115 but there are critical bugs yet to fix, so
> attention on these would be welcome. Please get involved.
Can we have a 0.114.9x series of RCs done as we go towards that
release tagged? That would make it easier to get it into Rawhide and
people can then just grab nightly composes to test against which in
turn will assist in finding critical issues.
> https://github.com/orgs/sugarlabs/projects/1
>
> None of them are on the toolkit.
>
> > 3) Move the core sugar UX to python3. I believe we should be able
> > sugar UX and datastore over independently as I believe the Activities
> > communicate with the later via dbus.
>
> Yes, you can keep sugar on Python 2, if you can keep the Python 2
> Telepathy static binding. If you can't, you'll need sugar:f8f506b
> ("Port to TelepathyGLib").
I've got python-telepathy on the list of py2 packages we currently
depend on. Ultimately if we can move the core sugar UX, datastore and
any Activities to py3 while keeping a sugar-toolkit-gtk3 that's py2
compatible I would prefer moving as much as possible to py3.
> Yes, you can keep datastore on Python 2, if you can keep Xapian, which
> you said in April was failing to build. While the port to Python 3 is
> done, it introduced a new bug losing datatypes of metadata, breaking
> previews.
We actually got that fixed up with a terrible hack. Does datastore run
on it's own and can be moved to py3?
> https://github.com/sugarlabs/sugar-datastore/issues/16
>
> > What have I missed, what are your thoughts?
> >
> > > From what I can see at
> > >
