date:20080928

On Mon, Sep 29, 2008 at 12:04 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> I've installed it on a secured XO with a dev key (that's my usual
> machine); I'll have to try turning security off.

I mean, turning the *dev key* off.
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.

On Sun, Sep 28, 2008 at 6:45 PM, S Page <[EMAIL PROTECTED]> wrote:
> BUT! after I disabled my developer key and ran
>  sudo olpc-update candidate-765
> , my XO won't boot:
>Trying nand:\boot\runos.zip
>  OS found - No signature for our key
>Boot failed  :-(

Hmm, two bugs potentially here: olpc-update shouldn't let you upgrade
to an unsigned build (if that's what candidate-765 is giving you)
without an active developer key (unless you use the --force option, at
least).  I'll check this out on Monday.

> I've been asking on irc:#olpc if anyone has upgraded/installed candidate-765
> on a secure or developer-key XO, with no response.

I've installed it on a secured XO with a dev key (that's my usual
machine); I'll have to try turning security off.
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Fwd: Re: Odd occurance when installing 764]

On Sun, Sep 28, 2008 at 9:50 PM, Gary C Martin <[EMAIL PROTECTED]> wrote:
> On 29 Sep 2008, at 02:06, Michael Stone wrote:
>
>> On Sun, Sep 28, 2008 at 03:21:49PM +0100, Gary C Martin wrote:
>>> To Michael: Not sure who to direct this to, but should the post
>>> install scripts do some extra checks for this potential upgrade
>>> fluff? Not sure how many upgrades this could effect.
>>
>> What might we do with it if we found it?
>
> Well I can't think of a reasonable reason for leaving an old copy of
> Journal kicking around in /home/olpc/Activities (faint chance a dev is

It's useful if you want to alt-boot back to an old build.

> The Clac issue I guess is a special case in that that there was a
> 'Calculate' from MIT that was replaced by Reinier's 'Calc' at some
> point (at least as I understand the history), so I'm guessing
> bundle_id didn't exist  (or perhaps now depreciated service thingy) so
> there's no way the updater would officially know to replace/remove
> Calc and replace with Calculate. This could be a special case for post
> cleanup, removing Calc if Calculate has been installed.

In 9.1, I hope that Michael will provide me with the security
framework I need to handle 'upgrades' between bundles with different
IDs (and authors!), so I can express that 'calculate' is really an
updated 'calc' and have that managed properly.  So the 'fluff' ought
to be removed at that time.

> P.S. what's the post install script called by the way? I'm sure I've
> seen it mentioned in passing or rushing past the console after an
> install, doing 'rainbow' type stuff I think, hence me invoking your
> name here.

olpc-configure, part of the olpc-utils package.  It's really a "first
boot" script, but you "first boot" immediately "post install" so it
wears both hats.
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Fwd: Re: Odd occurance when installing 764]

On 29 Sep 2008, at 02:06, Michael Stone wrote:

> On Sun, Sep 28, 2008 at 03:21:49PM +0100, Gary C Martin wrote:
>> To Michael: Not sure who to direct this to, but should the post  
>> install scripts do some extra checks for this potential upgrade  
>> fluff? Not sure how many upgrades this could effect.
>
> What might we do with it if we found it?
>
> Michael

:-)

Well I can't think of a reasonable reason for leaving an old copy of  
Journal kicking around in /home/olpc/Activities (faint chance a dev is  
keeping old keep sakes). So that would be a rm, in my book. Unless you  
think there is a faint chance of the user booting back to some pre 6xx  
build and have it still work?

The Clac issue I guess is a special case in that that there was a  
'Calculate' from MIT that was replaced by Reinier's 'Calc' at some  
point (at least as I understand the history), so I'm guessing  
bundle_id didn't exist  (or perhaps now depreciated service thingy) so  
there's no way the updater would officially know to replace/remove  
Calc and replace with Calculate. This could be a special case for post  
cleanup, removing Calc if Calculate has been installed.

I guess it's a trade-off between fielding support questions, risk of  
deleting something the user actually wanted still, and complexity of  
the post install script (as it surly will grow over time). I don't  
claim to know enough to answer, just enough to ask the question :-)

--Gary

P.S. what's the post install script called by the way? I'm sure I've  
seen it mentioned in passing or rushing past the console after an  
install, doing 'rainbow' type stuff I think, hence me invoking your  
name here.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-28 Thread Erik Blankinship

> On Sun, Sep 28, 2008 at 6:02 AM, Gary C Martin <[EMAIL PROTECTED]>
wrote:
> > On 26 Sep 2008, at 19:31, Arjun Sarwal wrote:
> >
> >> 2008/9/26 Gary C Martin <[EMAIL PROTECTED]>:
> >>>
> >>> Here's a set of basic Activity test results for build 8.2-763, hope
the
> >>> ASCI
> >>> art doesn't get too mangled by the list server (need to view with a
fixed
> >>>  Measure-20 . . - . x x x . x Doesn't sleep when Activity is in
the
> >>>   background (eats 75% cpu). Can't
seem
> >>> to
> >>>   record anything. Keep error when
> >>
> >> -- When Measure is in background and some other Activity comes in
> >> foreground, then Measure releases sound device - you can record sound
> >> using any other program/application. In this state Measure also
> >> doesn't hog CPU.
> >
> > Just testing with Measure-21 and 8.2-765, yes I see this now. However
> > switching to any of the Neighborhood/Group/Home views does not seem
count as
> > putting Measure into the background, it still consumes the cpu and
claims
> > the sound input device. I'm guessing this is a Sugar behaviour? Is this
a
> > bug or a feature (feels like a Sugar bug that would make the UI sluggish
for
> > no go reason)?
>
> See #7856. Seems like a Sugar related issue to me. I had borrowed the
> code and concept from Record activity, which now apparently uses some
> other method to determine switch of view/context/activity.( I think
> they detect whether one of the main gtk widgets is the topmost or not
> etc. not sure) I should try exploring that. Any help on this would be
> great.

Record listens for "visibility-notify-event":

self.playOggWindow.add_events(gtk.gdk.VISIBILITY_NOTIFY_MASK)
self.playOggWindow.connect("visibility-notify-event", self._visibleNotifyCb)

Because Record has many different windows, we listen on each window and run
through a series of checks on the callback to determine if it is the active
activity anymore.

Be sure to look out for #5500 when trying to get access to a resource like
the camera or microphone.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Fwd: Re: Odd occurance when installing 764]

2008-09-28 Thread Michael Stone

On Sun, Sep 28, 2008 at 03:21:49PM +0100, Gary C Martin wrote:
> To Michael: Not sure who to direct this to, but should the post install 
> scripts do some extra checks for this potential upgrade fluff? Not sure 
> how many upgrades this could effect.

What might we do with it if we found it?

Michael
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Another pass through some basic Activity test results

2008-09-28 Thread Walter Bender

Gary, this is a very helpful analysis. Thanks.
Arjun, I wonder if Measure isn't exceptional in regard to when it is
not in the foreground. I can imagine wanted to log data while doing
other things: It isn't clear it should go idle when not visible. My
naive guess would be to assume that a timer were enabled, Measure
always behave as if it had focus, but otherwise sleep. That said, I
imagine it would be difficult to algorithmically determine the user's
intention.

-walter
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: idea for running out of RAM

2008-09-28 Thread Walter Bender

> So UI changes that help make this clearer will probably be a good idea
> for a 9.1 ... :-/

There was an early sketch of a mechanism similar to the old Home View
circle, where there was a space allocated to each open activity
proportional to the amount of memory it was consuming. In any case, it
is just as easy to make a bar graph as a pie chart...

-walter
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Testing] [sugar] Signed candidate-765 and gg-765-2 builds available for testing.

OK, I can't really test the candidate-765 here. My B4 starts to secure  
boot (hold the X gamepad down), shows an SD card, then flashes what  
looks like a USB key in red a few times, then a wireless symbol,  
before telling me "activation lease not found - no se encontrò  
elpermiso de activiòn - permis d'activation introuvable". Shutting  
down faster than I can type the text into this email :-)

This is very probably as expected, as I'm a developer and have never  
activated an XO lease in any way, shape, or form. Is there a way I can  
get a lease so I can test this side of things (just curious)? I guess  
I'd need a local school server set-up.

Booting in insecure mode was no problem, seemed to work just like what  
I had running before in 765 with the .toc and .usb images from pilgrim.

--Gary

On 28 Sep 2008, at 23:59, Gary C Martin wrote:

> Off list, I'm just "sudo olpc-update candidate-765" on my B4 now.  
> I'll reboot with security** temporally off and let you know how it  
> goes.
>
> **I don't have a dev key, funnily enough, I was shipped a B4 with  
> the Firmware set to disable security and have always just rolled  
> with that set-up, so no dev key to hide.
>
> On 28 Sep 2008, at 23:45, S Page wrote:
>
>> Important: has anyone successfully upgraded/installed to the signed
>> "candidate-765"?
>>
>> If so, someone can edit
>> http://wiki.laptop.org/go/Friends_in_testing/current_image_stream
>> changing it from "8.2" to "candidate" and links and banners should  
>> work.
>>
>> C. Scott Ananian wrote:
>>> On Sat, Sep 27, 2008 at 3:47 AM, S Page <[EMAIL PROTECTED]> wrote:
 So I think you could or should change
 http://wiki.laptop.org/go/Template:Latest_Releases/rc to
 "candidate-765", and update Friend_in_testing to replace "1. Get a
 developer key for your XO laptop." with "Anyone with a mass  
 production
 XO can upgrade to this candidate release (you don't need a  
 developer key)."
>>>
>>> This sounds good to me.  I don't think you need to wait for  
>>> Michael to
>>> make this change, could you go ahead and update the wiki?
>>
>> I made
>> http://wiki.laptop.org/go/Template:candidate-jffs2-link , pointing to
>> >  
>> >
>> There might be other templates and fragments needed.
>>
>> BUT! after I disabled my developer key and ran
>>  sudo olpc-update candidate-765
>> , my XO won't boot:
>>Trying nand:\boot\runos.zip
>>  OS found - No signature for our key
>>Boot failed  :-(
>>
>> I've been asking on irc:#olpc if anyone has upgraded/installed
>> candidate-765 on a secure or developer-key XO, with no response.
>>
>> So I haven't permanently changed
>> http://wiki.laptop.org/go/Friends_in_testing/current_image_stream   
>> from
>> "8.2" to "candidate" , but I believe the wiki is set up for the  
>> change.
>>
>> Michael Stone wrote:
>>> I have also published gg-765-2, a signed G1G1 candidate
>>> composite image, created by Scott. gg-765-2 is similar to what we  
>>> hope
>>> to put into manufacturing next week.
>>> ...
>>> http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1  
>>> composite)
>>
>> Where should this be mentioned?  Should someone doing
>> http://wiki.laptop.org/go/Clean-install_procedure copy this image?
>>
>> --
>> =S Page   user:skierpage
>> ___
>> Testing mailing list
>> [EMAIL PROTECTED]
>> http://lists.laptop.org/listinfo/testing
>

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.

2008-09-28 Thread S Page

Important: has anyone successfully upgraded/installed to the signed 
"candidate-765"?

If so, someone can edit 
http://wiki.laptop.org/go/Friends_in_testing/current_image_stream 
changing it from "8.2" to "candidate" and links and banners should work.

C. Scott Ananian wrote:
> On Sat, Sep 27, 2008 at 3:47 AM, S Page <[EMAIL PROTECTED]> wrote:
>> So I think you could or should change
>> http://wiki.laptop.org/go/Template:Latest_Releases/rc to
>> "candidate-765", and update Friend_in_testing to replace "1. Get a
>> developer key for your XO laptop." with "Anyone with a mass production
>> XO can upgrade to this candidate release (you don't need a developer key)."
> 
> This sounds good to me.  I don't think you need to wait for Michael to
> make this change, could you go ahead and update the wiki?

I made
http://wiki.laptop.org/go/Template:candidate-jffs2-link , pointing to

There might be other templates and fragments needed.

BUT! after I disabled my developer key and ran
   sudo olpc-update candidate-765
, my XO won't boot:
 Trying nand:\boot\runos.zip
   OS found - No signature for our key
 Boot failed  :-(

I've been asking on irc:#olpc if anyone has upgraded/installed 
candidate-765 on a secure or developer-key XO, with no response.

So I haven't permanently changed 
http://wiki.laptop.org/go/Friends_in_testing/current_image_stream  from 
"8.2" to "candidate" , but I believe the wiki is set up for the change.

Michael Stone wrote:
>  I have also published gg-765-2, a signed G1G1 candidate
> composite image, created by Scott. gg-765-2 is similar to what we hope
> to put into manufacturing next week. 
> ...
> http://download.laptop.org/xo-1/custom/g1g1/gg-765-2/ (G1G1 composite)

Where should this be mentioned?  Should someone doing 
http://wiki.laptop.org/go/Clean-install_procedure copy this image?

--
=S Page   user:skierpage
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] rendering test

2008-09-28 Thread Tomeu Vizoso

On Sun, Sep 28, 2008 at 8:57 PM, Bernie Innocenti <[EMAIL PROTECTED]> wrote:
> Riccardo Lucchese wrote:
>>
>> I haven't tried to run oprofile on the xo yet (it is on my todo list).
>
> Be careful, there's a catch with jffs2: it does not support the writable
> shared mmap that oprofiled needs.  This leads to a confusing situation where
> you get an empty report file without any error given.
>
> Refer to this (possibly outdated) documentation for an easy workaround:
>  http://wiki.laptop.org/go/Oprofile_setup
>
>
>> If I remember well, ExaDoMoveOutPixmap (or a function with a similar
>> name) and memcpy were always on top of sysprof profiles in rendering
>> tests.
>
> One advantage of repeating the profile now would be comparing the absolute
> times between different X servers and Fedora runtimes.
>
> Also, leaf functions tell us very little.  memcpy() might be called from
> many different places to do different things.  oprofile also supports stack
> traces, but for some reason I could never get them to work on the XO.  One
> clue is that oprofile cannot use the NMI interrupt on the XO and falls back
> to using a software timer instead.  Perhaps the stack tracing code doesn't
> like that.

In that case, maybe sysprof is just enough (and much easier to set up).

Regards,

Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Major differences between releases

On Sun, Sep 28, 2008 at 2:56 PM, Bert Freudenberg <[EMAIL PROTECTED]> wrote:
> I think it would be a good idea for everyone (activity authors in
> particular) to cross-check the changes in what packages are included
> in the new stable release, in particular what packages are *going away*:
>
>http://dev.laptop.org/~bert/update.1-8.2.html

That list is slightly misleading, as it includes several cases where
two packages were folded into one or a package was renamed.

Others changes are inherited from the F7->F9 transition -- does anyone
know if Fedora documents API changes between releases of Fedora?

> Also, is there any chance someone will take on
>
>http://dev.laptop.org/ticket/4695
>(Document API changes between Ship.1 and Update.1 and 8.2)
>
> after the release before working on the next one?

I did see an email from morgs recently mentioning his interest in
documenting sugar API changes?
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

2008-09-28 Thread david

On Sun, 28 Sep 2008, C. Scott Ananian wrote:

> 2008/9/28  <[EMAIL PROTECTED]>:
>> On Sun, 28 Sep 2008, Carol Lerche wrote:
>>
>>> Why not call it a "tester's key"?  It is principally useful for testing
>>> late-breaking versions.
>>
>> tester key or experimenter key would be better (although experimenter key
>> may have implications that make it sound too attractive)
>
> This does disable antitheft protections, which may not be important to
> most "developers" and "testers" but are considered *very* important by
> many of our deployments.  (We can debate whether or not they are
> mistaken elsewhere, but please take it as a given for the purposes of
> this particular thread.).
>
> I find it vaguely amusing that developers, who first came up with the
> implementation, named it a "developer's key", and now the more popular
> name from the testing community is "tester's key".  It seems we're all
> a bit vain, imagining our own selves to be the most "typical" users.
> =)

I think the issue isn't who the most 'typical' users are, but rather the 
fact that the name can imply who 'should' be using it.

it may be best to just name it 'security bypass' key and then explain why 
developers and testers may want to bypass security on their systems.

David Lang
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Suggested change for Colors! to make quitting the activity work

2008-09-28 Thread Dan Krejsa

Hi,

Here's a patch that seems to make quitting the Colors! (version 4)
activity work on candidate-765.  I don't know how this change would
affect operation on older XO builds.

---8<--
[EMAIL PROTECTED] Colors.activity]$ diff -u colors.py ../colors.py 
--- colors.py   2008-05-09 03:16:10.0 -0700
+++ ../colors.py2008-09-28 11:48:37.0 -0700
@@ -1487,7 +1487,7 @@
 
 def take_screenshot (self):
 if self.easelarea and self.easelarea.bin_window:
-self._preview.take_screenshot(self.easelarea.bin_window)
+   self._preview.take_screenshot(self.easelarea)
 
 def save_thumbnail(self, filename):
 pbuf = gtk.gdk.Pixbuf(gtk.gdk.COLORSPACE_RGB, False, 8,
self.width, self.height)
---8<--

A couple of other questions on Colors!

-  Is it supposed to play back the saved painting automatically
   when an instance starts? Currently it does not.

-  After manually going to the watch tab and playing back
   the saved painting, then returning to the Paint tab, the
   first stroke fails to apply any paint.  The second stroke
   succeeds.





___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] rendering test

2008-09-28 Thread Bernie Innocenti

Riccardo Lucchese wrote:
>> Was fbdev running with EXA or XAA?  (does fbdev even support EXA?)
> http://www.x.org/wiki/ExaStatus lists fbdev in the `Probably unsuitable
> for EXA support' section; so, I guess XAA.

Confirmed: there's absolutely no EXA code in xf86-video-fbdev.  Too bad, 
it would have been perfect to measure the relative overhead of going 
through the EXA fallbacks.

>> My performance tests with X 1.3 and 1.4 had shown that turning on EXA 
>> makes many operations slower.  It's hard to tell why, but it might have to 
>> do with loosing XShmPut() (MIT shared memory), excessive migration of 
>> pixmaps to the framebuffer, and so on.  X 1.5 was supposed to have a much 
>> better EXA, at least judging from the stream of patches landed on the tree.
>>
>> I'd be very interested in seeing the output of oprofile while running your 
>> benchmark on X 1.4 and X 1.5.  Please, remember to install the debuginfo 
>> packages for the X server, libcairo, and the geode driver.
> 
> I haven't tried to run oprofile on the xo yet (it is on my todo list).

Be careful, there's a catch with jffs2: it does not support the writable 
shared mmap that oprofiled needs.  This leads to a confusing situation 
where you get an empty report file without any error given.

Refer to this (possibly outdated) documentation for an easy workaround:
   http://wiki.laptop.org/go/Oprofile_setup

> If I remember well, ExaDoMoveOutPixmap (or a function with a similar
> name) and memcpy were always on top of sysprof profiles in rendering
> tests.

One advantage of repeating the profile now would be comparing the absolute 
times between different X servers and Fedora runtimes.

Also, leaf functions tell us very little.  memcpy() might be called from 
many different places to do different things.  oprofile also supports 
stack traces, but for some reason I could never get them to work on the 
XO.  One clue is that oprofile cannot use the NMI interrupt on the XO and 
falls back to using a software timer instead.  Perhaps the stack tracing 
code doesn't like that.

-- 
\___/  Bernie Innocenti - http://www.codewiz.org/
   _| X |  Sugar Labs Team  - http://www.sugarlabs.org/
   \|_O_|  "It's an education project, not a laptop project!"
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Major differences between releases

I think it would be a good idea for everyone (activity authors in  
particular) to cross-check the changes in what packages are included  
in the new stable release, in particular what packages are *going away*:

http://dev.laptop.org/~bert/update.1-8.2.html

Also, is there any chance someone will take on

http://dev.laptop.org/ticket/4695
(Document API changes between Ship.1 and Update.1 and 8.2)

after the release before working on the next one?

- Bert -

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

2008/9/28  <[EMAIL PROTECTED]>:
> On Sun, 28 Sep 2008, Carol Lerche wrote:
>
>> Why not call it a "tester's key"?  It is principally useful for testing
>> late-breaking versions.
>
> tester key or experimenter key would be better (although experimenter key
> may have implications that make it sound too attractive)

This does disable antitheft protections, which may not be important to
most "developers" and "testers" but are considered *very* important by
many of our deployments.  (We can debate whether or not they are
mistaken elsewhere, but please take it as a given for the purposes of
this particular thread.).

I find it vaguely amusing that developers, who first came up with the
implementation, named it a "developer's key", and now the more popular
name from the testing community is "tester's key".  It seems we're all
a bit vain, imagining our own selves to be the most "typical" users.
=)
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Please unlock Activities/G1G1/8.2


Am 28.09.2008 um 11:30 schrieb C. Scott Ananian:

> On Sun, Sep 28, 2008 at 1:46 PM, Bert Freudenberg <[EMAIL PROTECTED] 
> > wrote:
>>
>> Am 28.09.2008 um 07:59 schrieb C. Scott Ananian:
>>
>>> On Fri, Sep 26, 2008 at 7:55 PM, Bert Freudenberg <[EMAIL PROTECTED] 
>>> >
>>> wrote:

 The lock-down of this page (which causes lock-down of all  
 included pages
 transitively) was fine until Scott replaced the references to the  
 8.2
 versions of activities with the old G1G1 page. E.g., when the  
 page was
 locked, it included

 http://wiki.laptop.org/go/Activities/Etoys_(8.2)

 which is okay to be pegged at v. 94.

 But now it includes and locks down

 http://wiki.laptop.org/go/Activities/Etoys_(latest)

 which makes it impossible for me to update that page to v. 95 to  
 match
 the
 latest joyride.

 Please unlock as long as the page references the original G1G1  
 page. See
 edit history at

 http://wiki.laptop.org/go/Activities/G1G1/8.2
>>>
>>> I expect to refork the Activities/G1G1 page soon (probably as soon  
>>> as
>>> we declare an 8.2 final).  In the interim, it makes my life easier  
>>> to
>>> both (a) have 8.2 point to G1G1, so I don't have to edit things in  
>>> two
>>> places, and (b) have the 8.2 (and G1G1) page locked, so that I am
>>> certain I know what activity version changes are being
>>> proposed/tested.  I don't expect this to last for long.
>>>
>>> For now, can you either ask me via email or file a trac request
>>> assigned to me for the etoys update you'd like to make?  You can  
>>> also
>>> copy/paste the template into Activities/Joyride for now to get
>>> testing; that shouldn't be locked.  Should the etoys update be
>>> considered if we made another release candidate?  (I've noticed
>>> there's a new etoys RPM in joyride).
>>>
>>> I know this is inconvenient, but if you can bear with me, it will  
>>> make
>>> my life in the next week easier.  You can transfer the inconvenience
>>> to me by making me update your activity info for you, and if that  
>>> gets
>>> to be too much work it will motivate me to reconsider unprotecting  
>>> the
>>> page to let you do it yourself. =)
>>
>> Hehe. So please s/94/95/g in [Activities/Etoys (latest)].
>>
>> And yes, if #8608 gets approved and etoys-3.0.2159 gets in then  
>> please use
>> Etoys-95, too (this is just if you are doing a new build anyway, do  
>> not hold
>> the release for it).
>
> Out of an abundance of caution: is there any problem with using
> Etoys-95 if the etoys rpm is *not* updated?  I've upgraded Etoys on
> the [[Activities/G1G1]] page, so our testers are probably testing
> Etoys-95 + 765, which has etoys-2153-1.  Is that okay?

Yes, no problem. The only relevant change there is use of bundle_id  
instead of service_name.

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Please unlock Activities/G1G1/8.2

On Sun, Sep 28, 2008 at 1:46 PM, Bert Freudenberg <[EMAIL PROTECTED]> wrote:
>
> Am 28.09.2008 um 07:59 schrieb C. Scott Ananian:
>
>> On Fri, Sep 26, 2008 at 7:55 PM, Bert Freudenberg <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> The lock-down of this page (which causes lock-down of all included pages
>>> transitively) was fine until Scott replaced the references to the 8.2
>>> versions of activities with the old G1G1 page. E.g., when the page was
>>> locked, it included
>>>
>>>  http://wiki.laptop.org/go/Activities/Etoys_(8.2)
>>>
>>> which is okay to be pegged at v. 94.
>>>
>>> But now it includes and locks down
>>>
>>>  http://wiki.laptop.org/go/Activities/Etoys_(latest)
>>>
>>> which makes it impossible for me to update that page to v. 95 to match
>>> the
>>> latest joyride.
>>>
>>> Please unlock as long as the page references the original G1G1 page. See
>>> edit history at
>>>
>>>  http://wiki.laptop.org/go/Activities/G1G1/8.2
>>
>> I expect to refork the Activities/G1G1 page soon (probably as soon as
>> we declare an 8.2 final).  In the interim, it makes my life easier to
>> both (a) have 8.2 point to G1G1, so I don't have to edit things in two
>> places, and (b) have the 8.2 (and G1G1) page locked, so that I am
>> certain I know what activity version changes are being
>> proposed/tested.  I don't expect this to last for long.
>>
>> For now, can you either ask me via email or file a trac request
>> assigned to me for the etoys update you'd like to make?  You can also
>> copy/paste the template into Activities/Joyride for now to get
>> testing; that shouldn't be locked.  Should the etoys update be
>> considered if we made another release candidate?  (I've noticed
>> there's a new etoys RPM in joyride).
>>
>> I know this is inconvenient, but if you can bear with me, it will make
>> my life in the next week easier.  You can transfer the inconvenience
>> to me by making me update your activity info for you, and if that gets
>> to be too much work it will motivate me to reconsider unprotecting the
>> page to let you do it yourself. =)
>
> Hehe. So please s/94/95/g in [Activities/Etoys (latest)].
>
> And yes, if #8608 gets approved and etoys-3.0.2159 gets in then please use
> Etoys-95, too (this is just if you are doing a new build anyway, do not hold
> the release for it).

Out of an abundance of caution: is there any problem with using
Etoys-95 if the etoys rpm is *not* updated?  I've upgraded Etoys on
the [[Activities/G1G1]] page, so our testers are probably testing
Etoys-95 + 765, which has etoys-2153-1.  Is that okay?
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: gcompris activities regression

2008-09-28 Thread Bruno Coudoin

Le dimanche 28 septembre 2008 à 19:36 +0200, [EMAIL PROTECTED] a
écrit :
> Bonjour Bruno,
> 
> I have just installed the last release on a xo. The installation procesure 
> with
> xoget failed, an I used the alternative with wget.
> 
> The gcompris-activity runs well.
> However, if I try to launch an activity in the "letter"-group of activities, I
> get following error message:
> "Error: the activity requires that you first install the packages with 
> GCompris
> voices for the locale 'fr' or 'en'.
> 
> This error occurs again on the LiveCD (for example in the version from
> ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_080919.iso ), which are
> an important promotion tool, especially in France, where the liveCD is the
> unique possibility to explore GCompris in the sugar environment.
> 

This is because I don't distribute french voices. In order to keep the
full bundle small, well relatively small, I exclude all the voices
except en, es, pt, pt_BR. 

It is relatively easy to create a full bundle that includes french.
- Get the gcomprixo branch
  http://gcompris.net/wiki/index.php/Developer%27s_corner
- Get everything needed to build GCompris:
  apt-get build-dep gcompris
- Edit the file tools/full_xo_bundle.sh to no more remove the 'fr'
  directory where the fr voices are.
- Run the script ./tools/full_xo_bundle.sh
- Once complete the bundle is in /tmp/

Tested on Ubuntu Hardy only.

On the long term as anybody a better solution to distribute GCompris and
it's localized voices in an efficient manner.

-- 
Bruno Coudoin
http://gcompris.net Free educational software for kids
http://toulibre.org Logiciel Libre à Toulouse

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] rendering test

2008-09-28 Thread Riccardo Lucchese

On Sun, 2008-09-28 at 18:46 +0200, Bernie Innocenti wrote:
> >>> - joyride regressed sensibly at rendering with cairo since 703
> >>> - rendering pixbufs is extremely slow on the xo
> >>> - server side surfaces are awesome ;)
> >>>
> >> and btw why is fbdev faster than the geode driver at rendering pixbufs ?
> 
> Was fbdev running with EXA or XAA?  (does fbdev even support EXA?)
http://www.x.org/wiki/ExaStatus lists fbdev in the `Probably unsuitable
for EXA support' section; so, I guess XAA.

> My performance tests with X 1.3 and 1.4 had shown that turning on EXA 
> makes many operations slower.  It's hard to tell why, but it might have to 
> do with loosing XShmPut() (MIT shared memory), excessive migration of 
> pixmaps to the framebuffer, and so on.  X 1.5 was supposed to have a much 
> better EXA, at least judging from the stream of patches landed on the tree.
> 
> I'd be very interested in seeing the output of oprofile while running your 
> benchmark on X 1.4 and X 1.5.  Please, remember to install the debuginfo 
> packages for the X server, libcairo, and the geode driver.

I haven't tried to run oprofile on the xo yet (it is on my todo list).

If I remember well, ExaDoMoveOutPixmap (or a function with a similar
name) and memcpy were always on top of sysprof profiles in rendering
tests.

riccardo

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Feedback on Measure (was Re: Another pass through some basic Activity test results)

2008-09-28 Thread Arjun Sarwal

(have changed the subject line since we are drifting off topic from
the previous subject )

Hi,

On Sun, Sep 28, 2008 at 6:02 AM, Gary C Martin <[EMAIL PROTECTED]> wrote:
> On 26 Sep 2008, at 19:31, Arjun Sarwal wrote:
>
>> 2008/9/26 Gary C Martin <[EMAIL PROTECTED]>:
>>>
>>> Here's a set of basic Activity test results for build 8.2-763, hope the
>>> ASCI
>>> art doesn't get too mangled by the list server (need to view with a fixed
>>>  Measure-20 . . - . x x x . x Doesn't sleep when Activity is in the
>>>   background (eats 75% cpu). Can't seem
>>> to
>>>   record anything. Keep error when
>>
>> -- When Measure is in background and some other Activity comes in
>> foreground, then Measure releases sound device - you can record sound
>> using any other program/application. In this state Measure also
>> doesn't hog CPU.
>
> Just testing with Measure-21 and 8.2-765, yes I see this now. However
> switching to any of the Neighborhood/Group/Home views does not seem count as
> putting Measure into the background, it still consumes the cpu and claims
> the sound input device. I'm guessing this is a Sugar behaviour? Is this a
> bug or a feature (feels like a Sugar bug that would make the UI sluggish for
> no go reason)?

See #7856. Seems like a Sugar related issue to me. I had borrowed the
code and concept from Record activity, which now apparently uses some
other method to determine switch of view/context/activity.( I think
they detect whether one of the main gtk widgets is the topmost or not
etc. not sure) I should try exploring that. Any help on this would be
great.

>
>> -- For recording the waveforms, within 'Sound' in toolbar, if 'Now' is
>> selected  and the record button next to it is pressed, it will capture
>> the current displayed waveform. If you select an interval and then
>> press the record button, it will start saving waveforms at the
>> specified interval and the record button will change to a 'stop'
>> button. It will record a maximum of 10 waveforms.
>>
>> You will be able to see the waveforms as picture files in the Journal
>
> Ahhh, thanks Arjun, so that's where they go to. I was expecting some visual
> representation within Measure, perhaps like Record does, where there is a
> tray at the bottom of the screen, or Browse and its bookmark thumbnails.
>

Thats very much on my list for the next set of TODOs. I am however not
sure from the UI point of view where this tray could go, and where
this textbox could go...or if there is an alternate replacement for
both ?


> Is there a way to capture waveform images without the entire UI also
> appearing in the  screen shot?
>

There is and I thought about that. But then I figured that along with
the waveform one would also need to know things like, what was the
timebase scale when the waveform was being displayed, was it in time
mode or fft mode etc. So I took the whole screen shot that would also
have all other information included.

Maybe just the waveform area saved along with some meta-data stored in
the journal entry might be an idea to consider ?

>> --For recording sensor values, within the 'Sensors' context , when one
>> presses the record button it will start writing the sensor values (of
>> the sensor connected at Analog Input) at the specified interval.
>> You can have multiple recording sessions,i.e. stop it and then resume
>> it and stop it again and resume it.
>>
>> You can see the logged sensor values in the Journal.  They are saved
>> in csv format.
>> (I am waiting for the spreadsheet activity to come soon! :) )
>
> Thanks, I understand this now as well. I had not noticed that new entries
> were silently being entered in to the Journal. BTW: you can resume the CSV
> file and Write will display the list of values. I also tried copying the CSV
> to the clipboard, but it generated a blank clipboard icon and would not
> paste anywhere (probably a Sugar issue, the clipboard isn't very robust
> yet).
>

I tried that too. It didn't work - Write doesn't copy anything on the
clip-board if one is viewing a csv file. Seems like a bug?

> Some quick suggestions:
>
> - The "Start Recording" text could say "Start Recording to Journal", that
> would have pointed me to check in the Journal after clicking record.
>

Agreed, good idea.

> - The time section menu could say "Every 30 seconds", "Every 2 minutes" etc.
> Before you explained, I believed that the times were the duration of the
> sample to be recorded, not the interval between each sample. The little
> toolbar interval icon makes more sense now that I know what the menu does
> ;-)

Hmm...so the interval needs to be made more intuitive...

>
>> Lastly, thanks for the feedback, its really useful. It helped me
>> figure out a minor problem in sensor values recording (#8683) and I
>> released ver21 that corrects that!
>
>
> Glad it was of use! I'm a bit of an electronics type, so I'm really glad
> Measure is up and working again.
>

Re: New release8.2 build 764

2008-09-28 Thread david

On Sun, 28 Sep 2008, Carol Lerche wrote:

Why not call it a "tester's key"? It is principally useful for testing
late-breaking versions.

tester key or experimenter key would be better (although experimenter key
may have implications that make it sound too attractive)

David Lang

On Sun, Sep 28, 2008 at 9:34 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:

On Sun, Sep 28, 2008 at 12:31 PM, <[EMAIL PROTECTED]> wrote:

On Sun, 28 Sep 2008, C. Scott Ananian wrote:

Requesting dev keys should not be difficult! How can we fix that

problem?

one headache (at least from the initial G1G1 machines) was the inability

do a cut-n-paste of the long key between the terminal and the browser and
therefor the need to copy the long key manually between screens (or to

and

from paper)

That is true. http://dev.laptop.org/ticket/5709 and
http://dev.laptop.org/ticket/6428 track these issues. I regret I
wasn't able to get time to fix them for 8.2; they are on my 9.1
roadmap, but help would be appreciated!

another one (very relevant to conference situations) is the one business

day

delay in getting the keys issues. this isn't usually a problem, but when

you

only have people togeather for a couple of days (especially over the
weekend) it may not be possible to get keys for people who don't already
have them.

http://wiki.laptop.org/go/Activation_and_developer_keys#Getting_devkey_data_for_many_XOs_at_once

many people who would be good testers don't consider themselves

'developers'

so would not get them on their own.

Can you suggest a better name, or how we might improve our documentation?
--scott

--
( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Please unlock Activities/G1G1/8.2


Am 28.09.2008 um 07:59 schrieb C. Scott Ananian:

> On Fri, Sep 26, 2008 at 7:55 PM, Bert Freudenberg <[EMAIL PROTECTED] 
> > wrote:
>> The lock-down of this page (which causes lock-down of all included  
>> pages
>> transitively) was fine until Scott replaced the references to the 8.2
>> versions of activities with the old G1G1 page. E.g., when the page  
>> was
>> locked, it included
>>
>>   http://wiki.laptop.org/go/Activities/Etoys_(8.2)
>>
>> which is okay to be pegged at v. 94.
>>
>> But now it includes and locks down
>>
>>   http://wiki.laptop.org/go/Activities/Etoys_(latest)
>>
>> which makes it impossible for me to update that page to v. 95 to  
>> match the
>> latest joyride.
>>
>> Please unlock as long as the page references the original G1G1  
>> page. See
>> edit history at
>>
>>   http://wiki.laptop.org/go/Activities/G1G1/8.2
>
> I expect to refork the Activities/G1G1 page soon (probably as soon as
> we declare an 8.2 final).  In the interim, it makes my life easier to
> both (a) have 8.2 point to G1G1, so I don't have to edit things in two
> places, and (b) have the 8.2 (and G1G1) page locked, so that I am
> certain I know what activity version changes are being
> proposed/tested.  I don't expect this to last for long.
>
> For now, can you either ask me via email or file a trac request
> assigned to me for the etoys update you'd like to make?  You can also
> copy/paste the template into Activities/Joyride for now to get
> testing; that shouldn't be locked.  Should the etoys update be
> considered if we made another release candidate?  (I've noticed
> there's a new etoys RPM in joyride).
>
> I know this is inconvenient, but if you can bear with me, it will make
> my life in the next week easier.  You can transfer the inconvenience
> to me by making me update your activity info for you, and if that gets
> to be too much work it will motivate me to reconsider unprotecting the
> page to let you do it yourself. =)

Hehe. So please s/94/95/g in [Activities/Etoys (latest)].

And yes, if #8608 gets approved and etoys-3.0.2159 gets in then please  
use Etoys-95, too (this is just if you are doing a new build anyway,  
do not hold the release for it).

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: gcompris activities regression

2008-09-28 Thread s . boutayeb

Bonjour Bruno,

I have just installed the last release on a xo. The installation procesure with
xoget failed, an I used the alternative with wget.

The gcompris-activity runs well.
However, if I try to launch an activity in the "letter"-group of activities, I
get following error message:
"Error: the activity requires that you first install the packages with GCompris
voices for the locale 'fr' or 'en'.

This error occurs again on the LiveCD (for example in the version from
ftp://rohrmoser-engineering.de/pub/XO-LiveCD/XO-LiveCD_080919.iso ), which are
an important promotion tool, especially in France, where the liveCD is the
unique possibility to explore GCompris in the sugar environment.

Bravo encore for the impressive work

Bien cordialement

Bests

Samy



Re: gcompris activities regression
> I just completed the step 2. The new release is uploaded, each
> activities and the full bundle. They should work as before now.
>
> --
> Bruno Coudoin
> http://gcompris.net Free educational software for kids
> http://toulibre.org Logiciel Libre ? Toulouse
>
>
>
> --
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>
> End of Devel Digest, Vol 31, Issue 129
> **
>


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New joyride build 2491

2008-09-28 Thread Build Announcer v2

http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2491

Changes in build 2491 from build: 2489

Size delta: 0.13M

-sugar-update-control 0.16-1
+sugar-update-control 0.17-1

--- Changes for sugar-update-control 0.17-1 from 0.16-1 ---
  + Trac #7845, #8681: don't die if ~/Activities doesn't exist.

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

Am 28.09.2008 um 09:38 schrieb Carol Lerche:

> Why not call it a "tester's key"?  It is principally useful for  
> testing late-breaking versions.

IMHO a user doesn't even have to know there is a "key", let alone  
worry about its name. The "test" designation is a good one, so why not  
simply have a checkbox in the control panel labeled something like  
"allow running test builds"?

I added this to
http://dev.laptop.org/ticket/1502

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] rendering test

2008-09-28 Thread Bernie Innocenti

Tomeu Vizoso wrote:
> Ooops. cc'ing to some other people/list in the hope someone more
> knowledgeable than me will comment.

Thanks.  Please Cc me on posts like these to make sure I don't miss them. 
  No, it doesn't bother me to receive 0.001% more mail.

I've also Cc'd the Xorg list in case someone can give us more insight.

> On Sun, Sep 28, 2008 at 12:46 PM, Riccardo Lucchese
> <[EMAIL PROTECTED]> wrote:
>> On Sun, 2008-09-28 at 12:43 +0200, Riccardo Lucchese wrote:
>>> * build 703, xorg driver = amd, redraws = 200
>>> - pixbuf:
>>>   98.63s
>>>   96.96s
>>>   96.58s
>>>   97.14s
>>>   99.21s
>>>
>>> * build 703, xorg driver = fbdev, redraws = 200
>>> - pixbuf:
>>>   55.81s
>>>   55.40s
>>>   55.22s
>>>   55.50s
>>>   55.63s
>>>
>>> * build 2489, xorg driver = amd, redraws = 200
>>> - pixbuf:
>>>   84.21s
>>>   84.81s
>>>   81.94s
>>>   81.79s
>>>   85.29s
>>>
>>> * build 2489, xorg driver = fbdev, redraws = 200
>>> - pixbuf:
>>>   62.83s
>>>   62.81s
>>>   62.81s
>>>   62.66s
>>>   63.14s
>>>
>>> - joyride regressed sensibly at rendering with cairo since 703
>>> - rendering pixbufs is extremely slow on the xo
>>> - server side surfaces are awesome ;)
>>>
>> and btw why is fbdev faster than the geode driver at rendering pixbufs ?

Was fbdev running with EXA or XAA?  (does fbdev even support EXA?)

My performance tests with X 1.3 and 1.4 had shown that turning on EXA 
makes many operations slower.  It's hard to tell why, but it might have to 
do with loosing XShmPut() (MIT shared memory), excessive migration of 
pixmaps to the framebuffer, and so on.  X 1.5 was supposed to have a much 
better EXA, at least judging from the stream of patches landed on the tree.

I'd be very interested in seeing the output of oprofile while running your 
benchmark on X 1.4 and X 1.5.  Please, remember to install the debuginfo 
packages for the X server, libcairo, and the geode driver.

-- 
\___/  Bernie Innocenti - http://www.codewiz.org/
   _| X |  Sugar Labs Team  - http://www.sugarlabs.org/
   \|_O_|  "It's an education project, not a laptop project!"
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

2008-09-28 Thread Carol Lerche

Why not call it a "tester's key"?  It is principally useful for testing
late-breaking versions.

On Sun, Sep 28, 2008 at 9:34 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:

> On Sun, Sep 28, 2008 at 12:31 PM,  <[EMAIL PROTECTED]> wrote:
> > On Sun, 28 Sep 2008, C. Scott Ananian wrote:
> >> Requesting dev keys should not be difficult!  How can we fix that
> problem?
> >
> > one headache (at least from the initial G1G1 machines) was the inability
> to
> > do a cut-n-paste of the long key between the terminal and the browser and
> > therefor the need to copy the long key manually between screens (or to
> and
> > from paper)
>
> That is true.  http://dev.laptop.org/ticket/5709 and
> http://dev.laptop.org/ticket/6428 track these issues.  I regret I
> wasn't able to get time to fix them for 8.2; they are on my 9.1
> roadmap, but help would be appreciated!
>
> > another one (very relevant to conference situations) is the one business
> day
> > delay in getting the keys issues. this isn't usually a problem, but when
> you
> > only have people togeather for a couple of days (especially over the
> > weekend) it may not be possible to get keys for people who don't already
> > have them.
>
>
> http://wiki.laptop.org/go/Activation_and_developer_keys#Getting_devkey_data_for_many_XOs_at_once
>
> > many people who would be good testers don't consider themselves
> 'developers'
> > so would not get them on their own.
>
> Can you suggest a better name, or how we might improve our documentation?
>  --scott
>
> --
> ( http://cscott.net/ )
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>



-- 
"The water won't clear up 'til we get the hogs out of the creek." -- Jim
Hightower
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

On Sun, Sep 28, 2008 at 12:31 PM,  <[EMAIL PROTECTED]> wrote:
> On Sun, 28 Sep 2008, C. Scott Ananian wrote:
>> Requesting dev keys should not be difficult!  How can we fix that problem?
>
> one headache (at least from the initial G1G1 machines) was the inability to
> do a cut-n-paste of the long key between the terminal and the browser and
> therefor the need to copy the long key manually between screens (or to and
> from paper)

That is true.  http://dev.laptop.org/ticket/5709 and
http://dev.laptop.org/ticket/6428 track these issues.  I regret I
wasn't able to get time to fix them for 8.2; they are on my 9.1
roadmap, but help would be appreciated!

> another one (very relevant to conference situations) is the one business day
> delay in getting the keys issues. this isn't usually a problem, but when you
> only have people togeather for a couple of days (especially over the
> weekend) it may not be possible to get keys for people who don't already
> have them.

http://wiki.laptop.org/go/Activation_and_developer_keys#Getting_devkey_data_for_many_XOs_at_once

> many people who would be good testers don't consider themselves 'developers'
> so would not get them on their own.

Can you suggest a better name, or how we might improve our documentation?
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

2008-09-28 Thread david

On Sun, 28 Sep 2008, C. Scott Ananian wrote:

> On Fri, Sep 26, 2008 at 6:44 AM, Walter Bender <[EMAIL PROTECTED]> wrote:
>> Any of these 76X builds signed ? There are a bunch of people here at
>> the Open Minds conference with XOs who'd love to test them, but they
>> don't have developer keys installed.
>
> candidate-765 is signed.
>
> Requesting dev keys should not be difficult!  How can we fix that problem?

one headache (at least from the initial G1G1 machines) was the inability 
to do a cut-n-paste of the long key between the terminal and the browser 
and therefor the need to copy the long key manually between screens (or to 
and from paper)

another one (very relevant to conference situations) is the one business 
day delay in getting the keys issues. this isn't usually a problem, but 
when you only have people togeather for a couple of days (especially over 
the weekend) it may not be possible to get keys for people who don't 
already have them.

many people who would be good testers don't consider themselves 
'developers' so would not get them on their own.

David Lang
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: gcompris activities regression

2008-09-28 Thread Bruno Coudoin

Le samedi 27 septembre 2008 à 00:57 +0200, Marco Pesenti Gritti a
écrit :
> Unless someone find time to track it down I guess we will have to:
> 
> 1 Downgrade libxml2
> 2 Rely on a gcompris fix/workaround.

I just completed the step 2. The new release is uploaded, each
activities and the full bundle. They should work as before now.

-- 
Bruno Coudoin
http://gcompris.net Free educational software for kids
http://toulibre.org Logiciel Libre à Toulouse

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 764 is imminent

On 26 Sep 2008, at 09:15, Marco Pesenti Gritti wrote:

> On Fri, Sep 26, 2008 at 3:30 AM, Eben Eliason  
> <[EMAIL PROTECTED]> wrote:
>> Yup, we were getting several reports that kids accidentally pressed
>> keys while at the Home screen (which auto-focuses the search  
>> field.)..
>
> Did we actually get reports from kids about this?

I've just added two very small patches to http://dev.laptop.org/ticket/7969 
  that keep search available, but not focused by default, on the Home  
favourites view. It basically just reverts the  
self.search_entry.set_sensitive(False) changes; moves the focus away  
from the search field; and stops the zoom transition from re-focusing  
on Home favourites view search – took me a while to find that last  
one :-).

Built and tested on an XO 8.2-765 using "diif -u" and "patch -p1"

--Gary
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Please unlock Activities/G1G1/8.2

On Fri, Sep 26, 2008 at 7:55 PM, Bert Freudenberg <[EMAIL PROTECTED]> wrote:
> The lock-down of this page (which causes lock-down of all included pages
> transitively) was fine until Scott replaced the references to the 8.2
> versions of activities with the old G1G1 page. E.g., when the page was
> locked, it included
>
>http://wiki.laptop.org/go/Activities/Etoys_(8.2)
>
> which is okay to be pegged at v. 94.
>
> But now it includes and locks down
>
>http://wiki.laptop.org/go/Activities/Etoys_(latest)
>
> which makes it impossible for me to update that page to v. 95 to match the
> latest joyride.
>
> Please unlock as long as the page references the original G1G1 page. See
> edit history at
>
>http://wiki.laptop.org/go/Activities/G1G1/8.2

I expect to refork the Activities/G1G1 page soon (probably as soon as
we declare an 8.2 final).  In the interim, it makes my life easier to
both (a) have 8.2 point to G1G1, so I don't have to edit things in two
places, and (b) have the 8.2 (and G1G1) page locked, so that I am
certain I know what activity version changes are being
proposed/tested.  I don't expect this to last for long.

For now, can you either ask me via email or file a trac request
assigned to me for the etoys update you'd like to make?  You can also
copy/paste the template into Activities/Joyride for now to get
testing; that shouldn't be locked.  Should the etoys update be
considered if we made another release candidate?  (I've noticed
there's a new etoys RPM in joyride).

I know this is inconvenient, but if you can bear with me, it will make
my life in the next week easier.  You can transfer the inconvenience
to me by making me update your activity info for you, and if that gets
to be too much work it will motivate me to reconsider unprotecting the
page to let you do it yourself. =)
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

On Fri, Sep 26, 2008 at 8:47 PM, Bastien <[EMAIL PROTECTED]> wrote:
> "C. Scott Ananian" <[EMAIL PROTECTED]> writes:
>
>>> http://lumiere.ens.fr/~guerry/olpc_install_sugar_activities_usb.php
>>
>> Please ensure that your activities and content list matches
>> [[Activities/G1G1]].
>
> Do you mean the activities listed here:
>
> http://wiki.laptop.org/go/Activities/G1G1/8.2

The /8.2 version of the page are the 'stable' versions.  When we get
into 9.1 development, the [[Activities/G1G1]] page will contain the
latest 9.1 or development versions, while [[Activities/G1G1/8.2]] will
only be updated monthly or so, with those activity versions which are
expected to work well on 8.2.  At the moment, they should be
identical.
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: New release8.2 build 764

On Fri, Sep 26, 2008 at 6:44 AM, Walter Bender <[EMAIL PROTECTED]> wrote:
> Any of these 76X builds signed ? There are a bunch of people here at
> the Open Minds conference with XOs who'd love to test them, but they
> don't have developer keys installed.

candidate-765 is signed.

Requesting dev keys should not be difficult!  How can we fix that problem?
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [sugar] Signed candidate-765 and gg-765-2 builds available for testing.

On Sat, Sep 27, 2008 at 3:47 AM, S Page <[EMAIL PROTECTED]> wrote:
> Michael Stone wrote:
>> I have decided to publish 8.2-765 as a signed Candidate
[...]
>   sudo olpc-update 8.2-765
> led to
>   WARNING: You seem to be attempting to download an unsigned
[...]
>   sudo olpc-update candidate-765
> is updating without complaint on my un-security-disabled XO.

Yes, that's the expected behavior.  The 'candidate' name gives you the
signed image; the 8.2-xyz is still the unsigned version of the same
build.

In the past I tried to retroactively make tags like 8.2-xyz point to
the signed image once a build had obtained the necessary checkoffs to
be signed, but this turned out to be too confusing: when people
reported problems with 8.2-xyz, I wouldn't know whether they'd tried
before or after I'd make the change, or if the image was signed or
unsigned.

> So I think you could or should change
> http://wiki.laptop.org/go/Template:Latest_Releases/rc to
> "candidate-765", and update Friend_in_testing to replace "1. Get a
> developer key for your XO laptop." with "Anyone with a mass production
> XO can upgrade to this candidate release (you don't need a developer key)."

This sounds good to me.  I don't think you need to wait for Michael to
make this change, could you go ahead and update the wiki?

>> I have also published gg-765-2, a signed G1G1 candidate
>> composite image, created by Scott. gg-765-2 is similar to what we hope
>> to put into manufacturing next week.
>
> This doesn't work using olpc-update, right?
>   sudo olpc-update gg-765-2
> gave
>   @ERROR: unknown module 'build-gg-765-2': bad build identifier: gg-765-2.

No, the gg-752-2 is a "clean install" image, with preinstalled
activities.  The factory installs this with 'copy-nand' before the
machines leave the assembly line.  It *should* be exactly the same as
what you'd get if you 'olpc-update' to candidate-765 and then let the
software updater install updated activities -- except that olpc-update
will also preserve whatever "extra" activities you've already got
installed, the contents of your journal, etc.
  --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Fwd: Re: Odd occurance when installing 764]