[Sugar-devel] Sugarizer School Portal - Meeting: 25 May 2020

[NIKHIL MEHRA]

Hi,

Today, I had a meeting with Michaël and had discussions about work items
from the last week which basically includes:
- Add i18n translation in the app.
- Start working on the "Request for Deployments" feature.

Problems experienced last week:
- Had difficulty finding suitable i18n library for client-side
translations. In the end, we used i18next with jquery-i18next and modified
jquery-i18next code to allow moment-js localisation and taking JS objects
as input.

Here is a list of tasks that we have decided for this week:
- Connect Sugarizer-School-Portal with helm and add a feature to install a
simple chart from the interface.
- Add more translations for the Deployments part and update the error codes.
- Fix bugs and add improvements in current Sugarizer-School-Portal

PFA slack logs for reference. Next meeting is scheduled for next Monday.

Regards,
Nikhil
Michaël Ohayon  2:45 PM
Yes let’s begin!

Nikhil  2:45 PM
How are you doing?

Michaël Ohayon  2:45 PM
Great and you? How are you doing?

Nikhil  2:46 PM
I'm doing great
2:46
We still have a week before GSoC coding officially begins.

Michaël Ohayon  2:47 PM
Yes :smile:

Nikhil  2:47 PM
Last week tasks were:
Add i18n translation in the app.
Start working on the "Request for Deployments" feature.

Michaël Ohayon  2:48 PM
:thumbsup:

Nikhil  2:48 PM
I used i18next, jqeury-i18next, and moment-with-locale for localisation.
2:49
The translation is completely client based. You don't need to refresh the browser to update the translation.
I had to modify the code of this library (https://github.com/i18next/jquery-i18next) to allow moment.js dynamic translation. I also made some changes to allow passing JS Objects as parameters. The library has MIT license to I think it'll be fine to freely modify its code.
The translation set-up took more time than expected.
2:50
I have also added a view for the Client Sign-up.
2:52
I started working on the "Request for Deployments" feature. I have added a view using which Clients/Moderators/Admins and create a Deployment request.
2:53
Only Admin can approve/reject the deployment request.
Only Admin can start/stop the deployment. (The code to actually start/stop deployment is not added yet)
2:53
Moderators can view all the deployments but can only edit the deployments created by them. (edited) 
2:54
Clients can only view and edit the deployments created by them.
2:54
Admin can view/edit any deployment.
2:54
The school-short-name once set cannot be edited

Michaël Ohayon  2:55 PM
That is nice, maybe you could list that under a table in the README

Nikhil  2:55 PM
Oh. Okay
2:56
Should I create a Features section in the README and mention these points under that section? (edited) 

Michaël Ohayon  2:56 PM
:smile: that may help you in a few weeks to be sure what you are willing to achieve
2:56
Yes that is great

Nikhil  2:56 PM
Cool
2:57
What are your views about the Sugarizer-School-Portal-Server? You were just tested it
2:57
What do you think about the interface of the Deployments view?

Michaël Ohayon  2:58 PM
It is nice, I did not have struggle using it

Nikhil  2:58 PM
Great!

Michaël Ohayon  2:59 PM
Maybe you could give hints about default microk8s helm location

Nikhil  3:00 PM
Give hints where exactly?
3:00
I have mentioned in the readme to modify the helm location in the config file.
3:00
This week I was planning to work further on the Deployments feature. Connect with helm and install some simple charts (Not Sugarizer-Chart)

Michaël Ohayon  3:01 PM
Yes, but using microk8s I guess the path is always the same

Nikhil  3:01 PM
Readme:
Changes:
- Modify line 17 in node-modules/node-helm/helm.js. Change this.executer.callByArguments(command, callbackHandler(done)); to this.executer.callByArguments(command, callbackHandler(done, true), true);
- Update env/config.ini and set helm_binary to the location to helm binary in your system.

Michaël Ohayon  3:01 PM
So maybe you could provide yours to avoid looking for it :smile:

Nikhil  3:03 PM
I think when microk8s finishes installation, it can be accessed with microk8s.helm3 from the terminal (edited) 

Michaël Ohayon  3:03 PM
Yes I went looking for the path
3:03
Can I leave microk8s.helm3 ?
3:03
It is path or binary name :thinking_face: ?

Nikhil  3:03 PM
Yeah
3:03
It works for me

Michaël Ohayon  3:04 PM
Ah nice, maybe you could add that in the readme then :smile:
:+1:
1

3:04
I was thinking path was required :smile:

Nikhil  3:04 PM
Okay
3:06
I have finished the translation part, now I just have to keep updating the .json files to add more translations

Michaël Ohayon  3:06 PM
:smile:
3:06
That is nice
3:06
Well done :ok_hand:

Nikhil  3:07 PM
So this week I'll add more translations for the Deployments part. I also have to update the error codes and add their meaning in .json file.

Michaël Ohayon  3:08 PM
I can give the fr.json a look :upside_down_face:

Nikhil  3:08 PM
I'll also make some improvements like improve the search feature to not just search for name but search fo

[Sugar-devel] Situation update

[Anindya Kundu]

Hello,

Thanks for understanding my situation. Electricity has finally been
restored and things are recovering. There is an issue with the broadband
which will hopefully be fixed in a couple of days, now that the
electricity is back.

I joined our daily meeting today from my phone, barely getting in before it
ended. I had a quick chat and informed about my state. I'll be meeting
tomorrow half an hour early with Walter, before out group gathering.

Meanwhile, I'll get back to work by tonight. I'll start with some
experiment code I was trying out, to eventually get on with the Note class
we were discussing.

I've previously mentioned that I'll be working on a branch wip-note-class
in my fork  of Music Blocks. I
was exploring the 'Projects' feature on GitHub, and found that it can be
useful. I've created a project in the said repository and I'll be updating
my progress there.

Regards.

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

Re: [Sugar-devel] Weekly Progress: Scale Degree vs n^th Modal Pitch

[Devin Ulibarri]

Hi,
Aviral is publishing his progress on musicblocks.net which you can
track at https://musicblocks.net/author/aviralgangwar24/
You can subscribe via https://musicblocks.net/feed/ for instant
updates.
He has made a lot of progress on GH as well. https://github.com/sugarla
bs/musicblocks/pulls/aviral243
Best,
Devin
On Mon, 2020-05-18 at 06:17 +0530, Aviral Gangwar wrote:
> Hello all,
> 
> This is a weekly report of my work for the time frame 9/05/20 -
> 15/05/20.
> 
> I had group meetings with Walter, Vaibhav, Sumit, Jaskirat and other
> Music Blocks participants, everyday except weekends. This week we
> finished first aspect of our ES6 porting. [var-->let conversion].
> Moving to arrow functions still remains.
> 
> Meetings mostly included general discussion related to non-trivial
> issues and clarification of certain doubts of student developers. 
> 
> Each group meeting was followed by a meeting with my mentor [ Devin
> Ulibarri ], except for Tuesday. 
> We made significant process on octave calculation issue, entirely
> revamping the whole process and are close to resolving it. This
> should be done by this the end of this week.
> 
> Apart from that, Devin discussed with me several movable and non-
> movable systems and a workflow for the summer.
> 
> Lastly, I started work, locally, on the implementation of the new
> scale degree block, mostly creating the basic pie menus as discussed
> during our meetings.
> 
> Objective for the upcoming week:
> 
> 1. Finish with the octave calculation issue.
> 2. More design thinking on the new scale degree block.
> 3. Resolve flat/sharp preference issue for some scales.
> 
> Thank You
> 
> Aviral Gangwar
> 
> 
> ___
> 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] Music Blocks v3.1 GSoC Bonding Period Release

[Walter Bender]

We pushed out a new release [1] based on the work done during the Bonding
Period. Thanks to all who contributed.

regards.

-walter

[1] https://github.com/sugarlabs/musicblocks/releases/tag/v3.1

-- 
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] Adding SVG for a new block in Music Blocks

[Aviral Gangwar]

Hello

I have been trying to add help for the nth modal pitch block and since
there was a help string and SVG unavailable, I've been trying to add one.

What is the procedure for generating the SVG for a macro?

I have added SVG's for blocks in the past but I usually had a workaround
using the code for a similar block. I tried using the blockArt but it is
only helpful for individual blocks.

I've attached the macro that needs to be generated.

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

Re: [Sugar-devel] Adding SVG for a new block in Music Blocks

[Walter Bender]

Export using the Save Block Artwork option.

On Mon, May 25, 2020 at 12:17 PM Aviral Gangwar 
wrote:

> Hello
>
> I have been trying to add help for the nth modal pitch block and since
> there was a help string and SVG unavailable, I've been trying to add one.
>
> What is the procedure for generating the SVG for a macro?
>
> I have added SVG's for blocks in the past but I usually had a workaround
> using the code for a similar block. I tried using the blockArt but it is
> only helpful for individual blocks.
>
> I've attached the macro that needs to be generated.
>
> Thanks
> Aviral
>
>

-- 
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] Music Blocks v3.1 GSoC Bonding Period Release

[Sumit Srivastava]

Congratulations!

On Mon, May 25, 2020, 7:31 PM Walter Bender  wrote:

> We pushed out a new release [1] based on the work done during the Bonding
> Period. Thanks to all who contributed.
>
> regards.
>
> -walter
>
> [1] https://github.com/sugarlabs/musicblocks/releases/tag/v3.1
>
> --
> 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] Situation update

[James Cameron]

Welcome back, Anindya.

I'm very familiar with electricity transmission networks.  After a
severe storm, replacement components are taken from storage and put in
service, and new component orders made.  The delay you experienced is
expected.

Be cautious about using Projects feature.  I've used it too.  It is
good for organising work, but you must take the time to measure
engagement by others, otherwise it creates an isolation.  Once the
isolation is identified, you have to do two things each day (a) update
the project, and (b) tell people you updated the project.

On Mon, May 25, 2020 at 06:15:41PM +0530, Anindya Kundu wrote:
> Hello,
> 
> Thanks for understanding my situation. Electricity has finally been restored
> and things are recovering. There is an issue with the broadband which will
> hopefully be fixed in a couple of days, now that the electricity is back.
> 
> I joined our daily meeting today from my phone, barely getting in before it
> ended. I had a quick chat and informed about my state. I'll be meeting 
> tomorrow
> half an hour early with Walter, before out group gathering.
> 
> Meanwhile, I'll get back to work by tonight. I'll start with some experiment
> code I was trying out, to eventually get on with the Note class we were
> discussing.
> 
> I've previously mentioned that I'll be working on a branch wip-note-class in 
> [1]my fork of Music Blocks. I was exploring the 'Projects' feature on GitHub,
> and found that it can be useful. I've created a project in the said repository
> and I'll be updating my progress there.
> 
> Regards.
> 
> Anindya Kundu
> 
> References:
> 
> [1] https://github.com/meganindya/musicblocks

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

[Sugar-devel] Sugarizer game activity pack meeting

[prakash ujjwal]

I and my mentor Ashish had a meeting on sugarizer game activity pack at
3:00 PM IST on 23th May.

We had discussion about the progress of the demo of tangram activity and
the evaluation algorithm and it's different approaches.


   1. Previous week task: to create a small demo for tangram activity.
   2. problems faced in previous week tasks: faced problem in evaluation
   algorithm, snapping algorithm
   3. Tasks in upcoming week: add a feature to flip parallelogram, complete
   evaluation algorithm, finalize UI for activities

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

Re: [Sugar-devel] Situation update

[Anindya Kundu]

Dear James,

Thanks for the feedback. In the last meeting before the interruption I
briefly informed that I was exploring the feature.

Walter has been walking me through some of the important code, and I'm
experimenting to figure out how to create the required class structures. I
feel there will be a lot of moving parts, and so keeping a dynamic log is
crucial for us to synchronize along, and keeping it close to the code feels
helpful.

I'll bring this up with him in today's meeting and push an update. Since
we're having a brief group meeting every weekday, I think communication
should be fine.

On Tue, 26 May 2020, 2:47 am James Cameron,  wrote:

> Welcome back, Anindya.
>
> I'm very familiar with electricity transmission networks.  After a
> severe storm, replacement components are taken from storage and put in
> service, and new component orders made.  The delay you experienced is
> expected.
>
> Be cautious about using Projects feature.  I've used it too.  It is
> good for organising work, but you must take the time to measure
> engagement by others, otherwise it creates an isolation.  Once the
> isolation is identified, you have to do two things each day (a) update
> the project, and (b) tell people you updated the project.
>
> On Mon, May 25, 2020 at 06:15:41PM +0530, Anindya Kundu wrote:
> > Hello,
> >
> > Thanks for understanding my situation. Electricity has finally been
> restored
> > and things are recovering. There is an issue with the broadband which
> will
> > hopefully be fixed in a couple of days, now that the electricity is back.
> >
> > I joined our daily meeting today from my phone, barely getting in before
> it
> > ended. I had a quick chat and informed about my state. I'll be meeting
> tomorrow
> > half an hour early with Walter, before out group gathering.
> >
> > Meanwhile, I'll get back to work by tonight. I'll start with some
> experiment
> > code I was trying out, to eventually get on with the Note class we were
> > discussing.
> >
> > I've previously mentioned that I'll be working on a branch
> wip-note-class in
> > [1]my fork of Music Blocks. I was exploring the 'Projects' feature on
> GitHub,
> > and found that it can be useful. I've created a project in the said
> repository
> > and I'll be updating my progress there.
> >
> > Regards.
> >
> > Anindya Kundu
> >
> > References:
> >
> > [1] https://github.com/meganindya/musicblocks
>
> --
> 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] Situation update

[James Cameron]

Thanks, Anindya.

Yes, you will find communication fine within your group as a
consequence of meeting regularly.  That's good.

However, not everyone is in your meeting, and nor should we expect
them to be.

There is a risk of excluding community members by accident.  It
happens often with GSoC at Sugar Labs, because students are spending
seven hours a day, mentors at least one hour a day, and everyone else
some smaller time each day.

You can link to your GitHub Projects page in future updates;
https://github.com/meganindya/musicblocks/projects/1

On Tue, May 26, 2020 at 09:00:03AM +0530, Anindya Kundu wrote:
> Dear James,
> 
> Thanks for the feedback. In the last meeting before the interruption I briefly
> informed that I was exploring the feature.
> 
> Walter has been walking me through some of the important code, and I'm
> experimenting to figure out how to create the required class structures. I 
> feel
> there will be a lot of moving parts, and so keeping a dynamic log is crucial
> for us to synchronize along, and keeping it close to the code feels helpful.
> 
> I'll bring this up with him in today's meeting and push an update. Since we're
> having a brief group meeting every weekday, I think communication should be
> fine.
> 
> On Tue, 26 May 2020, 2:47 am James Cameron, <[1]qu...@laptop.org> wrote:
> 
> Welcome back, Anindya.
> 
> I'm very familiar with electricity transmission networks.  After a
> severe storm, replacement components are taken from storage and put in
> service, and new component orders made.  The delay you experienced is
> expected.
> 
> Be cautious about using Projects feature.  I've used it too.  It is
> good for organising work, but you must take the time to measure
> engagement by others, otherwise it creates an isolation.  Once the
> isolation is identified, you have to do two things each day (a) update
> the project, and (b) tell people you updated the project.
> 
> On Mon, May 25, 2020 at 06:15:41PM +0530, Anindya Kundu wrote:
> > Hello,
> >
> > Thanks for understanding my situation. Electricity has finally been
> restored
> > and things are recovering. There is an issue with the broadband which
> will
> > hopefully be fixed in a couple of days, now that the electricity is 
> back.
> >
> > I joined our daily meeting today from my phone, barely getting in before
> it
> > ended. I had a quick chat and informed about my state. I'll be meeting
> tomorrow
> > half an hour early with Walter, before out group gathering.
> >
> > Meanwhile, I'll get back to work by tonight. I'll start with some
> experiment
> > code I was trying out, to eventually get on with the Note class we were
> > discussing.
> >
> > I've previously mentioned that I'll be working on a branch 
> wip-note-class
> in 
> > [1]my fork of Music Blocks. I was exploring the 'Projects' feature on
> GitHub,
> > and found that it can be useful. I've created a project in the said
> repository
> > and I'll be updating my progress there.
> >
> > Regards.
> >
> >     Anindya Kundu
> >
> > References:
> >
> > [1] [2]https://github.com/meganindya/musicblocks
> 
> --
> James Cameron
> [3]http://quozl.netrek.org/
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] https://github.com/meganindya/musicblocks
> [3] 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] Situation update

[Anindya Kundu]

Sure. I'll keep that in mind.



On Tue, 26 May 2020 at 09:26, James Cameron  wrote:

> Thanks, Anindya.
>
> Yes, you will find communication fine within your group as a
> consequence of meeting regularly.  That's good.
>
> However, not everyone is in your meeting, and nor should we expect
> them to be.
>
> There is a risk of excluding community members by accident.  It
> happens often with GSoC at Sugar Labs, because students are spending
> seven hours a day, mentors at least one hour a day, and everyone else
> some smaller time each day.
>
> You can link to your GitHub Projects page in future updates;
> https://github.com/meganindya/musicblocks/projects/1
>
> On Tue, May 26, 2020 at 09:00:03AM +0530, Anindya Kundu wrote:
> > Dear James,
> >
> > Thanks for the feedback. In the last meeting before the interruption I
> briefly
> > informed that I was exploring the feature.
> >
> > Walter has been walking me through some of the important code, and I'm
> > experimenting to figure out how to create the required class structures.
> I feel
> > there will be a lot of moving parts, and so keeping a dynamic log is
> crucial
> > for us to synchronize along, and keeping it close to the code feels
> helpful.
> >
> > I'll bring this up with him in today's meeting and push an update. Since
> we're
> > having a brief group meeting every weekday, I think communication should
> be
> > fine.
> >
> > On Tue, 26 May 2020, 2:47 am James Cameron, <[1]qu...@laptop.org> wrote:
> >
> > Welcome back, Anindya.
> >
> > I'm very familiar with electricity transmission networks.  After a
> > severe storm, replacement components are taken from storage and put
> in
> > service, and new component orders made.  The delay you experienced is
> > expected.
> >
> > Be cautious about using Projects feature.  I've used it too.  It is
> > good for organising work, but you must take the time to measure
> > engagement by others, otherwise it creates an isolation.  Once the
> > isolation is identified, you have to do two things each day (a)
> update
> > the project, and (b) tell people you updated the project.
> >
> > On Mon, May 25, 2020 at 06:15:41PM +0530, Anindya Kundu wrote:
> > > Hello,
> > >
> > > Thanks for understanding my situation. Electricity has finally been
> > restored
> > > and things are recovering. There is an issue with the broadband
> which
> > will
> > > hopefully be fixed in a couple of days, now that the
> electricity is back.
> > >
> > > I joined our daily meeting today from my phone, barely getting in
> before
> > it
> > > ended. I had a quick chat and informed about my state. I'll be
> meeting
> > tomorrow
> > > half an hour early with Walter, before out group gathering.
> > >
> > > Meanwhile, I'll get back to work by tonight. I'll start with some
> > experiment
> > > code I was trying out, to eventually get on with the Note class
> we were
> > > discussing.
> > >
> > > I've previously mentioned that I'll be working on a branch
> wip-note-class
> > in
> > > [1]my fork of Music Blocks. I was exploring the 'Projects' feature
> on
> > GitHub,
> > > and found that it can be useful. I've created a project in the said
> > repository
> > > and I'll be updating my progress there.
> > >
> > > Regards.
> > >
> > > Anindya Kundu
> > >
> > > References:
> > >
> > > [1] [2]https://github.com/meganindya/musicblocks
> >
> > --
> > James Cameron
> > [3]http://quozl.netrek.org/
> >
> > References:
> >
> > [1] mailto:qu...@laptop.org
> > [2] https://github.com/meganindya/musicblocks
> > [3] 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] Help in modifying sugar for testing

[James Cameron]

Yes, that's a problem I've seen before, and I reproduced it just now.

Sugar Live Build includes /usr/src/sugar which is a clone of the Sugar
repository, not a tarball.  When autogen, make and make install are
run, the files are placed in site-packages, not dist-packages.

site-packages is logically correct, but Debian does not look at
site-packages when it runs Sugar.

During build, we have a special step after make install;
https://github.com/sugarlabs/sugar-live-build/blob/master/src/config/hooks/normal/0900-sugar.hook.chroot#L42

So in addition to make install, you should also do;

rm -rf /usr/lib/python3.7/dist-packages/jarabe/
mv /usr/lib/python3.7/site-packages/jarabe /usr/lib/python3.7/dist-packages/

I've no explanation for "make: nothing to be done for 'main.py", the
message makes no sense to me.  I don't see it when I test.

On Tue, May 26, 2020 at 06:32:52AM +0200, su...@radii.dev wrote:
> Based on [1]https://github.com/sugarlabs/sugar/blob/master/docs/
> development-environment.md#sugar-live-build I am making changes to:
> /usr/src/sugar/src/jarabe/main.py
> and than
> # make install
> But nothing changes. I get message in the end
> "make: nothing to be done for 'main.py"
> Any help?
> 
> Regards,
> Manish
> 
> References:
> 
> [1] 
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md#sugar-live-build

> ___
> 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] Help in modifying sugar for testing

[Saumya Mishra]

Thanks James, This was the problem I was also facing while testing sugar
live build, My changes were not reflecting, Hope that helps.



On Tue, May 26, 2020 at 10:50 AM James Cameron  wrote:

> Yes, that's a problem I've seen before, and I reproduced it just now.
>
> Sugar Live Build includes /usr/src/sugar which is a clone of the Sugar
> repository, not a tarball.  When autogen, make and make install are
> run, the files are placed in site-packages, not dist-packages.
>
> site-packages is logically correct, but Debian does not look at
> site-packages when it runs Sugar.
>
> During build, we have a special step after make install;
>
> https://github.com/sugarlabs/sugar-live-build/blob/master/src/config/hooks/normal/0900-sugar.hook.chroot#L42
>
> So in addition to make install, you should also do;
>
> rm -rf /usr/lib/python3.7/dist-packages/jarabe/
> mv /usr/lib/python3.7/site-packages/jarabe
> /usr/lib/python3.7/dist-packages/
>
> I've no explanation for "make: nothing to be done for 'main.py", the
> message makes no sense to me.  I don't see it when I test.
>
> On Tue, May 26, 2020 at 06:32:52AM +0200, su...@radii.dev wrote:
> > Based on [1]https://github.com/sugarlabs/sugar/blob/master/docs/
> > development-environment.md#sugar-live-build I am making changes to:
> > /usr/src/sugar/src/jarabe/main.py
> > and than
> > # make install
> > But nothing changes. I get message in the end
> > "make: nothing to be done for 'main.py"
> > Any help?
> >
> > Regards,
> > Manish
> >
> > References:
> >
> > [1]
> https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md#sugar-live-build
>
> > ___
> > 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