Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Samson Goddy]

Hello James,

I think you replied to the thread already.


On Wed, May 15, 2019, 9:59 PM James Cameron  wrote:

> Hey Samson, yes, missed it, where was it?
>
> On Wed, May 15, 2019 at 09:39:30AM -0700, Samson Goddy wrote:
> > Hello Alex and James,
> >
> > I guess you both miss this thread. Can you please guide Jeff on how to
> get
> > started?
> >
> > On Fri, May 10, 2019, 8:14 AM Jeff Elkner <[1]jeff.elk...@gmail.com>
> wrote:
> >
> > Dear Sugar Labs Devs,
> >
> > I am a high school / community college computer science teacher in
> > Arlington Virginia who was an active member of the OLPC project for
> > years and who would like to rejoin the community.
> >
> > I am convinced being able to run the Sugar desktop on the same
> > underlying OS (Debian) as Raspbian uses is the key to that working
> for
> > me.
> >
> > I tried creating a basic buster install and then running:
> >
> > $ sudo apt install sugar sucrose lightdm
> >
> > The result is not a usable Sugar installation.  I am most eager to
> > participate as a tester, power user, and curriculum developer, but I
> > need to start with a working system.
> >
> > Thanks!
> >
> > Jeff Elkner
> >
> > Let's work together to create a just and sustainable world!
> >
> > References:
> >
> > [1] mailto:jeff.elk...@gmail.com
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[James Cameron]

Hey Samson, yes, missed it, where was it?

On Wed, May 15, 2019 at 09:39:30AM -0700, Samson Goddy wrote:
> Hello Alex and James,
> 
> I guess you both miss this thread. Can you please guide Jeff on how to get
> started?
> 
> On Fri, May 10, 2019, 8:14 AM Jeff Elkner <[1]jeff.elk...@gmail.com> wrote:
> 
> Dear Sugar Labs Devs,
> 
> I am a high school / community college computer science teacher in
> Arlington Virginia who was an active member of the OLPC project for
> years and who would like to rejoin the community.
> 
> I am convinced being able to run the Sugar desktop on the same
> underlying OS (Debian) as Raspbian uses is the key to that working for
> me.
> 
> I tried creating a basic buster install and then running:
> 
> $ sudo apt install sugar sucrose lightdm
> 
> The result is not a usable Sugar installation.  I am most eager to
> participate as a tester, power user, and curriculum developer, but I
> need to start with a working system.
> 
> Thanks!
> 
> Jeff Elkner
> 
> Let's work together to create a just and sustainable world!
> 
> References:
> 
> [1] mailto:jeff.elk...@gmail.com

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[James Cameron]

python-sugar3_0.112-3 has migrated to testing just now.

On Wed, May 15, 2019 at 10:56:03AM -0700, Alex Perez wrote:
> Jeff,
> 
> Most, if not all, of the Sugar-specific bugs that are present in Debian
> should be fixed if you use the "0.112-3" (the 3 is critically important)
> Debian packages from the _unstable_ Debian repo. They have not yet been
> promoted to testing, and will likely not be included in Debian 10 when it is
> released, as it is late in the package freeze process.
> 
> So, you have a few options here...the easiest thing to do would be to run an
> entire "unstable" install of Debian, since you will get these packages by
> default, but otherwise, you have to configure Apt with the unstable repo,
> and then use package pinning. This is documented at 
> https://serverfault.com/questions/371383/install-whitelist-of-packages-using-unstable-in-debian.
> 
> See https://packages.debian.org/buster/sucrose for a list of these packages,
> and https://wiki.debian.org/DebianUnstable#Installation can explain how to
> enable the unstable apt repo on a stable or testing install.
> 
> This may also be of use 
> https://serverfault.com/questions/22414/how-can-i-run-debian-stable-but-install-some-packages-from-testing
> 
> 
> Jeff Elkner wrote on 5/15/19 9:54 AM:
> > Great to meet you (virtually), Alex and James.  I'm a high school /
> > community college teacher in Arlington, Virginia who was an early
> > member of the OLPC community here in the DC area.  I run Debian in my
> > classroom and would very much be interested in using the Sugar desktop
> > to work on that platform.  It doesn't currently seem to work.  I don't
> > have the capacity to fix it myself, but I can provide reliable testing
> > and feedback in an educational setting should that be of use to you.
> > I'm hoping to rejoin the Sugar community once it is in a state where
> > it can be used both in my classroom and on Raspberry Pi's.
> > 
> > Thanks!
> > Jeff Elkner
> > Arlington Career Center
> > Arlington, VA
> > 
> > On Wed, May 15, 2019 at 12:39 PM Samson Goddy  wrote:
> > > Hello Alex and James,
> > > 
> > > I guess you both miss this thread. Can you please guide Jeff on how to 
> > > get started?
> > > 
> > > 
> > > 
> > > On Fri, May 10, 2019, 8:14 AM Jeff Elkner  wrote:
> > > > Dear Sugar Labs Devs,
> > > > 
> > > > I am a high school / community college computer science teacher in
> > > > Arlington Virginia who was an active member of the OLPC project for
> > > > years and who would like to rejoin the community.
> > > > 
> > > > I am convinced being able to run the Sugar desktop on the same
> > > > underlying OS (Debian) as Raspbian uses is the key to that working for
> > > > me.
> > > > 
> > > > I tried creating a basic buster install and then running:
> > > > 
> > > > $ sudo apt install sugar sucrose lightdm
> > > > 
> > > > The result is not a usable Sugar installation.  I am most eager to
> > > > participate as a tester, power user, and curriculum developer, but I
> > > > need to start with a working system.
> > > > 
> > > > Thanks!
> > > > 
> > > > Jeff Elkner
> > > > 
> > > > 
> > > > Let's work together to create a just and sustainable world!
> 

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[James Cameron]

Thanks for testing, Aniket.

Because 0.113 introduces a dependency on Six for the first time, the
method of resolving dependencies in the instructions is out of date.

I've added
https://github.com/sugarlabs/sugar/pull/829/commits/97d1ef60b65a0fffe52ec4070944e2b03fe56ac2
to the pull request.

Yes, you are correct that dependencies are not added during build,
this is something you may have to do yourself.

For instance, after you've built Sugar, there are a set of run-time
dependencies to install.  I'm working on refining the instructions
some more.  Let me know how you go.

On Thu, May 16, 2019 at 09:23:08AM +0530, ANIKET MATHUR wrote:
> hey,
> I tested the changes that James made.
> I started with a fresh Ubuntu 18.04 VM. Cloned artwork, datastore,
> toolkit-gtk3, and sugar.
> Applied his patch to toolkit-gtk3 and then followed the native procedure in 
> the
> documentation considering his changes.
> I installed the toolkit for both python2 and python3.
> But when I run sugar from the command line I got an import error 
> "import six
> "ImportError:No module named six"
> I am not sure why I got this error, do the dependencies and libraries used by
> python3 do not get installed when the toolkit for python 3 is built?
> Please help.
> Thanks!
> 
> On Wed, May 15, 2019 at 1:49 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Thanks!
> 
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
> 
> [2]https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> [3]https://github.com/sugarlabs/sugar/pull/829
> 
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
> 
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
> 
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2, 
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able 
> to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2][4]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3][5]qu...@laptop.org>
> wrote:
> >
> >     G'day Aniket,
> >
> >     If you were using the native sugar build method, then you are using
> >     HEAD, which contains all patches since 0.113.  Don't try to apply 
> the
> >     patch that Alex pointed out, as it is already applied.
> >
> >     The error message "ImportError: No module named sugar3" is caused by
> >     not installing the Toolkit for Python 2.
> >
> >     Sugar 0.113 requires Python 2.
> >
> >     Toolkit by default installs for Python 3.
> >
> >     You can verify this is the situation by testing the import by hand
> >     using different versions of Python;
> >
> >     python3 -c 'import sugar3'  # expect pass
> >
> >     python2 -c 'import sugar3'  # expect fail
> >
> >     You'll find in [4][6]configure.ac where the Python version is 
> chosen.
> >
> >     [5][7]https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/
> configure.ac
> >     #L18
> >
> >     Perhaps that line should allow the caller to specify the version.
> >
> >     What do you think?
> >
> >     On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> >     > Greetings everyone,
> >     >
> >     > I was installing Sugar v0.113 using the Native Sugar build method 
> [1]
> >     here. I
> >     > was using Ubuntu 18.10. After installation, on running Sugar I
> received
> >     the
> >     > error message "ImportError: No module named sugar3". Need help 
> with
> a
> >     couple of
> >     > questions 
> >     > 1) Is there a need to have a build of 

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

hey,
I tested the changes that James made.
I started with a fresh Ubuntu 18.04 VM. Cloned artwork, datastore,
toolkit-gtk3, and sugar.
Applied his patch to toolkit-gtk3 and then followed the native procedure in
the documentation considering his changes.
I installed the toolkit for both python2 and python3.
But when I run sugar from the command line I got an import error
"import six
"ImportError:No module named six"
I am not sure why I got this error, do the dependencies and libraries used
by python3 do not get installed when the toolkit for python 3 is built?
Please help.
Thanks!

On Wed, May 15, 2019 at 1:49 PM James Cameron  wrote:

> Thanks!
>
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> https://github.com/sugarlabs/sugar/pull/829
>
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
>
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
>
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2,
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org>
> wrote:
> >
> > G'day Aniket,
> >
> > If you were using the native sugar build method, then you are using
> > HEAD, which contains all patches since 0.113.  Don't try to apply the
> > patch that Alex pointed out, as it is already applied.
> >
> > The error message "ImportError: No module named sugar3" is caused by
> > not installing the Toolkit for Python 2.
> >
> > Sugar 0.113 requires Python 2.
> >
> > Toolkit by default installs for Python 3.
> >
> > You can verify this is the situation by testing the import by hand
> > using different versions of Python;
> >
> > python3 -c 'import sugar3'  # expect pass
> >
> > python2 -c 'import sugar3'  # expect fail
> >
> > You'll find in [4]configure.ac where the Python version is chosen.
> >
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> > #L18
> >
> > Perhaps that line should allow the caller to specify the version.
> >
> > What do you think?
> >
> > On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > > Greetings everyone,
> > >
> > > I was installing Sugar v0.113 using the Native Sugar build
> method [1]
> > here. I
> > > was using Ubuntu 18.10. After installation, on running Sugar I
> received
> > the
> > > error message "ImportError: No module named sugar3". Need help
> with a
> > couple of
> > > questions
> > > 1) Is there a need to have a build of the older version for v0.113
> to
> > work
> > > properly?
> > > (never paid attention to that before).
> > >  2) What is the correct procedure for installing v0.113?
> > > Thanks!
> > >
> > > References:
> > >
> > > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md
> >
> > > ___
> > > Sugar-devel mailing list
> > > [7]Sugar-devel@lists.sugarlabs.org
> > > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [9]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] https://github.com/sugarlabs/sugar/pull/805
> > [2] http://configure.ac/
> > [3] mailto:qu...@laptop.org
> > [4] http://configure.ac/
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> > [6]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> > [7] mailto:Sugar-devel@lists.sugarlabs.org
> > [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [9] 

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Alex Perez]

Jeff,

Most, if not all, of the Sugar-specific bugs that are present in Debian 
should be fixed if you use the "0.112-3" (the 3 is critically important) 
Debian packages from the _unstable_ Debian repo. They have not yet been 
promoted to testing, and will likely not be included in Debian 10 when 
it is released, as it is late in the package freeze process.


So, you have a few options here...the easiest thing to do would be to 
run an entire "unstable" install of Debian, since you will get these 
packages by default, but otherwise, you have to configure Apt with the 
unstable repo, and then use package pinning. This is documented at 
https://serverfault.com/questions/371383/install-whitelist-of-packages-using-unstable-in-debian.


See https://packages.debian.org/buster/sucrose for a list of these 
packages, and https://wiki.debian.org/DebianUnstable#Installation can 
explain how to enable the unstable apt repo on a stable or testing install.


This may also be of use 
https://serverfault.com/questions/22414/how-can-i-run-debian-stable-but-install-some-packages-from-testing



Jeff Elkner wrote on 5/15/19 9:54 AM:

Great to meet you (virtually), Alex and James.  I'm a high school /
community college teacher in Arlington, Virginia who was an early
member of the OLPC community here in the DC area.  I run Debian in my
classroom and would very much be interested in using the Sugar desktop
to work on that platform.  It doesn't currently seem to work.  I don't
have the capacity to fix it myself, but I can provide reliable testing
and feedback in an educational setting should that be of use to you.
I'm hoping to rejoin the Sugar community once it is in a state where
it can be used both in my classroom and on Raspberry Pi's.

Thanks!
Jeff Elkner
Arlington Career Center
Arlington, VA

On Wed, May 15, 2019 at 12:39 PM Samson Goddy  wrote:

Hello Alex and James,

I guess you both miss this thread. Can you please guide Jeff on how to get 
started?



On Fri, May 10, 2019, 8:14 AM Jeff Elkner  wrote:

Dear Sugar Labs Devs,

I am a high school / community college computer science teacher in
Arlington Virginia who was an active member of the OLPC project for
years and who would like to rejoin the community.

I am convinced being able to run the Sugar desktop on the same
underlying OS (Debian) as Raspbian uses is the key to that working for
me.

I tried creating a basic buster install and then running:

$ sudo apt install sugar sucrose lightdm

The result is not a usable Sugar installation.  I am most eager to
participate as a tester, power user, and curriculum developer, but I
need to start with a working system.

Thanks!

Jeff Elkner


Let's work together to create a just and sustainable world!


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar on Debian 10 (Buster)?

[Samson Goddy]

Hello Alex and James,

I guess you both miss this thread. Can you please guide Jeff on how to get
started?



On Fri, May 10, 2019, 8:14 AM Jeff Elkner  wrote:

> Dear Sugar Labs Devs,
>
> I am a high school / community college computer science teacher in
> Arlington Virginia who was an active member of the OLPC project for
> years and who would like to rejoin the community.
>
> I am convinced being able to run the Sugar desktop on the same
> underlying OS (Debian) as Raspbian uses is the key to that working for
> me.
>
> I tried creating a basic buster install and then running:
>
> $ sudo apt install sugar sucrose lightdm
>
> The result is not a usable Sugar installation.  I am most eager to
> participate as a tester, power user, and curriculum developer, but I
> need to start with a working system.
>
> Thanks!
>
> Jeff Elkner
>
>
> Let's work together to create a just and sustainable world!
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

James by v 0.113 I mean HEAD. Sorry for the confusion.

On Wed, 15 May 2019, 1:49 pm James Cameron,  wrote:

> Thanks!
>
> I've proposed a pull request to let the caller specify the Python
> version, and a draft pull request documenting how to build for both
> versions.
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> https://github.com/sugarlabs/sugar/pull/829
>
> Aniket, when you say v0.113 this means you are using either git tag
> v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
> but instead you would be using HEAD of master branch instead.  Is my
> guess right?
>
> Regarding the segmentation fault, please check
> .sugar/default/logs/shell.log for any details, or run within gdb and
> capture a backtrace of all threads.
>
> On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> > Regards,
> > I agree with, James. What I think is that since [1]this pr is not yet
> merged
> > into master, sugar requires python 2,
> > and the way I was installing Sugar builds the toolkit for Python 3. So I
> first
> > installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113
> by
> > hand.
> > Doing this I am able to test ported activities through the command line
> using
> > Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation
> fault"
> > with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> > figure out the reason for this.
> >
> > Regarding the Python version in [2]configure.ac, I think that the
> caller should
> > be allowed to specify the version or alternatively since we are porting
> to six,
> > a method building for both python2 and python3 would be great.
> >
> > I don't expect myself to be 100 percent right and expect to be corrected
> > wherever required.
> >
> > Thanks a lot, everyone. ☺
> >
> > On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org>
> wrote:
> >
> > G'day Aniket,
> >
> > If you were using the native sugar build method, then you are using
> > HEAD, which contains all patches since 0.113.  Don't try to apply the
> > patch that Alex pointed out, as it is already applied.
> >
> > The error message "ImportError: No module named sugar3" is caused by
> > not installing the Toolkit for Python 2.
> >
> > Sugar 0.113 requires Python 2.
> >
> > Toolkit by default installs for Python 3.
> >
> > You can verify this is the situation by testing the import by hand
> > using different versions of Python;
> >
> > python3 -c 'import sugar3'  # expect pass
> >
> > python2 -c 'import sugar3'  # expect fail
> >
> > You'll find in [4]configure.ac where the Python version is chosen.
> >
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> > #L18
> >
> > Perhaps that line should allow the caller to specify the version.
> >
> > What do you think?
> >
> > On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > > Greetings everyone,
> > >
> > > I was installing Sugar v0.113 using the Native Sugar build
> method [1]
> > here. I
> > > was using Ubuntu 18.10. After installation, on running Sugar I
> received
> > the
> > > error message "ImportError: No module named sugar3". Need help
> with a
> > couple of
> > > questions
> > > 1) Is there a need to have a build of the older version for v0.113
> to
> > work
> > > properly?
> > > (never paid attention to that before).
> > >  2) What is the correct procedure for installing v0.113?
> > > Thanks!
> > >
> > > References:
> > >
> > > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md
> >
> > > ___
> > > Sugar-devel mailing list
> > > [7]Sugar-devel@lists.sugarlabs.org
> > > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> > --
> > James Cameron
> > [9]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] https://github.com/sugarlabs/sugar/pull/805
> > [2] http://configure.ac/
> > [3] mailto:qu...@laptop.org
> > [4] http://configure.ac/
> > [5]
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> > [6]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> > [7] mailto:Sugar-devel@lists.sugarlabs.org
> > [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [9] http://quozl.netrek.org/
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[James Cameron]

Thanks!

I've proposed a pull request to let the caller specify the Python
version, and a draft pull request documenting how to build for both
versions.

https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
https://github.com/sugarlabs/sugar/pull/829

Aniket, when you say v0.113 this means you are using either git tag
v0.113 (i.e. e30b73f) or tarball.  Seems unlikely you are doing that,
but instead you would be using HEAD of master branch instead.  Is my
guess right?

Regarding the segmentation fault, please check
.sugar/default/logs/shell.log for any details, or run within gdb and
capture a backtrace of all threads.

On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> Regards,
> I agree with, James. What I think is that since [1]this pr is not yet merged
> into master, sugar requires python 2, 
> and the way I was installing Sugar builds the toolkit for Python 3. So I first
> installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113 by
> hand.
> Doing this I am able to test ported activities through the command line using
> Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation fault"
> with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> figure out the reason for this.
> 
> Regarding the Python version in [2]configure.ac, I think that the caller 
> should
> be allowed to specify the version or alternatively since we are porting to 
> six,
> a method building for both python2 and python3 would be great.
> 
> I don't expect myself to be 100 percent right and expect to be corrected
> wherever required.
> 
> Thanks a lot, everyone. ☺
> 
> On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]qu...@laptop.org> wrote:
> 
> G'day Aniket,
> 
> If you were using the native sugar build method, then you are using
> HEAD, which contains all patches since 0.113.  Don't try to apply the
> patch that Alex pointed out, as it is already applied.
> 
> The error message "ImportError: No module named sugar3" is caused by
> not installing the Toolkit for Python 2.
> 
> Sugar 0.113 requires Python 2.
> 
> Toolkit by default installs for Python 3.
> 
> You can verify this is the situation by testing the import by hand
> using different versions of Python;
> 
> python3 -c 'import sugar3'  # expect pass
> 
> python2 -c 'import sugar3'  # expect fail
> 
> You'll find in [4]configure.ac where the Python version is chosen.
> 
> 
> [5]https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> #L18
> 
> Perhaps that line should allow the caller to specify the version.
> 
> What do you think?
> 
> On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > Greetings everyone,
> >
> > I was installing Sugar v0.113 using the Native Sugar build method [1]
> here. I
> > was using Ubuntu 18.10. After installation, on running Sugar I received
> the
> > error message "ImportError: No module named sugar3". Need help with a
> couple of
> > questions 
> > 1) Is there a need to have a build of the older version for v0.113 to
> work
> > properly?
> > (never paid attention to that before).
> >  2) What is the correct procedure for installing v0.113?
> > Thanks!  
> >
> > References:
> >
> > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> development-environment.md
> 
> > ___
> > Sugar-devel mailing list
> > [7]Sugar-devel@lists.sugarlabs.org
> > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [9]http://quozl.netrek.org/
> 
> References:
> 
> [1] https://github.com/sugarlabs/sugar/pull/805
> [2] http://configure.ac/
> [3] mailto:qu...@laptop.org
> [4] http://configure.ac/
> [5] 
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> [6] 
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> [7] mailto:Sugar-devel@lists.sugarlabs.org
> [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> [9] http://quozl.netrek.org/

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

Regards,
I agree with, James. What I think is that since this pr
 is not yet merged into
master, sugar requires python 2,
and the way I was installing Sugar builds the toolkit for Python 3. So I
first installed Sugar from sucrose and then installed the toolkit-gtk3
v0.113 by hand.
Doing this I am able to test ported activities through the command line
using Ubuntu 18.04 terminal, but opening Sugar home view causes
"Segmentation fault" with a warning "python2.7 has stopped unexpectedly". I
am not yet able to figure out the reason for this.

Regarding the Python version in configure.ac, I think that the caller
should be allowed to specify the version or alternatively since we are
porting to six, a method building for both python2 and python3 would be
great.

I don't expect myself to be 100 percent right and expect to be corrected
wherever required.

Thanks a lot, everyone. ☺



On Wed, May 15, 2019 at 3:17 AM James Cameron  wrote:

> G'day Aniket,
>
> If you were using the native sugar build method, then you are using
> HEAD, which contains all patches since 0.113.  Don't try to apply the
> patch that Alex pointed out, as it is already applied.
>
> The error message "ImportError: No module named sugar3" is caused by
> not installing the Toolkit for Python 2.
>
> Sugar 0.113 requires Python 2.
>
> Toolkit by default installs for Python 3.
>
> You can verify this is the situation by testing the import by hand
> using different versions of Python;
>
> python3 -c 'import sugar3'  # expect pass
>
> python2 -c 'import sugar3'  # expect fail
>
> You'll find in configure.ac where the Python version is chosen.
>
>
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
>
> Perhaps that line should allow the caller to specify the version.
>
> What do you think?
>
> On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > Greetings everyone,
> >
> > I was installing Sugar v0.113 using the Native Sugar build
> method [1]here. I
> > was using Ubuntu 18.10. After installation, on running Sugar I received
> the
> > error message "ImportError: No module named sugar3". Need help with a
> couple of
> > questions
> > 1) Is there a need to have a build of the older version for v0.113 to
> work
> > properly?
> > (never paid attention to that before).
> >  2) What is the correct procedure for installing v0.113?
> > Thanks!
> >
> > References:
> >
> > [1]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
>
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Toolkit Installation Sugar v0.113

[Tony Anderson]

+1

On 5/14/19 8:41 PM, Walter Bender wrote:
Any chance of a 0.113.1 maintenance release [1] to make this patch 
available? Seems unreasonable to expect mere mortals to find and apply 
patches just to get started.


regards.

-walter

[1] https://en.wikipedia.org/wiki/Maintenance_release

On Tue, May 14, 2019 at 11:46 AM Alex Perez > wrote:


Aniket,

You have hit a known bug for 0.113. Please see
https://github.com/sugarlabs/sugar/issues/822

I should also point out that this was an easily search-able issue,
and would encourage you to use Google or your preferred search
engine, when you encounter issues like this in the future.

This bug will be fixed in 0.114, whenever that is released, which
I have no direct control over. For now, you can download

https://github.com/sugarlabs/sugar/commit/a83257bcf791e237afb55ed37f04d776f0fd927b.patch/
and patch Sugar manually, using the 'patch' command.

ANIKET MATHUR wrote on 5/14/19 4:12 AM:

Greetings everyone,

I was installing Sugar v0.113 using the Native Sugar build method
here

.
I was using Ubuntu 18.10. After installation, on running Sugar I
received the error message "ImportError: No module named sugar3".
Need help with a couple of questions
1) Is there a need to have a build of the older version for
v0.113 to work properly?
(never paid attention to that before).
 2) What is the correct procedure for installing v0.113?
Thanks!


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org

http://lists.sugarlabs.org/listinfo/sugar-devel



--
Walter Bender
Sugar Labs
http://www.sugarlabs.org


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel