[Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/76 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed GConf-dbus build sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar-Developers meeting REMINDER (12 February, 2009 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
Hi, AGENDA: This Friday is 0.84 Release Candidate 1 [1] - are we in good shape, what is left - blockers, what needs focusing, where can people help TODO list: update and add possible items [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule See you there, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Auto-authentication for Browse -
Martin Langhoff wrote: > On Wed, Feb 11, 2009 at 11:18 PM, Martin Langhoff > wrote: >> On Wed, Feb 11, 2009 at 10:25 PM, Andrés Ambrois >>> I might be missing something, but you're storing the laptop serial number >>> instead of the pubkey inside the cookie (unless /ofw/mfg-data/SN doesnt >>> stores a pubkey), which was the original plan C. >> Good point. I didn't refer back to the spec. I think SN and the pubkey >> are roughly equal in this situation >> >> - the XS has both >> - if a 3rd party sniffs the cookie from the ether... is either of >> them more damaging than the other? > > Having slept on this, I think it's better to use a hash of the pubkey. > The SN known by other XOs without sniffing, as all the XMPP traffic > has it as your username/jid. Right and the SN is XO specific - thought we want to use this mechanism as well in non XO land. Will look at the new patch now, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] buildbot failure in Sugar Labs Buildbot on sugar-base-Ubuntu804
On Wed, Feb 11, 2009 at 23:59, wrote: > BUILD FAILED: failed failed slave lost *cringe* The history of cane sugar is intertwined with slavery... This is a rather unfortunate juxtaposition. Anyway, back to the bits and bytes Morgan ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
Martin Langhoff wrote: > On Thu, Feb 12, 2009 at 6:47 PM, wrote: >> When starting up, call seed_xs_cookie() to > > Hi Simon, > > Hoping for some review :-) . Do you think this patch can make it into > the sucrose-0.82 branch? With a tad of elbow grease, it also applies > on top of master. > > The reason I ask for it on the 0.82 branch is that > > - It's low low risk -- in fact, the interesting ops are wrapped in a > try/except block so a failure won't stop Browse from starting up. > > - It allows me to do a XS 0.5.2 or 0.6 relatively soon that > integrates smoothly with the XO 0.8.2.x series. Deployments can ensure > that they have an updated Browse.xo... > > cheers, Is your main request to get it into 0.82.1? Is this only a temporary solution and we get something else later? Thanks, Simon PS: I am not a security person - so for this discussion of security impact you are better of asking someone else - I can only comment on the general layout of the patch. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Thu, Feb 12, 2009 at 11:32 PM, Simon Schampijer wrote: > Is your main request to get it into 0.82.1? Is this only a temporary > solution and we get something else later? I think it'll be our "current" solution for a while... both branches? > PS: I am not a security person - so for this discussion of security impact > you are better of asking someone else - I can only comment on the general > layout of the patch. The main 'right way' in security terms is following the 'Plan A' that I outlined in my other email. It is a ton of work and some parts require infra in other tools that I'm not sure is ready... so as soon as a security expert turns up, we'll charge him/her with implementing it :-) cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
Martin Langhoff wrote: > On Thu, Feb 12, 2009 at 11:32 PM, Simon Schampijer > wrote: >> Is your main request to get it into 0.82.1? Is this only a temporary >> solution and we get something else later? > > I think it'll be our "current" solution for a while... both branches? > >> PS: I am not a security person - so for this discussion of security impact >> you are better of asking someone else - I can only comment on the general >> layout of the patch. > > The main 'right way' in security terms is following the 'Plan A' that > I outlined in my other email. _ Plan A - HTTPS to the rescue Use HTTPS and client certs. On the Browse.xo, either create a client cert at first boot or derive one from the SSL priv key we already have. Lacking a PKI ( in this case XSs will have self-signed certs, and the whole network will often be offline), we will need to grab the cert from the XS at registration time so we can whitelist it for Browse.xo. This is safer, allows us to upgrade later to always using HTTPS if desired. It has downsides however - we'll have to change the registration protocol, and deal with up/downwards compat issues. - https is significantly more costly in terms of CPU on the XS Just to understand better. Is the main issue that we have to change the protocol - or are you more worried about the CPU cost? So as I understand the process: At registration time with the XS the cert is created and transferred to the client. Probably stored than in the profile. Browse does than integrate it when it starts. The cert integration itself in Browse should not be hard. Thanks for clearing up, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Thu, Feb 12, 2009 at 11:54 PM, Simon Schampijer wrote: > Plan A - HTTPS to the rescue > Just to understand better. > > Is the main issue that we have to change the protocol - or are you more > worried about the CPU cost? Both. And also HTTPS network load, as HTTPS is a lot less cache-friendly. > So as I understand the process: At registration time with the XS the cert is > created and transferred to the client. Probably stored than in the profile. > Browse does than integrate it when it starts. The cert integration itself in > Browse should not be hard. You are right, it shouldn't be hard if you "seed" it in the same way my patch is seeding the cookies. Carol pointed out another alternative a couple of emails ago. Seems to sidestep the registration rework, but may be complex to implement. But I'm more than happy with my simple Plan C :-) - which is about as safe as gmail over http as most people use everyday! cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
Martin Langhoff wrote: > On Thu, Feb 12, 2009 at 11:54 PM, Simon Schampijer > wrote: >> Plan A - HTTPS to the rescue >> Just to understand better. >> >> Is the main issue that we have to change the protocol - or are you more >> worried about the CPU cost? > > Both. And also HTTPS network load, as HTTPS is a lot less cache-friendly. > >> So as I understand the process: At registration time with the XS the cert is >> created and transferred to the client. Probably stored than in the profile. >> Browse does than integrate it when it starts. The cert integration itself in >> Browse should not be hard. > > You are right, it shouldn't be hard if you "seed" it in the same way > my patch is seeding the cookies. > > Carol pointed out another alternative a couple of emails ago. Seems to > sidestep the registration rework, but may be complex to implement. > > But I'm more than happy with my simple Plan C :-) - which is about as > safe as gmail over http as most people use everyday! As save as having your email indexed by the provider... :) When thinking about it a bit more - the big plus with your approach that it's only affects Browse - code wise, which is when back porting to 0.82 a big plus, actually maybe the only way. Cheers, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Fri, Feb 13, 2009 at 12:19 AM, Simon Schampijer wrote: > When thinking about it a bit more - the big plus with your approach that > it's only affects Browse - code wise, which is when back porting to 0.82 a > big plus, actually maybe the only way. Bingo! I think you're starting to read my mind... m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] logging irc setup
well, u can find it here: http://www.nubae.com/logs/sugar There are various curious commands the bot can help with based on google stuff the list is as follows: [control command is @ and not !] example: @google define:sugarlabs # !google [.google.country.code] [define:|spell:|movie:] # # <1+1> <1 cm in ft> # ## # !images [.google.country.code]# # !groups [.google.country.code]# # !news [.google.country.code] # # !local [.google.country.code] near# # !book [.google.country.code] # # !video [.google.country.code] # # !scholar [.google.country.code] # # !fight vs# # !youtube [.google.country.code] # # !trans reg...@region # # !gamespot # # !gamefaqs in # # !blog [.google.country.code] # # !ebay [.ebay.country.code]# # !ebayfight vs# # !wikipedia [.2-digit-country-code] [#subtag] # # !wikimedia [.www.wikisite.org[/wiki]] [#subtag] # !locate # # !review [@ ] # # !torrent # # !top# # !popular# # !dailymotion # # !ign # # !myspace # # !trends [.google.country.code] # ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar.profile.jabber_registered and sugar.profile.is_registered() are deprecated?
Martin Langhoff wrote:
> On Wed, Feb 11, 2009 at 11:39 PM, Morgan Collett
> wrote:
>> I mean if we need to reinstate the is_registered tracking, or
>> something like that... I'm not sure of the status of the registration
>> feature in 0.84 - all I can say authoritatively is that from a jabber
>> server connection perspective, PS always automatically tries to
>> reregister if necessary. I don't know off hand what else the register
>> function for the XS does in terms of state in Sugar.
>
> Registration in 0.82 contacts the XS via XMLRPC, passing its SN, nick
> and pubkey. In return, it gets a backup server "url" (u...@fqdn) and a
> jabber server fqdn.
>
> I hope it still works, without that quite a few things break...
>
>
>
> m
It still does work :) The backup_url is in gconf
('/desktop/sugar/backup_url') now in 0.84. Once we have an url - we use
this as a way to know we have been registered. You can un-register using
the cp command line tool.
So the code in browse should for 0.82 use the old way of checking if we
are registered and for the master code check the gconf value of
'/desktop/sugar/backup_url'.
Make sense?
Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] consequences of re-registering with XS
Hi, As I noted here: http://wiki.laptop.org/go/Deployment_wishlist#Delete_registration_info we are in a sticky situation where a load of XOs are registered to one XS, which no longer exists. We want to register them to a new one, and we are having to manually go to each laptop and modify the sugar config file to allow us to register again. To avoid this situation in future (should we ever run into it again, fingers crossed we won't), we are considering a small modification to the paraguay OS build which makes the "Discard network history" button also clear the XS registration information (by deleting the server.backup1 line from sugar config). This code modification can be done with a single sed call, since there is already an unused sugar function to clear registration info. Of course, this means that the users (children) can now trivially lose their registration data. Are there any undesirable consequences of this that I am missing? For example, what happens if a user deletes the registration data and then re-registers with the same server.. does the XS cope with that happily? Any other points I should keep in mind, or any other options to avoiding this small nightmare in future? Thanks, Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] joyride, staging builds, sugar releases
Sorry to insist on this, but I have not got it quite yet. Joyrides => obsolete (even though the builder script keeps churning them out and telling the olpc devel list). staging => what are these? Obsolete too? release builds => only last week there was a release build announced on the olpc devel list. Are these obsolete too? And another thing: olpc-update is not to be used anymore, or is it still on? Any clarification greatly appreciated! Victor ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] joyride, staging builds, sugar releases
2009/2/12 victor : > Sorry to insist on this, but I have not got it quite yet. > > Joyrides => obsolete (even though the builder script keeps > churning them out and telling the olpc devel list). Obsolete, but not really obsoleted by anything usable *yet*. > staging => what are these? Obsolete too? This is where we are staging changes to be used in v8.2.1. > release builds => only last week there was a release build > announced on the olpc devel list. Are these obsolete too? You are referring to the v8.2.1 candidate release? This is not obsolete, it is being pushed to various deployments. > And another thing: olpc-update is not to be used anymore, > or is it still on? It is still on for v8.2. It's future is perhaps a bit uncertain (maybe once we have working pure-Fedora builds it won't be active for a while, but it possibly will be resuscitated or replaced in future). I think the real question is: who are you developing for? v8.2 is pretty frozen and slow moving - the upcoming 8.2.1 includes only a handful of fixes (plus a couple of features for much improved deployability, that do not really affect the user experience). It will be adopted by deployments over the next few months, and will continue to be rolled out for probably a long time (e.g. Uruguay still using build 656 even though development terminated a long time ago). There may be an 8.2.2 with a similar collection of small fixes, depending on demand from deployments. If you want to develop for these deployments on this timeline, then you should work on top of 8.2 (sugar-0.82) and limit yourself to activity-level changes only. As for the future, the hope is that we will have a similarly-functional OS that includes the latest version of sugar asap. OLPC is working with Fedora on this, and while I suspect that the end result will be pushed as a "reference OS" by OLPC, there are also some other efforts which I think OLPC would probably be happy to flash onto machines at the factory (I can't speak officially, I am only a volunteer right now), including debXO, and a possibility of the community taking the 8.2 OS release and adding sugar-0.84 and some other things as an intermediate step before the pure-Fedora builds are suitable replacements. However, I personally think that all of these efforts are 6-12 months away (at least) from producing something adoptable by deployments. If you want to develop for the-future-with-unknown-timeframe, then you should work upstream at sugarlabs for sugar-0.84. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Soas meeting tomorrow, 17 UTC
Hello, we are going to have a Soas planning meeting tomorrow, at 17 UTC. Here is a quick agenda, feel free to add to it. * Build system setup and infrastructure. * Release announcement and changelogs. * Activities packaging. * Custom repositories. * File system layout and customization. * Testing. * TODO. If you would like to participate but the time does not work for you, please let us know and we will try to figure it out. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Soas meeting tomorrow, 17 UTC
On Thu, Feb 12, 2009 at 2:59 PM, Marco Pesenti Gritti wrote: > Hello, > > we are going to have a Soas planning meeting tomorrow, at 17 UTC. Here > is a quick agenda, feel free to add to it. Place is the usual one, irc.freenode.net #sugar-meeting Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Soas meeting tomorrow, 17 UTC
Let's also plan on a slobs meeting tomorrow (Friday) as well, 14 UTC on #sugar-meeting -walter On Thu, Feb 12, 2009 at 8:59 AM, Marco Pesenti Gritti wrote: > Hello, > > we are going to have a Soas planning meeting tomorrow, at 17 UTC. Here > is a quick agenda, feel free to add to it. > > * Build system setup and infrastructure. > * Release announcement and changelogs. > * Activities packaging. > * Custom repositories. > * File system layout and customization. > * Testing. > * TODO. > > If you would like to participate but the time does not work for you, > please let us know and we will try to figure it out. > > Marco > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > -- 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] FoodForce2 Storyboard
I guess there is some error with the attached file. I am unable to download it. -- Ankur 2009/2/11 Mohit Taneja > Hi All, > Please find attached the storyboard for the game FoodForce2. > > Looking forward to your feedback. > > Regards, > Mohit > > ___ > Devel mailing list > de...@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > -- Best regards, Ankur Verma Email : an...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Migrated] Design
I have just gotten done migrated the design section from wiki.lp.org to sl.org. DesignTeam/Designs DesignTeam/Designs/Activity Management DesignTeam/Designs/Control Panel DesignTeam/Designs/Creative commons DesignTeam/Designs/Frame DesignTeam/Designs/Frame/lang-es DesignTeam/Designs/Journal DesignTeam/Designs/Object Chooser DesignTeam/Designs/Toolbars DesignTeam/Designs/translations Will someone proof the pages and add the necessary links to the rest of the wiki? Bug to mark pages as migrated in on wiki.lt.org filed http://dev.laptop.org/ticket/9247 david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/77 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed GConf-dbus build sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
Should these perhaps be going to Fedora-olpc list as well? --g -- Got an XO that you're not using? Loan it to a needy developer! [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] On Thu, 12 Feb 2009, build...@sugarlabs.org wrote: > The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs > Buildbot. > Full details are available at: > http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/77 > > Buildbot URL: http://buildbot.sugarlabs.org/ > > Buildslave for this Build: Fedora10 > > Build Reason: > Build Source Stamp: HEAD > Blamelist: > > BUILD FAILED: failed GConf-dbus build > > sincerely, > -The Buildbot > > ___ > 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] [PATCH] webactivity: seed the XS cookie at startup
Martin, I want to understand what https traffic you are concerned will affect performance and caching. As far as I understand the need for https, it would only be used infrequently, when reauthenticating to the server. I.e..: 1. XO connects to Moodle without valid cookie and is redirected to https login. 2. https client cert is exchanged, and cookie of limited duration is planted). 3. XO connects to Moodle, cookie is valid, no redirection needed. There might be particular use cases where the data in transit needed to be protected against snooping, but a use case analysis needs to be done to identify these. I can't imagine that it would be needed in day-to-day classroom use by students. On Thu, Feb 12, 2009 at 6:55 AM, wrote: > On Fri, 13 Feb 2009, Martin Langhoff wrote: > > > On Thu, Feb 12, 2009 at 11:54 PM, Simon Schampijer > wrote: > >> Plan A - HTTPS to the rescue > >> Just to understand better. > >> > >> Is the main issue that we have to change the protocol - or are you more > >> worried about the CPU cost? > > > > Both. And also HTTPS network load, as HTTPS is a lot less cache-friendly. > > note that if the XS is acting as a proxy the cache issue can be addressed. > The XS can get a copy of the XO client cert at registration time, and with > it can decrypt the HTTPS traffic and cache the unencrypted version. this > is a lot of cpu, but it's on the XS not the XO, so it shouldn't be as bad > (and there are hardware SSL encryption cards available that can be put in > an XS for high-volume situations) > > it's not just a matter of downloading a package and installing it, but > it's not rocket science either. > > this would have the side effect of making the XS security even more > critical, but I think that it's already critical enough that this won't > really make much difference in how it's secured. > > David Lang > ___ > Devel mailing list > de...@lists.laptop.org > http://lists.laptop.org/listinfo/devel > -- "It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/78 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed GConf-dbus build sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
Added. You might need to white-list buildbot in the list moderation. david On Fri, Feb 13, 2009 at 11:56 AM, Greg Dekoenigsberg wrote: > > Should these perhaps be going to Fedora-olpc list as well? > > --g > > -- > Got an XO that you're not using? Loan it to a needy developer! > [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] > > On Thu, 12 Feb 2009, build...@sugarlabs.org wrote: > >> The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar >> Labs Buildbot. >> Full details are available at: >> http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/77 >> >> Buildbot URL: http://buildbot.sugarlabs.org/ >> >> Buildslave for this Build: Fedora10 >> >> Build Reason: >> Build Source Stamp: HEAD >> Blamelist: >> >> BUILD FAILED: failed GConf-dbus build >> >> sincerely, >> -The Buildbot >> >> ___ >> 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 mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
On Fri, 13 Feb 2009, David Farning wrote: > Added. > > You might need to white-list buildbot in the list moderation. Done, thanks. --g -- Got an XO that you're not using? Loan it to a needy developer! [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Notes on triage meeting
erikos ran an awesome meeting. My notes on what I think the purpose should be: First Goal. To go through all UNCONFIRMED bug reports and determine: * whether the bug report is a dupe. if so, close as Duplicate. * whether the bug report is missing key info. if so, ask questions in bug and set status to Needinfo. * whether the bug is from a previous release and has already been fixed. if so, close as Obsolete. * whether the bug is relatively minor. if so, set to block next release (right now 0.86) and set status to "new". * whether the bug is urgent. if so, set to block current release (right now 0.84) and set status to "new". Every bug should fit into one of these categories. How does that sound? Simple enough to get a good triage team off and running? --g -- Got an XO that you're not using? Loan it to a needy developer! [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Soas3 XO image quick report
Hi folks, Here's just a very quick run through of the Activities currently part of the SoaS3 XO image that Marco provided last week to help get some wider SoaS testing going: http://download.sugarlabs.org/soas/xoimages/ For the record, apart from some low level OS type issues (no camera, no sound, some odd Fedora login screen, no power saving, no screen brightness, some dodgy key bindings, and not much free nand space), it's a reasonable place to try out the new 8.3.x sugar changes and test your activities there. I have a non-critical unsecured XO here for testing, so I used copy- nand from the open firmware prompt to do a clean install of the images Marco provided: First the fail to launch: Speak-9 --> no useful logs, assume some core lib is missing Write-61 --> no useful logs, assume some core lib is missing Joke Machine-8 --> fails to launch complaining about 'No translation file found for domain:' Launch and casual usage was fine: Analyze-8 Calculate-28 CartoonBuilder-1 Chat-62 Etoys-97 FlipSticks-1 Image Viewer-5 Jigsaw Puzzle-5 Jukebox-6 Log-16 Memorize-29 Moon-8 Paint-23 Pippy-30 --> number of examples fail due to missing imports (pygame et al) Poll-21 Slider Puzzle-6 Terminal-16 Turtle Art-23 And finally: Browse-103 --> launches and browses fine, but e, boy was it beaten with the ugly custom theme stick, was this intended? ;-) Regards, --Gary P.S. Will be re-flashing this (and another) XO over to 8.2.1-800 tomorrow for some OLPC release candidate testing. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] FoodForce2 Storyboard
Sure, I would keep that thing in mind next time. Regards, Mohit On Fri, Feb 13, 2009 at 8:49 AM, James Cameron wrote: > The attachment was readable using xpdf. Nice work. You should seek > hosting for HTTP download of large attachments though, because many many > people are given the attachment who may not need it. > > -- > James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ > -- Joan Rivers - "Never floss with a stranger." ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] logging irc setup
Nice! Thanks! /Ties On Thu, Feb 12, 2009 at 5:46 PM, David Van Assche wrote: > well, u can find it here: http://www.nubae.com/logs/sugar > > There are various curious commands the bot can help with based on > google stuff the list is as follows: > > [control command is @ and not !] > example: @google define:sugarlabs > > # !google [.google.country.code] [define:|spell:|movie:] # > # <1+1> <1 cm in ft> # > ## > # !images [.google.country.code]# > # !groups [.google.country.code]# > # !news [.google.country.code] # > # !local [.google.country.code] near# > # !book [.google.country.code] # > # !video [.google.country.code] # > # !scholar [.google.country.code] # > # !fight vs# > # !youtube [.google.country.code] # > # !trans reg...@region # > # !gamespot # > # !gamefaqs in # > # !blog [.google.country.code] # > # !ebay [.ebay.country.code]# > # !ebayfight vs# > # !wikipedia [.2-digit-country-code] [#subtag] # > # !wikimedia [.www.wikisite.org[/wiki]] [#subtag] > # !locate # > # !review [@ ] # > # !torrent # > # !top# > # !popular# > # !dailymotion # > # !ign # > # !myspace # > # !trends [.google.country.code] # > ___ > 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] buildbot failure in Sugar Labs Buildbot on GConf-dbus-Fedora10
The Buildbot has detected a failed build of GConf-dbus-Fedora10 on Sugar Labs Buildbot. Full details are available at: http://buildbot.sugarlabs.org/builders/GConf-dbus-Fedora10/builds/79 Buildbot URL: http://buildbot.sugarlabs.org/ Buildslave for this Build: Fedora10 Build Reason: Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed GConf-dbus build sincerely, -The Buildbot ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
