Re: [IAEP] [ANNOUNCE] Sucrose 0.83.4 Development Release
Walter Bender wrote: Wow!! We have great release notes lately. To credit authors, I'd also append the patch summary by author, Linus-style. It can quickly be obtained this way: git log v0.83.3..HEAD | git-shortlog -- // Bernie Innocenti - http://www.codewiz.org/ \X/ Sugar Labs - http://www.sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [IAEP] [ANNOUNCE] Sucrose 0.83.4 Development Release
Bernie Innocenti wrote: Walter Bender wrote: Wow!! We have great release notes lately. To credit authors, I'd also append the patch summary by author, Linus-style. It can quickly be obtained this way: git log v0.83.3..HEAD | git-shortlog Excellent, will do that for the next release. So the command for sugar for this release would be (no-merges to get rid of the messages when you merge the master tree Merge branch 'master' of gitori...@git.sugarlabs.org:sugar/mainline): git log v0.83.4..v0.83.5 --no-merges | git-shortlog That will encourage people to write nice commit messages :) I would suggest to put up some guidelines (no rules), so a reader can more easily parse them. For example: - ticket number always at the beginning of the commit message - Start message with a capital letter - For typo fixes use: _Typo - For pylint fixes use: _Pylint More thoughts? Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem running Sugar on openSUSE 11.0
Jigish, I upgraded to open SUSE 11.1 last night, added the repositories and installed sugar and sugar-activities as you instructed. Everything seemed to install just fine, except that sugar-activities said it required etoys and that was not available. It did let me ignore this dependency and continue. When I tried to logout and log back in with a Sugar session instead of my usual WindowMaker the screen went black for a bit, then I found myself at the login prompt. I tried it a couple of times. Then I logged back in using WindowMaker and tried to run sugar at the command prompt. I got a stack trace with a message saying module hippo was not found. I went to Yast and found that there were a couple of Hippo Canvas RPMs that were not installed, so I tried installing those. Running sugar gave me this: sugar matchbox-window-manager: Failed to connect to session manager root window unavailible (maybe another wm is running?) /usr/lib/python2.6/site-packages/jarabe/desktop/meshbox.py:19: DeprecationWarnin g: the sha module is deprecated; use the hashlib module instead import sha Traceback (most recent call last): File /usr/bin/sugar-session, line 41, in module from jarabe.desktop.homewindow import HomeWindow File /usr/lib/python2.6/site-packages/jarabe/desktop/homewindow.py, line 24, in module from jarabe.desktop.meshbox import MeshBox File /usr/lib/python2.6/site-packages/jarabe/desktop/meshbox.py, line 35, in module from sugar.activity import activityfactory File /usr/lib/python2.6/site-packages/sugar/activity/activityfactory.py, lin e 29, in module from sugar.presence import presenceservice File /usr/lib/python2.6/site-packages/sugar/presence/presenceservice.py, lin e 32, in module from sugar.presence.activity import Activity File /usr/lib/python2.6/site-packages/sugar/presence/activity.py, line 27, i n module import telepathy ImportError: No module named telepathy I tried YAST again to see if telepathy was installed. It looked to me like it was. There were a few RPMs related to telepathy that I had not installed, but none of them looked relevant to Sugar so I didn't try to install them. So this is where I am now and I hope you can suggest something. I appreciate the work you put in creating this, by the way, even though I haven't got it working yet. My current Sugar test environment in on another machine running Xubuntu and while it was very easy to set up it is incomplete, buggy, and badly out of date. Also, it looks like your version of Sugar does not make use of Zephyr to run in a window like sugar-jhbuild does. I find being able to run multiple instances of the Sugar environment on the same box very useful for testing the sharing features that all Sugar activities should support. Is there a way to run what you have created this way? Thanks again, James Simmons Jigish Gohil wrote: On Mon, Jan 19, 2009 at 8:33 PM, James Simmons jim.simm...@walgreens.com wrote: Cyberorg, I recently upgraded my PC from openSUSE 10.2 to openSUSE 11.0. Hi Please update to openSUSE 11.1, add the following repositories before installing sugar and sugar-activities packages: http://download.opensuse.org/repositories/home:/cyberorg:/sugar/openSUSE_11.1 http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_11.1 http://download.opensuse.org/distribution/11.1/repo/oss/ Cheers -J ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem running Sugar on openSUSE 11.0
Jigish, I'm pretty sure that one is installed. The only telepathy stuff that was not installed was stuff for QT, IRC clients, etc. And python-telepathy and the hippo canvas stuff should be in the RPM dependencies and get installed automatically, wouldn't you think? Also, is there a way to run sugar from the command line and have it run in a window like sugar-jhbuild does? James Simmons Jigish Gohil wrote: On Thu, Jan 22, 2009 at 10:32 PM, James Simmons jim.simm...@walgreens.com wrote: 27, i n module import telepathy ImportError: No module named telepathy You are missing python-telepathy Ciao -J ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Activities vs. RPM
After watching the XO/RPM FUDCon video I had some ideas. This post summarizes them: http://ivazquez.livejournal.com/9390.html If you're at all involved with activities I'd like you to read it and share your thoughts. -- Ignacio Vazquez-Abrams ivazquez...@gmail.com PLEASE don't CC me; I'm already subscribed signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem running Sugar on openSUSE 11.0
Jigish, The only thing I ignored deps on *should* have been sugar-activities. However, tonight I will uninstall both RPMs using YAST, then reinstall only sugar and see what happens. I'll let you know. James Simmons Jigish Gohil wrote: On Thu, Jan 22, 2009 at 10:45 PM, James Simmons jim.simm...@walgreens.com wrote: Jigish, I'm pretty sure that one is installed. The only telepathy stuff that was not installed was stuff for QT, IRC clients, etc. And python-telepathy and the hippo canvas stuff should be in the RPM dependencies and get installed automatically, wouldn't you think? Not if you ignore deps when installing :) Also, is there a way to run sugar from the command line and have it run in a window like sugar-jhbuild does? Try dbus-launch sugar Ciao -J ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [IAEP] [ANNOUNCE] Sucrose 0.83.4 Development Release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jan 22, 2009 at 09:54:36AM +0100, Simon Schampijer wrote: So the command for sugar for this release would be [...]: git log v0.83.4..v0.83.5 --no-merges | git-shortlog That will encourage people to write nice commit messages :) I would suggest to put up some guidelines (no rules), so a reader can more easily parse them. For example: - ticket number always at the beginning of the commit message - Start message with a capital letter - For typo fixes use: _Typo - For pylint fixes use: _Pylint Use the recommended style as mentioned in Git documentation somewhere: First line a summary of at most 40 chars, then empty line, then optional detailed commit message (which is stripped by git-shortlog). Also, I'd suggest mentioning ticket numbers at end instead, in the style used by Debian. Example: Fix foobar - barbaz. Closes: SL#1234, OLPC#1235. The logic is to always prepend Closes: and then either SL# or # for each comma-separated ticket closed, or prepend OLPC# for tickets closed at the laptop.org bugtracker. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkl4irQACgkQn7DbMsAkQLgCDQCbBObD5vCNDLrGX3HNLNK1RvFg vokAniZd0hz/KXxZ2JhUf1Fr8s6me++e =4VCG -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem running Sugar on openSUSE 11.0
On Thu, Jan 22, 2009 at 10:32 PM, James Simmons jim.simm...@walgreens.com wrote: 27, i n module import telepathy ImportError: No module named telepathy You are missing python-telepathy Ciao -J ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problem running Sugar on openSUSE 11.0
On Thu, Jan 22, 2009 at 10:45 PM, James Simmons jim.simm...@walgreens.com wrote: Jigish, I'm pretty sure that one is installed. The only telepathy stuff that was not installed was stuff for QT, IRC clients, etc. And python-telepathy and the hippo canvas stuff should be in the RPM dependencies and get installed automatically, wouldn't you think? Not if you ignore deps when installing :) Also, is there a way to run sugar from the command line and have it run in a window like sugar-jhbuild does? Try dbus-launch sugar Ciao -J ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SoaS on the XO progress
Hi Marco, Some extra steps: * Clone git://git.fedoraproject.org/spin-kickstarts * If you want F10 apply spin.patch * Apply live.patch in /usr/lib/python2.5/site-packages/imgcreate * sudo yum -y install livecd-tools mtd-utils crcimg * If you're building on F10, s/ext4/ext3/ in fedora-live-base.ks * sudo livecd-creator --cache=cache -c fedora-livecd-desktop.ks I'm still not able to get the images I create to boot on the XO -- could you confirm that you're using the Fedora kernel and initrd? I wonder what else could be different between our setups.. Thanks! - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Notes from an impromptu 8.2.1 Release Mtg.
Hi folks, Kim Quirk kindly stopped by #olpc-meeting this evening and precipitated an impromptu discussion between herself, me, cjb, edmcnierney, mchua, and garycmartin on how to push 8.2.1 a few inches closer to release. The main conclusion that we reached after we updated http://dev.laptop.org/report/38 was that staging-9 [1] needs some testing! In particular, it's got long-awaited new wireless firmware and wifi kernel drivers which means that we need to know whether it still associates with your crazy encrypted access points. :) At any rate, the bottom line is that YOU can personally help 100k kids in Uruguay get access to 8.2.* faster by helping to test this build. (Guadalupe and Emiliano in Uruguay have already helped to test fixes for some of the issues they found in 8.2.0 but more (your!) testing help is still needed!) So, on that note, thanks very much in advance for any help that you can provide. Voluntarily yours, Michael P.S. - Bryan -- would you please update FiT with instructions for staging-9 wifi-testing? P.P.S. - I'd like to host a test party at 1cc sometime in the next two weeks to try to do some large-scale collaboration and wifi testing such as was requested by dsd [2] in preparation for his trip to Paraguay tomorrow [3]. Would interested people who might be in Boston in the next two weeks please mail me to let me know good days and times for them to come help test? P.P.P.S. - The major coding work left before we can wrap up 8.2.1 is currently resting on Mitch Bradley's capable shoulders [4]. I'm looking forward to receiving a new OFW snapshot from him for testing in the not-too-distant future. [1]: (http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build9/devel_jffs2) [2]: http://wiki.laptop.org/go/Profiles/DanielDrake -- dsd, update you profile! [3]: http://wiki.laptop.org/go/Deployment_meetings/20090120#Summary [4]: http://wiki.laptop.org/go/Profiles/wmb ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: SoaS on the XO progress
On Thu, 2009-01-22 at 18:01 -0500, Chris Ball wrote:
Hi Marco,
Some extra steps:
* Clone git://git.fedoraproject.org/spin-kickstarts
* If you want F10 apply spin.patch
* Apply live.patch in /usr/lib/python2.5/site-packages/imgcreate
* sudo yum -y install livecd-tools mtd-utils crcimg
* If you're building on F10, s/ext4/ext3/ in fedora-live-base.ks
* sudo livecd-creator --cache=cache -c fedora-livecd-desktop.ks
I'm still not able to get the images I create to boot on the XO -- could
you confirm that you're using the Fedora kernel and initrd? I wonder
what else could be different between our setups..
Thanks!
- Chris.
Chris what are you using for the /boot/olpc.fth file? I have luck using
the below, in that file, on a usb-drive:
\ Boot script for USB boot
hex rom-pa fffc7 + 4 $number drop h# 2e19 [if]
patch 2drop erase claim-params
: high-ramdisk ( -- )
cv-load-ramdisk
h# 22c +lp l@ 1+ memory-limit umin /ramdisk - .f000 and
( new-ramdisk-adr )
ramdisk-adr over /ramdisk move ( new-ramdisk-adr )
to ramdisk-adr
;
' high-ramdisk to load-ramdisk
[then]
: set-bootpath-dev ( -- )
/chosen find-package if ( phandle )
bootpath rot get-package-property 0= if ( propval$ )
get-encoded-string ( bootpath$ )
[char] \ left-parse-string 2nip( dn$ )
dn-buf place( )
then
then
/sd dn-buf count sindex 0= if
sd:
else
u:
then
BOOTPATHDEV $set-macro
;
set-bootpath-dev
text ks=hd:LABEL=XSRepo:/ks.cfg to boot-file
${BOOTPATHDEV}\boot\initrd.img expand$ to ramdisk
${BOOTPATHDEV}\boot\vmlinuz expand$ to boot-device
unfreeze
boot
The above code is found in the latest livecd-tools and is added if you
pass --XO on the cmdline. I'm booting the xs-05 installer with the above
code, you would have to edit:to boot-file for that boot arguments
you want and the vmlinuz and initrd.img lines or make links pointing to
the real files.
Jerry
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
