Re: Initial F14 developers-only release for XO and XO-1.5
On 09/01/2010 07:22 AM, Daniel Drake wrote: Hi, Hi Daniel, first of all - thanks for your excellent work! After seeing the community help significantly with F11-on-XO development, I'm wondering if we can do something similar for a future release. So, I've taken the first few steps in getting OLPC's technologies rebased on Fedora 14 and Linux v2.6.35. The result has lots of problems, but I figure that publishing the work so far is the first step in getting things fixed. Things are in such an early stage that I'm labelling this as a developers-only release. To name a few: Sugar crashes all the time, the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. For now, please don't file bugs unless you include patches. And, to take 1 bite at a time out of this huge task, lets ignore all but the biggest sugar issues for now because there is plenty of OS work to be done first. (or alternatively lets take sugar issues directly to SL trac) And the links: 2.6.35 kernel is in git://dev.laptop.org/olpc-2.6 branch olpc-2.6.35 OS build is done from 'f14' branch of olpc-os-builder First released images are at http://build.laptop.org/F14/os1/ Trac is at http://dev.laptop.org/milestone/F14 (basically my immediate TODO), please don't file tickets unless you include patches in these early days Note: I haven't tested those exact images (since Chris @ OLPC built them), so boot-testing them can be the first task for someone. I have been working from the same codebases making local images successfully, so they will probably work (to the extent that things are working). The XO-1.0 build does boot fine here. After installing the latest sugar package [1] I get quite good results. This is very promising. Yay!!! The XO-1.5 build does not boot for me, I get the following after flashing the image: Boot device: /wlan Argumenst: Scan for: OLPCOFW not found Scan for: school-mesh-0 not found Scan for: school-mesh-1 not found Scan for: school-mesh-2 not found buf...@ff83b080:0: Can't open boot device Anyone else booted the XO-1.5 image already? Regards, Simon [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=193501 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
The XO-1.5 build does not boot for me, I get the following after flashing the image: Boot device: /wlan Argumenst: Scan for: OLPCOFW not found Scan for: school-mesh-0 not found Scan for: school-mesh-1 not found Scan for: school-mesh-2 not found buf...@ff83b080:0: Can't open boot device Anyone else booted the XO-1.5 image already? I have booted the XO-1.5 image but did not use OFW to install it. Since I am running it from an SDHC card I manually extracted the filesystems onto the card. I have an updated kernel rpm that fixes a few of initial bugs that needed squashing with the XO 1.5. I can post that if people want to do extended testing. That error looks like OFW is not finding a bootable device. What output do you get if you do dir int:\boot\ from the OFW prompt? -Jon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 09/11/2010 04:20 PM, Jon Nettleton wrote: The XO-1.5 build does not boot for me, I get the following after flashing the image: Boot device: /wlan Argumenst: Scan for: OLPCOFW not found Scan for: school-mesh-0 not found Scan for: school-mesh-1 not found Scan for: school-mesh-2 not found buf...@ff83b080:0: Can't open boot device Anyone else booted the XO-1.5 image already? I have booted the XO-1.5 image but did not use OFW to install it. Since I am running it from an SDHC card I manually extracted the filesystems onto the card. I have an updated kernel rpm that fixes a few of initial bugs that needed squashing with the XO 1.5. I can post that if people want to do extended testing. Sure! Keep it rolling :) That error looks like OFW is not finding a bootable device. What output do you get if you do dir int:\boot\ from the OFW prompt? -Jon Thanks Jon for following up and sharing the command. It helped to find out that the bootfw package was missing. Daniel will do a new build. Regards, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 09/02/2010 07:43 PM, Mikus Grinbergs wrote: In Terminal, cursor movement keys don't work. [I also saw interference to Terminal (white background) from dmesg? lines (black background), after each boot -- but these would go away if I just restarted Sugar.] This could be X using the xfree86 keycodes instead of the evdev ones. What does setxkbmap -v say? 0 [olpc]# setxkbmap -v Trying to build keymap using the following components: keycodes: evdev+aliases(qwerty) types: complete compat: complete symbols:pc+us(olpc)+inet(evdev)+terminate(ctrl_alt_bksp) geometry: pc(pc104) 0 [olpc]# By the way, in Terminal 'vi' appears to be placing the text it shows onto a NON-EMPTY screen - there is present background text from what had in the past been shown on the Terminal screen. If I want to look at something, I now use 'cat' (which has blank background) instead of 'vi'. Among the non-starters were Chat and TamTam. Could you determine why? Activity output logs attached. Chat fails because no attribute _pservice. This has been fixed in git: http://git.sugarlabs.org/projects/chat/repos/mainline/commits/997ca380edbc59bbae1da9950369d3f50ffa6991 Aleksey will do a new release. Regards, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
Chat fails because no attribute _pservice. This has been fixed in git: http://git.sugarlabs.org/projects/chat/repos/mainline/commits/997ca380edbc59bbae1da9950369d3f50ffa6991 With that change applied on an XO-1 system to the Chat-66 on os1, I was able to collaborate with an XO-1 system running Chat-66 on os604dx, plus an XO-1 system running Chat-65 on os856, plus an XO-1 system running Chat-48 on build 802 -- that's a four-way-chat collaboration, using regular mesh, NOT ad-hoc. [By the way, Chat on the os604dx system still worked, even after I applied the pippy_apps.py fix there, as well.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Sat, 2010-09-11 at 16:47 -0500, Mikus Grinbergs wrote: With that change applied on an XO-1 system to the Chat-66 on os1, I was able to collaborate with an XO-1 system running Chat-66 on os604dx, plus an XO-1 system running Chat-65 on os856, plus an XO-1 system running Chat-48 on build 802 -- that's a four-way-chat collaboration, using regular mesh, NOT ad-hoc. [By the way, Chat on the os604dx system still worked, even after I applied the pippy_apps.py fix there, as well.] Out of curiosity... what's build os604dx? :-) -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
Out of curiosity... what's build os604dx? I meant os406dx. I'm getting frequent senior moments - and more and more often I don't spot that what I've actually typed is not what I should have typed. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Sun, Sep 5, 2010 at 10:57 AM, Bernie Innocenti ber...@codewiz.org wrote: El Sun, 05-09-2010 a las 00:53 +0100, pbrobin...@gmail.com escribió: Well I am for SoaS related things which while isn't XO hardware related it does affect everything further up the stack does that not count :-( Such parallel efforts are indeed mutually beneficial. Dextrose also enjoyed the pioneering packaging and testing effort carried on on 0.88 by the SoaS folks, plus the platform stabilization work done by dsd, pgf and cjb. Isn't this the normal thing in FLOSS development? No point as its directly Fedora related but if people could add positive karma to this it would be fixed quicker, else in about 4-5 days it will head to F-14 stable. https://admin.fedoraproject.org/updates/gnome-python2-desktop-2.31.1-5.fc14 Done, but I'm afraid I had to give it negative karma: Looking at the upstream GIT of evince it looks like this is another of the apis that have been deprecated upstream and Read needs to be updated to fix the issue http://git.gnome.org/browse/evince/diff/libdocument/ev-selection.h?id=18d2af9bce80392407fae997c8dfa029f5a54123 Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Mon, 06-09-2010 a las 11:49 +0100, pbrobin...@gmail.com escribió: Done, but I'm afraid I had to give it negative karma: Looking at the upstream GIT of evince it looks like this is another of the apis that have been deprecated upstream and Read needs to be updated to fix the issue http://git.gnome.org/browse/evince/diff/libdocument/ev-selection.h?id=18d2af9bce80392407fae997c8dfa029f5a54123 To keep the testing cycle shorter, couldn't you just build the rpms locally and test them once on your system before pushing them to bodhi? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Mon, Sep 6, 2010 at 10:46 PM, Bernie Innocenti ber...@codewiz.org wrote: El Mon, 06-09-2010 a las 11:49 +0100, pbrobin...@gmail.com escribió: Done, but I'm afraid I had to give it negative karma: Looking at the upstream GIT of evince it looks like this is another of the apis that have been deprecated upstream and Read needs to be updated to fix the issue http://git.gnome.org/browse/evince/diff/libdocument/ev-selection.h?id=18d2af9bce80392407fae997c8dfa029f5a54123 To keep the testing cycle shorter, couldn't you just build the rpms locally and test them once on your system before pushing them to bodhi? I don't maintain that package. I also don't maintain Read. The gnome-python2 package I did update was just re-enabling the upstream. In that regard i did test the gnome-python2 package but but not against Read as where I was in the world at the time I didn't have a working F-14 system to hand with X working so its pretty hard to. At the moment I've worked every day in the last month and I've being travelling around Europe at least once a week so I'm battling to have time to do the basic stuff and I didn't believe I'm the only person in the sugar testing world. The problem isn't evince or gnome-python2 but that Read needs to be updated again for the new upstream evince api changes (again). Looking in Read git the last tagged release is Read 79 yet on a.sl.o is Read 86. I'm not sure what the rest of the changes are or which version is correct so going on the official Read 79 release it wouldn't work any way. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 6 September 2010 15:59, pbrobin...@gmail.com pbrobin...@gmail.com wrote: The problem isn't evince or gnome-python2 but that Read needs to be updated again for the new upstream evince api changes (again). You're right in that Read changes are needed, but there is already a git tree floating around with such changes (that still need a bit of work). However the problem that Bernie pointed out is different, and will continue to occur even after updating Read. The file installed by gnome-python2-evince is broken. that is, the following simple command will fail: python -c 'import evince' It is probably a bug in the upstream code. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Mon, 06-09-2010 a las 22:59 +0100, pbrobin...@gmail.com escribió: I don't maintain that package. I also don't maintain Read. The gnome-python2 package I did update was just re-enabling the upstream. In that regard i did test the gnome-python2 package but but not against Read as where I was in the world at the time I didn't have a working F-14 system to hand with X working so its pretty hard to. At the moment I've worked every day in the last month and I've being travelling around Europe at least once a week so I'm battling to have time to do the basic stuff and I didn't believe I'm the only person in the sugar testing world. Sorry, didn't mean to sound like I did not appreciate your packaging work. Let me know how I could help, besides testing (although I'm also spreading myself very thin, as you know). The problem isn't evince or gnome-python2 but that Read needs to be updated again for the new upstream evince api changes (again). Looking in Read git the last tagged release is Read 79 yet on a.sl.o is Read 86. I'm not sure what the rest of the changes are or which version is correct so going on the official Read 79 release it wouldn't work any way. Sayamindu may know. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Sun, 05-09-2010 a las 00:53 +0100, pbrobin...@gmail.com escribió: Well I am for SoaS related things which while isn't XO hardware related it does affect everything further up the stack does that not count :-( Such parallel efforts are indeed mutually beneficial. Dextrose also enjoyed the pioneering packaging and testing effort carried on on 0.88 by the SoaS folks, plus the platform stabilization work done by dsd, pgf and cjb. Isn't this the normal thing in FLOSS development? No point as its directly Fedora related but if people could add positive karma to this it would be fixed quicker, else in about 4-5 days it will head to F-14 stable. https://admin.fedoraproject.org/updates/gnome-python2-desktop-2.31.1-5.fc14 Done, but I'm afraid I had to give it negative karma: ---cut--- Traceback (most recent call last): File /usr/bin/sugar-activity, line 21, in module main.main() File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 115, in main module = __import__(module_name) File /home/bernie/Activities/Read.activity/readactivity.py, line 25, in module import evince ImportError: /usr/lib64/python2.7/site-packages/gtk-2.0/evince.so: undefined symbol: ev_selection_get_selection_map Exited with status 1, pid 5410 data (None, open file 'fdopen', mode 'w' at 0x261a150, 'c9a33f84910d7499496f16cb75f4a930a1f234d4') ---cut--- -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
For now, please don't file bugs unless you include patches. I can understand not wanting bug reports against items which OLPC/Sugar are still in the process of changing. But why defer reporting problems which might not be addressed unless there was a report ? For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. mikus Traceback (most recent call last): File /usr/bin/sugar-activity, line 21, in module main.main() File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 115, in main module = __import__(module_name) File /home/olpc/Activities/Read.activity/readactivity.py, line 25, in module import evince ImportError: /usr/lib/python2.7/site-packages/gtk-2.0/evince.so: undefined symbol: ev_selection_get_selection_map 1283617092.832518 DEBUG root: _cleanup_temp_files Exited with status 1, pid 1919 data (None, open file 'fdopen', mode 'w' at 0x94ff5f8, 'cc1399fc91616fa81d576acdc0389304f4e8bce9') ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Sat, Sep 4, 2010 at 4:24 AM, Mikus Grinbergs mi...@bga.com wrote: For now, please don't file bugs unless you include patches. I can understand not wanting bug reports against items which OLPC/Sugar are still in the process of changing. But why defer reporting problems which might not be addressed unless there was a report ? Just to take a stab at answer Because Daniel is tired. He has been on the road for months/years solving other peoples problems. Now he is spending some time (I hesitate to call it 'free' time) working on a project which is personally interesting while generously sharing it with the world. If anyone wants to set up a formal bug tracker... and work on those bugs I am sure Daniel would be happy to work _with_ them. But for now, he has enough on his hands. Based on his track record for getting things done, I am inclined to give Daniel the benefit of the doubt that what he is doing will become the basis of a future software release! david For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. 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: Initial F14 developers-only release for XO and XO-1.5
But why defer reporting problems which might not be addressed unless there was a report ? Just to take a stab at answer Because Daniel is tired. Are other developers really so tied up that THEY can't look at bug reports ? Why would Daniel need to be involved when (for instance) an Activity had a problem ? [I thought others, not Daniel, were doing the Activities.] Not only does Daniel's new release use F14 -- it is the *first* release (I know of) with Sugar-0.89 that can install onto the jffs2 in an XO-1. I thought SugarLabs might be interested, ahead of releasing 0.90, how it would run on the XO -- I would think the sooner 0.90-precursor bugs were reported, the greater the chance of those bugs being addressed. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 4 September 2010 03:24, Mikus Grinbergs mi...@bga.com wrote: For now, please don't file bugs unless you include patches. I can understand not wanting bug reports against items which OLPC/Sugar are still in the process of changing. But why defer reporting problems which might not be addressed unless there was a report ? Because nobody other than me is fixing the problems right now, and the bugs will go stale. And if someone is available to fix bugs, you only have to spend 5 minutes working with the image to encounter several of them. A bug tracker is needless overhead for such early and loose development. This of course will change with time, if the project continues to progress. For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. As this is a topic purely related to Sugar you are welcome to file a bug on the SL bug tracker, or start a discussion on the sugar mailing list. I should also clarify that if you have an easy solution for a bug (such as: add package XYZ) you are welcome to file a bug - by only file bugs with patches I guess I meant only file bugs with patches or simple solutions I'm just trying to focus and organize the OS-level work, and to avoid wasting time on bug tracking in this early stage. Thanks for working with me on this... Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
Hi Mikus, On 4 Sep 2010, at 10:24, Mikus Grinbergs mi...@bga.com wrote: For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. FWIW, long story, and much traffic about this. The evince API has radically changed. Read was/is broken on distros that shipped the new evince. Lucian very kindly took some time out from his Browse/Surf web kit work to update Read (he had been already working with new evince for PDF support). I think the only feature regression was that of Epub support (works, but the toolbars have been disabled until it's also hooked into the new API — on my todo but quite far down and quite complicated for me). ... and just to complicate matters the git rep mainline (which Lucian updated to support the new evince) is at version 79 — no idea where 87 came from, looks like releases have been made from some other rep/branch, so am not sure what other changes happened 78 - 87, yes it's a mess :-( When I last tested, the current version in git is good for F14 (excluding the above Epub UI regression). Regards, --Gary mikus Traceback (most recent call last): File /usr/bin/sugar-activity, line 21, in main.main() File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 115, in main module = __import__(module_name) File /home/olpc/Activities/Read.activity/readactivity.py, line 25, in import evince ImportError: /usr/lib/python2.7/site-packages/gtk-2.0/evince.so: undefined symbol: ev_selection_get_selection_map 1283617092.832518 DEBUG root: _cleanup_temp_files Exited with status 1, pid 1919 data (None, ', mode 'w' at 0x94ff5f8, 'cc1399fc91616fa81d576acdc0389304f4e8bce9') ___ 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: Initial F14 developers-only release for XO and XO-1.5
For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to
'import evince'. Though the necessary gnome-python2-evince package was
not included in the os1 build, when I manually install that package from
the yum Fedora-14 repositories, the import statement still fails --
apparently because the evince.so module provided by the current
Fedora-14 package has internal inconsistencies. I myself do not have a
Python test case which does 'import evince' - nor do I have a patch -
but perhaps the maintainers of the Read Activity might want to discuss
this situation with the maintainers of Python on Fedora 14.
As this is a topic purely related to Sugar you are welcome to file a
bug on the SL bug tracker, or start a discussion on the sugar mailing
list.
Daniel - I deliberately posted to fedora-olpc-list with a
hard-to-pin-down situation (in hopes that someone other than you would
read it). The error in this case (shown in the log attached to my post)
is ImportError: /usr/lib/python2.7/site-packages/gtk-2.0/evince.so:
undefined symbol: ev_selection_get_selection_map.
I expect that Sugar's invocation ('import evince') has not changed since
F11, where it works. But the called 'evince.so' module is smaller in
F11 (and has other install dependencies), whereas it has grown to three
times that size in F14. Is it kosher to file a bug against Sugar
because something *called* by Sugar has (in the version fetched by 'yum'
when running build os1) a problem in F14 ? I don't know the answer.
nobody other than me is fixing the problems right now
Bummer. I do think that problems with the 'evince.so' that came from an
F14 yum repository ought to be off your radar.
I'm just trying to focus and organize the OS-level work, and to avoid
wasting time on bug tracking in this early stage.
My question assumed that if a symptom shows up in 'Object Chooser' in
0.90 (which the XO-1 installs with F14), then bug tracking would not
need to be performed SEPARATELY for F14 than the bug tracking already
being done for 0.84 (which is included in, say, Milestone 10.0.3).
If nobody other than you looks at things uncovered in os1 but unrelated
to construction of an F14 build that will run on the XO -- then I
guess I would describe their attitude as problems are real only if they
show up in 'officially released' builds. Oh well.
mikus
p.s. My most obvious problem at first with os1 was the inability to use
the keyboard arrow keys in 'vi' in Terminal (I switched to using the
hjkl keys instead); plus the presence of garbage text in the background
of the 'vi' screen. Also, I couldn't get to a text console.
Eventually, I went into 'My Settings' - 'Keyboard' and specified a more
appropriate keyboard model. That seemed to activate the ctl-alt-Fn
sequence that allows me to get into a text console -- and now in a text
console 'vi' works properly with os1.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Sat, Sep 4, 2010 at 10:24 AM, Mikus Grinbergs mi...@bga.com wrote: For now, please don't file bugs unless you include patches. I can understand not wanting bug reports against items which OLPC/Sugar are still in the process of changing. But why defer reporting problems which might not be addressed unless there was a report ? For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. This is a known problem with Read at the moment. I fixed the package the other day and its filtering through the updates-testing. There's a number of fairly large number of issues with Fedora 14 at the moment due to the new systemd and python 2.7 not to mention some quite big gnome related changes. We're preparing the SoaS 4 release based on this as well so the SoaS team are aware of a number of issues and we're working as quickly as possible to fix them (but the 3 people in the team are also very busy with other life related things as well) and this will benefit this release as well because both teams can work towards the same goal. Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Sat, Sep 4, 2010 at 3:56 PM, Daniel Drake d...@laptop.org wrote: On 4 September 2010 03:24, Mikus Grinbergs mi...@bga.com wrote: For now, please don't file bugs unless you include patches. I can understand not wanting bug reports against items which OLPC/Sugar are still in the process of changing. But why defer reporting problems which might not be addressed unless there was a report ? Because nobody other than me is fixing the problems right now, and the bugs will go stale. And if someone is available to fix bugs, you only have to spend 5 minutes working with the image to encounter several of them. A bug tracker is needless overhead for such early and loose development. Well I am for SoaS related things which while isn't XO hardware related it does affect everything further up the stack does that not count :-( This of course will change with time, if the project continues to progress. For instance, Read-87 fails to launch on XO-1 os1 (F14) when it tries to 'import evince'. Though the necessary gnome-python2-evince package was not included in the os1 build, when I manually install that package from the yum Fedora-14 repositories, the import statement still fails -- apparently because the evince.so module provided by the current Fedora-14 package has internal inconsistencies. I myself do not have a Python test case which does 'import evince' - nor do I have a patch - but perhaps the maintainers of the Read Activity might want to discuss this situation with the maintainers of Python on Fedora 14. As this is a topic purely related to Sugar you are welcome to file a bug on the SL bug tracker, or start a discussion on the sugar mailing list. No point as its directly Fedora related but if people could add positive karma to this it would be fixed quicker, else in about 4-5 days it will head to F-14 stable. https://admin.fedoraproject.org/updates/gnome-python2-desktop-2.31.1-5.fc14 I should also clarify that if you have an easy solution for a bug (such as: add package XYZ) you are welcome to file a bug - by only file bugs with patches I guess I meant only file bugs with patches or simple solutions I'm just trying to focus and organize the OS-level work, and to avoid wasting time on bug tracking in this early stage. Thanks for working with me on this... Daniel ___ olpc mailing list o...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/olpc ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Wed, 01-09-2010 a las 07:57 -0500, Mikus Grinbergs escribió: the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. I recommend rebasing on the geode driver 2.11.9, which was just released by upstream. I've been testing it in Dextrose for about 3 weeks: it fixes all the known rendering bugs and has no regressions. The XO-1 os1 build already has xorg-x11-drv-geode-2.11.9-1.fc14.olpc1 This package is not in Fedora's git, though. I'll ask Dave Arlie if it's ok with him to update the package. I'm sure he'll be glad to hand-off this driver to someone who can actually test it. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Wed, 01-09-2010 a las 05:03 -0500, Mikus Grinbergs escribió: In Terminal, cursor movement keys don't work. [I also saw interference to Terminal (white background) from dmesg? lines (black background), after each boot -- but these would go away if I just restarted Sugar.] This could be X using the xfree86 keycodes instead of the evdev ones. What does setxkbmap -v say? Could not use text console (alt-ctl-Fn combo appears to be ignored). Same XKB misconfiguration, prolly. Among the non-starters were Chat and TamTam. Could you determine why? They do work with Sugar 0.88 on F11. So probably we have ABI issues in Fedora 14. (suppressed rant about Sugar not using a proper packaging system) Thank you muchly for your great leap forward, mikus Thank you very much for all the testing you've been doing. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
In Terminal, cursor movement keys don't work. [I also saw interference to Terminal (white background) from dmesg? lines (black background), after each boot -- but these would go away if I just restarted Sugar.] This could be X using the xfree86 keycodes instead of the evdev ones. What does setxkbmap -v say? 0 [olpc]# setxkbmap -v Trying to build keymap using the following components: keycodes: evdev+aliases(qwerty) types: complete compat: complete symbols:pc+us(olpc)+inet(evdev)+terminate(ctrl_alt_bksp) geometry: pc(pc104) 0 [olpc]# By the way, in Terminal 'vi' appears to be placing the text it shows onto a NON-EMPTY screen - there is present background text from what had in the past been shown on the Terminal screen. If I want to look at something, I now use 'cat' (which has blank background) instead of 'vi'. Among the non-starters were Chat and TamTam. Could you determine why? Activity output logs attached. Chat fails because no attribute _pservice. TamTam (all) crash. (shell.log excerpt attached) 'dmesg' says: TamTamMini 20c[1374]: segfault at b4bcd0 ip b665c4c2 sp bffa6250 error 7 in aclient.so[b6659000+b000] mikus p.s. I don't know if this is from my own customization, or if it came in the build -- but now Telepathy uses accounts within salut -- with the consequence that sometimes other systems are told the account's nickname for the system, instead of the nickname I specified to Sugar. ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) 1283506233.148647 DEBUG root: Calling GetActivity on /org/freedesktop/Telepathy/Account/salut/local_xmpp/account0 1283506233.218902 DEBUG root: There's no shared activity with the id afab4a658c90608fdbbe67141afecc6572021389 1283506233.220666 DEBUG root: *** Act afab4a658c90608fdbbe67141afecc6572021389, mesh instance None, scope private 1283506233.11 DEBUG root: Creating a jobject. 1283506233.229101 DEBUG root: datastore.write 1283506233.320121 DEBUG root: Written object 050759b1-6189-4b6a-ae41-bd755eb47957 to the datastore. 1283506234.155120 WARNING root: No gtk.AccelGroup in the top level window. 1283506234.187794 WARNING root: No gtk.AccelGroup in the top level window. Traceback (most recent call last): File /usr/bin/sugar-activity, line 21, in module main.main() File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 151, in main create_activity_instance(activity_constructor, activity_handle) File /usr/lib/python2.7/site-packages/sugar/activity/main.py, line 37, in create_activity_instance activity = constructor(handle) File /home/olpc/Activities/Chat.activity/pippy_app.py, line 80, in __init__ self.owner = self._pservice.get_owner() AttributeError: 'Chat' object has no attribute '_pservice' 1283506234.211332 DEBUG root: _cleanup_temp_files Exited with status 1, pid 1363 data (None, open file 'fdopen', mode 'w' at 0xaaf2498, 'afab4a658c90608fdbbe67141afecc6572021389') ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) 1283506334.676009 DEBUG root: Debug Level 0 1283506334.678066 DEBUG root: INFO: loaded TAMTAM_ROOT=/home/olpc/Activities/TamTamMini.activity 1283506335.281234 DEBUG root: skip /home/olpc/Activities/TamTamMini.activity/common/Util/Clooper/linux32_508 blobs: libcsound.so.5.1: cannot open shared object file: No such file or directory 1283506336.042935 DEBUG root: use /home/olpc/Activities/TamTamMini.activity/common/Util/Clooper/linux32_510 blobs 1283506339.601604 DEBUG root: Calling GetActivity on /org/freedesktop/Telepathy/Account/salut/local_xmpp/account0 1283506339.641105 DEBUG root: There's no shared activity with the id 20cf741a8c22ea39bbad5c09709214b01010bfb7 1283506339.642871 DEBUG root: *** Act 20cf741a8c22ea39bbad5c09709214b01010bfb7, mesh instance None, scope private 1283506339.644349 DEBUG root: Creating a jobject. 1283506339.651074 DEBUG root: datastore.write 1283506339.714733 DEBUG root: Written object b9045a30-f5db-4f51-8867-a66ad8e2bdb9 to the datastore. 1283506340.288413 WARNING root: No gtk.AccelGroup in the top level window. 1283506340.348108 WARNING root: No gtk.AccelGroup in the top level window. Logging disabled on purpose Terminated by signal 11, pid 1374 data (None, open file 'fdopen', mode 'w' at 0xa10f758, '20cf741a8c22ea39bbad5c09709214b01010bfb7') 1283506301.850570 DEBUG root: _key_pressed_cb: 69 0 F3 1283506301.863164 WARNING root: No gtk.AccelGroup in the top level window. 1283506301.865592 WARNING root: No gtk.AccelGroup in the top level window. 1283506301.895693 DEBUG root: new zoom level: 2 /usr/bin/sugar-session:264: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as amp; gtk.main() 1283506314.953176 DEBUG root: Activity afab4a658c90608fdbbe67141afecc6572021389 has been closed already. 1283506328.565523 DEBUG
Re: Initial F14 developers-only release for XO and XO-1.5
Disclaimer: I am not asking for help; I am just sharing my experience. I noticed - perhaps because of the Sugar 0.90 'Remove_Presence_Service' feature - THREE separate icons in F14 Neighborhood for one-and-the-same XO-1 system (which runs os852). Admittedly, that system can be simultaneously accessed from the F14 system via TWO different IP addresses (192.168.1.16 on ethernet, plus 169.254.8.104 on mesh) -- but three separate Neighborhood icons for that single system seem excessive. For now, please don't file bugs unless you include patches. I'll wait until bugs without patches are acceptable. And I need to be able to recreate the situation - I don't know how easy that will be. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Thu, 02-09-2010 a las 01:07 +0200, Bernie Innocenti escribió: rpm -Uvh http://download.sugarlabs.org/dextrose/testing/dxo2/rpms/i386/os/xorg-x11-drv-geode-2.11.9-1.fc14.i586.rpm The .fc14 is my mistake, this package is actually built for Fedora 11. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Thu, Sep 2, 2010 at 4:26 PM, Bernie Innocenti ber...@codewiz.org wrote: El Thu, 02-09-2010 a las 01:07 +0200, Bernie Innocenti escribió: rpm -Uvh http://download.sugarlabs.org/dextrose/testing/dxo2/rpms/i386/os/xorg-x11-drv-geode-2.11.9-1.fc14.i586.rpm The .fc14 is my mistake, this package is actually built for Fedora 11. Ah! I was wondering about that! 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
Hey Daniel, Yippee! I suspect the sugar starting issues is the same one we're seeing in SoaS for F-14. I'm very busy until Sunday but i hope to have at least some time to be able to look at that problem and help you out where possibly as no doubt both SoaS and the builds for the XO will share a lot of common problems. With the kernel nearing a recent release is there any plans to get a chunk of the kernel patches upstream to ease on going maintenance? As always ping me if there's anywhere specific I can be of assistance in upstream Fedora. Peter On Wed, Sep 1, 2010 at 6:22 AM, Daniel Drake d...@laptop.org wrote: Hi, After seeing the community help significantly with F11-on-XO development, I'm wondering if we can do something similar for a future release. So, I've taken the first few steps in getting OLPC's technologies rebased on Fedora 14 and Linux v2.6.35. The result has lots of problems, but I figure that publishing the work so far is the first step in getting things fixed. Things are in such an early stage that I'm labelling this as a developers-only release. To name a few: Sugar crashes all the time, the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. For now, please don't file bugs unless you include patches. And, to take 1 bite at a time out of this huge task, lets ignore all but the biggest sugar issues for now because there is plenty of OS work to be done first. (or alternatively lets take sugar issues directly to SL trac) And the links: 2.6.35 kernel is in git://dev.laptop.org/olpc-2.6 branch olpc-2.6.35 OS build is done from 'f14' branch of olpc-os-builder First released images are at http://build.laptop.org/F14/os1/ Trac is at http://dev.laptop.org/milestone/F14 (basically my immediate TODO), please don't file tickets unless you include patches in these early days Note: I haven't tested those exact images (since Chris @ OLPC built them), so boot-testing them can be the first task for someone. I have been working from the same codebases making local images successfully, so they will probably work (to the extent that things are working). At this point this is all something put together by me in my spare time. It's not known if or when OLPC would start working on an official release from these efforts. But I figure that if we get things properly stabilized and all the work is done cleanly, we'll find one way or another to get this in the hands of deployments. Daniel ___ 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: Initial F14 developers-only release for XO and XO-1.5
This is awesome news, kudos to Daniel. On Wed, Sep 1, 2010 at 08:49, pbrobin...@gmail.com pbrobin...@gmail.com wrote: Hey Daniel, Yippee! I suspect the sugar starting issues is the same one we're seeing in SoaS for F-14. Hmm, I had some trouble on mainstream F-14 booting both Sugar and GNOME (actually, even logging into the console was failing) but booting with enforce=0 fixed it until an update fixed it for good. Is it something different? At this point I'm booting into Sugar from gdm without problems. Regards, Tomeu I'm very busy until Sunday but i hope to have at least some time to be able to look at that problem and help you out where possibly as no doubt both SoaS and the builds for the XO will share a lot of common problems. With the kernel nearing a recent release is there any plans to get a chunk of the kernel patches upstream to ease on going maintenance? As always ping me if there's anywhere specific I can be of assistance in upstream Fedora. Peter On Wed, Sep 1, 2010 at 6:22 AM, Daniel Drake d...@laptop.org wrote: Hi, After seeing the community help significantly with F11-on-XO development, I'm wondering if we can do something similar for a future release. So, I've taken the first few steps in getting OLPC's technologies rebased on Fedora 14 and Linux v2.6.35. The result has lots of problems, but I figure that publishing the work so far is the first step in getting things fixed. Things are in such an early stage that I'm labelling this as a developers-only release. To name a few: Sugar crashes all the time, the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. For now, please don't file bugs unless you include patches. And, to take 1 bite at a time out of this huge task, lets ignore all but the biggest sugar issues for now because there is plenty of OS work to be done first. (or alternatively lets take sugar issues directly to SL trac) And the links: 2.6.35 kernel is in git://dev.laptop.org/olpc-2.6 branch olpc-2.6.35 OS build is done from 'f14' branch of olpc-os-builder First released images are at http://build.laptop.org/F14/os1/ Trac is at http://dev.laptop.org/milestone/F14 (basically my immediate TODO), please don't file tickets unless you include patches in these early days Note: I haven't tested those exact images (since Chris @ OLPC built them), so boot-testing them can be the first task for someone. I have been working from the same codebases making local images successfully, so they will probably work (to the extent that things are working). At this point this is all something put together by me in my spare time. It's not known if or when OLPC would start working on an official release from these efforts. But I figure that if we get things properly stabilized and all the work is done cleanly, we'll find one way or another to get this in the hands of deployments. Daniel ___ 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
Re: Initial F14 developers-only release for XO and XO-1.5
Booted ok on XO-1. At its current level, this system is already usable. [Was even able to apply my customizations, except for doing editing.] In Terminal, cursor movement keys don't work. [I also saw interference to Terminal (white background) from dmesg? lines (black background), after each boot -- but these would go away if I just restarted Sugar.] Could not use text console (alt-ctl-Fn combo appears to be ignored). Came up with ad-hoc network on channel 1 (interface wlan0). I stopped that, started mesh manually, made sure mesh multicast was active, was able to transfer files with rsync (via mesh) between XO-1 systems. Was able to run a number of Activities. The bowdlerized Speak refused to answer some of my questions. Record never crashed - not even in 'High' quality on XO-1. Among the non-starters were Chat and TamTam. The 'My Settings' XO-color choice will be nice, once I figure it out. Multimedia o.k. Never had Sugar crash in several hours running XO-1. Thank you muchly for your great leap forward, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Tue, 31-08-2010 a las 23:22 -0600, Daniel Drake escribió: Things are in such an early stage that I'm labelling this as a developers-only release. To name a few: Sugar crashes all the time, the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. I recommend rebasing on the geode driver 2.11.9, which was just released by upstream. I've been testing it in Dextrose for about 3 weeks: it fixes all the known rendering bugs and has no regressions. Hopefully it will also work well on newer X servers, but I have not had the opportunity to test yet. If you're ok with it, I could upgrade the xorg-x11-drv-geode package in Fedora 14. I really admire the work you're doing and wish I could help more than this, but time to work on XO builds is up for me. From now on I'll have just enough time to finish spinning-off Dextrose 2 in the hands of deployments. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
the XO-1.5 camera doesn't work, there are some funky graphics bugs on XO-1, no power management, DCON doesn't work right on either laptop, desktop switching lands you at a blank screen. I recommend rebasing on the geode driver 2.11.9, which was just released by upstream. I've been testing it in Dextrose for about 3 weeks: it fixes all the known rendering bugs and has no regressions. The XO-1 os1 build already has xorg-x11-drv-geode-2.11.9-1.fc14.olpc1 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 1 September 2010 00:49, pbrobin...@gmail.com pbrobin...@gmail.com wrote: With the kernel nearing a recent release is there any plans to get a chunk of the kernel patches upstream to ease on going maintenance? I cleaned up the history a lot, which is the first big step in doing this. It's a task I'd be interested in doing, but I'm not sure what priority I'll give it. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
--- On Wed, 9/1/10, Mikus Grinbergs mi...@bga.com wrote: I recommend rebasing on the geode driver 2.11.9, which was just released by upstream. I've been testing it in Dextrose for about 3 weeks: it fixes all the known rendering bugs and has no regressions. The XO-1 os1 build already has xorg-x11-drv-geode-2.11.9-1.fc14.olpc1 This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to 2.11.8 when I run it in puppy. The XO-1 is like a new machine. pls do _not_ wait for 10.1.3 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On 1 September 2010 10:14, Yioryos Asprobounitis mavrot...@yahoo.com wrote: This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to 2.11.8 when I run it in puppy. The XO-1 is like a new machine. pls do _not_ wait for 10.1.3 That's impossible. 10.1.2 has been released. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
--- On Wed, 9/1/10, Daniel Drake d...@laptop.org wrote: From: Daniel Drake d...@laptop.org Subject: Re: Initial F14 developers-only release for XO and XO-1.5 To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: Bernie Innocenti ber...@codewiz.org, mi...@bga.com, OLPC Devel devel@lists.laptop.org, fedora-olpc-list fedora-olpc-l...@redhat.com Date: Wednesday, September 1, 2010, 12:16 PM On 1 September 2010 10:14, Yioryos Asprobounitis mavrot...@yahoo.com wrote: This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to 2.11.8 when I run it in puppy. The XO-1 is like a new machine. pls do _not_ wait for 10.1.3 That's impossible. 10.1.2 has been released. :-) I guess what I imply is an F11 rpm. But you answer brings up an interesting issue, an olpc-critical-update mechanism similar to software update. Lets say a variant of yum with only one specific repo, or even just yum with only the olpc repo. A yum-olpc script Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
On Wed, Sep 1, 2010 at 2:30 PM, Yioryos Asprobounitis mavrot...@yahoo.com wrote: This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to 2.11.8 when I run it in puppy. The XO-1 is like a new machine. pls do _not_ wait for 10.1.3 That's impossible. 10.1.2 has been released. :-) I guess what I imply is an F11 rpm. But you answer brings up an interesting issue, an olpc-critical-update mechanism similar to software update. Lets say a variant of yum with only one specific repo, or even just yum with only the olpc repo. A yum-olpc script Yioryos, can you spin a F11 RPM of 2.11.9? If it's much improved, and a good testing shows it has no regressions, it's a candidate for 10.1.3. I will be pushing a nice list of fixups for 10.1.3 :-) 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: Initial F14 developers-only release for XO and XO-1.5
--- On Wed, 9/1/10, Martin Langhoff martin.langh...@gmail.com wrote: From: Martin Langhoff martin.langh...@gmail.com Subject: Re: Initial F14 developers-only release for XO and XO-1.5 To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: Daniel Drake d...@laptop.org, OLPC Devel devel@lists.laptop.org, Bernie Innocenti ber...@codewiz.org, fedora-olpc-list fedora-olpc-l...@redhat.com Date: Wednesday, September 1, 2010, 2:55 PM On Wed, Sep 1, 2010 at 2:30 PM, Yioryos Asprobounitis mavrot...@yahoo.com wrote: This driver should be ported to F11/10.1.2 ASAP. Is day and night compared to 2.11.8 when I run it in puppy. The XO-1 is like a new machine. pls do _not_ wait for 10.1.3 That's impossible. 10.1.2 has been released. :-) I guess what I imply is an F11 rpm. But you answer brings up an interesting issue, an olpc-critical-update mechanism similar to software update. Lets say a variant of yum with only one specific repo, or even just yum with only the olpc repo. A yum-olpc script Yioryos, can you spin a F11 RPM of 2.11.9? If it's much improved, and a good testing shows it has no regressions, it's a candidate for 10.1.3. I will be pushing a nice list of fixups for 10.1.3 :-) I could try it... Anybody has handy the 2.11.8/f11 .spec file for start? Though I think that Bernie should have one for the dx2 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Initial F14 developers-only release for XO and XO-1.5
El Wed, 01-09-2010 a las 15:55 -0300, Martin Langhoff escribió: can you spin a F11 RPM of 2.11.9? If it's much improved, and a good testing shows it has no regressions, it's a candidate for 10.1.3. Enjoy: rpm -Uvh http://download.sugarlabs.org/dextrose/testing/dxo2/rpms/i386/os/xorg-x11-drv-geode-2.11.9-1.fc14.i586.rpm -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
