Re: debxo 0.3 release
Or, as I found out, if you have the developer key on a pen drive, you can boot into debxo from that, and copy develop.sig into /boot/security/, and have security enabled and debxo at the same time, should you want to. Thanks, all. I'll see what I can do about creating a wiki page if there isn't one already. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: debxo 0.3 release
Every time I try one of the debxo 0.3 or debxo 0.2 JFFS2 images, I get the error message [EMAIL PROTECTED]:75: Error writing to NAND FLASH and it fails. From 0.3, I've tried JFFS2 base and kde, and from 0.2 I've tried KDE. Same error message. I've re-downloaded the images, tried a md5sum on them (I can't find a md5sum for the images anywhere . . . could someone post them?). The steps I am taking to install debxo: - Install base 703 image - Download developer.sig and stick it in /security - Reboot and press ESC to get into OFW - In OFW, type update-nand sd:\imagename.img - Wait - Watch it fail If I'm not doing anything correctly, could someone help me out here? Thanks. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: debxo 0.3 release
I have updated the firmware to Q2E20, and that error message is gone. Instead, once its complete, and I try to boot into debxo, it gives me a sad face and powers off after 10 seconds. Is this because it's an unsigned build, and I have no devel key after the reflash? If so, how can I put a devel key onto an unbootable XO? Thanks. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Rainbow problems
I'm having a bit of trouble with Rainbow in one of the activities I'm writing, FiftyTwo. I've attached the logs that I'm getting, for reference. Basically, FiftyTwo worked on build 656, which did not have the Rainbow security system. Now that I've upgraded to 703, it no longer works. AFAIK, Rainbow is supposed to limit access outside of the temporary user it creates, and FiftyTwo is violating that and accessing ~/Activities/FiftyTwo.activity/data, which is apparently outside the scope that Rainbow allows. Anyone have any suggestions? KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Initial FiftyTwo release
I've released FiftyTwo onto the internet (finally . . .): wiki.laptop.org/go/Games/FiftyTwo Can anyone give me feedback on how I'm doing? Thanks, KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project submission: FiftyTwo
1. Project name : Tic-Tac-Toe
2. Existing website, if any :
3. One-line description : Tic-Tac-Toe for the XO
4. Longer description : A Tic-Tac-Toe game for the XO, using the actual
X
: and O from the front of the XO.
:
:
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 URLE-mail
- --
#1 kawk kawk Already submitted [EMAIL
PROTECTED]
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. Translation
[X] Set up the laptop.org Pootle server to allow translation commits to be
made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
I noticed this page: http://wiki.laptop.org/go/Tic_tac_toe , and decided to do
something about it. This is the result.
Thanks,
KAWK
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Sugar problems
I'm having a problem running Sugar on an amd64 linux computer. I downloaded and built Sugar using sugar-jhbuild, and using a hardlinked python in ~/bin. It built with no sugar-jhbuild warnings or errors (plenty of compiler warnings, nothing serious). I had a problem where it would say AttributeError: 'DeviceView' object has no attribute 'get_icon', but I fixed that fairly quickly by commenting out the lines that had the problem. A hackish fix, to be sure, but so far it seems to have worked. Now, I have a different problem. It says IOError: [Errno 2] No such file or directory: '/home/user/.sugar/default/datastore'. When I go mkdir -p ~/.sugar/default/datastore, I get a different error: (full error dump) Traceback (most recent call last): File /home/user/sugar/sugar-jhbuild/build/share/sugar/shell/view/Shell.py, line 93, in _start_journal_idle DBUS_PYTHON_TIMEOUT_UNITS_PER_SECOND) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/datastore.py, line 311, in mount return dbus_helpers.mount(uri, options, timeout=timeout) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/dbus_helpers.py, line 86, in mount return _get_data_store().mount(uri, options, timeout=timeout) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/sugar/datastore/dbus_helpers.py, line 39, in _get_data_store DS_DBUS_PATH), File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 244, in get_object follow_name_owner_changes=follow_name_owner_changes) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/proxies.py, line 237, in __init__ self._named_service = conn.activate_name_owner(bus_name) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 183, in activate_name_owner self.start_service_by_name(bus_name) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/bus.py, line 281, in start_service_by_name 'su', (bus_name, flags))) File /home/user/sugar/sugar-jhbuild/build/lib/python2.5/site-packages/dbus/connection.py, line 607, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /home/user/sugar/sugar-jhbuild/build/bin/datastore-service exited with status 1 I rebuilt the datastore module, to no avail. I get the same problem. It seems to be that datastore is not running or something, or is timing out on dbus. Any suggestions? I'm running a 2.6.23-amd64 kernel on a Centrino Dual-core with Debian Lenny (testing), updated yesterday. Thanks. KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
hippo-canvas, etc. not checking out properly?
I just noticed that ./sugar-jhbuild update fails on hippo-canvas (among others). Any suggestions why? Are the repos being updated or something? KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: hippo-canvas, etc. not checking out properly?
kawk wrote: I just noticed that ./sugar-jhbuild update fails on hippo-canvas (among others). Any suggestions why? Are the repos being updated or something? KAWK ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel Ach, never mind. My bad. Subversion was being upgraded as I was checking out, and therefore the /usr/bin/svn executable wasn't there. Sorry about that. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Project submission - FiftyTwo
1. Project name : FiftyTwo
2. Existing website, if any :
3. One-line description : A set of card games for the OLPC XO laptop
4. Longer description : FiftyTwo will be a set of card games for
the XO laptop,
: hopefully including games such as Hearts,
Crazy Eights,
: Solitaire, and Go Fish. Eventually,
multi-player mesh-games
: will be supported.
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 kawk
[EMAIL PROTECTED]
#2
#3
...
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. Translation
[X] Set up the laptop.org Pootle server to allow translation commits
to be made
[ ] Translation arrangements have already been made at ___
12. Notes/comments:
I've set up a Wiki page here: http://wiki.laptop.org/go/Activities/FiftyTwo
I would prefer not to release my name over the internet, so I have not
included my name in the developer list.
My ssh key is attached to this e-mail.
I may have submitted this project request already, but I'm not
completely sure if it went through. Sorry if it has.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
