Re: sugar 0.83 in joyride
On Mon, Nov 10, 2008 at 4:10 AM, genesee [EMAIL PROTECTED] wrote: Daniel Drake-5 wrote: We're mid-way through the upgrade to sugar-0.83. And even when that's done, there will be mucho breakage (see Tomeu's earlier post). I think joyride will break often over the course of the next few months as development runs in full swing. Thanks for letting us know anyway. Sure thing! BTW, olpc-update is now broken due to NM issues and /versions has no alt build files, just current. yum update wants NM 0.6 here and NM 0.7 there. What the...? This domino breakage is the worst yet. What next? Will my xo 'brick'? Whatever that is, I don't want to find out as the xo is my ONLY computer. Genesee: If your XO is your only computer, then please don't use joyride at all. Developers need a place where to break everything (including all data in the laptop) in order to do their job, and that place is now joyride. All: seems like we have failed to explain what can be expected from joyride builds. How can we better warn of the breakage that joyride builds can cause? Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
Aw, you're no fun! Since first upgrading from 656 to Update 2, there is no turning back. Warnings are so droll. So far nothing in joyride has been fatal. Not getting rid of me so easy! Tomeu Vizoso wrote: Genesee: If your XO is your only computer, then please don't use joyride at all. Developers need a place where to break everything (including all data in the laptop) in order to do their job, and that place is now joyride. All: seems like we have failed to explain what can be expected from joyride builds. How can we better warn of the breakage that joyride builds can cause? -- View this message in context: http://n2.nabble.com/sugar-0.83-in-joyride-tp1459344p1483669.html Sent from the OLPC Software development mailing list archive at Nabble.com. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
On Tue, Nov 11, 2008 at 4:46 AM, genesee [EMAIL PROTECTED] wrote: Aw, you're no fun! Since first upgrading from 656 to Update 2, there is no turning back. Warnings are so droll. So far nothing in joyride has been fatal. Not getting rid of me so easy! Oh, in that case, keep trying explosive stuff ;) Joyride will be really broken for at least a couple of days, but soon (I hope) it will be usable by curious people who want to see where development is heading. Though will keep eating people's files and failing to do basic stuff for several months ;) Regards, Tomeu Tomeu Vizoso wrote: Genesee: If your XO is your only computer, then please don't use joyride at all. Developers need a place where to break everything (including all data in the laptop) in order to do their job, and that place is now joyride. All: seems like we have failed to explain what can be expected from joyride builds. How can we better warn of the breakage that joyride builds can cause? -- View this message in context: http://n2.nabble.com/sugar-0.83-in-joyride-tp1459344p1483669.html Sent from the OLPC Software development mailing list archive at Nabble.com. ___ 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: sugar 0.83 in joyride
On Sun, Nov 9, 2008 at 12:13 AM, Mikus Grinbergs [EMAIL PROTECTED] wrote: genesee writes: NetworkManager-0.7 and/or NetworkManager-glib killed my Neigborhood view. Same problem here. We're mid-way through the upgrade to sugar-0.83. And even when that's done, there will be mucho breakage (see Tomeu's earlier post). I think joyride will break often over the course of the next few months as development runs in full swing. Thanks for letting us know anyway. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
Daniel Drake-5 wrote: We're mid-way through the upgrade to sugar-0.83. And even when that's done, there will be mucho breakage (see Tomeu's earlier post). I think joyride will break often over the course of the next few months as development runs in full swing. Thanks for letting us know anyway. Sure thing! BTW, olpc-update is now broken due to NM issues and /versions has no alt build files, just current. yum update wants NM 0.6 here and NM 0.7 there. What the...? This domino breakage is the worst yet. What next? Will my xo 'brick'? Whatever that is, I don't want to find out as the xo is my ONLY computer. -- View this message in context: http://n2.nabble.com/sugar-0.83-in-joyride-tp1459344p1479201.html Sent from the OLPC Software development mailing list archive at Nabble.com. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
Tomeu Vizoso wrote: Had to install these two from F9: NetworkManager-0.7.0-0.11.svn4175.fc9.i386.rpm NetworkManager-glib-0.7.0-0.11.svn4175.fc9.i386.rpm Howdy, NetworkManager-0.7 and/or NetworkManager-glib killed my Neigborhood view. After 'olpc-update' to joyride-2532, 'yum update' upgraded NetworkManager to 0.7 and installed NetworkManager-glib. There was no wifi connectivity at all. Just my xo-guy in Neighborhood view, no Software updates connection, no radio icon in the frame, no Browse, and in Terminal the prompt read 'localhost', (no wget or yum or olpc-update of course). This time I thought I went too far. Nothing has scared me like this, (the 'root' fix early in Update 2 was over my head but worked with no side effects). Reverted to Build 767, Sugar 0.82.1, Firmware Q2E22. All is well with the Stable Build. Tried 2532 again with the same results. The moral of this cautionary tale is my reach exceeded my grasp. Glad 767 survived. Not messing with joyride until I can downgrade NetworkManager, which I have not the foggiest notion how to do. Searched Trac and the wiki for how to do it myself, but did not find the relevant info. ¡Gracias! genesee -- View this message in context: http://n2.nabble.com/sugar-0.83-in-joyride-tp1459344p1474452.html Sent from the OLPC Software development mailing list archive at Nabble.com. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
genesee writes: NetworkManager-0.7 and/or NetworkManager-glib killed my Neigborhood view. Same problem here. But I'm using a wired ethernet connection -- and with this new NM this is the FIRST time ever that my wired connection is being correctly re-established following a suspend !! mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
Hi again, I'm thinking that perhaps best would be to create a joyride branch similar to faster that sugar developers could administer by ourselves. In that way we wouldn't be blocking on each other so often and Sugar developers could more easily adapt Sugar to the OLPC hardware. Sounds good? If there's any problem with this, please explain. Thanks, Tomeu On Wed, Nov 5, 2008 at 10:31 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: Dear Masters of Joyride, have built updated sugar rpms and they seem to work fine on last joyrides. Built locally these rpms. Anybody sees any problem if I build them in the OLPC-3 branch? Or should be in F9? Or F10 if we intend to switch soon? What if we decide to do a 8.2.1 release? sugar-0.83.2-2.fc9.i386.rpm sugar-artwork-0.83.1-1.fc9.i386.rpm sugar-base-0.83.1-1.fc9.i386.rpm sugar-datastore-0.83.0-1.fc9.i386.rpm sugar-presence-service-0.83.1-1.fc9.noarch.rpm sugar-toolkit-0.83.1-1.fc9.i386.rpm Had to install these two from F9: NetworkManager-0.7.0-0.11.svn4175.fc9.i386.rpm NetworkManager-glib-0.7.0-0.11.svn4175.fc9.i386.rpm And these ones from F10: libasyncns-0.7-1.fc10.i386.rpm python-telepathy-0.15.3-1.fc10.noarch.rpm telepathy-gabble-0.7.12-1.fc10.i386.rpm telepathy-glib-0.7.17-1.fc10.i386.rpm telepathy-salut-0.3.5-1.fc10.i386.rpm So, how would you prefer to move forward? Thanks, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
Hi, Hi again, I'm thinking that perhaps best would be to create a joyride branch similar to faster that sugar developers could administer by ourselves. In that way we wouldn't be blocking on each other so often and Sugar developers could more easily adapt Sugar to the OLPC hardware. I'm fine with giving commit access to pilgrim/joyride to any Sugar developers who want it. Shall we just do that instead? Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
This certainly seems like a reasonable solution. - Ed On Nov 6, 2008, at 10:16 AM, Chris Ball wrote: Hi, Hi again, I'm thinking that perhaps best would be to create a joyride branch similar to faster that sugar developers could administer by ourselves. In that way we wouldn't be blocking on each other so often and Sugar developers could more easily adapt Sugar to the OLPC hardware. I'm fine with giving commit access to pilgrim/joyride to any Sugar developers who want it. Shall we just do that instead? Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
On Thu, Nov 6, 2008 at 4:34 PM, Ed McNierney [EMAIL PROTECTED] wrote: This certainly seems like a reasonable solution. Awesome, how much time would it take to get implemented? Thanks, Tomeu On Nov 6, 2008, at 10:16 AM, Chris Ball wrote: Hi, Hi again, I'm thinking that perhaps best would be to create a joyride branch similar to faster that sugar developers could administer by ourselves. In that way we wouldn't be blocking on each other so often and Sugar developers could more easily adapt Sugar to the OLPC hardware. I'm fine with giving commit access to pilgrim/joyride to any Sugar developers who want it. Shall we just do that instead? Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: sugar 0.83 in joyride
On Wed, Nov 5, 2008 at 10:31 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: Dear Masters of Joyride, have built updated sugar rpms and they seem to work fine on last joyrides. Marco pointed me out in #sugar that work fine may need some clarification. In fact, the following things are known to be broken currently: - no WAP support (simon is working on this) - no mesh support (sjoerd has done work on this) - rainbow is broken because depends on the old config file being present - no removable devices support in the journal other than that and several bugs not yet discovered, it works great ;) Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
