[Sugar-devel] e1000 driver not working on my custom spins
Hello Sebastian, I'm putting together custom spins with pre set activities for GPA. It seems the recent spin I made either doesn't have the ethernet drivers or they are failing to initialize. I am using http://git.sugarlabs.org/projects/soas/repos/mainline/trees/strawberry to build the spins. I noticed that my latest spin has a new kernel pushed from the fedora updates site which maybe the source of the issue. Caroline says that the Strawberry iso (http://download.sugarlabs.org/soas/releases/soas-1-strawberry.iso) works just fine. I was wondering if you have any ideas about the issue. I'm almost certain it's the new kernel but there maybe something else that I'm not aware of. Thanks in advance. Best, Hamilton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] how to pick older version of an activity for a custom sugar spin
Hello, I am creating custom spins from strawberry branch with sugar 0.84 and I have modified the kickstart file (soas-sugar.ks) to get the latest versions of the activites from activities.sugarlabs.org. The problem is that some of the latest activities are no longer compatible with 0.84 and now work with 0.86. Is there a way for me to tell the kickstart file to get to 0.84 compatible version of the activity instead of the latest version of the activity? Thanks in advance for any help. Best, Hamilton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] how to pick older version of an activity for a custom sugar spin
Hi Aleksey, Thanks for pointing this out. This change eluded me as I am still using the code tagged strawberry but this looks easy enough to backport and include into the kickstart files I am using. Thanks ! Hamilton For now, SugarPlatform version is hardcoded in .ks, see http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/soas-aslo-and-content.ks#line61 so, you just need to change it to 0.84 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Request Feature Freeze Exception for ticket #916 to allow sugar on non-xo hardware to register with a schoolserver
Hello Bill, If my vote counts, I'll +1 as well. In the XO case, it should work the same as before. In the non-XO, it tries to do something useful rather then nothing. Thanks ! :-) However, I have some concerns/questions: 1. In the non-XO case, why do you replace the files which contain previously generated uuid/sn/backup_url rather then using them as is? I'm not sure I understand. On non-XO hardware, there is no UUID and SN to begin with, both have to be generated when Register is clicked. The backup_url is the registration server or in the case of non-xo hardware the jabber server. 2. The XO always uses a static schoolserver URL to register while a non-XO will use it's jabber server instead. For minimum impact on current XO usage, I understand this. Going forward, I think this inconsistent behavior will be a problem. I believe there are already deployments using both XO's and SoaS based systems. At a minimum, I would suggest creating a bug ticket for this inconsistency so it can be dealt with correctly in a later release. Yeah I suppose it is a problem in cases where the jabber server and registration server are not the same machine. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Request Feature Freeze Exception for ticket #916 to allow sugar on non-xo hardware to register with a schoolserver
Hello, I would like to kindly request for an exception to the feature freeze currently in place to allow the inclusion of a patch that will enable sugar on non-xo hardware to register with a schoolserver. The relevant ticket with details is at http://dev.sugarlabs.org/ticket/916 The patch is register-non-xo-with-xs.patch which can be downloaded directly from http://dev.sugarlabs.org/attachment/ticket/916/register-non-xo-with-xs.patch Thank you very much. Best, Hamilton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: [Bugs] #916 NORM: Allow SoaS to register with an XS server
Hi Tomeu, Although the modifications are specific to supporting registration with SoaS, I tried to make sure that they don't break the default behavior when Sugar is installed on an XO. If there are no objections I'm in favor of moving it to upstream Sugar as the modifications could be useful when sugar is installed on non-XO hardware or as a livecd. Please advise. I'll update the ticket if there are no objections to making these modifications for upstream Sugar. Many thanks ! Hamilton On Tue, 2009-08-18 at 12:04 +0200, Tomeu Vizoso wrote: Hi, is Hamilton or SolutionsGrove interested in having this in upstream Sugar? Or really want to maintain it in SoaS as the ticket says? I don't see why this wouldn't work for other Sugar distros. Thanks, Tomeu -- Forwarded message -- From: SugarLabs Bugs bugtracker-nore...@sugarlabs.org Date: Mon, Jun 1, 2009 at 16:53 Subject: [Bugs] #916 NORM: Allow SoaS to register with an XS server To: Cc: b...@lists.sugarlabs.org #916: Allow SoaS to register with an XS server -+-- Reporter: hamiltonchua | Owner: sdz Type: enhancement | Status: new Priority: Normal| Milestone: Unspecified by Release Team Component: SoaS |Version: Unspecified Severity: Unspecified | Keywords: Distribution: Unspecified | Status_field: Unconfirmed -+-- We would like to allow an SoaS to register with an XS. I have attached here diff files for schoolesrver.py and ds-backup.py that will hopefully allow this. The modifications should still allow these scripts to work normally when installed in an XO. Attached here are the diffs against the original files and the modified python scripts. This is for review. -- Ticket URL: http://dev.sugarlabs.org/ticket/916 Sugar Labs http://sugarlabs.org/ Sugar Labs bug tracking system ___ Bugs mailing list b...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/bugs ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore for Sugar on a Stick
Hello Tomeu, The modifications are intended for SoaS only but I'm programming them in such a way that they should not break if Sugar is running on SoaS. Although I already have patches in the form of diffs, they were not created using 'git format-patch. I've read the code review procedures and will get to work making the preparations. Thanks, Ham On Fri, 2009-08-07 at 10:39 +0200, Tomeu Vizoso wrote: On Thu, Aug 6, 2009 at 15:29, Caroline Meekscarol...@solutiongrove.com wrote: This email is especially for Miguel Salazar and the Chiapas deployment. The code for backup and restore of Sugar Sticks using the XS is awaiting code review, if you can please test it. http://dev.sugarlabs.org/ticket/916 http://dev.sugarlabs.org/ticket/1124 Is it intended to be integrated in Sugar? Or only for SoaS? If it's for Sugar, then please follow the review process outlined here: http://wiki.sugarlabs.org/go/Development_Team/CodeReview Thanks, Tomeu Thanks, Caroline -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ 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] Backup and Restore for Sugar on a Stick
but I'm programming them in such a way that they should not break if Sugar is running on SoaS. I'm confused, did you meant to say not break if _not_ running on SoaS? Haha, yes sorry. I meant that it should not break when running in an OLPC Laptop :-) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Ticket for modifications to schoolserver.py and ds-backup.py
Tomeu, Thanks. I created a ticket and uploaded the diffs and the modified files themselves. I hope I did it right :-) Thanks, Hamilton ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] modifications to schoolserver.py and ds-backup.py
Hello, I have been testing SoaS and implemented a couple of modificaitons to schoolserver.py and ds-backup.py that basically .. - enable an SoaS to register with an XS - read the registration info in order to allow backup/restore with the XS the SoaS is registered with I would like to kindly ask how I can get the modifications reviewed by the group and into the release build. Should I open a ticket with the files attached ? Thanks, Hamilton Chua ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Server-devel] backup : problem opening /library/users/XXXX/datastore-xxxxx/store
Martin, Good news. I had a chance to test it today and it looks like the Moodle UI is picking up on the back ups now. I'll be doing a couple of tests over the course of the next few days. I'll be sure to let you know if we encounter problems. Thanks you so much for quickly updating the moodle backup ui. Best, Hamilton On Thu, May 7, 2009 at 8:11 AM, Hamilton Chua hamilton.c...@gmail.com wrote: Martin, Thanks, sorry I don't have a lot of activities to backup yet on my test SoaS. I'll give this a go today and report back the results here. Best, Hamilton On Wed, 2009-05-06 at 19:23 +0200, Martin Langhoff wrote: On Tue, May 5, 2009 at 4:52 PM, Martin Langhoff martin.langh...@gmail.com wrote: Let's keep this on the list. Is that from a recent SoaS? The datastore storage format has changed then, and we need to add support to Moodle for it. More work! :-p Done - not tested much -- the zipfile you've given me didn't have much data. http://dev.laptop.org/git/users/martin/moodle.git/commit/?h=mdl19-xsid=5f522dbef1878284d15ae2ef0872c8dd5caa1953 So I need your help in reporting whether it works well for your SoaS clients. I assume you're already using my moodle branch, so a mere git pull will get you the right code... ;-) Note: It won't list metadata-only entries. If there's no 'data' file, it's not listed. cheers, m ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Server-devel] backup : problem opening /library/users/XXXX/datastore-xxxxx/store
Martin, Thanks, sorry I don't have a lot of activities to backup yet on my test SoaS. I'll give this a go today and report back the results here. Best, Hamilton On Wed, 2009-05-06 at 19:23 +0200, Martin Langhoff wrote: On Tue, May 5, 2009 at 4:52 PM, Martin Langhoff martin.langh...@gmail.com wrote: Let's keep this on the list. Is that from a recent SoaS? The datastore storage format has changed then, and we need to add support to Moodle for it. More work! :-p Done - not tested much -- the zipfile you've given me didn't have much data. http://dev.laptop.org/git/users/martin/moodle.git/commit/?h=mdl19-xsid=5f522dbef1878284d15ae2ef0872c8dd5caa1953 So I need your help in reporting whether it works well for your SoaS clients. I assume you're already using my moodle branch, so a mere git pull will get you the right code... ;-) Note: It won't list metadata-only entries. If there's no 'data' file, it's not listed. cheers, m signature.asc Description: This is a digitally signed message part ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Auto-authentication for Browse -
Hello Everyone, My name is Hamilton Chua and I am new to these lists and even newer to sugar development and the olpc in general so please do forgive me if the questions I am about to ask have been asked and answered before. I am using a development snapshot of Sugar on a Stick (SoaS) and XS (0.5.1) on Virtualbox 2.1.4. So here are my questions : 1) It seems registration does not work on SoaS because it lacks the info that you normally have on an OLPC laptop in order to successfully register with an XS server. I would like to ask what the significance, if any, of registration. In the snapshot I have, it seems that I can set the jabber server on the control panel and it seemed that I was all set. 2) For the XS Cookie (Plan C here) to work, do I need to register sugar with an XS server ? 3) Are there plans to make registration work for Sugar installed on hardware other than an OLPC ? Thanks for much in advance. Best, Hamilton -- View this message in context: http://n2.nabble.com/Auto-authentication-for-Browse---tp2204988p2383223.html Sent from the Sugar Development mailing list archive at Nabble.com. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Auto-authentication for Browse -
Hello Everyone, My name is Hamilton Chua and I am new to these lists and even newer to sugar development and the olpc in general so please do forgive me if the questions I am about to ask have been asked and answered before. I am using a development snapshot of Sugar on a Stick (SoaS) and XS (0.5.1) on Virtualbox 2.1.4. So here are my questions : 1) It seems registration does not work on SoaS because it lacks the info that you normally have on an OLPC laptop in order to successfully register with an XS server. I would like to ask what the significance, if any, of registration. In the snapshot I have, it seems that I can set the jabber server on the control panel and it seemed that I was all set. 2) For the XS Cookie (Plan C here) to work, do I need to register sugar with an XS server ? 3) Are there plans to make registration work for Sugar installed on hardware other than an OLPC ? Thanks very much in advance. Best, Hamilton -- View this message in context: http://n2.nabble.com/Auto-authentication-for-Browse---tp2204988p2383357.html Sent from the Sugar Development mailing list archive at Nabble.com. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
