Re: [Sugar-devel] Cannot sugar-jhbuild update
2009/2/8 Ties Stuij cjst...@gmail.com: On Sun, Feb 8, 2009 at 11:41 AM, Ties Stuij cjst...@gmail.com wrote: On Fri, Feb 6, 2009 at 5:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/6 Alex Holkner alex.holk...@gmail.com: File /home/alex/foreign/sugar-jhbuild/sjhbuild/main.py, line 31, in module import jhbuild.commands ImportError: No module named jhbuild.commands This happened to me some days ago, it was caused because the sugar-jhbuild/jhbuild submodule was pointing to the old location. Deleting that directory and updating sugar-jhbuild solved the issue. I think the problem here is that the path to the gnome git repo is wrong in the sugar-jhbuild script. It's git://git.gnome.org/preview/jhbuild, not git://git.gnome.org/jhbuild. s/think/know/, since I had the same problem with a clean checkout. But see http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline/blobs/master/sugar-jhbuild#line39 That code will git-pull an existing jhbuild dir or git-clone from git://git.gnome.org/jhbuild . So maybe the jhbuild dir needs to be deleted first, then git-pull in the sugar-jhbuild dir and then ./sugar-jhbuild update? Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cannot sugar-jhbuild update
On Sun, Feb 8, 2009 at 1:44 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/8 Ties Stuij cjst...@gmail.com: On Sun, Feb 8, 2009 at 11:41 AM, Ties Stuij cjst...@gmail.com wrote: On Fri, Feb 6, 2009 at 5:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/6 Alex Holkner alex.holk...@gmail.com: File /home/alex/foreign/sugar-jhbuild/sjhbuild/main.py, line 31, in module import jhbuild.commands ImportError: No module named jhbuild.commands This happened to me some days ago, it was caused because the sugar-jhbuild/jhbuild submodule was pointing to the old location. Deleting that directory and updating sugar-jhbuild solved the issue. I think the problem here is that the path to the gnome git repo is wrong in the sugar-jhbuild script. It's git://git.gnome.org/preview/jhbuild, not git://git.gnome.org/jhbuild. s/think/know/, since I had the same problem with a clean checkout. But see http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline/blobs/master/sugar-jhbuild#line39 That code will git-pull an existing jhbuild dir or git-clone from git://git.gnome.org/jhbuild . So maybe the jhbuild dir needs to be deleted first, then git-pull in the sugar-jhbuild dir and then ./sugar-jhbuild update? On a clean sugar-jhbuild there isn't even a jhbuild dir. And indeed then git tries to pull in jhbuild. As you can see from Alex's post, git can't. Again, there is no git.gnome.org/jhbuild. The path is wrong (changed perhaps recently?). See http://git.gnome.org/cgit/. The right path is (now) git.gnome.org/preview/jhbuild. Worked for me in any case. /Ties ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cannot sugar-jhbuild update
On Sun, Feb 8, 2009 at 09:10, Ties Stuij cjst...@gmail.com wrote: On Sun, Feb 8, 2009 at 1:44 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/8 Ties Stuij cjst...@gmail.com: On Sun, Feb 8, 2009 at 11:41 AM, Ties Stuij cjst...@gmail.com wrote: On Fri, Feb 6, 2009 at 5:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/6 Alex Holkner alex.holk...@gmail.com: File /home/alex/foreign/sugar-jhbuild/sjhbuild/main.py, line 31, in module import jhbuild.commands ImportError: No module named jhbuild.commands This happened to me some days ago, it was caused because the sugar-jhbuild/jhbuild submodule was pointing to the old location. Deleting that directory and updating sugar-jhbuild solved the issue. I think the problem here is that the path to the gnome git repo is wrong in the sugar-jhbuild script. It's git://git.gnome.org/preview/jhbuild, not git://git.gnome.org/jhbuild. s/think/know/, since I had the same problem with a clean checkout. But see http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline/blobs/master/sugar-jhbuild#line39 That code will git-pull an existing jhbuild dir or git-clone from git://git.gnome.org/jhbuild . So maybe the jhbuild dir needs to be deleted first, then git-pull in the sugar-jhbuild dir and then ./sugar-jhbuild update? On a clean sugar-jhbuild there isn't even a jhbuild dir. And indeed then git tries to pull in jhbuild. As you can see from Alex's post, git can't. Again, there is no git.gnome.org/jhbuild. The path is wrong (changed perhaps recently?). See http://git.gnome.org/cgit/. The right path is (now) git.gnome.org/preview/jhbuild. Worked for me in any case. I see now, I understood the opposite. Will change accordingly. Thanks! Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cannot sugar-jhbuild update
Thanks for finding this. Indeed, Gnome must have recently moved the location of jhbuild in their git repo. A couple of weeks ago there was a poll at Gnome about changing their VCS to git. The changes to the gnome git infrastructure have been fast and furious since then. david On Mon, Feb 9, 2009 at 3:37 AM, Tomeu Vizoso to...@sugarlabs.org wrote: On Sun, Feb 8, 2009 at 09:10, Ties Stuij cjst...@gmail.com wrote: On Sun, Feb 8, 2009 at 1:44 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/8 Ties Stuij cjst...@gmail.com: On Sun, Feb 8, 2009 at 11:41 AM, Ties Stuij cjst...@gmail.com wrote: On Fri, Feb 6, 2009 at 5:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/6 Alex Holkner alex.holk...@gmail.com: File /home/alex/foreign/sugar-jhbuild/sjhbuild/main.py, line 31, in module import jhbuild.commands ImportError: No module named jhbuild.commands This happened to me some days ago, it was caused because the sugar-jhbuild/jhbuild submodule was pointing to the old location. Deleting that directory and updating sugar-jhbuild solved the issue. I think the problem here is that the path to the gnome git repo is wrong in the sugar-jhbuild script. It's git://git.gnome.org/preview/jhbuild, not git://git.gnome.org/jhbuild. s/think/know/, since I had the same problem with a clean checkout. But see http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline/blobs/master/sugar-jhbuild#line39 That code will git-pull an existing jhbuild dir or git-clone from git://git.gnome.org/jhbuild . So maybe the jhbuild dir needs to be deleted first, then git-pull in the sugar-jhbuild dir and then ./sugar-jhbuild update? On a clean sugar-jhbuild there isn't even a jhbuild dir. And indeed then git tries to pull in jhbuild. As you can see from Alex's post, git can't. Again, there is no git.gnome.org/jhbuild. The path is wrong (changed perhaps recently?). See http://git.gnome.org/cgit/. The right path is (now) git.gnome.org/preview/jhbuild. Worked for me in any case. I see now, I understood the opposite. Will change accordingly. Thanks! Tomeu ___ 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] Cannot sugar-jhbuild update
On Sun, Feb 8, 2009 at 4:56 PM, Ties Stuij cjst...@gmail.com wrote: On Fri, Feb 6, 2009 at 5:06 PM, Tomeu Vizoso to...@sugarlabs.org wrote: 2009/2/6 Alex Holkner alex.holk...@gmail.com: File /home/alex/foreign/sugar-jhbuild/sjhbuild/main.py, line 31, in module import jhbuild.commands ImportError: No module named jhbuild.commands This happened to me some days ago, it was caused because the sugar-jhbuild/jhbuild submodule was pointing to the old location. Deleting that directory and updating sugar-jhbuild solved the issue. I think the problem here is that the path to the gnome git repo is wrong in the sugar-jhbuild script. It's git://git.gnome.org/preview/jhbuild, not git://git.gnome.org/jhbuild. Thank you, appears to be working now. Alex. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] VirtualBox Sugar on a Stick assembly question
http://sugarlabs.org/go/Sugar_on_a_Stick_VirtualBox http://sugarlabs.org/go/Sugar_on_a_Stick_VirtualBox references a VirtualBox disk image created from SoaS-7 that allows saving changes and includes VirtualBox Guest Additions which allows 1024x768 resolution. Could the creator please provide more detail on how this image was assembled? Thank you for your efforts! FYI, Sugar on a Stick testers are also using this Moodle forum, http://schools.sugarlabs.org/mod/forum/view.php?id=530 http://schools.sugarlabs.org/mod/forum/view.php?id=530 , to collaborate. -- View this message in context: http://n2.nabble.com/VirtualBox-Sugar-on-a-Stick-assembly-question-tp2293374p2293374.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
[Sugar-devel] [ANNOUNCE] gst-plugins-espeak
Hi all, http://sugarlabs.org/go/DevelopmentTeam/gst-plugins-espeak http://git.sugarlabs.org/projects/gst-plugins-espeak Guess it could be useful for activities that use speech synthesizer. It is very simple implementation(it process the whole text at once), thats why I'm not going to push it to official gstreamer plugins. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Auto-authentication for Browse -
Hi Simon, Sugaristas, ... any comments on the topic? If I don't hear anything, I'm going to draft a patch for plan C, aka how I learned to stop worrying and love the plain http cookie. - cheers, martin On Sat, Jan 24, 2009 at 7:40 AM, Martin Langhoff martin.langh...@gmail.com wrote: On Thu, Jan 22, 2009 at 12:39 PM, Simon Schampijer si...@schampijer.de wrote: ===Topics=== c) Auto-authentication for Browse when visiting web-based tools on the XS it has registered to (guest speaker Martin Langhoff) First, *apologies* for the no-show -- I got confused between 14hs UTC and 14hs EST. In terms of what to do with Browse.xo, I have a couple of rough ideas to propose. It's a very tentative thing -- and I don't want or expect to dictate the implementation. There's been a few discussions verbally (at 1CC, and at SugarCamp), plus quite a bit on the devel@ list. Might be worthwhile a re-read. Here's my outline of opportunities and constraints as I understand them * We want seamless, magic auto-authentication for the XO when visiting web-based tools on the XS it has registered to. * We hope this to be low-impact on Browse.xo and 9.1 in general. It'd be a big win if the feature works on 8.2 as well. It cannot hamper using normal websites. * It is better to avoid making it too OLPC-specific. XOs should be able to interop with a XS or something roughly like it. (Later down the path, perhaps more than one XSish server...) * We'd like conventional browsers to able to use the same mechanism (but I can add suitable fallbacks on the XS to support non-XO users...) * We hope this is low impact on the XS too. It cannot hamper other clients. * The XO shares at 'registration' time its local and unique public ssh key with the XS. We can use that bit of knowledge clearly and without more infra changes. * We can change the registration protocol to exchange more data, but that will widen the impact of this change significantly. * The general idea is to hook a special in the background handshake when Browse.xo visits a server that looks like an XS. (But for example, I don't know what hooks we have in there!). After that handshake, which we'd like to be reasonably secure against eavesdroppers and replay attacks, traffic falls back to plain http with the client having an http cookie. Based on that general idea, two approaches have been discussea 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 Plan B - Secure handshake - http cookie - option Assuming Browse.xo can get its grubby hands on .sugar/default/owner.key (not sure how to negotiate that with Rainbow) then it can perform a simple handshake with the XS over plain HTTP, where the XS issues a challenge string that has to be signed by Browse.xo with the private key. The XS, having the public key can verify the signature. Once it has verified it, it gives Browse.xo a traditional HTTP cookie. This is cryptographically much weaker because - It allows third parties to pose as an XS, and generally play MITM. - After the handshake - the interaction continues over plain http. The cookie may be set to short-lived, but within its lifetime it is trivially sniffed and reused. On the other hand, it allows us to just issue an updated Browse.xo perhaps even for 8.2. Plan C - Simple HTTP cookie Bryan Berry mentioned this strategy at XOCamp: at Browse.xo startup time create a 'fake' cookie in cookies.sqlite . We could use the pubkey -- or a hash of it -- as a cookie. This is trivially MITM'able, and trivially sniffable and reused. It cuts to the chase on plan B. - - - - - Thoughts? Opinions? Code? 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 -- 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] [ANNOUNCE] gst-plugins-espeak
You rock! david On Mon, Feb 9, 2009 at 4:31 PM, Aleksey Lim alsr...@member.fsf.org wrote: Hi all, http://sugarlabs.org/go/DevelopmentTeam/gst-plugins-espeak http://git.sugarlabs.org/projects/gst-plugins-espeak Guess it could be useful for activities that use speech synthesizer. It is very simple implementation(it process the whole text at once), thats why I'm not going to push it to official gstreamer plugins. -- Aleksey ___ 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] Getting sugar-jhbuild run working
Thanks for the previous help in getting sugar-jhbuild updating from the correct git repository. I've now got a successful install (this involved upgrading to Ubuntu 8.10 and installing some additional packages not listed on the wiki -- I've added them now). Running './sugar-jhbuild run' brings up an empty Xephyr window (just the patterned background) and does nothing else. The output is: [linux] ~/foreign/sugar-jhbuild% ./sugar-jhbuild run Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed 1234153991.2729919 STARTUP: Starting the shell Thanks for any help Alex. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cannot sugar-jhbuild update
On Sun, Feb 8, 2009 at 1:47 PM, David Farning dfarn...@sugarlabs.org wrote: Thanks for finding this. Indeed, Gnome must have recently moved the location of jhbuild in their git repo. A couple of weeks ago there was a poll at Gnome about changing their VCS to git. The changes to the gnome git infrastructure have been fast and furious since then. afaik GNOME git is experimental for now (their official repos are on svn and it has not yet been decided if they will be actually migrated to git, flamewars still going on about it). Perhaps it would be better to do our clone of jhbuild on git.sugarlabs.org and pull from there for now. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting sugar-jhbuild run working
Can you send ~/.sugar/default/logs/shell.log? Marco On Mon, Feb 9, 2009 at 5:47 AM, Alex Holkner alex.holk...@gmail.com wrote: Thanks for the previous help in getting sugar-jhbuild updating from the correct git repository. I've now got a successful install (this involved upgrading to Ubuntu 8.10 and installing some additional packages not listed on the wiki -- I've added them now). Running './sugar-jhbuild run' brings up an empty Xephyr window (just the patterned background) and does nothing else. The output is: [linux] ~/foreign/sugar-jhbuild% ./sugar-jhbuild run Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed 1234153991.2729919 STARTUP: Starting the shell Thanks for any help Alex. ___ 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
