New release8.2.1 build 790

[Build Announcer v2]

http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2.1/build790

Changes in build 790 from build: 0

Size delta: 245.10M

+ConsoleKit-x11 0.2.10-3.fc9
+SDL_image 1.2.6-6.fc9
+acl 2.2.47-2.fc9
+SDL_mixer 1.2.8-8.olpc3.1
+SDL_ttf 2.0.9-4.fc9
+NetworkManager 1:0.6.5-0.11.svn3246.olpc3
+SDL 1.2.13-4.fc9.1
+PolicyKit 0.8-3.fc9
+SDL_Pango 0.1.2-8
+ORBit2 2.14.12-3.fc9
+MAKEDEV 3.23-5.fc9
+ConsoleKit 0.2.10-3.fc9
+GConf2 2.22.0-1.fc9
+yum 3.2.19-3.1.olpc3
+ConsoleKit-libs 0.2.10-3.fc9
+xorg-x11-xinit 1.0.9-1.fc9
+xorg-x11-drv-cirrus 1.2.0-1.fc9
+xorg-x11-drv-fbdev 0.3.1-7.fc9
+xorg-x11-utils 7.4-2.olpc3
+xorg-x11-drv-vmware 10.16.0-1.fc9
+xorg-x11-drv-geode 2.10.1-1.fc9
+sugar-update-control 0.17-1
+tar 2:1.19-4.fc9
+unzip 5.52-9.fc9
+vim-minimal 2:7.1.291-1.fc9
+which 2.19-3.fc9
+vte 0.16.13-1.fc9
+wvdial 1.60-5.fc9
+vnc 4.1.2-31.fc9
+tree 1.5.0-9.fc9
+totem-mozplugin 2.23.4-1.olpc3.6
+thaifonts-scalable 0.4.9-3.fc9
+python-json 3.4-3.fc9
+olpcsudo 1.4-1
+python-sqlite2 1:2.3.3-3.fc9
+abyssinica-fonts 1.0-2.fc8
+rainbow 0.7.24-1.fc9
+sugar-journal 99-4.olpc3
+sugar-evince-python 2.20.1.1-3.olpc3
+strace 4.5.16-5.fc9
+rdesktop 1.6.0-1.fc9
+Mothanna-fonts 0.02-3.olpc3
+openssh-clients 5.1p1-2.fc9
+openssh-server 5.1p1-2.fc9
+olpcsound 5.08.92-11.olpc3
+PolicyKit-olpc 1.2-1.fc9
+pygtksourceview 2.2.0-1.fc9
+python-alsaaudio 0.3-1.fc9
+pygame 1.8.0-1.olpc3.3
+pyabiword 0.6.1-4.olpc3
+anacron 2.3-59.fc9
+Thabit-fonts 0.02-3.fc9
+bootanim 1.2-1
+alsa-utils 1.0.17-2.fc9
+avahi-dnsconfd 0.6.22-10.fc9
+bzip2 1.0.5-2.fc9
+cerebro 2.9.16-1.olpc3
+dbus-x11 1.2.1-1.fc9
+compat-libstdc++-33 3.2.3-63
+dejavu-lgc-fonts 2.24-3.fc9
+ds-backup-client 0.8.1-1.olpc3
+diffutils 2.8.1-21.fc9
+eject 2.1.5-11.fc9
+espeak 1.31-5.fc9
+etoys 3.0.2153-1
+file 4.23-5.fc9
+gdb 6.8-21.fc9
+gettext 0.17-4.fc9
+gzip 1.3.12-6.fc9
+gnash-plugin 0.8.3-1.olpc3.2
+gtk2-engines 2.14.3-1.fc9
+hulahop 0.4.6-1.olpc3
+kernel 2.6.25-20080925.1.olpc.f10b654367d7065
+iptables-ipv6 1.4.1.1-2.fc9
+libXdamage 1.1.1-4.fc9
+libertas-usb8388-firmware 2:5.110.22.p18-1.olpc2
+libxml2-python 2.7.1-1.fc9
+lohit-fonts-hindi 2.2.1-2.fc9
+lrzsz 0.12.20-23.fc9
+ltrace 0.5-10.45svn.fc9
+mtd-utils 1.2.0-1.fc9
+mailcap 2.1.28-1.fc9
+nafees-web-naskh-fonts 1.0-1.fc8
+nano 2.0.6-4.fc9
+ntp-ntpdate 4.2.4p4-7.olpc3
+ohm 0.1.1-6.21.20080921git.olpc3
+olpc-library-common 1-30
+olpc-licenses 8.2.0.0-1.olpc3
+olpc-netutils 0.7-1.fc9
+olpcrd 0.48-0
+olpc-utils 0.89-1.olpc3
+alsa-lib 1.0.17-2.fc9
+agg 2.5-6.fc9
+atk 1.22.0-1.fc9
+atlas 3.6.0-15.fc9
+audit-libs 1.7.5-1.fc9
+avahi 0.6.22-10.fc9
+avahi-autoipd 0.6.22-10.fc9
+basesystem 8.1-1
+avahi-glib 0.6.22-10.fc9
+avahi-gobject 0.6.22-10.fc9
+avahi-tools 0.6.22-10.fc9
+bash 3.2-22.fc9
+blas 3.1.1-4.fc9
+boost 1.34.1-15.fc9
+bootfw q2e18-1.olpc2.unsigned
+bzip2-libs 1.0.5-2.fc9
+cairo 1.6.4-1.fc9
+chkconfig 1.3.37-2
+coreutils 6.10-30.fc9
+cpio 2.9-8.fc9
+cpp 4.3.0-8
+cracklib 2.8.12-2
+cracklib-dicts 2.8.12-2
+cronie 1.0-7.fc9
+crontabs 1.10-19.fc9
+cryptsetup-luks 1.0.6-2.fc9
+db4 4.6.21-6.fc9
+cups-libs 1:1.3.7-8.fc9
+cyrus-sasl-lib 2.1.22-15.fc9
+dbus 1.2.1-1.fc9
+dbus-glib 0.74-8.fc9
+dbus-libs 1.2.1-1.fc9
+desktop-file-utils 0.15-1.fc9
+dbus-python 0.83.0-3.fc9
+device-mapper-libs 1.02.24-11.fc9
+device-mapper 1.02.24-11.fc9
+dhclient 12:4.0.0-17.fc9
+dirmngr 1.0.1-2.fc9
+dhcp 12:4.0.0-17.fc9
+djvulibre-libs 3.5.20-2.fc9
+e2fsprogs 1.40.8-3.fc9
+dmidecode 1:2.9-1.30.1.fc9
+dnsmasq 2.41-0.8.fc9
+ethtool 6-1.fc9
+e2fsprogs-libs 1.40.8-3.fc9
+elfutils-libelf 0.135-1.fc9
+enchant 1:1.4.2-2.fc9
+expat 2.0.1-5
+fedora-release 9-5.transition.1
+file-libs 4.23-5.fc9
+filesystem 2.4.13-1.fc9
+flac 1.2.1-4.fc9
+findutils 1:4.2.33-3.fc9
+fontconfig 2.5.0-2.fc9
+fribidi 0.19.1-2.fc9
+freetype 2.3.5-6.fc9
+gamin 0.1.9-5.fc9
+gawk 3.1.5-17.fc9
+gdbm 1.8.0-28.fc9
+glib2 2.16.5-1.fc9
+glibc 2.8-8
+glibc-common 2.8-8
+gmp 4.2.2-7.fc9
+gnash 0.8.3-1.olpc3.2
+gnome-python2-gnomevfs 2.22.1-3.olpc3
+gnome-mime-data 2.18.0-2.fc7
+gnome-python2 2.22.1-3.olpc3
+gnome-python2-libwnck 2.22.0-4.fc9
+gnome-python2-rsvg 2.22.0-4.fc9
+gnome-vfs2 2.22.0-3.olpc3
+gnupg2 2.0.9-1.fc9
+gnutls 2.0.4-3.fc9
+gpgme 1.1.6-3.fc9
+grep 2.5.1-59.fc9
+gstreamer 0.10.12-3.olpc3
+gstreamer-plugins-base 0.10.12-4.olpc3.4
+gstreamer-plugins-flumpegdemux 0.10.15-2.fc9
+gstreamer-plugins-good 0.10.5-7.olpc3.1
+gstreamer-python 0.10.7-2.olpc3.1
+gstreamer-tools 0.10.12-3.olpc3
+gtk2 2.12.11-1.fc9
+gtksourceview2 2.2.2-1.fc9
+hal-info 20080607-1.olpc3.1
+hal 0.5.11-2.olpc3.1
+hdparm 8.6-1.fc9
+hal-libs 0.5.11-2.olpc3.1
+hicolor-icon-theme 0.10-4
+hippo-canvas-python 0.3.0-2.fc9
+hippo-canvas 0.3.0-2.fc9
+hunspell 1.2.1-7.fc9
+hwdata 0.217-1.fc9
+info 4.11-8.fc9
+iptables 1.4.1.1-2.fc9
+initscripts 8.76.2-1.olpc3.7
+iproute 2.6.25-1.fc9
+ipython 0.8.2-1.fc9
+iputils 20071127-2.fc9
+iso-codes 2.0-1.fc9
+jack-audio-connection-kit 0.109.2-3.fc9
+kbd 1.12-31.fc9
+keyutils-libs 1.2-3.fc9
+lcms 1.17-5.fc9
+krb5-libs 1.6.3-10.fc9
+lcms-libs 1.17-5.fc9
+less 418-3.fc9
+libICE 1.0.4-3.fc9
+

Re: 2588 - Journal unusable

[James Cameron]

G'day Chris,

I'll give a partial line of reasoning response ... this is not complete,
I'm short of time.

Where I said public, I meant developer builds that can be used by other
developers.  I didn't mean to imply public builds for testing by
non-developers.  I mean the difference between what a developer does and
what a developer releases.  That isn't only OLPC originated code, that's
also the choice of what RPMs to accept from outside.  Accepting lots of
RPMs at once is the same as making lots of code change.

Why don't you have private build streams?  That's what I can do with
debxo, for instance ... build on my desktop, test on an XO, and then
avoid releasing anything to the public until I've verified that what
I've changed actually works.

Why can't the build system be replicated so that each developer can test
their change before releasing it?  What is it about the build system that
prevents it?  I thought the build system was just a set of downloads and
put-it-together processes.

-- 
James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 2588 - Journal unusable

[Chris Ball]

Hi James,

Thanks for these thoughts.  They seem like worthwhile goals, but I don't
think we're likely to get there in practise.  In specific:

   > It is as if joyride is being used as part of developers' edit,
   > compile and test sequence.  Wouldn't it be more appropriate to do
   > this sequence privately before a developer releases their changes
   > to the public?

So, first of all, this "developers -> public" distinction is bogus;
these aren't "public" builds, they're developer builds, and the only
reason this seems odd is that most companies aren't doing their
development in public.  We _do not have_ a private build stream to use
to stage builds in before letting you see them, and we don't want one.

   > Here's how it would happen ... the developer would build a new RPM,
   > install it on a test unit, test that it works, *before* publishing
   > the RPM for the joyride to pick up.  If any failures occur due to
   > integration against other developer changes, then stronger
   > dependencies should be added.

Many of the people supplying RPMs that we end up using in Joyride are
not writing them for the XO -- they might be Fedora updates, or even
upstream Sugar changes that are tested under jhbuild and not the XO.
We're going to have to deal with this as part of accepting that we
(OLPC-the-company) don't write >90% of the code we ship, and don't
have influence over the people who do write it, most of whom we'll
never meet.

Finally, I think it's a little unfair (but not in an offended kind of
way) to expect us to have stable or even working Joyride builds at the
moment: we just moved to Fedora 10, and it's always going to be the case
that a bunch of stuff breaks and you have to go through the breakage
piece by piece; this isn't a case where we'd have a working build if
only some developer had tested her changes before throwing them over
the wall into Joyride.

   > I'm also waiting for the joyride builds to be usable before I
   > consume download data resources on them.

All that said, the desire to *have* a working build is a very reasonable
thing, and that's why we're trying hard not to trick anyone into
thinking that Joyride contains that build.  If you have the time and
bandwidth to help shake out the bugs, we'd love your help; if you don't,
that's fine too and you should stay on 8.2.x for another few weeks.

Hope that helps!

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

New joyride build 2592

[Build Announcer v2]

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

Changes in build 2592 from build: 2591

Size delta: -0.13M

-bootfw q2e23-1.olpc2.unsigned
+bootfw q2e24-1.olpc2.unsigned

--- Changes for bootfw q2e24-1.olpc2.unsigned from q2e23-1.olpc2.unsigned ---
  + Fixed a few NANDblaster UI bugs found in early testing.

--
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

Firmware Q2E24 works for me!

[445 ride]

I was having problems with Teapot's Ubuntu Intrepid release with a new
"Verbatim SDHC Premium 8GB Class 6" card.  Each boot I was getting the "Card
didn't power up after 1 second" error message which I worked around by
simply typing "boot" to continue.  Trac 8987 problem.  However after
flashing to Q2E24 the problem has disappeared and the machine boots straight
into Ubuntu without problems.

Latest firmware was at..
http://dev.laptop.org/pub/firmware/LATEST/

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

Re: [Server-devel] Server-devel Digest, Vol 20, Issue 13

[Eroni Tuiloma]

 Installing : xs-config [1/1]
> /etc /
> # It may be dirty
> xs-commitchanged -m 'Dirty state' rsyslog.conf
> # Overwrite
> cp -p rsyslog.conf.in rsyslog.conf
> xs-commitchanged -m "Made from rsyslog.conf.in" rsyslog.conf
> # It may be dirty
> xs-commitchanged -m 'Dirty state' motd
> # Overwrite
> cp -p motd.in motd
> xs-commitchanged -m "Made from motd.in" motd
> xs-commitchanged -m 'Dirty state' sysctl.conf
> cp -p sysctl.conf.in sysctl.conf
> xs-commitchanged -m "Made from sysctl.conf.in" sysctl.conf
> sysctl -p sysctl.conf
> net.ipv4.ip_forward = 1
> net.ipv4.conf.default.rp_filter = 1
> net.ipv4.conf.default.accept_source_route = 0
> kernel.sysrq = 1
> kernel.core_uses_pid = 1
> net.ipv4.tcp_syncookies = 1
> kernel.shmmax = 268435456
> # It may be dirty
> xs-commitchanged -m 'Dirty state' ssh/sshd_config
> # Overwrite
> cp -p ssh/sshd_config.in ssh/sshd_config
> xs-commitchanged -m "Made from ssh/sshd_config.in" ssh/sshd_config
> Created commit bb554ba: Made from ssh/sshd_config.in - changed file
> /etc/ssh/sshd_config
>  1 files changed, 3 insertions(+), 3 deletions(-)
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/named
> # Overwrite
> cp -p sysconfig/named.in sysconfig/named
> xs-commitchanged -m "Made from sysconfig/named.in" sysconfig/named
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/init
> # Overwrite
> cp -p sysconfig/init.in sysconfig/init
> xs-commitchanged -m "Made from sysconfig/init.in" sysconfig/init
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/iptables-config
> # Overwrite
> cp -p sysconfig/iptables-config.in sysconfig/iptables-config
> xs-commitchanged -m "Made from sysconfig/iptables-config.in"
> sysconfig/iptables-config
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/squid
> # Overwrite
> cp -p sysconfig/squid.in sysconfig/squid
> xs-commitchanged -m "Made from sysconfig/squid.in" sysconfig/squid
> touch sudoers.tmp
> chmod 640 sudoers.tmp
> cat-parts sudoers.d > sudoers.tmp
> chmod 440 sudoers.tmp
> xs-commitchanged -m 'Dirty state' sudoers
> mv -f sudoers.tmp sudoers
> xs-commitchanged -m "Made from sudoers.d" sudoers
> # It may be dirty
> xs-commitchanged -m 'Dirty state' rssh.conf
> # Overwrite
> cp -p rssh.conf.in rssh.conf
> xs-commitchanged -m "Made from rssh.conf.in" rssh.conf
> # It may be dirty
> xs-commitchanged -m 'Dirty state' php.ini
> # Overwrite
> cp -p php.ini.in php.ini
> xs-commitchanged -m "Made from php.ini.in" php.ini
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/httpd
> # Overwrite
> cp -p sysconfig/httpd.in sysconfig/httpd
> xs-commitchanged -m "Made from sysconfig/httpd.in" sysconfig/httpd
> # It may be dirty
> xs-commitchanged -m 'Dirty state' init.d/squid
> # Overwrite
> cp -p init.d/squid.in init.d/squid
> xs-commitchanged -m "Made from init.d/squid.in" init.d/squid
> # It may be dirty
> xs-commitchanged -m 'Dirty state' sysconfig/ejabberd
> # Overwrite
> cp -p sysconfig/ejabberd.in sysconfig/ejabberd
> xs-commitchanged -m "Made from sysconfig/ejabberd.in" sysconfig/ejabberd
> xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth0
> cp -p sysconfig/olpc-scripts/ifcfg-eth0
> sysconfig/network-scripts/ifcfg-eth0
> xs-commitchanged -m "Made from olpc-scripts"
> sysconfig/network-scripts/ifcfg-eth0
> xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth1
> cp -p sysconfig/olpc-scripts/ifcfg-eth1
> sysconfig/network-scripts/ifcfg-eth1
> xs-commitchanged -m "Made from olpc-scripts"
> sysconfig/network-scripts/ifcfg-eth1
> # It may be dirty
> xs-commitchanged -m 'Dirty state' httpd/conf.d/proxy_ajp.conf
> # Overwrite
> cp -p httpd/conf.d/proxy_ajp.conf.in httpd/conf.d/proxy_ajp.conf
> xs-commitchanged -m "Made from httpd/conf.d/proxy_ajp.conf.in"
> httpd/conf.d/proxy_ajp.conf
> # It may be dirty
> xs-commitchanged -m 'Dirty state' httpd/conf.d/ssl.conf
> # Overwrite
> cp -p httpd/conf.d/ssl.conf.in httpd/conf.d/ssl.conf
> xs-commitchanged -m "Made from httpd/conf.d/ssl.conf.in"
> httpd/conf.d/ssl.conf
> Using default domain name
> Setting the base dns name to random.xs.laptop.org
> find: ./domain_config.d/: No such file or directory
> xs-commitchanged -m 'Dirty state' sysconfig/network
> sed -

New joyride build 2591

[Build Announcer v2]

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

Changes in build 2591 from build: 2590

Size delta: 0.00M

-kernel 2.6.27-20081210.1.olpc.05aa2d840dc7b96
+kernel 2.6.27-20081211.2.olpc.d2f19da5993402b

--
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

8.2.1 builds now underway.

[Michael Stone]

Dear world,

I pasted together an 8.2.1 build stream by copying the 8.2 build stream
on pilgrim.laptop.org, substituting "8.2.1" for "8.2" everywhere
appropriate, adding a branch to mock.laptop.org's git repository, and
updating the upgrade server's branch->url map.

In short, you can now:

   download 8.2.1 builds from 
 http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2.1/
   olpc-update 8.2.1-790 (and soon more)
   view 8.2.1 trac tickets at http://dev.laptop.org/report/35

Other comments: 

So far as I know, the http://wiki.laptop.org/go/Trac_ticket_workflow is
still in force, though I'm certain that suggestions on ways that it
could be improved would be more than welcome.

I don't know yet what evidence Ed wants to see before accepting packaged
changes into this buildstream but I imagine that we'll work it out soon.

Regards,

Michael

P.S. - People who maintain build-announcers -- please update them;
they're really helpful! Thanks!
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 2588 - Journal unusable

[quozl]

On Thu, Dec 11, 2008 at 04:24:32PM -0500, Eben Eliason wrote:
> 1) Joyide is the development build stream.  It doesn't by any means
> promise stability, in general.
> 2) It's early in the release cycle, so things are even more likely to
> break in fairly big ways.

It is as if joyride is being used as part of developers' edit, compile
and test sequence.  Wouldn't it be more appropriate to do this sequence
privately before a developer releases their changes to the public?

Here's how it would happen ... the developer would build a new RPM,
install it on a test unit, test that it works, *before* publishing the
RPM for the joyride to pick up.  If any failures occur due to
integration against other developer changes, then stronger dependencies
should be added.

I'm also waiting for the joyride builds to be usable before I consume
download data resources on them.

-- 
James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 2588 - Journal unusable

[david]

On Thu, 11 Dec 2008, Eben Eliason wrote:

> On Thu, Dec 11, 2008 at 3:57 PM, Mikus Grinbergs  wrote:
>>
>> It is likely that the regression in Journal was caused by releasing
>> sugar-toolkit without simultaneously releasing something which that
>> package interacted with.  But how is the person who gets the Joyride
>> build to know what he needs to wait for?  For "taskID=993286" ??
>
> Well, there are a few factors here:
>
> 1) Joyide is the development build stream.  It doesn't by any means
> promise stability, in general.
> 2) It's early in the release cycle, so things are even more likely to
> break in fairly big ways.
> 3) As was mentioned, a few days to a week is really quite short, all
> things considered.
>
> We don't suggest that people who depend on day to day use of their XO
> use the joyride builds all the time. However, we certainly appreciate
> everyone who does help test it, since it's clearly best to catch any
> and all regressions as early as possible, as large or small as they
> might be.  For that, I'm sure we all thank you!

when I was reporting errors a few weeks ago I got the response "we're 
early in the process, don't bother to report anything until we have it 
stabilized a bit, we'll tell you when to start testing". I asked within 
the last week or so if it was time to start testing yet and was told no.

David Lang

> Of course, writing a ticket is /always/ the correct thing to do in
> such circumstances, so that we can adequately triage the bug, and
> ensure it doesn't get lost. Even if we don't get it fixed within a day
> or two, this will ensure that it does get fixed. Thanks!
>
> - Eben
>
>
>> mikus
>>
>> ___
>> 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

2588 - Journal unusable

[Mikus Grinbergs]

With 2590 the Joyride Journal problem of entries not displaying an 
icon (so those Activities can be re-launched) has been corrected.

Thank you,  mikus




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

Re: What's going on with Text To Speech on the XO?

[Edward Cherlin]

Welcome back. There is significant interest from other organizations
in our use of TTS with text coloring. I have just started discussions
with the Doug Engelbart Foundation, Creative Commons ccLearn, Alan
Kay's Viewpoints Research, and OLE about a new project to create a
full range of teaching materials around Sugar. TTS-TC is important for
literacy, of course, and also for language learning.

On Thu, Dec 11, 2008 at 1:38 PM, James Simmons
 wrote:
> I've haven't been working on the XO lately (my basement office had to go
> through Mold Remediation after a flood) but I have been monitoring  this
> mailing list every day.  When I last did any development work on the XO
> it was to create a mostly successful text to speech feature for the Read
> Etexts activity.  Using this successfully would require some RPMs
> installed on the XO that Hemant Goyal was working on for Fedora, plus a
> newer version of Python that resolved some problems caused by
> threading.  What I remember is that if you used threading at all in your
> activity it prevented power management from working.
>
> I've been cleaning up my basement after the tile installers finished and
> there is some hope that I can resume working on my activity, at least a
> little.  I have my XO upgraded to the latest release of Sugar and it
> looks like Speech Dispatcher still is not part of that release.
>
> I'm well aware of all the other work going on with the XO and I don't
> kid myself that this should be a priority for anyone, but if someone
> could bring me up to date on what's happening with text to speech on the
> XO I'd be much obliged.
>
> James Simmons
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>



-- 
Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name
And Children are my nation.
The Cosmos is my dwelling place, The Truth my destination.
http://wiki.sugarlabs.org/go/User:Mokurai
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New joyride build 2590

[Build Announcer v2]

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

Changes in build 2590 from build: 2589

Size delta: 0.13M

-bootfw q2f01-1.olpc2.unsigned
+bootfw q2e23-1.olpc2.unsigned
-sugar 0.83.3-1.olpc4
+sugar 0.83.3-2.20081211git78c54da36b.olpc4
-sugar-artwork 0.83.1-1.olpc4
+sugar-artwork 0.83.1-2.20081211git3fe6ebe6a8.olpc4
-telepathy-gabble 0.7.15-1.olpc4
+telepathy-gabble 0.7.16-1.olpc4
-telepathy-glib 0.7.18-1.olpc4
+telepathy-glib 0.7.19-1.olpc4

--- Changes for bootfw q2e23-1.olpc2.unsigned from q2f01-1.olpc2.unsigned ---
  + Built on new firmware build vhost on weka.laptop.org
  + USB - fixed bulk-in timeout setting; only seems to affect some USB CD-ROM 
drives.
  + USB - CDROM support.
  + NANDBlaster support. [http://wiki.laptop.org/go/Multicast_NAND_FLASH_Update 
details]
  + OLPC trac 8987 - Reinstated a missing Marvell quirk workaround
  + Erase SPI FLASH blocks just before writing them, as weak protection against 
bricking.
  + Attempt to make SD startup a little more robust by retrying if the first 
power-up attempt failed.
  + New EC version scheme to remove confusion with the system firmware version 
scheme.
  + Refactored EC code structure and large code cleanups
  + New build system based on wine
  + Quick power LED blink before power shut-off

--- Changes for sugar 0.83.3-2.20081211git78c54da36b.olpc4 from 0.83.3-1.olpc4 
---
  + CanvasPulsingIcon: Don't begin pulse loop on resume if not pulsing
  + Use g_timeout_add_seconds() for power efficiency
  + Add the journal button to the volumes toolbar in the journal
  + Remove jarabe/model/volume.py and use gio instead
  + First try at restoring removable devices support in the journal
  + make the image viewer activity the default one for iamges

--
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

What's going on with Text To Speech on the XO?

[James Simmons]

I've haven't been working on the XO lately (my basement office had to go 
through Mold Remediation after a flood) but I have been monitoring  this 
mailing list every day.  When I last did any development work on the XO 
it was to create a mostly successful text to speech feature for the Read 
Etexts activity.  Using this successfully would require some RPMs 
installed on the XO that Hemant Goyal was working on for Fedora, plus a 
newer version of Python that resolved some problems caused by 
threading.  What I remember is that if you used threading at all in your 
activity it prevented power management from working.

I've been cleaning up my basement after the tile installers finished and 
there is some hope that I can resume working on my activity, at least a 
little.  I have my XO upgraded to the latest release of Sugar and it 
looks like Speech Dispatcher still is not part of that release.

I'm well aware of all the other work going on with the XO and I don't 
kid myself that this should be a priority for anyone, but if someone 
could bring me up to date on what's happening with text to speech on the 
XO I'd be much obliged.

James Simmons


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

Re: 2588 - Journal unusable

[Eben Eliason]

On Thu, Dec 11, 2008 at 3:57 PM, Mikus Grinbergs  wrote:
>> I am just making a new snapshot release of sugar since there were some
>> deps of sugar-toolkit on the sugar package. What is helpful when writing
>> those emails is always to have a quick look at the logs.
>>
>> For the impatient ones:
>> http://koji.fedoraproject.org/koji/taskinfo?taskID=993286
>
> Disclaimer:  META-discussion follows
>
> Putting 'patience' into context:  For an example of me getting
> impatient - having Journal unexpectedly stop working in Joyride
> (with no one seeming to care).  For an example of me remaining
> patient, this list (of where F9 is apparently at a later level than
> F10) has been the output of Joyride's 'yum check-update' for ages:
>
>> iproute.i386 2.6.27-1.fc9
>> nspr.i3864.7.3-1.1.fc9
>> pyabiword.i386   0.6.1-4.olpc3
>> python-telepathy.noarch  0.15.3-1.olpc3
>> sugar-artwork.i386   0.83.1-2.olpc3
>> sugar-base.i386  0.83.1-2.olpc3
>> sugar-journal.noarch 100-1.olpc3
>> xorg-x11-drv-evdev.i386  2.0.8-1.fc9
>
>
> It is likely that the regression in Journal was caused by releasing
> sugar-toolkit without simultaneously releasing something which that
> package interacted with.  But how is the person who gets the Joyride
> build to know what he needs to wait for?  For "taskID=993286" ??

Well, there are a few factors here:

1) Joyide is the development build stream.  It doesn't by any means
promise stability, in general.
2) It's early in the release cycle, so things are even more likely to
break in fairly big ways.
3) As was mentioned, a few days to a week is really quite short, all
things considered.

We don't suggest that people who depend on day to day use of their XO
use the joyride builds all the time. However, we certainly appreciate
everyone who does help test it, since it's clearly best to catch any
and all regressions as early as possible, as large or small as they
might be.  For that, I'm sure we all thank you!

Of course, writing a ticket is /always/ the correct thing to do in
such circumstances, so that we can adequately triage the bug, and
ensure it doesn't get lost. Even if we don't get it fixed within a day
or two, this will ensure that it does get fixed. Thanks!

- Eben


> mikus
>
> ___
> 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: 2588 - Journal unusable

[Mikus Grinbergs]

> I am just making a new snapshot release of sugar since there were some
> deps of sugar-toolkit on the sugar package. What is helpful when writing
> those emails is always to have a quick look at the logs.
> 
> For the impatient ones:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=993286

Disclaimer:  META-discussion follows

Putting 'patience' into context:  For an example of me getting 
impatient - having Journal unexpectedly stop working in Joyride 
(with no one seeming to care).  For an example of me remaining 
patient, this list (of where F9 is apparently at a later level than 
F10) has been the output of Joyride's 'yum check-update' for ages:

> iproute.i386 2.6.27-1.fc9 
> nspr.i3864.7.3-1.1.fc9
> pyabiword.i386   0.6.1-4.olpc3
> python-telepathy.noarch  0.15.3-1.olpc3   
> sugar-artwork.i386   0.83.1-2.olpc3   
> sugar-base.i386  0.83.1-2.olpc3   
> sugar-journal.noarch 100-1.olpc3  
> xorg-x11-drv-evdev.i386  2.0.8-1.fc9  


It is likely that the regression in Journal was caused by releasing 
sugar-toolkit without simultaneously releasing something which that 
package interacted with.  But how is the person who gets the Joyride 
build to know what he needs to wait for?  For "taskID=993286" ??

mikus

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

Re: Wine activity

[Vincent Povirk]

I have put up a new version (12) that I am hoping will fix any
problems where the whole activity crashes. That shouldn't happen
anymore.

It is at http://ftp.winehq.org/pub/wine/Wine.xo

I can't reproduce such crashes reliably so I don't know for sure they're gone.

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

Re: 8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[Ed McNierney]

Folks -

I have tagged all the "correct" 8.2.1 tickets with the keyword "8.2.1:+" and
Michael is assisting in reclassifying these bugs to the correct milestone.

In case of further difficulty, the fifteen tickets that were set to a
Milestone:8.2.1 value this morning (and to which I was referring in my
request for review and discussion) are the following:

http://dev.laptop.org/ticket/6028
http://dev.laptop.org/ticket/8155
http://dev.laptop.org/ticket/8451
http://dev.laptop.org/ticket/8667
http://dev.laptop.org/ticket/8745
http://dev.laptop.org/ticket/8767
http://dev.laptop.org/ticket/8942
http://dev.laptop.org/ticket/8976
http://dev.laptop.org/ticket/8982
http://dev.laptop.org/ticket/9044
http://dev.laptop.org/ticket/9045
http://dev.laptop.org/ticket/9053
http://dev.laptop.org/ticket/9102
http://dev.laptop.org/ticket/9107
http://dev.laptop.org/ticket/9109

These are the tickets we will be considering for 8.2.1 inclusion.  At the
moment I believe it is an inclusive list but I expect we will decide not to
fix all of them for 8.2.1.

- Ed

On 12/11/08 2:11 PM, "Michael Stone"  wrote:

> On Thu, Dec 11, 2008 at 01:50:58PM -0500, Ed McNierney wrote:
>> OK, someone made a boo-boo.  Some time in the last hour or two Trac got
>> "updated" with 308 new Milestone=8.2.1 tickets.  I'd appreciate anyone who's
>> recently made bulk updates reconsider their actions.  Thanks!
> 
> Someone closed the 8.2.0 milestone, which auto-pushed all the tickets in
> that milestone into the next milestone, which happens to be 8.2.1.
> 
> Michael
> 


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

Re: 8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[Michael Stone]

On Thu, Dec 11, 2008 at 01:50:58PM -0500, Ed McNierney wrote:
>OK, someone made a boo-boo.  Some time in the last hour or two Trac got
>"updated" with 308 new Milestone=8.2.1 tickets.  I'd appreciate anyone who's
>recently made bulk updates reconsider their actions.  Thanks!

Someone closed the 8.2.0 milestone, which auto-pushed all the tickets in
that milestone into the next milestone, which happens to be 8.2.1.

Michael

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

Re: 8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[Ed McNierney]

OK, someone made a boo-boo.  Some time in the last hour or two Trac got
"updated" with 308 new Milestone=8.2.1 tickets.  I'd appreciate anyone who's
recently made bulk updates reconsider their actions.  Thanks!

- Ed 


On 12/11/08 1:48 PM, "Deepak Saxena"  wrote:

> On Dec 11 2008, at 13:38, p...@laptop.org was caught saying:
>> ed wrote:
>>> Folks -
>>> 
>>> We?re trying to get a very focused 8.2.1 release wrapped up to address a
>>> small number of problems affecting or blocking key country deployments of
>>> 8.2.  A few bugs have been tagged for an 8.2.1 milestone (fifteen of them),
>> 
>> i went looking for a canned report to find those 15 tickets for
>> me.  i found two:  http://dev.laptop.org/report/34 and 35.
>> 
>> clearly i don't understand how reports work, because they each
>> return 323 tickets, in different orderings, 8 of which are marked
>> as blockers.
> 
> My interpreation of Ed's email was that we are to review
> all 323 8.2.1 tickets tommorrow(!), not just the 15. Ed,
> can you clarify?
> 
> Thanks,
> ~Deepak


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

Re: 8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[Deepak Saxena]

On Dec 11 2008, at 13:38, p...@laptop.org was caught saying:
> ed wrote:
>  > Folks -
>  > 
>  > We?re trying to get a very focused 8.2.1 release wrapped up to address a
>  > small number of problems affecting or blocking key country deployments of
>  > 8.2.  A few bugs have been tagged for an 8.2.1 milestone (fifteen of them),
> 
> i went looking for a canned report to find those 15 tickets for
> me.  i found two:  http://dev.laptop.org/report/34 and 35.
>
> clearly i don't understand how reports work, because they each
> return 323 tickets, in different orderings, 8 of which are marked
> as blockers.

My interpreation of Ed's email was that we are to review
all 323 8.2.1 tickets tommorrow(!), not just the 15. Ed,
can you clarify?

Thanks,
~Deepak

-- 
 Deepak Saxena - Kernel Developer, One Laptop Per Child
   _   __o   (o>
---\<,  Give One Laptop, Get One Laptop  //\
 - ( )/ ( )  http://www.amazon.com/xoV_/_

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

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Martin Langhoff]

On Thu, Dec 11, 2008 at 4:19 PM, Anna  wrote:
> Will that work?  I need to keep the install steps to a minimum and I'd
> rather make the changes to the iso.

If you just grab the rpm and put it in the iso, it should work.
However, I might spin a 0.5.1 in the coming days. Just want to see if
there's any other major issue...

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
___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: 8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[pgf]

ed wrote:
 > Folks -
 > 
 > We¹re trying to get a very focused 8.2.1 release wrapped up to address a
 > small number of problems affecting or blocking key country deployments of
 > 8.2.  A few bugs have been tagged for an 8.2.1 milestone (fifteen of them),

i went looking for a canned report to find those 15 tickets for
me.  i found two:  http://dev.laptop.org/report/34 and 35.

clearly i don't understand how reports work, because they each
return 323 tickets, in different orderings, 8 of which are marked
as blockers.

how do i get that list of 15?

paul
=-
 paul fox, p...@laptop.org
 give one laptop, get one laptop --- http://www.laptop.com/xo
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Server-devel] Gadget fedora package

[Robert McQueen]

Martin Langhoff wrote:
> But I'm working on this space at the moment - switching away from the
> "all online users" patch that I suspect Guillaume is talking about and
> shifting to a different strategy using PostgreSQL.
> 
> So its "mostly behind us" (emphasis on mostly) as I mentioned but
> things are looking promising. The strategies I'm planning to use are
> in use by several large scale sites based on ejabberd with custom
> roster behaviours.

I thought about having the server subdivide people into smaller mutually
visible groups, particularly in G1G1 when having magic groups which try
and group by network proximity or random grouping is reasonable. It
works just because that the n^2 scalability problems are avoided by
simply making n smaller, but I still believe that approaches based
around shared rosters aren't ultimately the right thing to do.

Remember that what we're talking about isn't simply whether people can
see each other's presence or not, but that we rely on a bidirectional
presence subscription to use PEP to publish the extra OLPC-specific
properties of a buddy, as well as their currently active activity, all
of the activities they're running, and the properties of all of those
activities.

Problems with this:

 * It's further from what XMPP does normally because it continues and
   presumes/presupposes that the server knows best who should see each
   other. Gadget only publishes buddy information if they subscribe to
   it, and only publishes activities if it's invited to it, allowing
   fine-grained control, and for the other cases we should allow people
   to punch in JIDs or find people in activities/groups and make their
   own friendship subscriptions.

 * It's inefficient because every client in an activity ends up pushing
   PEP nodes with verbose details of their activities, when actually if
   the server had a concept of the activity it would only need to be
   aware of one copy of this information. That means when an activity
   changes its properties, you get the changed activity details N times,
   once for each participant. Gadget receives the activity details
   directly from the activity once only.

 * It's inefficient because the server pushes all of these to all
   clients in the mutually-visible group, even if that's too much
   information for the UI to display, or it's just not relevant because
   that view isn't open currently. Gadget pushes changes to only those
   people who are interested in a certain activity.

 * It precludes finer-grained visibility controls - you can't set up
   activities which are only visibile to certain groups of people
   without letting those people see all of your activities, or none.
   Although Gadget currently allows all people on a server to query an
   activity it's invited to, it gives us one place to implement
   functionality like sharing with certain groups or list of people.

 * You're limited to having subsets of people who are on one server, and
   because we need bi-directional subscriptions for PEP to work, both
   servers need to agree, so you really have very few options for
   including other people from other servers unless you start setting up
   a protocol by which servers inter-agree who should see each other on
   users' behalves. Seems pretty tricky...

Further to this Gadget offers:
 * Searches for buddies and activities are made out of all information
   available to Gadget, rather than people being split into different
   "silos". So even if people in different classes are using some niche
   activity, they can still find each other.

 * If server to server connections are enabled, its possible to invite a
   Gadget from another server (a partner school, for example) into an
   activity to make it searchable by people in the other school. We
   could even look at gadget<->gadget propogation of activities and
   buddies if we wanted to.

> cheers,
> 
> martin

Regards,
Rob

-- 
Robert McQueen +44 7876 562 564
Director, Collabora Ltd. http://www.collabora.co.uk

___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Raul Gutierrez Segales]

Will a new ISO (XS-0.5.1?) be released to address this issue? 


On Wed, 2008-12-10 at 18:51 -0200, Martin Langhoff wrote:
> On Wed, Dec 10, 2008 at 6:09 PM, Martin Langhoff > I spotted exactly
> the same difference and tested it -- does not seem
> > to work. Hope to get to the bottom of it.
> 
> Alright, fixed. Credit to Anna and Jerry for narrowing down on the issue.
> 
> The actual problem is laughably simple -- late in the dev cycle of 0.5
> a typo sneaked in. A minor edit of ifcfg-eth1 fixes it, see:
> 
> http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=acd64ab3d2342fbda08a944e31878db6b3b563f2
> 
> In any case, you can grab the rpm with the fix from
> 
> http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm
> 
> or perform
> 
> yum --enablerepo=olpcxstesting install xs-config
> 
> thanks everyone -- specially Anna -- for you help and patience.
> 
> cheers,
> 
> 
> 
> martin

___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Anna]

On Thu, Dec 11, 2008 at 12:04 PM, Martin Langhoff  wrote:

>
>  - we do respect sshd_config.in -- if you edit sshd_config.in, your
> changes will be preserved, and any new sshd_config.in we want to
> deploy will be written as sshd_config.in.rpmnew
>
>
Well, I did edit sshd_config.in and then did the make xs-config thing like I
was supposed to.  My changes were preserved in
/etc/ssh/sshd_config.in.rpmsave.

But going forward, and since I'm looking at possibly installing XS 0.5 on
quite a few machines here, before I burn the CD again, can I edit
/etc/sysconfig/network-scripts/ifcfg-eth1 on the iso like so:

(Edit this line to look like this)
 if [ "foo$XS_LANBOND_MAINXS_IPADDR" != "foo" ]; then
(Add this line)
HOTPLUG=yes

Will that work?  I need to keep the install steps to a minimum and I'd
rather make the changes to the iso.

Anna Schoolfield
Birmingham
___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: Wireless activation improvements.

[Martin Langhoff]

On Thu, Dec 11, 2008 at 4:01 PM, Michael Stone  wrote:
> If you boot a boot-locked machine with no valid lease, it will search
> for one on USB, SD, and the mesh. Therefore, while I agree that things
> would be nicer if leases were also renewed while the machine was
> running, it's obviously not preventing all use of the activation
> feature by our deployments.

I'm confused here. not sure what you mean to say. Perhaps I should say
that it's clear to me (and hopefully to Daniel too) that there are 2
different things being discussed

 - "initial activation" (what your proposed fix is about, and
generally within reach for 8.2.1)
 - "lease renewal" (what Daniel asks about -- involving a lot of work
to complete)

Both are closely related (and I am describing them with the
nomenclature from the scenario they support).

Having initial activation is good, even on its own -- we had in in an
earlier release.  I suspect this is what you are trying to say, and I
agree.

> Finally, don't you agree that there are
> lots of different ways to solve this problem that are within the reach
> of those deployments interested in pushing our activation technology
> along faster?

Not sure where you're trying to go... Yes, they can implement lease
renewal/blacklisting infrastructure themselves, as Uy has. I don't
think is a viable option for anyone but Uruguay, there are lots
ofdownsides to having it outside the signed initrd and I'm sure they
would have been happy spending their effort elsewhere.

So yes, someone else could do our job. But they won't, cause it's ours :-)



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
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Anna]

On Thu, Dec 11, 2008 at 10:09 AM, Martin Langhoff  wrote:

>
>yum --enablerepo=olpcxs-testing install xs-config
>
> which if you try now will bring xs-config-0.5.9.g13a7973-1.noarch.rpm
> which has two fixes. This has a further typo fix (that I had made in
> the script I tested, but forgot to include) and also sets it to be
> HOTPLUG=yes so if eth1 is slow to come up, it should work once it's
> up.
>
> let me know if it helps...


It worked for me, however, it looks like it returns a bunch of config files
to their "pristine" state, which isn't a big deal on this particular test
machine, as I had only edited sshd_config.in and sshd_config to allow for
password authentication.  This might be something users might want to be
aware of if they've been testing other stuff and have tweaked some of these
files.

Downloading Packages:
xs-config-0.5.9.g13a7973-1.noarch.rpm| 106 kB
00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : xs-config [1/1]
/etc /
# It may be dirty
xs-commitchanged -m 'Dirty state' rsyslog.conf
# Overwrite
cp -p rsyslog.conf.in rsyslog.conf
xs-commitchanged -m "Made from rsyslog.conf.in" rsyslog.conf
# It may be dirty
xs-commitchanged -m 'Dirty state' motd
# Overwrite
cp -p motd.in motd
xs-commitchanged -m "Made from motd.in" motd
xs-commitchanged -m 'Dirty state' sysctl.conf
cp -p sysctl.conf.in sysctl.conf
xs-commitchanged -m "Made from sysctl.conf.in" sysctl.conf
sysctl -p sysctl.conf
net.ipv4.ip_forward = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 1
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.shmmax = 268435456
# It may be dirty
xs-commitchanged -m 'Dirty state' ssh/sshd_config
# Overwrite
cp -p ssh/sshd_config.in ssh/sshd_config
xs-commitchanged -m "Made from ssh/sshd_config.in" ssh/sshd_config
Created commit bb554ba: Made from ssh/sshd_config.in - changed file
/etc/ssh/sshd_config
 1 files changed, 3 insertions(+), 3 deletions(-)
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/named
# Overwrite
cp -p sysconfig/named.in sysconfig/named
xs-commitchanged -m "Made from sysconfig/named.in" sysconfig/named
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/init
# Overwrite
cp -p sysconfig/init.in sysconfig/init
xs-commitchanged -m "Made from sysconfig/init.in" sysconfig/init
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/iptables-config
# Overwrite
cp -p sysconfig/iptables-config.in sysconfig/iptables-config
xs-commitchanged -m "Made from sysconfig/iptables-config.in"
sysconfig/iptables-config
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/squid
# Overwrite
cp -p sysconfig/squid.in sysconfig/squid
xs-commitchanged -m "Made from sysconfig/squid.in" sysconfig/squid
touch sudoers.tmp
chmod 640 sudoers.tmp
cat-parts sudoers.d > sudoers.tmp
chmod 440 sudoers.tmp
xs-commitchanged -m 'Dirty state' sudoers
mv -f sudoers.tmp sudoers
xs-commitchanged -m "Made from sudoers.d" sudoers
# It may be dirty
xs-commitchanged -m 'Dirty state' rssh.conf
# Overwrite
cp -p rssh.conf.in rssh.conf
xs-commitchanged -m "Made from rssh.conf.in" rssh.conf
# It may be dirty
xs-commitchanged -m 'Dirty state' php.ini
# Overwrite
cp -p php.ini.in php.ini
xs-commitchanged -m "Made from php.ini.in" php.ini
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/httpd
# Overwrite
cp -p sysconfig/httpd.in sysconfig/httpd
xs-commitchanged -m "Made from sysconfig/httpd.in" sysconfig/httpd
# It may be dirty
xs-commitchanged -m 'Dirty state' init.d/squid
# Overwrite
cp -p init.d/squid.in init.d/squid
xs-commitchanged -m "Made from init.d/squid.in" init.d/squid
# It may be dirty
xs-commitchanged -m 'Dirty state' sysconfig/ejabberd
# Overwrite
cp -p sysconfig/ejabberd.in sysconfig/ejabberd
xs-commitchanged -m "Made from sysconfig/ejabberd.in" sysconfig/ejabberd
xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth0
cp -p sysconfig/olpc-scripts/ifcfg-eth0 sysconfig/network-scripts/ifcfg-eth0
xs-commitchanged -m "Made from olpc-scripts"
sysconfig/network-scripts/ifcfg-eth0
xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth1
cp -p sysconfig/olpc-scripts/ifcfg-eth1 sysconfig/network-scripts/ifcfg-eth1
xs-commitchanged -m "Made from olpc-scripts"
sysconfig/network-scripts/ifcfg-eth1
# It may be dirty
xs-commitchanged -m 'Dirty state' httpd/conf.d/proxy_ajp.conf
# Overwrite
cp -p httpd/conf.d/proxy_ajp.conf.in httpd/conf.d/proxy_ajp.conf
xs-commitchanged -m "Made from httpd/conf.d/proxy_ajp.conf.in"
httpd/conf.d/proxy_ajp.conf
# It may be dirty
xs-commitchanged -m 'Dirty state' httpd/conf.d/ssl.conf
# Overwrite
cp -p httpd/conf.d/ssl.conf.in httpd/conf.d/ssl.conf
xs-commitchanged -m "Made from httpd/conf.d/ssl.conf.in"
httpd/conf.d/ssl.conf
Using default domain name
Setting the base dns name to random.xs.laptop.org
fin

8.2.1 Bug review meeting - 1 PM EST Friday 12/12/08

[Ed McNierney]

Folks -

We¹re trying to get a very focused 8.2.1 release wrapped up to address a
small number of problems affecting or blocking key country deployments of
8.2.  A few bugs have been tagged for an 8.2.1 milestone (fifteen of them),
and we have hit one critical enough to merit triggering a release (a
regression in wireless activation, Trac #8976
https://dev.laptop.org/ticket/8976).

I would like to review and discuss all tickets tagged with an 8.2.1
Milestone to ensure we understand the work and have a path forward to get an
update out quickly.  Please join an IRC discussion on #olpc-devel
(irc.freenode.net) at 1 PM Eastern time tomorrow (Friday, 12/12).  We will
walk through each of the tickets tagged with an 8.2.1 Milestone set.

Please review these tickets in Trac before the meeting and add comments as
necessary, especially if you can¹t attend the meeting.  If you have any
questions or need more information please let me know.  Thanks very much for
the help!

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

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Martin Langhoff]

On Thu, Dec 11, 2008 at 3:55 PM, Anna  wrote:
> It worked for me, however, it looks like it returns a bunch of config files
> to their "pristine" state, which isn't a big deal on this particular test
> machine, as I had only edited sshd_config.in and sshd_config to allow for
> password authentication.  This might be something users might want to be
> aware of if they've been testing other stuff and have tweaked some of these
> files.

Good to hear it works for you!

Yes, we do override some files -- including sshd_config. However

 - we store a copy in git to be able to retrieve it later
 - we do respect sshd_config.in -- if you edit sshd_config.in, your
changes will be preserved, and any new sshd_config.in we want to
deploy will be written as sshd_config.in.rpmnew

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
___
Server-devel mailing list
server-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: Wireless activation improvements.

[Greg Smith]

Hi Guys,

Lease management/renewal is a different feaure which I call Activation 
lease security. The requirements are written: 
http://wiki.laptop.org/go/Feature_roadmap#Activation_lease_security

Ethiopia and Peru have signed off that those requirements meet their 
needs and I am tracking it as a top priority for 9.1.0. I plan to run it 
by Uruguayan technical leads ASAP.

I mention Ethiopia in regards to initial Activation because they use a 
custom image and I know its painful to setup all the XOs via USB in a 
"warehouse".

Peru, Rwanda, Haiti and essentially all the large deployments will 
benefit from this feature, when its available (hopefully 8.2.1 but no 
confirmed date yet). That is, if they are willing to put an AP and a 
school server in their installation "warehouse".

We still have to tease apart in the "in school activation" case from the 
"warehouse" case. My impression is that they are always activated in the 
"warehouse" but that needs validation.

FYI, two other related features on the docket for 9.1 are:
Faster imaging
and
Image customization
in the section: 
http://wiki.laptop.org/go/Feature_roadmap#Security.2C_activation_and_deployability

Those are due for an update (preview: I plan to ask for one click XO 
image cloning) and another round of sanity check with engineers and 
users. I hope to get to that next week.

Thanks,

Greg S

Martin Langhoff wrote:
> On Thu, Dec 11, 2008 at 3:27 PM, Daniel Drake  wrote:
>> The primary use case that the Ethiopia team is interested in is
>> automating/simplifying the lease *renewal* which is done at schools,
>> not a warehouse.
> 
> Lease renewal is -- unfortunately -- missing big chunks in 8.2 . I
> don't think it's doable for 8.2.1. I'm trying to coordinate an effort
> (eith Ed's help) to team up with Michael and/or Scott to get this done
> as soon as 8.2.1 is out, with a target of 9.1 or (if people make a
> strong case for it) 8.2.2.
> 
> cheers,
> 
> 
> 
> m
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Wireless activation improvements.

[Michael Stone]

On Thu, Dec 11, 2008 at 03:35:53PM -0200, Martin Langhoff wrote:
>On Thu, Dec 11, 2008 at 3:27 PM, Daniel Drake  wrote:
>> The primary use case that the Ethiopia team is interested in is
>> automating/simplifying the lease *renewal* which is done at schools,
>> not a warehouse.
>
>Lease renewal is -- unfortunately -- missing big chunks in 8.2 . I
>don't think it's doable for 8.2.1. I'm trying to coordinate an effort
>(eith Ed's help) to team up with Michael and/or Scott to get this done
>as soon as 8.2.1 is out, with a target of 9.1 or (if people make a
>strong case for it) 8.2.2.

Martin,

If you boot a boot-locked machine with no valid lease, it will search
for one on USB, SD, and the mesh. Therefore, while I agree that things
would be nicer if leases were also renewed while the machine was
running, it's obviously not preventing all use of the activation
feature by our deployments. Finally, don't you agree that there are
lots of different ways to solve this problem that are within the reach
of those deployments interested in pushing our activation technology
along faster?

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

Re: Wireless activation improvements.

[Martin Langhoff]

On Thu, Dec 11, 2008 at 3:27 PM, Daniel Drake <[EMAIL PROTECTED]> wrote:
> The primary use case that the Ethiopia team is interested in is
> automating/simplifying the lease *renewal* which is done at schools,
> not a warehouse.

Lease renewal is -- unfortunately -- missing big chunks in 8.2 . I
don't think it's doable for 8.2.1. I'm trying to coordinate an effort
(eith Ed's help) to team up with Michael and/or Scott to get this done
as soon as 8.2.1 is out, with a target of 9.1 or (if people make a
strong case for it) 8.2.2.

cheers,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Wireless activation improvements.

[Daniel Drake]

On Thu, Dec 11, 2008 at 2:49 PM, Greg Smith <[EMAIL PROTECTED]> wrote:
> This is definitely a must have/must fix item for 9.1.0. It is needed by
> Ethiopia and other deployments. It may be used in a "warehouse" where
> the XOs are prepared as opposed to in a school where we assume there is
> less ability to change/tweak the AP ESSID. I'll try to get more feedback
> on that but right now my impression is that the primary use case is in a
> warehouse.

The primary use case that the Ethiopia team is interested in is
automating/simplifying the lease *renewal* which is done at schools,
not a warehouse.

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

Re: [Sugar-devel] Wacom Bamboo with XO?

[Wade Brainerd]

BTW, if any of you guys playing around with Colors! have access to multiple
XOs, I would love to hear how the collaboration feature is working (and what
you think about it).

-Wade

On Thu, Dec 11, 2008 at 8:07 AM, Wade Brainerd <[EMAIL PROTECTED]> wrote:

> Hi Chris,
>
> On Thu, Dec 11, 2008 at 7:05 AM, Chris Marshall <[EMAIL PROTECTED]
> > wrote:
>
>> I tried to get an image of my finished drawing
>> from the Journal but the only option was to
>> resume Colors!.  Then when it resumed it seemed
>> to hang.  I then clicked on Play and dragged
>> the slider to 100 and the image finally appeared.
>
>
> Gary Martin reported this too.  It's an issue that appeared when I stopped
> Colors! from pegging the CPU all the time.  There is an idle event that
> needs to be turned on when playback is running, it should be a simple fix.
>
>
>> Trying to reproduce the problem, I noticed that
>> if I move the stylus pointer while the program
>> was resuming, it looked like progress started to
>> be made or at least updates to the display.
>
>
> Yep, makes sense - the mouse events wake up the 'update' loop which allows
> the playback to make progress.  There should be an idle event doing this
> while playback is active.
>
> How can one get an image of the drawing for
>> sharing/printing/...?
>
>
> Git builds have a Copy button which copies the canvas to the clipboard.
> Note that Copy & Paste semantics will be slightly different from normal
> apps, in that Copy will copy the current canvas state, while Paste will
> paste into the Reference Image.
>
> I don't know if all wacom tablets have the same linear
>> resolution.  Ideally, the value for "Suppress" would be
>> calculated from the native tablet resolution and the
>> drawing area pixel dimensions.  e.g. a tablet with only
>> 1000lpi resolution might work better with a value of 25.
>
>
> Good point - It would be nice to be able to specify Suppress as a ratio
> that takes into account the screen resolution.  Perhaps a filter in the
> mouse event handler would be more effective after all, since it could just
> take into account the screen space movement when discarding events.
>
>
>> Maybe whiten the image slightly as if looking through
>> paper and make it easier to have it be a visual guide
>> independent of the drawing itself?
>
>
> Yeah, I will have to play with this to figure out how to make it most
> useful.
>
> You might keep track of the zoom center for each
>> level and then just pop the stack.  The problem
>> I had would not have occurred if the zoom in and
>> zoom out operations were inverses.
>
>
> Good idea!  Zoom in will remain the same (e.g. focus on the mouse cursor),
> but I will change Zoom out to pop the stack.
>
>  Maybe one of the Wacom buttons could be assigned to the Frame key event?
>>  Can this be done in xorg-dcon.conf?
>>
>
> I think the buttons look like mouse-ish events.  At any
>> rate they can be detected and acted upon.
>
>
> Perhaps we can map it to Mouse4 or some other obscure mouse button, and
> then patch Sugar to recognize that as the frame key.  That would actually be
> kind of nice for people with many-button mice to be able to open the Frame
> without reaching for the keyboard, since the Frame is mouse driven anyway.
>
> Best,
> Wade
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Martin Langhoff]

On Thu, Dec 11, 2008 at 12:54 PM, Reuben K. Caron <[EMAIL PROTECTED]> wrote:
> Alright, so I am still seeing problems.
>
> yum --enablerepo=olpcxstesting install xs-config , did not work for me.

Missing hyphen, my fault. Try

yum --enablerepo=olpcxs-testing install xs-config

which if you try now will bring xs-config-0.5.9.g13a7973-1.noarch.rpm
which has two fixes. This has a further typo fix (that I had made in
the script I tested, but forgot to include) and also sets it to be
HOTPLUG=yes so if eth1 is slow to come up, it should work once it's
up.

let me know if it helps...




m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: [Sugar-devel] Wacom Bamboo with XO?

[Wade Brainerd]

Hi Chris,

On Thu, Dec 11, 2008 at 7:05 AM, Chris Marshall
<[EMAIL PROTECTED]>wrote:

> I tried to get an image of my finished drawing
> from the Journal but the only option was to
> resume Colors!.  Then when it resumed it seemed
> to hang.  I then clicked on Play and dragged
> the slider to 100 and the image finally appeared.


Gary Martin reported this too.  It's an issue that appeared when I stopped
Colors! from pegging the CPU all the time.  There is an idle event that
needs to be turned on when playback is running, it should be a simple fix.


> Trying to reproduce the problem, I noticed that
> if I move the stylus pointer while the program
> was resuming, it looked like progress started to
> be made or at least updates to the display.


Yep, makes sense - the mouse events wake up the 'update' loop which allows
the playback to make progress.  There should be an idle event doing this
while playback is active.

How can one get an image of the drawing for
> sharing/printing/...?


Git builds have a Copy button which copies the canvas to the clipboard.
Note that Copy & Paste semantics will be slightly different from normal
apps, in that Copy will copy the current canvas state, while Paste will
paste into the Reference Image.

I don't know if all wacom tablets have the same linear
> resolution.  Ideally, the value for "Suppress" would be
> calculated from the native tablet resolution and the
> drawing area pixel dimensions.  e.g. a tablet with only
> 1000lpi resolution might work better with a value of 25.


Good point - It would be nice to be able to specify Suppress as a ratio that
takes into account the screen resolution.  Perhaps a filter in the mouse
event handler would be more effective after all, since it could just take
into account the screen space movement when discarding events.


> Maybe whiten the image slightly as if looking through
> paper and make it easier to have it be a visual guide
> independent of the drawing itself?


Yeah, I will have to play with this to figure out how to make it most
useful.

You might keep track of the zoom center for each
> level and then just pop the stack.  The problem
> I had would not have occurred if the zoom in and
> zoom out operations were inverses.


Good idea!  Zoom in will remain the same (e.g. focus on the mouse cursor),
but I will change Zoom out to pop the stack.

 Maybe one of the Wacom buttons could be assigned to the Frame key event?
>  Can this be done in xorg-dcon.conf?
>

I think the buttons look like mouse-ish events.  At any
> rate they can be detected and acted upon.


Perhaps we can map it to Mouse4 or some other obscure mouse button, and then
patch Sugar to recognize that as the frame key.  That would actually be kind
of nice for people with many-button mice to be able to open the Frame
without reaching for the keyboard, since the Frame is mouse driven anyway.

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

Re: mock.laptop.org repos repo

[Ties Stuij]

On Wed, Dec 10, 2008 at 3:55 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> I think upgrading to a newer version of git will solve the memory
> errors?  That was something that happened often with debian/stable-era
> git.

Hmm, I get the same errors from dev.laptop.org which has git version
1.5.3.8. Which is a bit lower than the one on the only box here that I
have access to which has a reasonable connection to the outside world.
I don't know about how far back you're talking about, but perhaps it
might mean dev.laptop.org should upgrade as well a bit? But since
crank is Ubuntu and you use the word 'era' on top of the phrase
'debian stable' (that's three times another phrase for old in one
word!) it really was an old version perhaps.

I also tried to reel in a snapshot .gz, but eventually the connection
timed out. Now the site can't even serve me a page anymore, so I'm
pretty much out of options. How big is this repository anyways,
with... what 26 thousand something package-blobs? Ah well, I don't
need it THAT much. I got the packages I need local. But if someone
would be willing to scp the dir over to dev.laptop or something, I
wouldn't be sad... If only for the frustration I feel not being able
to copy over a simple repo in this day and age (era).

/Ties

> If you've looked at the pilgrim repo, you'll have noticed that we
> export via http (w/ gitweb) as well.  There's a snapshot link at
>   http://mock.laptop.org/gitweb/?p=repos;a=summary
> and the individual packages are available via http as well.
>  --scott
>
> --
> ( http://cscott.net/ )
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Sugar-devel] Wacom Bamboo with XO?

[Chris Marshall]

Wade Brainerd wrote:
> Hey Chris, thanks for the feedback!  It's great to hear from people 
> using Colors! on XO.

You're welcome, Wade.

I tried to get an image of my finished drawing
from the Journal but the only option was to
resume Colors!.  Then when it resumed it seemed
to hang.  I then clicked on Play and dragged
the slider to 100 and the image finally appeared.

Trying to reproduce the problem, I noticed that
if I move the stylus pointer while the program
was resuming, it looked like progress started to
be made or at least updates to the display.

When I tried Play in with my current drawing
made via wacom tablet, the animation never
did complete.  I don't know if the problem
was me not waiting long enough or what

How can one get an image of the drawing for
sharing/printing/...?

> Yep, 60 works well enough though that it's probably not worth a 
> configuration option.  I will still work on optimizing the painting 
> performance though.

I don't know if all wacom tablets have the same linear
resolution.  Ideally, the value for "Suppress" would be
calculated from the native tablet resolution and the
drawing area pixel dimensions.  e.g. a tablet with only
1000lpi resolution might work better with a value of 25.

> I tried the earlier photo snap and it was awkward to toggle
> the underlying photo image.  It would be more helpful if the
> photo could be drawn over as if on tracing paper.  The toggle
> on/off would still be useful at different levels of refinement
> of the painting.
> 
> 
> That's a good idea.  When I reimplement Photo Snap, I'll do it that way 
> (so you are painting over it, e.g. the white background will show the 
> image when it's enabled).

Maybe whiten the image slightly as if looking through
paper and make it easier to have it be a visual guide
independent of the drawing itself?

> There appeared to be a problem with the Zoom in and
> out function as zooming all the way out, and then back in
> results in the canvas offset by various amounts.  I was not
> able to make it shift back without restarting the Activity.
> 
> 
> This should be documented better, or maybe have some visual feedback.  
> Zoom in & out keep the mouse cursor on the same point in the canvas 
> before and after the zoom operation.

You might keep track of the zoom center for each
level and then just pop the stack.  The problem
I had would not have occurred if the zoom in and
zoom out operations were inverses.

The 'Center image' toolbar button is great, too.

> Maybe one of the Wacom buttons could be assigned to the Frame key 
> event?  Can this be done in xorg-dcon.conf?

I think the buttons look like mouse-ish events.  At any
rate they can be detected and acted upon.

> I've got an old serial Intuos that I'll try to get configured
> this weekend.  I'll let you know how it goes...  If we get
> this working, maybe Amazon could add a "People who bought this
> item [the XO], also bought this [Wacom Bamboo]"...  :-)
> 
> 
> Great!  Thanks again for the feedback, I'll try to release a new version 
> before long with these suggestions.

Looking forward to it.

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

Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1

[Reuben K. Caron]

Alright, so I am still seeing problems. 

yum --enablerepo=olpcxstesting install xs-config , did not work for me.

So I:

-wget 
http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm

-yum localinstall xs-config-0.5.7.g11aaacf-1.noarch.rpm --nogpgcheck

- reran domain config
-check hostname
-restart

log file still shows:

Dec 11 09:33:06 schoolserver kernel: bonding: lanbond0 is being created...
Dec 11 09:33:06 schoolserver kernel: ADDRCONF(NETDEV_UP): lanbond0: link
is not ready

until I issue the:

-ifenslave lanbond0 eth1

which results in:

Dec 11 09:52:47 schoolserver kernel: bonding: lanbond0: enslaving eth1
as an active interface with an up link.
Dec 11 09:52:47 schoolserver kernel: ADDRCONF(NETDEV_CHANGE): lanbond0:
link becomes ready

and then dhcp works.



Martin Langhoff wrote:
> On Wed, Dec 10, 2008 at 6:09 PM, Martin Langhoff > I spotted exactly
> the same difference and tested it -- does not seem
>   
>> to work. Hope to get to the bottom of it.
>> 
>
> Alright, fixed. Credit to Anna and Jerry for narrowing down on the issue.
>
> The actual problem is laughably simple -- late in the dev cycle of 0.5
> a typo sneaked in. A minor edit of ifcfg-eth1 fixes it, see:
>
> http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=acd64ab3d2342fbda08a944e31878db6b3b563f2
>
> In any case, you can grab the rpm with the fix from
>
> http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm
>
> or perform
>
> yum --enablerepo=olpcxstesting install xs-config
>
> thanks everyone -- specially Anna -- for you help and patience.
>
> cheers,
>
>
>
> martin
>   

-- 
Reuben K. Caron
Country Support Engineer
One Laptop per Child
Mobile: +1-617-230-3893
[EMAIL PROTECTED]
Deployments Support 
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: Wireless activation improvements.

[Greg Smith]

Hi Michael,

This is definitely a must have/must fix item for 9.1.0. It is needed by 
Ethiopia and other deployments. It may be used in a "warehouse" where 
the XOs are prepared as opposed to in a school where we assume there is 
less ability to change/tweak the AP ESSID. I'll try to get more feedback 
on that but right now my impression is that the primary use case is in a 
warehouse.

I was treating it like a bug so it didn't have a full write up on the 
Feature page. I see there is some design needed so I'll make a section 
for it here: 
http://wiki.laptop.org/go/Feature_roadmap#Activation_lease_security

I'm not completely sure what you mean by "mesh" but if that refers to 
our Active Antenna (AA) I need to remind everyone that the AA is not a 
product right now, not supported and not available from OLPC. That may 
change in the future but right now its not being sold.

The bottom line is that wireless activation through an AP to the school 
server is a must have item for 9.1.0 which fits perfectly in the 
Deployability and Maintainability theme of the release.

Thanks,

Greg S

*

Date: Thu, 11 Dec 2008 11:18:47 -0200
From: "Martin Langhoff" <[EMAIL PROTECTED]>
Subject: Re: Wireless activation improvements.
To: "Michael Stone" <[EMAIL PROTECTED]>
Cc: devel@lists.laptop.org, Kim Quirk <[EMAIL PROTECTED]>,  Guadalupe
Artigas <[EMAIL PROTECTED]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Dec 10, 2008 at 11:33 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
 > > Therefore: do we have any
 > > interest in developing such a feature?

Yes, we want this.

The main thing with 802.11abg is that we need to pick an essid using a
reasonably stable mechanism. A few months ago we discussed the topic
of selecting an essid (on techteam - no archive link, sorry). The
summary I have of that conversation is that we can hardcode an essid
prefix or suffix and assoc to the first open signal matching it:

  - Local deployments will probably want to use an ESSID that means
"school" in a local language. (Sidenote: is utf-8 usable in ESSID
strings? Sorting/collation rules to pick "the first" matching utf-8
ESSID are a potential headache.)

  - An alternative is to just hardcode 'SCHOOLSERVER'. The same signal,
however, will be usually be used to associate to the XS, so it's
better that it has a localised name for when users pick it from the
'Network view'.

  - Mitch offered to code up a chooser UI, but it was later agreed it
was overkill.

  - The ad-hoc IPv4 self-assignment done for mesh is ugly but ok. The
XS will talk to IPv4 addresses in that range over mesh or abg.

  - This assumes the signal will be unencrypted. Supporting encryption
so early in the game adds a lot of complexity - complex WiFi setups
can broadcast an unencrypted ESSID for activation services, and an
encrypted signal for the rest of their traffic.

  - If/when we get a stable Libertas HostAP driver, we can teach the XS
to run such a dual-signal configuration if desired.

  - One thing to keep in mind: no matter what technique we use to pick
the ESSID, someone with an AP set to the same ESSID and channel can
DoS us and make a bit of a mess. There aren't any usable workarounds.
OTOH, we can tell good data from bad as is signed.

cheers,


m
-- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server 
Architect - ask interesting questions - don't get distracted with shiny 
stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Way to tell if it is an XO

[Marcel Renaud]

On Thu, Dec 11, 2008 at 11:51 AM, Martin Langhoff <[EMAIL PROTECTED]
> wrote:

> On Thu, Dec 11, 2008 at 11:46 AM, Marcel Renaud <[EMAIL PROTECTED]>
> wrote:
> > We decided to run the app on the XO end for various reasons, but It would
> be
> > good to authenticate against the school server and route messages through
> > the school server anyways.
>
> You might want to keep track of the discussion (on this same list)
> about Browse.xo and "SSO" to the XS.


Thanks,  I will.

>
> > Yes I am only working in Uruguay.
>
> Barbaro - yo estoy en Buenos Aires hasta el 7 de Enero si les interesa
> hablar.
>

Muchas gracias.

Saludos,

marcel

>
> abrazos,
>
>
>
> m
> --
>  [EMAIL PROTECTED]
>  [EMAIL PROTECTED] -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: 2588 - Journal unusable

[Mikus Grinbergs]

> I assume from your language that this is a regression, i.e. it worked
> six joyride builds ago? This wasn't clear from your original mail, but
> is valuable info to have. Can you recall the most recent working
> version?

The last time the Joyride Journal did not have the problem was build 
2581 from 12/07.  The problem showed up in build 2583 from 12/09. 
(Building of 2582 failed, without producing an image.)

mikus

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

Re: [Server-devel] Gadget fedora package

[Marco Pesenti Gritti]

On Thu, Dec 11, 2008 at 3:01 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> Note - I have *no* idea of what is that server running.
>
> But I'm working on this space at the moment - switching away from the
> "all online users" patch that I suspect Guillaume is talking about and
> shifting to a different strategy using PostgreSQL.
>
> So its "mostly behind us" (emphasis on mostly) as I mentioned but
> things are looking promising. The strategies I'm planning to use are
> in use by several large scale sites based on ejabberd with custom
> roster behaviours.

When you have something working, it would be good to setup a server
with it so that we can play with it and see how reliable it is and how
well it scales.

Marco
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] Gadget fedora package

[Martin Langhoff]

On Thu, Dec 11, 2008 at 11:54 AM, Marco Pesenti Gritti
<[EMAIL PROTECTED]> wrote:
> On Thu, Dec 11, 2008 at 2:51 PM, Marco Pesenti Gritti
> <[EMAIL PROTECTED]> wrote:
>>> With the "OMG! ejabberd's memory and roster mgmt are Out Of Control"
>>> thing mostly behind us, I want to have a clear picture of why and how
>>> Gadget fits into the picture. And at what (cpu, memory) cost,
>>> specially for the 3K users scenarios we're looking at.
>
> Just to share my experience. We was testing with
> schoolserver.media.mit.edu and we run into several presence
> inconsistencies, which Guillame says are shared roster bugs (I don't
> have the numbers anymore, unfortunately).

Note - I have *no* idea of what is that server running.

But I'm working on this space at the moment - switching away from the
"all online users" patch that I suspect Guillaume is talking about and
shifting to a different strategy using PostgreSQL.

So its "mostly behind us" (emphasis on mostly) as I mentioned but
things are looking promising. The strategies I'm planning to use are
in use by several large scale sites based on ejabberd with custom
roster behaviours.

cheers,



martin
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: 2588 - Journal unusable

[Simon Schampijer]

Daniel Drake wrote:
> On Thu, Dec 11, 2008 at 5:06 AM, Mikus Grinbergs <[EMAIL PROTECTED]> wrote:
>> The Journal entries do not show the object icon - so they cannot be
>> launched from.
>>
>> This SEVERE error has now lasted through five Joyride builds.
> 
> joyride builds are automatic. 5 builds is about 1 day. Please be a
> little more patient.
> 
> I assume from your language that this is a regression, i.e. it worked
> six joyride builds ago? This wasn't clear from your original mail, but
> is valuable info to have. Can you recall the most recent working
> version?
> 
>> I'm posting here, rather than write a ticket, as a way to get
>> quickest to those who can do something about it.  Or should users
>> who have real XOs (rather than emulators) stop participating ?
> 
> I'd suggest tickets for all bugs because they are harder to get lost
> (and soon will be triaged into appropriate priority). Then, for the
> important ones, feel free to raise extra attention on the mailing
> list.
> 
> But even if you do both, you may have to wait more than 1 day for a fix.

I am just making a new snapshot release of sugar since there were some 
deps of sugar-toolkit on the sugar package. What is helpful when writing 
those emails is always to have a quick look at the logs.

For the impatient ones: 
http://koji.fedoraproject.org/koji/taskinfo?taskID=993286

Thanks for the notice,
Simon
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Server-devel] Gadget fedora package

[Marco Pesenti Gritti]

On Thu, Dec 11, 2008 at 2:51 PM, Marco Pesenti Gritti
<[EMAIL PROTECTED]> wrote:
>> With the "OMG! ejabberd's memory and roster mgmt are Out Of Control"
>> thing mostly behind us, I want to have a clear picture of why and how
>> Gadget fits into the picture. And at what (cpu, memory) cost,
>> specially for the 3K users scenarios we're looking at.

Just to share my experience. We was testing with
schoolserver.media.mit.edu and we run into several presence
inconsistencies, which Guillame says are shared roster bugs (I don't
have the numbers anymore, unfortunately).

Marco
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] Gadget fedora package

[Marco Pesenti Gritti]

This is really a question for Collabora :) Ccing them...

On Thu, Dec 11, 2008 at 2:49 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> On Thu, Dec 11, 2008 at 9:43 AM, Marco Pesenti Gritti
> <[EMAIL PROTECTED]> wrote:
>> Just fyi, I submitted a gadget fedora package for review. It's going
>> to require ejabberd 2.0.2.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=475971
>
> When you have a bit of time, I am still keen on understanding how does
> Gadget fit in the wider picture.
>
> With the "OMG! ejabberd's memory and roster mgmt are Out Of Control"
> thing mostly behind us, I want to have a clear picture of why and how
> Gadget fits into the picture. And at what (cpu, memory) cost,
> specially for the 3K users scenarios we're looking at.
>
> In other words, we are finding that ejabberd is very amenable to
> having its behaviour changed in interesting ways with
>
>  - minimalistic Erlang plugins
>  - poking at its internal mnesia DB via the xml-rpc plugin
>  - using an external DB instead of Mnesia, and having external
> programs manipulate the DB
>
> all of these things keep us on using standard XMPP (so our client and
> server are more generic, and interchangeable) and from a scalability
> POV avoid adding additional processes (except for the DB).
>
> OTOH, I'm not against Gadget. It's just that it's a big unknown to me
> at a stage where -- without that much effort -- we seem to be getting
> ejabberd under control and playing nice.
>
> cheers,
>
>
>
> m
> --
>  [EMAIL PROTECTED]
>  [EMAIL PROTECTED] -- School Server Architect
>  - ask interesting questions - don't get distracted with shiny stuff
> - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: Way to tell if it is an XO

[Martin Langhoff]

On Thu, Dec 11, 2008 at 11:46 AM, Marcel Renaud <[EMAIL PROTECTED]> wrote:
> We decided to run the app on the XO end for various reasons, but It would be
> good to authenticate against the school server and route messages through
> the school server anyways.

You might want to keep track of the discussion (on this same list)
about Browse.xo and "SSO" to the XS.

> Yes I am only working in Uruguay.

Barbaro - yo estoy en Buenos Aires hasta el 7 de Enero si les interesa hablar.

abrazos,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Server-devel] Gadget fedora package

[Martin Langhoff]

On Thu, Dec 11, 2008 at 9:43 AM, Marco Pesenti Gritti
<[EMAIL PROTECTED]> wrote:
> Just fyi, I submitted a gadget fedora package for review. It's going
> to require ejabberd 2.0.2.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=475971

When you have a bit of time, I am still keen on understanding how does
Gadget fit in the wider picture.

With the "OMG! ejabberd's memory and roster mgmt are Out Of Control"
thing mostly behind us, I want to have a clear picture of why and how
Gadget fits into the picture. And at what (cpu, memory) cost,
specially for the 3K users scenarios we're looking at.

In other words, we are finding that ejabberd is very amenable to
having its behaviour changed in interesting ways with

 - minimalistic Erlang plugins
 - poking at its internal mnesia DB via the xml-rpc plugin
 - using an external DB instead of Mnesia, and having external
programs manipulate the DB

all of these things keep us on using standard XMPP (so our client and
server are more generic, and interchangeable) and from a scalability
POV avoid adding additional processes (except for the DB).

OTOH, I'm not against Gadget. It's just that it's a big unknown to me
at a stage where -- without that much effort -- we seem to be getting
ejabberd under control and playing nice.

cheers,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions - don't get distracted with shiny stuff
- working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: Way to tell if it is an XO

[Marcel Renaud]

Hey Martin!

The auth mechanism you mention is what we hoped for when we started working
on this project :) So I am glad there's ppl working on that! It will help
many other projects too, to have a reliable and secure auth mechanism to be
deployed on school servers.

We basically had to propose one ourselves for the project definition because
otherwise it wouldn't be approved but I personally think that having an auth
method based on the school server is the way to go !

We decided to run the app on the XO end for various reasons, but It would be
good to authenticate against the school server and route messages through
the school server anyways.

Yes I am only working in Uruguay.

Thanks a lot!

Marcel



On Thu, Dec 11, 2008 at 11:27 AM, Martin Langhoff <[EMAIL PROTECTED]
> wrote:

> 2008/12/10 Marcel Renaud <[EMAIL PROTECTED]>:
> > I will give you guys some background info on the project
> >
> > The goal of the proyect is to provide some way of communication beteween
> the
> > children who have an XO and their parents and family.
>
> Hi Marcel,
>
> the project sounds very interesting. We are planning on building an XO
> to XS (School Server) authentication mechanism that could give you the
> kind of authentication you are after. And it would be trivial to have
> webbased UI on the XS -- which already knows who the user is -- to
> send those messages (relaying them to your xml-rpm/soap service).
>
> I mention this as an alternative -- seems like you're on your way
> already in building something XO based, and that's a valid path too.
> But it's also a lot more work :-)
>
> Are you working in Uruguay only?
>
> cheers,
>
>
>
> martin
> --
>  [EMAIL PROTECTED]
>  [EMAIL PROTECTED] -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Way to tell if it is an XO

[Martin Langhoff]

2008/12/10 Marcel Renaud <[EMAIL PROTECTED]>:
> I will give you guys some background info on the project
>
> The goal of the proyect is to provide some way of communication beteween the
> children who have an XO and their parents and family.

Hi Marcel,

the project sounds very interesting. We are planning on building an XO
to XS (School Server) authentication mechanism that could give you the
kind of authentication you are after. And it would be trivial to have
webbased UI on the XS -- which already knows who the user is -- to
send those messages (relaying them to your xml-rpm/soap service).

I mention this as an alternative -- seems like you're on your way
already in building something XO based, and that's a valid path too.
But it's also a lot more work :-)

Are you working in Uruguay only?

cheers,



martin
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

[Server-devel] Gadget fedora package

[Marco Pesenti Gritti]

Just fyi, I submitted a gadget fedora package for review. It's going
to require ejabberd 2.0.2.

https://bugzilla.redhat.com/show_bug.cgi?id=475971

Marco
___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

[Server-devel] Chinese PE rattan outdoor furniture

[蔡成明]

Title: fmc







	
		
		

 Home
		   Coverall series
		   HOT
		   Leisure series
		   Color board series
		   Factory scene
		   Contact us
		
		
	
	
		
		we recommend our Chinese hand-made PE rattan outdoor furniture to you, 
		which are made in Guangzhou, China.
		The exquisitely made and moderately priced furniture will be interest of 
		you. our products have been widely sold to various markets abroad.
		We make the great importance to production quality and try to be perfect 
		in every process from materials chosen, handmade weaving to packing. We 
		enjoy good reputation and have good partnership with most customers from 
		most of regions and countries. The quality of our products receives 
		their praise.
		We believe that also demand for it at your end. In order to give you a 
		general idea of the scope of our business, now we enclose our website 
		for your reference.
		Please study it and let us know your comments, so that we can discuss 
		the business possibilities. If you will give us your specific inquiry, 
		that will be most welcome and reply you as soon as possible.(We cannot 
		read them if you reply us directly, please sent emalis to our email 
		address in our website)
		Warmly welcome to visit our factory. We will provide warm and thoughtful 
		all-round service. We sincerely hope that we can build mutual trust and 
		win-win cooperation in the long term. And we believe that our 
		cooperation will have a bright prospect in the future.
		We hope to hear from you soon.
		
		
		Contact 
		us：Mary Liu
		Guangzhou QianDu Co.,Ltd
		Tel：0086-20-85928531  
		Fax：0086-20-83692867
		Add：Jiangxia Industrial Park, Baiyun district, Guangzhou, China,510510
		
		
		
If 
you can not refer to the link and the photos above,pls look at this website：http://hi.baidu.com/frhub/blog/item/4e3c6f13506754d5f6039e73.html
	
	




___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel

Re: Wireless activation improvements.

[Martin Langhoff]

On Wed, Dec 10, 2008 at 11:33 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
> Therefore: do we have any
> interest in developing such a feature?

Yes, we want this.

The main thing with 802.11abg is that we need to pick an essid using a
reasonably stable mechanism. A few months ago we discussed the topic
of selecting an essid (on techteam - no archive link, sorry). The
summary I have of that conversation is that we can hardcode an essid
prefix or suffix and assoc to the first open signal matching it:

 - Local deployments will probably want to use an ESSID that means
"school" in a local language. (Sidenote: is utf-8 usable in ESSID
strings? Sorting/collation rules to pick "the first" matching utf-8
ESSID are a potential headache.)

 - An alternative is to just hardcode 'SCHOOLSERVER'. The same signal,
however, will be usually be used to associate to the XS, so it's
better that it has a localised name for when users pick it from the
'Network view'.

 - Mitch offered to code up a chooser UI, but it was later agreed it
was overkill.

 - The ad-hoc IPv4 self-assignment done for mesh is ugly but ok. The
XS will talk to IPv4 addresses in that range over mesh or abg.

 - This assumes the signal will be unencrypted. Supporting encryption
so early in the game adds a lot of complexity - complex WiFi setups
can broadcast an unencrypted ESSID for activation services, and an
encrypted signal for the rest of their traffic.

 - If/when we get a stable Libertas HostAP driver, we can teach the XS
to run such a dual-signal configuration if desired.

 - One thing to keep in mind: no matter what technique we use to pick
the ESSID, someone with an AP set to the same ESSID and channel can
DoS us and make a bit of a mess. There aren't any usable workarounds.
OTOH, we can tell good data from bad as is signed.

cheers,


m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Way to tell if it is an XO

[Marcel Renaud]

On Thu, Dec 11, 2008 at 5:37 AM, John Gilmore <[EMAIL PROTECTED]> wrote:

> > Basically we want to offer a service just for the Xos and are working now
> on
> > the authentication model.
>
> Why would you want to offer a service just for machines by one
> manufacturer?
>
> If a kid has an XO and also has a Mac, do you want your service to
> refuse to run on their Mac?  If so, why?  It seems to me like shooting
> the messenger.  Why would you fail to provide service to someone who
> only had a Windows machine, or a Fedora machine that didn't happen to
> be an XO?  What about an Ubuntu machine that DOES happen to be an XO,
> does it qualify?


I don't think you get the full picture of how things are here in Uruguay.
Our target users will be kids with and XO and 98% of them don't have another
computer. They don't have an internet connection at home, so I doubt there
is ONE of them that has a MAC.

Apart from that, it is not that I want to block every other hardware of
software, it is just a way of restricting the use to kids in the Plan
Ceibal(Olpc implementation in Uruguay) in order to make it commercially
viable. This will be a service that many companies will have expenses to
have it functioning and it is meant to be free just for those kids on plan
Ceibal.


>  And are you sure that next year's XO software and
> hardware will continue to meet your test?  Ultimately, what "is" an
> XO, for your purposes?  Would an XO not running Sugar still be an XO?
> Do you even know whether you *want* next year's XO to work with your
> service, or not?


I don't know if you read my last email but we aren't going to restrict the
use to just kids with XO by testing against hardware or software on the XO.
We will by installing a signed certificate on each XO. This is a much safer
way atought it adds complexity to the deployment.
We are going to use a shared certificate authority scheme following the
OASIS WSS standard.

>
> It's far better to make your system depend on the presence of
> *features* that you depend on.  If it needs a Python client, then ok,
> it doesn't run on machines without Python.  X Window System
> dependency, ok, it's clear that Mac and Windows users will have to go
> an extra mile to use it.  Test for features you actually need!  Then
> don't add extra tests for random features (like /ofw/model) that you
> DON'T actually need.


Our client app does depend on X, python and and some other libs inside the
XO

>
>
> Almost all the schemes I see like this are poorly thought through --
> like most vendors' DRM systems (the sort where they decommission the
> key server after a few years, then are surprised at the public
> protest, then change their mind).  Perhaps yours is not, but that
> would be noteworthy.


Thanks for your comments John

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

Re: New joyride build 2587

[Peter Robinson]

> Build Announcer v2 wrote:
>> -libraw1394 2.0.0-4.fc10
>> +libraw1394 2.0.0-5.fc10
>
> For all those XO's with firewire ports...
>
> (cups was also on the list.  I don't know if that's deliberate or not.)

Cups is being pulled in by libgnome which is due to xulrunner, but
with the talk of printing it will no doubt be needed eventually.
libraw I suspect is due to gstreamer, I'll have a look at that later,
i have gstreamer on my list to file bugs to get it broken down into
some sub packages for deps.

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

Re: 2588 - Journal unusable

[Daniel Drake]

On Thu, Dec 11, 2008 at 5:06 AM, Mikus Grinbergs <[EMAIL PROTECTED]> wrote:
> The Journal entries do not show the object icon - so they cannot be
> launched from.
>
> This SEVERE error has now lasted through five Joyride builds.

joyride builds are automatic. 5 builds is about 1 day. Please be a
little more patient.

I assume from your language that this is a regression, i.e. it worked
six joyride builds ago? This wasn't clear from your original mail, but
is valuable info to have. Can you recall the most recent working
version?

> I'm posting here, rather than write a ticket, as a way to get
> quickest to those who can do something about it.  Or should users
> who have real XOs (rather than emulators) stop participating ?

I'd suggest tickets for all bugs because they are harder to get lost
(and soon will be triaged into appropriate priority). Then, for the
important ones, feel free to raise extra attention on the mailing
list.

But even if you do both, you may have to wait more than 1 day for a fix.

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

New joyride build 2589

[Build Announcer v2]

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

Changes in build 2589 from build: 2588

Size delta: 0.00M

-bootfw q2e22-1.olpc2.unsigned
+bootfw q2f01-1.olpc2.unsigned

--- Changes for bootfw q2f01-1.olpc2.unsigned from q2e22-1.olpc2.unsigned ---
  + Built on new firmware build vhost on weka.laptop.org
  + USB - fixed bulk-in timeout setting; only seems to affect some USB CD-ROM 
drives.
  + USB - CDROM support.
  + NANDBlaster support. [http://wiki.laptop.org/go/Multicast_NAND_FLASH_Update 
details]
  + OLPC trac 8987 - Reinstated a missing Marvell quirk workaround
  + Erase SPI FLASH blocks just before writing them, as weak protection against 
bricking.
  + Attempt to make SD startup a little more robust by retrying if the first 
power-up attempt failed.
  + New EC version scheme to remove confusion with the system firmware version 
scheme.
  + Refactored EC code structure and large code cleanups
  + New build system based on wine
  + Quick power LED blink before power shut-off

--
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: Way to tell if it is an XO

[quozl]

Agreed, any software that tests to see if it is running on XO hardware
that has no dependency on the XO hardware is probably testing
unnecessarily.

-- 
James Cameronmailto:[EMAIL PROTECTED] http://quozl.netrek.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel