Re: [SoaS] Fedora-15-Nightly-20110412.22-i686-Live-soas.iso TESTING
On 04/15/2011 09:29 AM, Bert Freudenberg wrote: On 15.04.2011, at 13:52, Peter Robinson wrote: Etoys have some kind of Problem after startup but run. Yes, known issue. I think I have a workaround that I should be able to put in place on the weekend. I just wish they'd release a version that doesn't use the presence service. I looked into this last week. It will take me some time to make it work, because there is no documentation at all on how to transition from presence service to mission control. Note I'm not complaining, I just need to reverse-engineer what Sugar is actually doing nowadays, just like I had to do when doing the initial Etoys port (which resulted in my Low-level Activity API document). Perhaps someone will help me do that at the Sugar code sprint in Uruguay 3 weeks from now. But for this SoaS release that might be too late. Deploying the presence service package for a while longer is the official workaround. After all, that's why Simon and Tomeu spent the time of reimplementing it as a compatibility fallback. I am happy to transfer the knowledge I have been gaining during the summit, would be great to advance on that end. I have a few more smaller Etoys related issues [1] I would like to pester you about and maybe upstream has moved on [2] by then :) Looking forward to meting you there, Simon [1] http://dev.laptop.org/ticket/10759 [2] http://dev.laptop.org/ticket/10743 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] Fwd: [Fedora Update] [CRITPATH] [comment] xorg-x11-drv-geode-2.11.9-1.fc14
Hi, I wonder why this has been moved to stable despite the unreached karma points. The broken Browse activity was similar last time. I know about a timeout system, but if a package that showed an error is moved to stable then the karma points seem unused then to me, me is confused :/ Regards, Simon Original Message Subject: [Fedora Update] [CRITPATH] [comment] xorg-x11-drv-geode-2.11.9-1.fc14 Date: Thu, 28 Oct 2010 06:04:06 + From: upda...@fedoraproject.org To: erikos The following comment has been added to the xorg-x11-drv-geode-2.11.9-1.fc14 update: bodhi - 2010-10-28 06:04:05 (karma: 0) This update has been pushed to stable To reply to this comment, please visit the URL at the bottom of this mail xorg-x11-drv-geode-2.11.9-1.fc14 Update ID: FEDORA-2010-14164 Release: Fedora 14 Status: stable Type: bugfix Karma: 2 Bugs: 628440 - X + geode doesn't survive VT switch Notes: Update version, fixes VT switching. Submitter: dsd Submitted: 2010-09-07 00:17:20 Comments: bodhi - 2010-09-07 00:17:32 (karma 0) This update has been submitted for testing by dsd. bodhi - 2010-09-07 06:46:15 (karma 0) This update has been pushed to testing mrunge (proventesters) - 2010-09-17 10:59:43 (karma 0) installs fine, no hardware to test, no regression noted. masami (proventesters) - 2010-09-18 12:56:50 (karma 0) not tested. bernie - 2010-10-05 13:19:06 (karma 1) erikos - 2010-10-05 13:59:57 (karma 1) The VT switch does work fine for me with this package. greenfeld - 2010-10-19 18:31:50 (karma 1) The VT switch, XVideo overlay, and all other basic functionality seems to work fine for me with an XO 1. erikos - 2010-10-22 09:48:21 (karma 0) I think Peter had issues with it on a non-xo. I will ping him to comment here his findings. pbrobinson (proventesters) - 2010-10-22 10:09:13 (karma -1) Crashes on a Fit-PC bodhi - 2010-10-28 06:04:05 (karma 0) This update has been pushed to stable https://admin.fedoraproject.org/updates/xorg-x11-drv-geode-2.11.9-1.fc14 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Fwd: [Fedora Update] [CRITPATH] [comment] xorg-x11-drv-geode-2.11.9-1.fc14
On 10/28/2010 11:04 AM, Peter Robinson wrote: On Thu, Oct 28, 2010 at 7:41 AM, Simon Schampijersi...@schampijer.de wrote: Hi, I wonder why this has been moved to stable despite the unreached karma points. The broken Browse activity was similar last time. I know about a timeout system, but if a package that showed an error is moved to stable then the karma points seem unused then to me, me is confused :/ Because it reached 3 positive which kicks the auto push due to karma, and then I added a negative after the fact which puts it back to 2 but doesn't revoke the push. Peter Ahh, ok, this sounds like an undesired behavior to me, hmm. Thanks for the explanation. Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] the final sprint to SoaS 4
On 10/14/2010 10:03 AM, Peter Robinson wrote: Hi All, We're on the final sprint to SoaS v4 Adam Williamson has created some testing guidelines for Fedora QA for Sugar desktop testing. You can find details here [1] and feedback would be greatly appreciated so we can improve this for the Fedora 15 / SoaS v5 cycle. [1] https://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_TC1_Desktop From the discussion (that I remember) that Simon, Thomas and I had the other night these were the issues we had: - Terminal issues - fixed with vte 0.26.1 release that will be in stable tomorrow - Physics issues - New version here please test https://admin.fedoraproject.org/updates/sugar-physics-7-1.fc14 - gnome-keyring issue. Not fixed yet. Helped wanted. I'm going to try and get time to look at this further today. - Read issue - Going to look at it today Looking through the rest of the list here [2] I'm not sure if there's anything else that's not specific to the XO hardware other than issues with Paint and Colors which I'm not sure what the status is. If there's anything else please speak up NOW!. I would like to add the following two issues: a) Input fields in sugar-browse are not correct https://bugzilla.redhat.com/show_bug.cgi?id=642941 b) latest physics does abort when closing https://bugzilla.redhat.com/show_bug.cgi?id=642937 There is as well the issue with tabbing between activities. More info at [1]. Regards, Simon [1] http://lists.sugarlabs.org/archive/sugar-devel/2010-October/027574.html ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [Sugar-devel] New upstream releases of telepathy-salut and telepathy-gabble
On 10/13/2010 01:40 PM, Peter Robinson wrote: These are in updates-testing but need some more karma ;-) Peter Awesome - Thanks to Brian! (if he can hear us :) /me did his verification testing as well. Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] Meeting today?
Hey, as the Final Change Deadline [1] is approaching quickly we maybe should meet today. I think there is a bank holiday in the US, though... What do others think? Regards, Simon [1] https://fedoraproject.org/wiki/Releases/14/Schedule ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Meeting today?
On 10/11/2010 03:26 PM, Peter Robinson wrote: On Mon, Oct 11, 2010 at 1:42 PM, Walter Benderwalter.ben...@gmail.com wrote: On Mon, Oct 11, 2010 at 8:29 AM, Simon Schampijersi...@schampijer.de wrote: Hey, as the Final Change Deadline [1] is approaching quickly we maybe should meet today. I think there is a bank holiday in the US, though... Columbus Day!! What do others think? I can join if we meet sooner than later... I can but it will need to be between 18:00 and 20:00 UK BST as I'm working either side of those and time is very tight today. Peter Basically, I wanted to sync up on the blocker items left to do. I am around now in IRC for the next hour, otherwise we can do it asynchronously. Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [Sugar-devel] Read Activity on Fedora 14 / SoaS v4
On 09/25/2010 04:01 AM, Peter Robinson wrote: Hi All, With this update below I've now fixed Read on Fedora 14. https://admin.fedoraproject.org/updates/gnome-python2-desktop-2.31.1-7.fc14 I've only given it a cursory test so if others could please do so and add Karma (remember you need to be logged into bodhi for your karma to actually have a + effect) so we can get this into the nightly builds. Cheers, This seem to have been broken again with the latest gnome-python2-* packages: http://koji.fedoraproject.org/koji/buildinfo?buildID=198219 - sugar-read-79-2 - gnome-python2-desktop and gnome-python2-evince: 2.32.0-1 Logs at: http://bugs.sugarlabs.org/ticket/2427 I verified by a downgrad to 2.31.1-7. Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] Sugar: Browse has no busy indication when loading pages
Hi, I did file that ticket [1] (previously a request from F11) since I think it is worth an inclusion. I patched the F11 rpm today and the experience is so much better, just the expected user feedback. If anyone has means of nagging the right people ... please do so :) Regards, Simon [1] https://bugzilla.redhat.com/show_bug.cgi?id=640581 [2] http://dev.laptop.org/ticket/10383 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] [ANNOUNCE] Sucrose 0.90 Final Release
Dear Sugar community, Sucrose 0.90 is the latest version of the Sugar learning platform: Sugar promotes collaborative learning through Sugar Activities that encourage critical thinking, the heart of a quality education. Designed from the ground up especially for children, Sugar offers an alternative to traditional “office-desktop” software. Furthermore it provides a flexible and powerful platform for activity developers. Sugar is Free and Open Source Software and consists of Glucose, the base system environment; and Fructose, a set of demonstration activities. This new release contains many new features, performance and code improvements, bug fixes, and translations. Full release notes can be found at: http://wiki.sugarlabs.org/go/0.90/Notes Thanks everyone for your great contributions! On behalf of the Sugar community, Your Release Team ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Update Karma points for Sugar 0.90 --- Current Summary
There is a new update that does need your karma points: https://admin.fedoraproject.org/updates/sugar-calculator-34-1.fc14,sugar-0.90.1-1.fc14?_csrf_token=c54ba3e24726013d673f640c64f01fa249a5dc6f Btw, you can use as well Easy Karma to report your findings: http://fedoraproject.org/wiki/Fedora_Easy_Karma Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] dist-f14-updates-candidate --- dist-f14-updates-testing
Hi, the packages below are in the status: dist-f14-updates-candidate. Do they need to get tagged in order to get into dist-f14-updates-testing? Who/Where can this be done? Or is it because we are in Freeze or for another reason? Sugar 0.90.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=198419 Sugar Calculate 34: http://koji.fedoraproject.org/koji/buildinfo?buildID=198416 Thanks for bringing light into this, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] Update Karma points for Sugar 0.90 --- Current Summary
Disclaimer: I am asking for help. And I am sharing my experiences: Hi, Sugar 0.90 has been packaged thanks to Peter in no time. Currently the packages are in updates-testing. They need three Karma points to get into the stable branch and hence can be included in the nightly builds. Only three points, I hear you say? Sounds easy enough. And actually here are the good news, it is easy enough! You can do the following: === Install latest Soas and install the 0.90 rpms === - grab the latest build from http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ and put it on a stick - when you booted successfully open a terminal et root: su - then you can install the latest packages with: yum update --enablerepo=updates-testing [package-name] example: yum update --enablerepo=updates-testing sugar - What should update you all the packages is the following command: yum groupinstall --enablerepo=updates-testing sugar-desktop - then it is good to enable the sugar logs before restarting sugar, in a terminal edit .sugar/debug and un-comment the last line (use your editor of choice here) - you now need to restart sugar and start you testing - Tip-of-the-day: if you want to see the current version of an installed package you can use the following command in the terminal (no need to be root) rpm -q [package-name] example: rpm -q sugar === Give the Karma points === After all the hard work of testing you will want to share your results. You can update the karma points at: https://admin.fedoraproject.org/updates/login?_csrf_token=22e572c58d9f8900afdd5092448f24e6c27d327c Yes you need to have an account for that, but it is easy to do. The packages below needs updating - and as you see I have done my job as well :) https://admin.fedoraproject.org/updates/sugar-browse-118-1.fc14,sugar-imageviewer-15-1.fc14,sugar-write-71-1.fc14 https://admin.fedoraproject.org/updates/etoys-4.1.2388-1.fc14,sugar-chat-68-1.fc14,sugar-datastore-0.90.0-1.fc14,sugar-base-0.90.1-1.fc14,sugar-toolkit-0.90.0-1.fc14,sugar-artwork-0.90.0-1.fc14,sugar-0.90.0-1.fc14 https://admin.fedoraproject.org/updates/sugar-turtleart-98-1.fc14,etoys-4.1.2387-1.fc14 Of course you can as well ask questions here, if you are unsure if something is a bug or not or if you just want to congratulate the team for their work - please drop us a line. === Known Issues === Here is a list of current Issues in the F14 Soas builds I have found so far: - Gnome keyring pops up at first start: http://bugs.sugarlabs.org/ticket/2339 --- At least a new behavior, if not fixable it should be documented what to do. - Physics crashes: http://bugs.sugarlabs.org/ticket/2363 --- We had a similar issue in Sugar, the same fix can be applied here. - Calculate does not start: http://bugs.sugarlabs.org/ticket/2245 --- Version 34 fixes it, has to be packaged - Terminal: Can not scroll when using less: Warning Terminal is not fully functional. On the XO builds I could not edit files with Vi neither which works here ok. There was a new version of VTE in updates-testing (0.26.0-1) but that one did not fix that issue. http://bugs.sugarlabs.org/ticket/2394 --- Maybe someone could test the gnome-terminal if that functions. - Activity icon not disappearing from the neighborhood view http://bugs.sugarlabs.org/ticket/2389 --- Tomeu has a fix in Gabble and is verifying now if that happens on Salut as well. - Sharing button not updated when resuming a previously-shared activity http://bugs.sugarlabs.org/ticket/2390 --- Tomeu is on that one as well. What started as a five minutes project turned out to take me a few minutes more :) - I hope you enjoyed the reading and we will see positive Karma points spreading all around. Cheers, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Missing gettext dependency needed for localised activities
On 09/21/2010 07:22 PM, Gary Martin wrote: Hi Simon, On 20 Sep 2010, at 11:30, Simon Schampijer wrote: On 09/18/2010 04:01 PM, Gary Martin wrote: On 18 Sep 2010, at 10:52, pbrobin...@gmail.compbrobin...@gmail.com wrote: On Fri, Sep 17, 2010 at 9:57 PM, Gary C Martin garycmar...@googlemail.com wrote: Hi Folks, Just wanted to email this ticket out and make sure the gettext package makes it into the Soas and Dextrose distros. Without it none of the activity po files will be built at bundle install time, thus failing to create the locale directory binary .mo files. Without this, activity translations will not work. This appears to be a break going back to at least Soas Mirabelle. Yep, it was dropped in Mirabelle because it pulled in horrific dependencies and when I asked about it I was told it was historical and that all the Activities should be pre-generating the translations and that they shouldn't generated on local install. Ouch, that is news to me, no wonder activity localization is broken. Can you point me to the thread/ticket/wiki with that discussion? Including the binary .mo locale files in the source and/or .xo bundles is, to the best of my knowledge, not the usual workflow for activity releases. When you use the sugar tools it should just work fine: ./setup.py dist_source will create a tarball with just the *.po files. Oooh, so it does, learn't something new today, thanks :) Excellent :) ./setup.py dist_xo will create the bundle with a locales folder that contains the .mo for the activity. Hmmm, now the question is does dist_xo build the locale folder and then make the bundle with it in, or do you have to manually build first before dist_xo? I've just looked through a mix of past .xo releases of mine, some have locale directories and some don't (aargh!). I'm pretty sure I alway use ./setup.py dist_xo on an XO-1 running an official OLPC 0.82 or 0.84 to build my official .xo bundle releases. The code should do the right thing [1]. And from my testing it works fine as well. Not sure what might have went wrong on your end :/ Can you retry? Regards, Simon [1] http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/blobs/sucrose-0.84/src/sugar/activity/bundlebuilder.py#line283 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [Sugar-devel] Sugar on Fedora and Sugar on a Stick QA Processes Announcement
Hi Peter, these are just excellent news indeed! On 09/22/2010 10:50 AM, Peter Robinson wrote: Hi All, As some of you know I was at FUDCon Zurich last weekend. I took the opportunity to sit down with Adam Williamson who is in charge of the Fedora QA team and process to discuss how we could incorporate Sugar and SoaS testing into the QA process. Congratulations! Adam agreed that we would be able to incorporate Sugar into the Desktop QA which will expand our testing massively as Fedora has a great QA team. It will also have the ability to allow us to block a release if there is things broken. That is a double edged sword as if its broken we'll also need to pull out all stops to ensure it is fixed as well, but overall I believe that is positive! Of course visibility does demand responsibility as well. But I agree, this is positive. In the short term this won't affect this release too much but I will be spending some time to define the criteria for Alpha, Beta and Final releases. It will also mean we have official spins for each of the Alpha, Beta as well as the usual Final releases. While we will see the start of the benefits for the home run this will really start to kick in for the SoaSv5 release process. I would be interested in these criteria too. I want to draft a new schedule for 0.92 in the next days. Knowing when the downstreams are expecting delivery will help there. Overall I think this is a massively positive opportunity for Sugar as it opens it out more to the wider Fedora community and allows us to get involved in the Fedora QA more and define what is important for us for our releases and allows us to ride on the coattails and gain the benefit of the awesome work that Adam and his team are doing upstream. It will be interesting to see how we can share the QA resources (testing plans). I think there are basic tests the upstream and each downstream is interested in. I hope the interested people will sit together and find good ways of working together on this. I think we need someone at Sugar Labs that coordinates the QA efforts. From a release management point of view we really lack that. If there is someone that wants to spend a few hours per month on working on this - now might be a good moment to speak up. Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Missing gettext dependency needed for localised activities
On 09/18/2010 04:01 PM, Gary Martin wrote: On 18 Sep 2010, at 10:52, pbrobin...@gmail.compbrobin...@gmail.com wrote: On Fri, Sep 17, 2010 at 9:57 PM, Gary C Martin garycmar...@googlemail.com wrote: Hi Folks, Just wanted to email this ticket out and make sure the gettext package makes it into the Soas and Dextrose distros. Without it none of the activity po files will be built at bundle install time, thus failing to create the locale directory binary .mo files. Without this, activity translations will not work. This appears to be a break going back to at least Soas Mirabelle. Yep, it was dropped in Mirabelle because it pulled in horrific dependencies and when I asked about it I was told it was historical and that all the Activities should be pre-generating the translations and that they shouldn't generated on local install. Ouch, that is news to me, no wonder activity localization is broken. Can you point me to the thread/ticket/wiki with that discussion? Including the binary .mo locale files in the source and/or .xo bundles is, to the best of my knowledge, not the usual workflow for activity releases. When you use the sugar tools it should just work fine: ./setup.py dist_source will create a tarball with just the *.po files. ./setup.py dist_xo will create the bundle with a locales folder that contains the .mo for the activity. Or do I miss something? Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] [Sugar-devel] Policy for activities for downstream inclusion
On 09/15/2010 01:58 AM, Gary Martin wrote: On 14 Sep 2010, at 15:14, Simon Schampijersi...@schampijer.de wrote: Thanks David and Walter for the feedback, On 09/14/2010 04:09 PM, Walter Bender wrote: On Tue, Sep 14, 2010 at 10:05 AM, David Farningdfarn...@gmail.com wrote: On Tue, Sep 14, 2010 at 5:27 AM, Simon Schampijersi...@schampijer.de wrote: Hi, what is the current status for activity releases in order to include them in distributions like Soas*? Do you guys need tarballs or did you switch over to construct the rpms from the .xo? For example the latest Paint rpm uses the .xo AFAIK (build even the binaries from the non-python sources in the bundle). And is the email from ASLO enough for packagers to know about new releases? Any other notification that packagers need? In the .deb side of the universe, we prefer tarballs but we can work directly from the git repository. We should not go from the git repository. Either use the .xo or a tarball. Is it not still the practice to put tarballs on download.sl.o ??? -walter Well, the latest mails I have seen about activity releases (besides Chat) does come from ASLO and only state the .xo. If there are tarballs at d.sl.o they have not been announced ;D I've been uploading me since Bernie kindly un blocked my shell account, though I totally understand why others might not manage this workflow, there's already many hoops to jump though for a casual activity developer to do for a release. Are all the ASLO emails not enough? I'm getting three separate emails from the system for every release already! Regards, --Gary Hi Gary, for me having one email from ASLO is fine. But the tarball if it exist should be referenced in the mail. Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Policy for activities for downstream inclusion
Thanks David and Walter for the feedback, On 09/14/2010 04:09 PM, Walter Bender wrote: On Tue, Sep 14, 2010 at 10:05 AM, David Farningdfarn...@gmail.com wrote: On Tue, Sep 14, 2010 at 5:27 AM, Simon Schampijersi...@schampijer.de wrote: Hi, what is the current status for activity releases in order to include them in distributions like Soas*? Do you guys need tarballs or did you switch over to construct the rpms from the .xo? For example the latest Paint rpm uses the .xo AFAIK (build even the binaries from the non-python sources in the bundle). And is the email from ASLO enough for packagers to know about new releases? Any other notification that packagers need? In the .deb side of the universe, we prefer tarballs but we can work directly from the git repository. We should not go from the git repository. Either use the .xo or a tarball. Is it not still the practice to put tarballs on download.sl.o ??? -walter Well, the latest mails I have seen about activity releases (besides Chat) does come from ASLO and only state the .xo. If there are tarballs at d.sl.o they have not been announced ;D Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Sugar on a Stick builds are broken. boots thru firstboot; then starts x ends up with blank screen with X cursor no gdm or sugar login ---been that way over 10 days....
On 08/30/2010 02:43 PM, pbrobin...@gmail.com wrote: Yes, Its a know problem that I'm actually looking at now. There's been alot of changes in Fedora 14 over the last couple of weeks with various major upstream changes which has caused some major churn. I hope to have it fixed in the next couple of days but I can't promise anything as work is extremely busy at the moment. Peter Fwiw, the logs do point to an SELinux issue. Peter, is there a bug already filed? In the meantime, to test sugar, you can go back to an old version and update just the sugar packages: yum update --enablerepo=updates-testing sugar sugar-toolkit sugar-datastore sugar-presence-service sugar-artwork telepathy-salut telpathy-gabble Regards, Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Sugar on a Stick builds are broken. boots thru firstboot; then starts x ends up with blank screen with X cursor no gdm or sugar login ---been that way over 10 days....
On 08/30/2010 04:38 PM, Simon Schampijer wrote: On 08/30/2010 02:43 PM, pbrobin...@gmail.com wrote: Yes, Its a know problem that I'm actually looking at now. There's been alot of changes in Fedora 14 over the last couple of weeks with various major upstream changes which has caused some major churn. I hope to have it fixed in the next couple of days but I can't promise anything as work is extremely busy at the moment. Peter Fwiw, the logs do point to an SELinux issue. Peter, is there a bug already filed? In the meantime, to test sugar, you can go back to an old version and update just the sugar packages: Damn, just seen that there are no older builds in the repo... Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Sugar on a Stick builds are broken. boots thru firstboot; then starts x ends up with blank screen with X cursor no gdm or sugar login ---been that way over 10 days....
On 08/30/2010 04:45 PM, Simon Schampijer wrote: On 08/30/2010 04:38 PM, Simon Schampijer wrote: On 08/30/2010 02:43 PM, pbrobin...@gmail.com wrote: Yes, Its a know problem that I'm actually looking at now. There's been alot of changes in Fedora 14 over the last couple of weeks with various major upstream changes which has caused some major churn. I hope to have it fixed in the next couple of days but I can't promise anything as work is extremely busy at the moment. Peter Fwiw, the logs do point to an SELinux issue. Peter, is there a bug already filed? In the meantime, to test sugar, you can go back to an old version and update just the sugar packages: Damn, just seen that there are no older builds in the repo... Simon Sorry for the noise: http://download.sugarlabs.org/soas/test/ Simon ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
[SoaS] Help testing new sugar packages in F14
Hi, to get the new Sugar release 0.90 [1] into shape and make it a stable release we want people to test the nightly Soas snapshots [2]. In order to get the new packaged tarballs into those builds they have to meet certain criteria first [3], hence we need people testing them. You can simply do this by getting the rpms from koji and install them into your latest soas snapshot and restart Sugar. What I do in short is: - open the Browse activity and go to http://koji.fedoraproject.org - search for the package (sugar, sugar-toolkit...) - click on the latest F14 version and then right-click on the download option of the 'noarch' rpm and choose 'copy link' from the palette (if you download directly it is stored in the Journal) - then open the terminal activity log in as root and you can copy in the address here using ctrl+shift+v or the edit tab in the toolbar - the command for updating the rpm is: 'rpm -U [name of rpm]' Once you tested the package you can comment on bodhi [4] about your findings and give karma points. If you have not done so yet, you should create a Fedora account [5], so your comments have a higher value. Why not start today? Here are some packages that would need your testing [6] [7]. Btw, there will be a Fedora testing day [8] this Thursday and we want to give a go on Sugar, too. More info to come. If you have questions please feel free to ask. I am as well on irc #sugar most of the day. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria [4] https://admin.fedoraproject.org/updates [5] https://admin.fedoraproject.org/accounts/user/new?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [6] https://admin.fedoraproject.org/updates/sugar-artwork-0.89.3-1.fc14,sugar-toolkit-0.89.3-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [7] https://admin.fedoraproject.org/updates/sugar-toolkit-0.89.2-1.fc14,sugar-presence-service-0.90.0-1.fc14,sugar-0.89.3-1.fc14,sugar-base-0.90.0-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [8] https://fedorahosted.org/fedora-qa/ticket/108 ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
Re: [SoaS] Help testing new sugar packages in F14
On 08/18/2010 11:52 AM, Simon Schampijer wrote: Hi, to get the new Sugar release 0.90 [1] into shape and make it a stable release we want people to test the nightly Soas snapshots [2]. In order to get the new packaged tarballs into those builds they have to meet certain criteria first [3], hence we need people testing them. You can simply do this by getting the rpms from koji and install them into your latest soas snapshot and restart Sugar. What I do in short is: - open the Browse activity and go to http://koji.fedoraproject.org - search for the package (sugar, sugar-toolkit...) - click on the latest F14 version and then right-click on the download option of the 'noarch' rpm and choose 'copy link' from the palette (if you download directly it is stored in the Journal) - then open the terminal activity log in as root and you can copy in the address here using ctrl+shift+v or the edit tab in the toolbar - the command for updating the rpm is: 'rpm -U [name of rpm]' Once you tested the package you can comment on bodhi [4] about your findings and give karma points. If you have not done so yet, you should create a Fedora account [5], so your comments have a higher value. Why not start today? Here are some packages that would need your testing [6] [7]. Btw, there will be a Fedora testing day [8] this Thursday and we want to give a go on Sugar, too. More info to come. If you have questions please feel free to ask. I am as well on irc #sugar most of the day. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://fedoraproject.org/wiki/Package_update_acceptance_criteria [4] https://admin.fedoraproject.org/updates [5] https://admin.fedoraproject.org/accounts/user/new?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [6] https://admin.fedoraproject.org/updates/sugar-artwork-0.89.3-1.fc14,sugar-toolkit-0.89.3-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [7] https://admin.fedoraproject.org/updates/sugar-toolkit-0.89.2-1.fc14,sugar-presence-service-0.90.0-1.fc14,sugar-0.89.3-1.fc14,sugar-base-0.90.0-1.fc14?_csrf_token=88fb044408f6ad820284d0a7f38dc7731efb1808 [8] https://fedorahosted.org/fedora-qa/ticket/108 Actually, you can use as well the updates testing repository to test new rpms. Completely forgot about that. yum --enablerepo=updates-testing update sugar sugar-toolkit... And Bernie pointed out that fedora-easy-karma [1] can be used for people who do not like to use web interfaces. Gary pointed out that he has issues running the latest snapshot under virtualization (Virtual Box) does not work for him (black screen). If anybody has an idea... Regards, Simon [1] http://fedoraproject.org/wiki/Fedora_Easy_Karma ___ SoaS mailing list SoaS@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas
