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

[ANIKET MATHUR]

Thanks James I was not starting Sugar as a desktop session. Now things work
fine for me.

On Tue, May 21, 2019 at 12:26 PM James Cameron  wrote:

> Thanks.
>
> Are you sure you gave me the correct log?  There's no segmentation
> fault shown there.  The log should be .sugar/default/logs/shell.log
>
> You can gather more information about a segmentation fault using gdb
> and backtrace command.
>
> Further reply in context below.
>
> On Tue, May 21, 2019 at 12:10:20PM +0530, ANIKET MATHUR wrote:
> > Regarding the Segmentation Fault.
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:16:32: The style property GtkExpander:expander-size
> is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> > gtk-widgets.css:17:35: The style property
> GtkExpander:expander-spacing is
> > deprecated and shouldn't be used anymore. It will be removed in a
> future
> > version
> >
> > (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > 1558420503.333096 ERROR root: window manager did fail, restarting
> > Traceback (most recent call last):
>
> Confirm you are starting Sugar as a desktop session and not as a
> program inside another desktop session?
>
> For example, on my Ubuntu 18.04 test system, `ps axfww` shows jarabe
> to be a child process of gdm-x-session, gdm-session-worker, and gdm3;
> thus;
>
> ...
>  1885 ?Ssl0:00 /usr/sbin/gdm3
>  2547 ?Sl 0:00  \_ gdm-session-worker [pam/gdm-password]
>  2557 tty2 Ssl+   0:00  \_ /usr/lib/gdm3/gdm-x-session
> --run-script sugar
>  2560 tty2 Sl+0:10  \_ /usr/lib/xorg/Xorg vt2 -displayfd 3
> -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty
> -verbose 3
>  2569 tty2 Sl+0:10  \_ python2 -m jarabe.main
>  2635 ?Ss 0:00  \_ /usr/bin/ssh-agent
> /usr/bin/im-launch sugar
>  2659 tty2 Z+ 0:00  \_ [sugar] 
>  2670 tty2 Sl+0:00  \_ metacity --no-force-fullscreen
> --no-composite
>
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 604, in
> > msg_reply_handler
> > reply_handler(*message.get_args_list(**get_args_opts))
> >   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 738, in __got_accounts_cb
> > self._server_account = self._ensure_server_account(account_paths)
> >   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> > neighborhood.py", line 851, in _ensure_server_account
> > properties)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70,
> in
> > __call__
> > return self._proxy_method(*args, **keywords)
> >   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145,
> in
> > __call__
> > **keywords)
> >   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line
> 651, in
> > call_blocking
> > message, timeout)
> > dbus.exceptions.DBusException:
> > org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber'
> not found
> > on CM 'gabble'
>
> Is Telepathy Gabble installed?
>
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
> >   Gtk.main()
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> unable
> > to set property 'buddy' of type 'PyObject' from value of type
> '(null)'
> >   Gtk.main()
> >
> > (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on
> display
> > ":0" already has a window manager; try using the --replace option to
> > replace the current window manager.
> > /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> > g_spawn_command_line_async: assertion 'command_line != NULL' failed
> >   Gtk.main()
> >
> > This is the log that I am getting on starting Sugar Desktop.
>
> Apart from the log, is there anything else that happens?  i.e. does
> Sugar start and show the activity ring or Journal?
>
> > 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 

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

[James Cameron]

Thanks.

Are you sure you gave me the correct log?  There's no segmentation
fault shown there.  The log should be .sugar/default/logs/shell.log

You can gather more information about a segmentation fault using gdb
and backtrace command.

Further reply in context below.

On Tue, May 21, 2019 at 12:10:20PM +0530, ANIKET MATHUR wrote:
> Regarding the Segmentation Fault.
> 
> (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:16:32: The style property GtkExpander:expander-size is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
> 
> (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:17:35: The style property GtkExpander:expander-spacing is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
> 
> (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> 1558420503.333096 ERROR root: window manager did fail, restarting
> Traceback (most recent call last):

Confirm you are starting Sugar as a desktop session and not as a
program inside another desktop session?

For example, on my Ubuntu 18.04 test system, `ps axfww` shows jarabe
to be a child process of gdm-x-session, gdm-session-worker, and gdm3;
thus;

...
 1885 ?Ssl0:00 /usr/sbin/gdm3
 2547 ?Sl 0:00  \_ gdm-session-worker [pam/gdm-password]
 2557 tty2 Ssl+   0:00  \_ /usr/lib/gdm3/gdm-x-session --run-script 
sugar
 2560 tty2 Sl+0:10  \_ /usr/lib/xorg/Xorg vt2 -displayfd 3 
-auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 
3
 2569 tty2 Sl+0:10  \_ python2 -m jarabe.main
 2635 ?Ss 0:00  \_ /usr/bin/ssh-agent 
/usr/bin/im-launch sugar
 2659 tty2 Z+ 0:00  \_ [sugar] 
 2670 tty2 Sl+0:00  \_ metacity --no-force-fullscreen 
--no-composite

>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in
> msg_reply_handler
>     reply_handler(*message.get_args_list(**get_args_opts))
>   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> neighborhood.py", line 738, in __got_accounts_cb
>     self._server_account = self._ensure_server_account(account_paths)
>   File "/usr/local/lib/python2.7/dist-packages/jarabe/model/
> neighborhood.py", line 851, in _ensure_server_account
>     properties)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
> __call__
>     return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
> __call__
>     **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
> call_blocking
>     message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber' not 
> found
> on CM 'gabble'

Is Telepathy Gabble installed?

> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
>   Gtk.main()
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning: unable
> to set property 'buddy' of type 'PyObject' from value of type '(null)'
>   Gtk.main()
> 
> (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_spawn_command_line_async: assertion 'command_line != NULL' failed
>   Gtk.main()
> 
> This is the log that I am getting on starting Sugar Desktop.

Apart from the log, is there anything else that happens?  i.e. does
Sugar start and show the activity ring or Journal?

> 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 

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

[ANIKET MATHUR]

Regarding the Segmentation Fault.

(main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:16:32: The style property GtkExpander:expander-size is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
>
> (main.py:2041): Gtk-WARNING **: 12:04:58.709: Theme parsing error:
> gtk-widgets.css:17:35: The style property GtkExpander:expander-spacing is
> deprecated and shouldn't be used anymore. It will be removed in a future
> version
>
> (metacity:2048): metacity-WARNING **: 12:04:58.799: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> 1558420503.333096 ERROR root: window manager did fail, restarting
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in
> msg_reply_handler
> reply_handler(*message.get_args_list(**get_args_opts))
>   File
> "/usr/local/lib/python2.7/dist-packages/jarabe/model/neighborhood.py", line
> 738, in __got_accounts_cb
> self._server_account = self._ensure_server_account(account_paths)
>   File
> "/usr/local/lib/python2.7/dist-packages/jarabe/model/neighborhood.py", line
> 851, in _ensure_server_account
> properties)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in
> __call__
> return self._proxy_method(*args, **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
> __call__
> **keywords)
>   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
> call_blocking
> message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.Telepathy.Error.NotImplemented: Protocol 'jabber' not found
> on CM 'gabble'
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_value_transform: assertion 'G_IS_VALUE (src_value)' failed
>   Gtk.main()
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning: unable
> to set property 'buddy' of type 'PyObject' from value of type '(null)'
>   Gtk.main()
>
> (metacity:2175): metacity-WARNING **: 12:05:04.405: Screen 0 on display
> ":0" already has a window manager; try using the --replace option to
> replace the current window manager.
> /usr/local/lib/python2.7/dist-packages/jarabe/main.py:378: Warning:
> g_spawn_command_line_async: assertion 'command_line != NULL' failed
>   Gtk.main()
>

This is the log that I am getting on starting Sugar Desktop.

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 

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

[James Cameron]

Aniket, I've refined the native environment instructions after testing
on Fedora 30 and Ubuntu 19.04.  I've made a pull request here;

https://github.com/sugarlabs/sugar/pull/830

It is a hybrid configuration, which may leave a copy of the downstream
Sugar packages in /usr, and our latest HEAD in /usr/local.  I'm not
sure how reliable this may be; there were some oddities with respect
to paths.  If using this hybrid configuration, look for problems
caused by the wrong code being run.

On Thu, May 16, 2019 at 02:00:59PM +1000, James Cameron wrote:
> 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 

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

[James Cameron]

It is a wicked problem.  Here are my thoughts;

1.  there are three temporal scopes of dependency; build time, run
time, and those for downloaded activities,

2.  our activity bundle specification doesn't list dependencies, so we
had early assumptions about what would be available,

3.  some of the dependencies are listed in old documentation on our
Wiki, such as;

https://wiki.sugarlabs.org/go/0.96/Platform_Components
https://wiki.sugarlabs.org/go/Sugar_Platform_Stack
https://wiki.sugarlabs.org/go/Sugar_System_Stack

4.  very few people need to know the dependencies, because most people
install the distribution packages, or install Fedora SoaS where all
the work is already done; this can be verified by seeing how
infrequently dependency related problems are reported; those that need
the dependencies in detail should have the knowledge and skill to
resolve them using tools,

5.  the Sugar and Toolkit dependencies have not changed much for a
long time, although the work you are doing will change that,

6.  package dependencies are tracked by the Fedora and Debian
developers who package Sugar, often using tools that detect object
libraries linked to executables, or static analysis of imports.  These
developers do the most toward maintaining a list of dependencies, and
it is stored in packaging metadata,

7.  package dependencies are not the same between our supported
distributions of Fedora and Debian, because of different standards in
naming packages,

8.  some of the package names are very strange and non-intuitive to
the outsider; e.g. the gir* packages, for the gi.repository imports,

9.  some of the apparent changes to dependencies occur because of
package name changes in Fedora and Debian, which are not our direct
concern and not in our control,

10.  some dependencies are in the platform components list only
because an activity once required them, but since then the activity is
broken, unmaintained, or the dependency removed after a port,

11.  dependencies of distribution packages are a subset of the
dependencies of the whole Sugar platform stack,

12.  packagers will often package a new release of Sugar and not
notice the new dependency, and not test, in which case Sugar will fail
to start, and some user has to notice and report a bug to the
distribution,

So I agree, I don't think mentioning them all in the documentation
will be a good idea; mainly because of how much work would be required
and how much benefit there would be from that work.

I welcome thoughts of others though, especially anybody who might want
to maintain the data.

On Fri, May 17, 2019 at 10:13:41AM +0530, ANIKET MATHUR wrote:
> Thanks. James.
> Agreed, there can be a number of runtime dependencies that the user has to
> install. I don't think mentioning them all in the documentation
> will be a good idea. What do you think?
> 
> On Thu, May 16, 2019 at 9:31 AM James Cameron <[1]qu...@laptop.org> wrote:
> 
> 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
> [2]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][3]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][4]https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
> >     [3][5]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 

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

[ANIKET MATHUR]

Thanks. James.
Agreed, there can be a number of runtime dependencies that the user has to
install. I don't think mentioning them all in the documentation
will be a good idea. What do you think?

On Thu, May 16, 2019 at 9:31 AM James Cameron  wrote:

> 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 

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] 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

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

[James Cameron]

I've two answers.

1.  No.  Aniket did not hit the problem for which this patch is the
solution.

2.  No.  Next release is 0.114, and I'm waiting on better evidence of
testing of 0.113 plus the errata patches.

Mere mortals may confine themselves to Fedora 30 which has Sugar
0.113, or Ubuntu 19.04 which has Sugar 0.112.

Aniket is to work on Port to Python 3, and this is not for mere
mortals.  That's why we chose Aniket.  I have confidence in Aniket.

On Tue, May 14, 2019 at 03:41:58PM -0400, 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] [1]https://en.wikipedia.org/wiki/Maintenance_release
> 
> On Tue, May 14, 2019 at 11:46 AM Alex Perez <[2]ape...@alexperez.com> wrote:
> 
> Aniket,
> 
> You have hit a known bug for 0.113. Please see [3]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 [4]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 [5]
> 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
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> Walter Bender
> Sugar Labs
> [8]http://www.sugarlabs.org
> [9]
> 
> References:
> 
> [1] https://en.wikipedia.org/wiki/Maintenance_release
> [2] mailto:ape...@alexperez.com
> [3] https://github.com/sugarlabs/sugar/issues/822
> [4] 
> https://github.com/sugarlabs/sugar/commit/a83257bcf791e237afb55ed37f04d776f0fd927b.patch/
> [5] 
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> [8] http://www.sugarlabs.org/
> [9] http://www.sugarlabs.org/

> ___
> 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

[James Cameron]

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

[Walter Bender]

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

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

[Alex Perez]

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

[Sugar-devel] Toolkit Installation Sugar v0.113

[ANIKET MATHUR]

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