New joyride build 2369
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2369 Changes in build 2369 from build: 2346 Size delta: 2.23M -totem-mozplugin 2.23.4-1.olpc3.5 +totem-mozplugin 2.23.4-1.olpc3.6 -sugar-journal 97-2.fc9 +sugar-journal 98-1.fc9 -etoys 3.0.2100-1 +etoys 3.0.2121-1 -gstreamer-python 0.10.11-2.fc9 +gstreamer-python 0.10.7-2.olpc3.1 -hulahop 0.4.3-1.olpc3 +hulahop 0.4.4-1.olpc3 -kernel 2.6.25-20080826.1.olpc.7bee90029d84945 +kernel 2.6.25-20080829.1.olpc.278a61522038c37 -ohm 0.1.1-6.17.20080805git.olpc3 +ohm 0.1.1-6.18.20080828git.olpc3 -bootfw q2e14-1.olpc2.unsigned +bootfw q2e15-1.olpc2.unsigned -gstreamer 0.10.19-1.fc9 +gstreamer 0.10.12-3.olpc3 -gstreamer-plugins-base 0.10.19-3.olpc3 +gstreamer-plugins-base 0.10.12-4.olpc3.4 -gstreamer-plugins-good 0.10.8-8.fc9 +gstreamer-plugins-good 0.10.5-7.olpc3.1 -gstreamer-tools 0.10.19-1.fc9 +gstreamer-tools 0.10.12-3.olpc3 -olpc-contents 2.4-1 +olpc-contents 2.5-1 -olpc-update 2.16-1 +olpc-update 2.17-1 -squeak-vm 3.10-3olpc8 +squeak-vm 3.10-3olpc10 -sugar 0.82.0-2.20080822git454def195d.fc9 +sugar 0.82.2-1.fc9 -sugar-artwork 0.82.0-1.fc9 +sugar-artwork 0.82.1-1.fc9 -sugar-base 0.82.1-1.fc9 +sugar-base 0.82.2-1.fc9 -sugar-toolkit 0.82.1-2.20080822git2e6be9ea55.fc9 +sugar-toolkit 0.82.3-1.fc9 -telepathy-gabble 0.7.6-2.olpc3 +telepathy-gabble 0.7.6-4.olpc3 -telepathy-salut 0.3.3-4.olpc3 +telepathy-salut 0.3.3-6.olpc3 -totem 2.23.4-1.olpc3.5 +totem 2.23.4-1.olpc3.6 -totem-gstreamer 2.23.4-1.olpc3.5 +totem-gstreamer 2.23.4-1.olpc3.6 -xorg-x11-server-Xorg 1.4.99.906-2.olpc3 +xorg-x11-server-Xorg 1.4.99.906-2.olpc3.2 -xorg-x11-server-common 1.4.99.906-2.olpc3 +xorg-x11-server-common 1.4.99.906-2.olpc3.2 -xulrunner 1.9-1.olpc3.3 +xulrunner 1.9-1.olpc3.4 -xulrunner-pyxpcom 1.9-1.olpc3.3 +xulrunner-pyxpcom 1.9-1.olpc3.4 -libsoup 2.4.1-1.fc9 -libvisual 0.4.0-6.fc9 -wavpack 4.50-1.fc9 --- Changes for sugar-journal 98-1.fc9 from 97-2.fc9 --- + 7588 Sugar should provide messages indicating when NAND is 'getting full' and 'critically full' + 6800 Journal window should be mirrored in RTL locales + correct Source0 field + translation updates for it, nl and ja + #7588 Show alert when available space is below 50MB + #6800 Reverse CollapsedEntry instead of BaseCollapsedEntry --- Changes for etoys 3.0.2121-1 from 3.0.2100-1 --- + updated translations: de, mn (#7976) + Fix crash in Russian locale (#8193) + Fix loggin errors (#6391) + Fix corrupted project names in Journal (#8199) + Fix Journal timestamps (#8176) + Automatically enable pango (#7610, #8163) + fix clipboard (#8199) + fix forward-direction and rotation-center halo issues (#8210) + various fixes (#7320, #7737, #8162, #8193, #8210) --- Changes for ohm 0.1.1-6.18.20080828git.olpc3 from 0.1.1-6.17.20080805git.olpc3 --- + #8010: Fix battery status by handling the EC mask over idle suspends. + #7879: Power down wifi chip when lid is closed and mesh is off. + #7986: Close /ofw/model after reading it. --- Changes for bootfw q2e15-1.olpc2.unsigned from q2e14-1.olpc2.unsigned --- + q2e15 this is an unsigned image + trac 8216 - Override persistent devkey when game-button-X is pressed, so you can run customization keys on a system with the dk tag. + New OFW font + Fix trac 8143 where suspend detection was broken after an auto power up reboot (ie a firmware reflash) + Fix typo in reading MAIN_ON pin. --- Changes for olpc-contents 2.5-1 from 2.4-1 --- + Changes to filename handling: no longer attempt to NFD/UTF-8 normalize + Trac #5805: improve memory usage of olpc-contents-create. --- Changes for olpc-update 2.17-1 from 2.16-1 --- + Trac #8190: make irsync_pristine more likely to work even if avahi is --- Changes for squeak-vm 3.10-3olpc10 from 3.10-3olpc8 --- + fix writing to stderr (#6391) + fix KedamaPlugin2 (exports where not listed) + fix show-source key + fix SEGFAULT in OggPlugin + add RomePlugin w/ Pango support + fix drag-n-drop + remove Mpeg3Plugin + fix dbus plugin not zero-terminating some strings + fix freeze in drag and drop + add analog input support + fix cursor keys + re-enable -O2 to get back speed (duh!) + handle view-source key + big merge with trunk + unicode key events + fixed dbus plugin + respect the TZ variable used by Sugar (#8176) --- Changes for sugar 0.82.2-1.fc9 from 0.82.0-2.20080822git454def195d.fc9 --- + 6929 Control panel: include copyright/licensing info in about dialogue + Fix some launcher issues + #2866 Network Manager GUI doesn't report success or failure + #3993 The color of network icon in Home view becomes white after restarting Sugar. + #2866 Network Manager GUI doesn't report success or failure + #7988 Sugar control panel doesn't have a language entry for kreyol + #7823 Non-modal alerts in CP remain when they shouldn't + #7733 Cannot install Wikipedia-10.xo + #7356 regression in activity view performance. + #7660 XO Neighborhood icon drawing amp; erase
Re: Write Collaboration - what is known to work / what is not?
Martin Langhoff wrote: We've had a few attempts to share Write ( http://wiki.laptop.org/go/Write ) with the Wellington test crowd, and there are a number of cases that don't seem to work well, but I'm not sure what the state of things is, and what is expected to work. The Wiki page doesn't say much either on what aspects of collaboration are working. I'm happy to file these as bugs, but I don't want to burden the tracker with stuff that is not in the design :-) In brief things work for the simple case, but for example - if the initial creator/sharer of the doc goes away, remaining users can continue editing, but don't 'share' the updates any more. There is no UI indication that things have changed. I *think* that's a limitation which will be addressed in a future version of abicollab. Mark? - Should invitees keep a copy in their journal and be able to resume it in private? I'm not sure to understand what you mean here. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Write Collaboration - what is known to work / what is not?
On Sat, 2008-08-30 at 10:47 +0200, Marco Pesenti Gritti wrote: Martin Langhoff wrote: We've had a few attempts to share Write ( http://wiki.laptop.org/go/Write ) with the Wellington test crowd, and there are a number of cases that don't seem to work well, but I'm not sure what the state of things is, and what is expected to work. The Wiki page doesn't say much either on what aspects of collaboration are working. I'm happy to file these as bugs, but I don't want to burden the tracker with stuff that is not in the design :-) In brief things work for the simple case, but for example - if the initial creator/sharer of the doc goes away, remaining users can continue editing, but don't 'share' the updates any more. There is no UI indication that things have changed. I *think* that's a limitation which will be addressed in a future version of abicollab. Mark? Yes, see my reply here: http://dev.laptop.org/ticket/8160#comment:2 It's *far* from trivial, so given that I'm implementing this in my spare time, I can't give a timeframe yet. - Should invitees keep a copy in their journal and be able to resume it in private? I'm not sure to understand what you mean here. If i understand correctly, this should already work. Every collaborator will get an entry in his/her journal automatically. Marc ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Survey of activity authors
I surveyed authors/maintainers of activities hosted in dev.laptop.org git over the past few weeks. The results are summarised at http://wiki.laptop.org/go/User:Morgs/Activities_survey I wish that your list were more of a reference document. [For instance, you have left off authors *you* know are keeping up-to-date -- but not everyone knows who is being active.] Plus, my list of interesting Activities is longer than yours. I presume that is because you have left off not only known active authors, but also not contactable authors. Nevertheless, if there was no response for Activities deemed useful, they ought to be listed centrally anyway -- in the hope that someone would step up and volunteer to follow up on what is happening with that Activity. It would also help if there were a compendium of contact information available. As it is, one has to search in the Activity's wiki page. [For instance, what is the address of the Map activity maintainer?] Thanks for a good job, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: How to get packages on the 8.2 branch?
On Fri, Aug 29, 2008 at 5:55 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: What do we need to do to get packages on the stable 8.2 branch? That's a good question. I assume we use the process we used for 8.1, which is that you create a trac bug naming the exact package you want and the reason for its inclusion, and assign it to ApprovalForUpdate. When Michael et al approve it, they assign it to me to pull into the stable repository. (This is documented on the wiki somewhere, but my internet access is poor at the moment. Maybe Michael can help.) I just fixed joyride this morning to pull from the dist-olpc3-devel tag in koji, fixing the issues we've had since the koji tags were reconfigured. If we use the Fedora process, there's a progression from dist-olpc3-devel to -testing to -updates, and you'd assign packages to the stable 8.2 branch by tagging them for -testing -- presumably after the same ApprovalForUpdate process. If I understand correctly, dist-olpc3-updates would be used only for 'released' builds, so moving from -testing to -updates would be a mostly-bookkeeping operation performed as part of the formal release of 8.2. In the same spirit, dist-olpc3-devel should be used only for packages which are *candidates* for 8.2, and the start of 9.1-related work should happen on dist-olpc4-devel. Perhaps 'faster' can be reopened on that branch for the time being. But all this is rather disruptive, and I'm not convinced it's an appropriate time to make the shift to the 'Fedora way'. My gut feeling would be to defer this until 9.1. In that case, I'd continue building the stable release for 8.2 from the git repo on http://mock.laptop.org/repos, which I'll manually add packages to as they are requested. Thoughts, comments, strong preferences? --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Faster build with XFCE
Can we turn faster back on with XFCE? I'm spending more time installing/configuring XFCE under joyride, than I am doing any real development. I'm working on power management, specifically with regards to dynamic idle suspend times based on user input vs WOL events. -- _ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] RFH - xs-rsync on F9 fails with an odd error
More fun to be had debugging! Rsync and xinetd - those two old friends - are not playing ball, and there error is not something I've ever seen before. So if you have an F9 machine and want to debug something (and hopefully help craft a patch). To start, add a repo to your F9 box pointing to http://fedora.laptop.org/xs/testing/olpc/7/i386 - keep it disabled by default - I don't want a yum update to switch your desktop machine into a school server. Not yet at least. Notes: - that repo contains a single dangerous package. Do NOT dare install xs-config - it will reconfigure your machine in unexpected ways. Everything else is pretty sane. - even if harmless, the packages here will create a directory called /library - assuming you don't have a /library dir you use, all is safe... 1 - From that repo, install xs-rsync, most dependencies are harmless, (see cleanup notes later). 2 - xs-rsync by default binds to an odd address, edit the bind address in /etc/xinet.d/xs-rsync so that it listens on localhost 3 - ah, magic moment: run `rsync rsync://localhost/` - normally, it should list one directory: 'builds' (this is from /library/xs-rsync/pub feel free to put something there). On my system, it errors out, and /var/log/messages talks about getpeeraddr errors, which I've never seen before. Nor has google :-/ 4 - ??? 5 - patch! Cleanup: - You will probably want to remove xinetd, incron, and usbmount if you are not otherwise using them. - rm /library if there is no content of yours there. 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 Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] RFH - xs-rsync on F9 fails with an odd error
On Sat, Aug 30, 2008 at 2:46 AM, Martin Langhoff [EMAIL PROTECTED] wrote: More fun to be had debugging! Rsync and xinetd - those two old friends - are not playing ball, and there error is not something I've ever seen before. [...] Well, it looks like fakechroot is the culprit, fwiw. If I take your configs and remove the fakechroot bit from the serverargs line: server_args = -i /library/xs-rsync/state/rsyncd.all -- /usr/bin/rsync --daemon --config /etc/xs-rsyncd.conf It works fine. I dunno anything much about fakechroot, though. -RN -- Robin Norwood The Sage does nothing, yet nothing remains undone. -Lao Tzu, Te Tao Ching ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] RFH - xs-rsync on F9 fails with an odd error
Argh, forgot replytoall again. On Sat, Aug 30, 2008 at 12:07 PM, Robin Norwood [EMAIL PROTECTED] wrote: On Sat, Aug 30, 2008 at 2:46 AM, Martin Langhoff [EMAIL PROTECTED] wrote: More fun to be had debugging! Rsync and xinetd - those two old friends - are not playing ball, and there error is not something I've ever seen before. [...] Well, it looks like fakechroot is the culprit, fwiw. If I take your configs and remove the fakechroot bit from the serverargs line: server_args = -i /library/xs-rsync/state/rsyncd.all -- /usr/bin/rsync --daemon --config /etc/xs-rsyncd.conf It works fine. I dunno anything much about fakechroot, though. Though I notice that rsync does some strange business to figure out the right args for getpeername() in configure.sh, and fakechroot seems to have it's own version of getpeername, et. al. so it's probably that getpeername from fakechroot uses different args than the system getpeername. And now I'm curious, so I'll poke around some more while the kids play Lego Indiana Jones. -RN -- Robin Norwood The Sage does nothing, yet nothing remains undone. -Lao Tzu, Te Tao Ching ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] RFH - xs-rsync on F9 fails with an odd error
On Sat, Aug 30, 2008 at 12:12 PM, Robin Norwood [EMAIL PROTECTED] wrote: Though I notice that rsync does some strange business to figure out the right args for getpeername() in configure.sh, and fakechroot seems to have it's own version of getpeername, et. al. so it's probably that getpeername from fakechroot uses different args than the system getpeername. Yeah, I can confirm that fakechroot's getpeername() is the problem. If I remove getpeername from fakechroot [1], then I get a fakechroot that works with your test [2]. Obviously we need to instead sort out the parameters to match the system getpeername like rsync does. Not really my area of expertise, but I can file a bug in RH bugzilla for fakechroot when I get back. Got to run, now. [1] http://rnorwood.fedorapeople.org/robin-fakechroot.patch [2] http://rnorwood.fedorapeople.org/fakechroot-2.8-13.fc9.2.i386.rpm -RN -- Robin Norwood The Sage does nothing, yet nothing remains undone. -Lao Tzu, Te Tao Ching ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] usb drive based installs.
Hi All: Here is a quick howto: Grab a usb flash drive, I chose a superstore core micro 2gb cost $11.19 cdn, no endorsement just the closest to my house. Insert the drive in to the usb port, mine became usb0 on the desktop, which is sdb1 in /dev. umount it, umount /dev/sdb1. toggle the bootable flag with fdisk, umount again. grab: http://members.shaw.ca/jvonau/pub/mkusbinstall run my mkusbinstall with: mkusbinstall path/to/iso /dev/path This creates a boot-able usb-drive based on the boot-able iso filename that was given. If you used a stock fedora boot.iso as the source, you could now boot the flash drive and do any installs except for harddrive based installs. To preform a usb drive based install you would need to use disc1 as the source and then copy over disc2-5 to the /iso on the drive. Patches welcome to enable an auto copy of the rest. With the kickstart file that I use, only about 500 packages are used by on disc1 and disc2, so I get away with the 2gb drive. If your usb size is large enough and have a filesystem to support it, I see no reason that you couldn't use the whole set, or use a dvd as the source. For XS, the plan is for one cd sized install disk so this should be no issue then. Just curious if pungi has to produces an iso that is larger that a cd then this should work anyway. Just can't burn the image to cdrom, just now it's a dvd.iso but still loopback mountable right? I'll play around later... Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] RFH: Script to make installable USB stick
Martin Langhoff wrote: On Fri, Aug 29, 2008 at 11:34 AM, Jerry Vonau [EMAIL PROTECTED] wrote: Need to see the usb's layout that you had in mind. You were trying to do tree-install or a iso source install? I'm thinking of applying it to the iso that Pungi creates. As far as I've seen, the main change is the renaming of isolinux. Might want to have a look at this thread: http://www.archivum.info/[EMAIL PROTECTED]/2008-05/msg00016.html I'm around for a couple of hours, See the usb based install thread. that seems to be on a different track -- you mentioned something yesterday about upgrade images. For now, plain installer CDs/USBs where anaconda has all the rpms needed for an install or an upgrade is what I am thinking of... That one is more for pre-populating the yum cache before a yum upgrade, or for an anaconda upgrade using the preupgrade hooks present in anaconda. Distribute the repo on a squashfs.img, with scripts that would mount the image, and start yum with a repo file pointing to the now local repo. In the anaconda case, that would be a bit different, but do-able. Just have to still test if there is space savings to be had before I look at anaconda. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] RFH - xs-rsync on F9 fails with an odd error
On Sat, Aug 30, 2008 at 12:28 PM, Robin Norwood [EMAIL PROTECTED] wrote: On Sat, Aug 30, 2008 at 12:12 PM, Robin Norwood [EMAIL PROTECTED] wrote: Yeah, I can confirm that fakechroot's getpeername() is the problem. If I remove getpeername from fakechroot [1], then I get a fakechroot that works with your test [2]. Obviously we need to instead sort out the parameters to match the system getpeername like rsync does. Not really my area of expertise, but I can file a bug in RH bugzilla for fakechroot when I get back. Got to run, now. Me again: https://bugzilla.redhat.com/show_bug.cgi?id=460753 Thanks, -RN -- Robin Norwood The Sage does nothing, yet nothing remains undone. -Lao Tzu, Te Tao Ching ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
