Build 542.3 out with local fixes

Please test as this will become the next stable build.

Build 542.3 fixes sugar so that it installed the translation files and
also fixes a Journal bug for the Spanish locale.

http://olpc.download.redhat.com/olpc/streams/development/build542.3/

--

-- 
John (J5) Palmieri <johnp <at> redhat.com>

Re: emergency server maintenance: 8/31

On Aug 31, 2007, at 5:19 PM, Ivan Krstić wrote:
> Public-facing development services (bugtracker, git, development
> hosting) are offline for emergency maintenance effective immediately,
> and for an expected duration of under 6 hours.

I'm extending this timeframe by up to another 12 hours, due to  
unexpected difficulties.

--
Ivan Krstić <krstic <at> solarsail.hcs.harvard.edu> | http://radian.org
_______________________________________________
Sugar mailing list
Sugar <at> lists.laptop.org
http://lists.laptop.org/listinfo/sugar

Re: [sugar] emergency server maintenance: 8/31

On Aug 31, 2007, at 11:47 PM, Ivan Krstić wrote:
> I'm extending this timeframe by up to another 12 hours, due to
> unexpected difficulties.

All services are up and looking good. If anyone notices something  
strange or broken, please let me know as soon as possible.

--
Ivan Krstić <krstic <at> solarsail.hcs.harvard.edu> | http://radian.org
_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: emergency server maintenance: 8/31

_______________________________________________
Sugar mailing list
Sugar <at> lists.laptop.org
http://lists.laptop.org/listinfo/sugar

Re: Build 542.3 out with local fixes

The os image should be named 'os5423.img' and 'os5423.crc'.  The FAT
filesystem will be unhappy with the double dots in the names given at
present, and the autoreinstallation script will thus refuse to install
them.
  --scott
--

-- 
                         ( http://cscott.net/ )

Re: Please test Xorg 1.4

On 8/31/07, Bernardo Innocenti <bernie <at> codewiz.org> wrote:

> > I also met the corrupted scrollbars in OS557.
> Is there a trac ticket for this bug?  It's pretty ugly when
I thought reading about this somewhere, but can't find in trac.
However, after the maintenance, I can't find the trac login link.
Anyway, I grab a screen shot of it in the attachment. This is only
seen in 16 bit mode, not in 24 bit mode. As to the broken flash shown
in the attachment, it seems to be a gnash bug for both 16 bit and 24
bit modes.

> In /home/olpc/.xinitrc, there's an "xset m default" line.
Thanks. It works.

--

-- 
Best regards,
Yuan Chao

_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Unable to update my machine

On 8/31/07, Mitch Bradley <wmb <at> laptop.org> wrote:

> FLASH device or a real disk?  We have seen some USB disks that take
> several seconds to detect.
Ok. Now I can confirm that it's a slow detection problem in my case.
Either holding the game key for 2+ sec or let the count down expires
then boot will make it work.

> When you hold down the game key to get the ok prompt, that gives the USB
> device a longer time between when USB power is applied and when
> enumeration starts - power is applied before the "Release the game key"
> message and enumeration happens afterwards, so you can control the time
> delay by holding the key longer.
>
> It should be possible to auto-boot by holding the key, then releasing
> it, then letting the countdown expire without typing the game key.
>
> You can also hold down a different game key, not the "X" one.  Any game
> key will trigger the "Release the game key" delay, but only the X key
> enables the OK prompt.
Thanks for the explanation.

--

-- 
Best regards,
Yuan Chao

Re: Please test Xorg 1.4

On Sep 1, 2007, at 5:07 AM, Yuan Chao wrote:

> However, after the maintenance, I can't find the trac login link.

I've diagnosed this and will have it fixed later in the day.

--
Ivan Krstić <krstic <at> solarsail.hcs.harvard.edu> | http://radian.org
_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel

Project Hosting Application

1. Project name             : XOIRC
2. Existing website, if any : ---
3. One-line description     :  Sugar Internet Relay chat.

4. Longer description       : A sugar IRC client based on URK/PURK
                            :
                            :
                            :

5. URLs of similar projects :

6. Committer list
   Please list the maintainer (lead developer) as the first entry. Only list
   developers who need to be given accounts so that they can commit to your
   project's code repository, or push their own. There is no need to list
   non-committer developers.

      Username   Full name             SSH2 key URL                    E-mail
      --------   ---------             ------------                    ------
   #1 edsiper   Eduardo Silva Pereira   already on d.l.o
edsiper <at> gmail.com
      ...

   If any developers don't have their SSH2 keys on the web, please attach them
   to the application e-mail.

7. Preferred development model

   [X] Central tree. Every developer can push his changes directly to the
       project's git tree. This is the standard model that will be familiar to
       CVS and Subversion users, and that tends to work well for most projects.

   [ ] Maintainer-owned tree. Every developer creates his own git tree, or
       multiple git trees. He periodically asks the maintainer to look at one
       or more of these trees, and merge changes into the maintainer-owned,
       "main" tree. This is the model used by the Linux kernel, and is
       well-suited to projects wishing to maintain a tighter control on code
       entering the main tree.

   If you choose the maintainer-owned tree model, but wish to set up some
   shared trees where all of your project's committers can commit directly,
   as might be the case with a "discussion" tree, or a tree for an individual
   feature, you may send us such a request by e-mail, and we will set up the
   tree for you.

8. Set up a project mailing list:

   [ ] Yes, named after our project name
   [ ] Yes, named ______________________
   [X] No

   When your project is just getting off the ground, we suggest you eschew
   a separate mailing list and instead keep discussion about your project
   on the main OLPC development list. This will give you more input and
   potentially attract more developers to your project; when the volume of
   messages related to your project reaches some critical mass, we can
   trivially create a separate mailing list for you.

   If you need multiple lists, let us know. We discourage having many
   mailing lists for smaller projects, as this tends to
   stunt the growth of your project community. You can always add more lists
   later.

9. Commit notifications

   [ ] Notification of commits to the main tree should be e-mailed to the list
       we chose to create above
   [ ] A separate mailing list, <projectname>-git, should be created for commit
       notifications
   [X] No commit notifications, please

10. Shell accounts

   As a general rule, we don't provide shell accounts to developers unless
   there's a demonstrated need. If you have one, please explain here, and
   list the usernames of the committers above needing shell access.

11. Notes/comments:

thanks.

Eduardo Silva.

Autoreinstallation problem --- current developer build

Autoreinstallation problem - 9/1/07

machine: B4
firmware: q2c25 and q2c26
build: 564

Hi all --- 'followed all the autoreinstallation instructions, plenty
of USB flash properly formatted as FAT; no partitions.  Several
successful autoreinstallations in past 4 weeks.

Firmware reinstalls fine, os564 installs fine until sugar comes up
with "name: " and then "click to change color" screens.

The function loops --- e.g. keeps asking me over and over "name:" and
"click to change color" and will not boot further.

Any ideas?  Has anyone experienced this.  I've tried alot of things
already.  I'll send in a ticket otherwise and try to downgrade to
build 552.

--

-- 
Regards,

Steve Fullerton
UCSD