Re: [Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread Hrishi Patel
Thanks. A few have been solved. I will try to fix the rest soon.

On Tue, Jun 11, 2019 at 2:27 PM James Cameron  wrote:

> Tested on OLPC OS, and issues opened.
>
> --
> 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] Problem packaging toolkit

2019-06-11 Thread James Cameron
No, configure.ac already installs for both versions, you just have to
run it twice.  This is how other projects handle mixed version
environment.  You would have seen that had you looked through the
other packages as I suggested.  ;-)

On Ubuntu 18.04 there are no more than 260 of those packages in main
suite, and 2082 in universe suite.  Choose a few, make sure the source
package is identical, make sure they use autotools, then evaluate the
source package to establish some best practices.

When you rebuild your packages of sugar-toolkit-gtk3, you should
supplant the files you have already built.  That's what package
versioning is for.

On Tue, Jun 11, 2019 at 11:46:31AM +0530, ANIKET MATHUR wrote:
> Thanks.
> Regarding packaging for both the version, first we have to make changes in 
> the 
> [1]configure.ac file so that the toolkit is installed for both the versions
> automatically?
> For Python 3 do I have to make a separate repo or just push the python3-sugar3
> to the current repo?
> Sorry, I am confused.
> 
> On Tue, Jun 11, 2019 at 11:21 AM James Cameron <[2]qu...@laptop.org> wrote:
> 
> Look for python-foo and python3-foo packages that have been built from
> the same source package.
> 
> Once you have it working, this lintian warning in
> sugar-toolkit-gtk3_0.114-1_amd64.build will vanish;
> 
> W: sugar-toolkit-gtk3 source: python-foo-but-no-python3-foo python-sugar3
> 
> Reviewed your packages; you have successfully reproduced what Ubuntu
> and Debian have done, plus you've adopted 0.114.  Well done.
> 
> Things to do;
> 
> * [ ] add new python3-sugar3 package into which the build for python3
>   will be constructed, as per above,
> 
> * [ ] ensure /usr/bin/sugar-activity3 is not in the python-sugar3
>   package,
> 
> * [ ] ensure /usr/bin/sugar-activity is not in the python3-sugar3
>   package,
> 
> * [ ] use a developer local version number, perhaps with a git hash,
> 
> * [ ] fix your mail address in debian/changelog
> 
> On Tue, Jun 11, 2019 at 10:58:22AM +0530, ANIKET MATHUR wrote:
> > Thanks, made a separate github repo. [1]Link.
> > áRegarding packaging for both Python 2 and Python 3, sorry I never came
> along
> > with same Ubuntu packages installing for both the versions of Python.
> Though I
> > have seen separate packages for Python 2 and Python 3 line pip and pip3.
> I will
> > do my research regarding this and will give updates if I found anything
> useful.
> >
> > On Tue, Jun 11, 2019 at 10:23 AM James Cameron <[2][3]qu...@laptop.org>
> wrote:
> >
> >     Put them somewhere for me to download; either a separate GitHub
> >     repository, or a web server.á We can make an account for you on
> >     sunjammer, see the Wiki Service/Shell page.
> >
> >     You may be interested in dcmd as a quick way to simplify copying
> >     these files.
> >
> >     Also look at how to use reprepro, which can make a package archive
> >     that you can then serve with a web server and use in sources.list
> >
> >     Once you've made the packages available to me, I'll check them.
> >
> >     Next step is to package for both Python 2 and Python 3.á I don't 
> know
> >     how to do that yet.á There are other Debian and Ubuntu packages with
> >     dual-version source that may be used as a template.
> >
> >     On Tue, Jun 11, 2019 at 10:01:08AM +0530, ANIKET MATHUR wrote:
> >     > Thanks.
> >     > I have build the packages.Now what should I do next, which files I
> have
> >     to
> >     > share?
> >     >
> >     > On Mon, Jun 10, 2019 at 2:28 PM James Cameron <[1][3][4]
> qu...@laptop.org>
> >     wrote:
> >     >
> >     >á á áI've checked, and po/LINGUAS does contain ach.á The problem is
> caused
> >     >á á áby bzr builddeb running the check-po target of the Makefile,
> which
> >     >á á ácurrently fails like this;
> >     >
> >     >á á áhost:sugar-toolkit-gtk3$ make check-po
> >     >á á á*** ach missing from po/LINGUAS ***
> >     >á á áMakefile:859: recipe for target 'check-po' failed
> >     >á á ámake: *** [check-po] Error 1
> >     >
> >     >á á áYou're welcome to fix this target.á See Makefile.am.á The
> failure is
> >     >á á áunrelated to packaging and can be reproduced easily.á I don't
> plan to
> >     >á á áfix it before the next release.
> >     >
> >     >á á áThe guide you refer to is for packaging new software for
> >     >á á áUbuntu, whereas the Toolkit is existing software from Debian
> that
> >     >á á áUbuntu has adopted without change.
> >     >
> >     >á á áUse the Debian source package instead.á You can get it from
> Ubuntu as
> >     >á á áa source package using `apt source`, or `dget` the dsc from
> >     >á á 

Re: [Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread James Cameron
Tested on OLPC OS, and issues opened.

-- 
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] Video: The Coolest Netbook You’ve Forgotten About: The OLPC XO-1

2019-06-11 Thread Sumit Srivastava
Watch the comments, I tried to help. :P

On Tue, 11 Jun 2019, 4:31 am James Cameron,  wrote:

> Thanks Ignacio,
>
> I like the Prius in the background.
>
> I like how my updates to the OLPC web site were visible.  Makes it
> worth the effort.  ;-)
>
> Software shown was from February 2008; with Write-55, Nano 2.0.6, and
> Python 2.5.1
>
> One of the battery latches was, as usual, left unlocked.
>
> On Mon, Jun 10, 2019 at 07:24:05PM -0300, Ignacio Rodríguez wrote:
> > [1]https://www.youtube.com/watch?v=UPP4ClRmVik
> >
> > References:
> >
> > [1] https://www.youtube.com/watch?v=UPP4ClRmVik
>
> > ___
> > 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread Hrishi Patel
Hello,

Sugar Dashboard is near completion. It'd be great if anyone can test it and
provide issues, feedback, bugs, etc. before we release it.
The link to repository: https://github.com/sugarlabs/Dashboard.Activity

You can open issues on the repository.

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


Re: [Sugar-devel] Problem packaging toolkit

2019-06-11 Thread ANIKET MATHUR
Thanks.
Regarding packaging for both the version, first we have to make changes in
the configure.ac file so that the toolkit is installed for both the
versions automatically?
For Python 3 do I have to make a separate repo or just push the
python3-sugar3 to the *current repo?*
Sorry, I am confused.

On Tue, Jun 11, 2019 at 11:21 AM James Cameron  wrote:

> Look for python-foo and python3-foo packages that have been built from
> the same source package.
>
> Once you have it working, this lintian warning in
> sugar-toolkit-gtk3_0.114-1_amd64.build will vanish;
>
> W: sugar-toolkit-gtk3 source: python-foo-but-no-python3-foo python-sugar3
>
> Reviewed your packages; you have successfully reproduced what Ubuntu
> and Debian have done, plus you've adopted 0.114.  Well done.
>
> Things to do;
>
> * [ ] add new python3-sugar3 package into which the build for python3
>   will be constructed, as per above,
>
> * [ ] ensure /usr/bin/sugar-activity3 is not in the python-sugar3
>   package,
>
> * [ ] ensure /usr/bin/sugar-activity is not in the python3-sugar3
>   package,
>
> * [ ] use a developer local version number, perhaps with a git hash,
>
> * [ ] fix your mail address in debian/changelog
>
> On Tue, Jun 11, 2019 at 10:58:22AM +0530, ANIKET MATHUR wrote:
> > Thanks, made a separate github repo. [1]Link.
> > áRegarding packaging for both Python 2 and Python 3, sorry I never came
> along
> > with same Ubuntu packages installing for both the versions of Python.
> Though I
> > have seen separate packages for Python 2 and Python 3 line pip and pip3.
> I will
> > do my research regarding this and will give updates if I found anything
> useful.
> >
> > On Tue, Jun 11, 2019 at 10:23 AM James Cameron <[2]qu...@laptop.org>
> wrote:
> >
> > Put them somewhere for me to download; either a separate GitHub
> > repository, or a web server.á We can make an account for you on
> > sunjammer, see the Wiki Service/Shell page.
> >
> > You may be interested in dcmd as a quick way to simplify copying
> > these files.
> >
> > Also look at how to use reprepro, which can make a package archive
> > that you can then serve with a web server and use in sources.list
> >
> > Once you've made the packages available to me, I'll check them.
> >
> > Next step is to package for both Python 2 and Python 3.á I don't know
> > how to do that yet.á There are other Debian and Ubuntu packages with
> > dual-version source that may be used as a template.
> >
> > On Tue, Jun 11, 2019 at 10:01:08AM +0530, ANIKET MATHUR wrote:
> > > Thanks.
> > > I have build the packages.Now what should I do next, which files I
> have
> > to
> > > share?
> > >
> > > On Mon, Jun 10, 2019 at 2:28 PM James Cameron <[1][3]
> qu...@laptop.org>
> > wrote:
> > >
> > >á á áI've checked, and po/LINGUAS does contain ach.á The problem is
> caused
> > >á á áby bzr builddeb running the check-po target of the Makefile,
> which
> > >á á ácurrently fails like this;
> > >
> > >á á áhost:sugar-toolkit-gtk3$ make check-po
> > >á á á*** ach missing from po/LINGUAS ***
> > >á á áMakefile:859: recipe for target 'check-po' failed
> > >á á ámake: *** [check-po] Error 1
> > >
> > >á á áYou're welcome to fix this target.á See Makefile.am.á The
> failure is
> > >á á áunrelated to packaging and can be reproduced easily.á I don't
> plan to
> > >á á áfix it before the next release.
> > >
> > >á á áThe guide you refer to is for packaging new software for
> > >á á áUbuntu, whereas the Toolkit is existing software from Debian
> that
> > >á á áUbuntu has adopted without change.
> > >
> > >á á áUse the Debian source package instead.á You can get it from
> Ubuntu as
> > >á á áa source package using `apt source`, or `dget` the dsc from
> > >á á á[2][4]packages.ubuntu.com.á Change the version in
> debian/changelog
> > and
> > >á á ásubstitute the new source tar.xz file.
> > >
> > >á á áSee also sugar/docs/debian-packaging-example.md
> > >
> > >á á áOn Mon, Jun 10, 2019 at 01:06:00PM +0530, ANIKET MATHUR wrote:
> > >á á á> Hello everyone.
> > >á á á> I was trying to package sugar-toolkit-gtk3 v 0.114 following
> the
> > [1]
> > >á á á> documentation.
> > >á á á> I successfully followed till 4.2, but on running the first
> command
> > in 4.3
> > >á á á>
> > >á á á> bzr builddeb -- -us -uc
> > >á á á>
> > >á á á> The build failed with
> > >á á á>
> > >á á á> `
> > >á á á> make[1]: Entering directory
> '/home/aniket21/toolkit/build-area/
> > >á á ásugar-toolkit-gtk3-0.114'
> > >á á á> *** ach missing from po/LINGUAS ***
> > >á á á> Makefile:859: recipe for target 'check-po' failed
> > >á á á> make[1]: *** [check-po] Error 1
> > >á á á> make[1]: Leaving directory
> '/home/aniket21/toolkit/build-area/
> > >á á ásugar-toolkit-gtk3-0.114'
> > >á á á>