[Sugar-devel] Activity updater crash
Hi Walter, the updater crash seems to be a bug in your code It looks like you should use get_data to get a python array from GBytes. (unref_to_array shouldn't really be exposed in python) diff --git a/extensions/cpsection/updater/backends/aslo.py b/extensions/cpsectio index e244af0..7c41ae6 100644 --- a/extensions/cpsection/updater/backends/aslo.py +++ b/extensions/cpsection/updater/backends/aslo.py @@ -116,7 +116,7 @@ class _UpdateFetcher(object): self._process_result() return else: -xml_data = data.unref_to_array() +xml_data = data.get_data() self._xml_data += str(xml_data) stream.read_bytes_async(self._CHUNK_SIZE, GLib.PRIORITY_DEFAULT, None, -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater crash
On 7 May 2013 22:59, Walter Bender walter.ben...@gmail.com wrote: Hi Walter, the updater crash seems to be a bug in your code It looks like you should use get_data to get a python array from GBytes. (unref_to_array shouldn't really be exposed in python) Thanks. /me wonders why it ever worked. I'll try to wrap up the other changes you requested ASAP so we can put this one to bed. It's memory corruption, so it could have worked once if really lucky :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater crash
On Tue, May 7, 2013 at 5:00 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 7 May 2013 22:59, Walter Bender walter.ben...@gmail.com wrote: Hi Walter, the updater crash seems to be a bug in your code It looks like you should use get_data to get a python array from GBytes. (unref_to_array shouldn't really be exposed in python) Thanks. /me wonders why it ever worked. I'll try to wrap up the other changes you requested ASAP so we can put this one to bed. It's memory corruption, so it could have worked once if really lucky :) I guess I should have bought a lottery ticket, because it worked many many times in my testing. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater crash
On 7 May 2013 23:01, Walter Bender walter.ben...@gmail.com wrote: It's memory corruption, so it could have worked once if really lucky :) I guess I should have bought a lottery ticket, because it worked many many times in my testing. Hehe. It might be that the glib we are now building with sugar-build is more aggressive reporting double frees (it probably have more debug stuff enabled than the glib shipped with your distro). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater crash
On Tue, May 7, 2013 at 4:20 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Hi Walter, the updater crash seems to be a bug in your code It looks like you should use get_data to get a python array from GBytes. (unref_to_array shouldn't really be exposed in python) Thanks. /me wonders why it ever worked. I'll try to wrap up the other changes you requested ASAP so we can put this one to bed. -walter diff --git a/extensions/cpsection/updater/backends/aslo.py b/extensions/cpsectio index e244af0..7c41ae6 100644 --- a/extensions/cpsection/updater/backends/aslo.py +++ b/extensions/cpsection/updater/backends/aslo.py @@ -116,7 +116,7 @@ class _UpdateFetcher(object): self._process_result() return else: -xml_data = data.unref_to_array() +xml_data = data.get_data() self._xml_data += str(xml_data) stream.read_bytes_async(self._CHUNK_SIZE, GLib.PRIORITY_DEFAULT, None, -- Daniel Narvaez -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
On 06/14/2010 11:02 AM, Tomeu Vizoso wrote: On Sun, Jun 13, 2010 at 23:51, Bernie Innocentiber...@codewiz.org wrote: El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. Wish I had time to help with that, but I wanted to mention that I greatly admire the work you have been doing since you arrived in Paraguay. I specially value your understanding of what is required in the field to make Sugar fulfill its mission and wish people like you had more voice in SLs as opposed to visionaries. Regards, Tomeu I want to second that! Thanks Bernie for your great work in Paraguay. And I am convinced that this is the sustainable way to move forward. To me, my experiences in the field helped a lot to understand what is needed. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
El Mon, 14-06-2010 a las 11:41 -0500, David Farning escribió: To give credit where credit is due, the ASLO updater is just a update of Scott's code to parse the xml ASLO dynamically creates rather than micoroformat. Ah, I thought it was a rewrite because the codebase is so much shorter and simpler. Which is what I like about it. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. What missing features are important? For our use-cases, these would suffice: 1) Activity groups (one is sufficient). This lets deployments point the updater at a page containing a list of activities to add or update. As a side-effect, it also lets teachers quickly restore deleted activities. 2) Configurable update URL (I think the old updater used a gconf key) 3) Also add/update content bundles 4) Support for the olpc microformat, which is nice, simple, fast and already supported by the schoolserver. We don't want to force everyone to go through ASLO for updates. Some time ago, Daniel posted a longer list. On the ASLO side, we need to add one php page to output an activity collection with microformat tags in it. The already existing collection summary page in ASLO was inadequate (can't remember why, maybe because it used pagination). We also need to add the ability to specify exact versions of each activity in a collection, otherwise deployments will be hit by untested and possibly broken activities as they are released by the owners. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
On Tue, Jun 15, 2010 at 8:14 AM, Bernie Innocenti ber...@codewiz.org wrote: El Mon, 14-06-2010 a las 11:41 -0500, David Farning escribió: To give credit where credit is due, the ASLO updater is just a update of Scott's code to parse the xml ASLO dynamically creates rather than micoroformat. Ah, I thought it was a rewrite because the codebase is so much shorter and simpler. Which is what I like about it. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. What missing features are important? For our use-cases, these would suffice: 1) Activity groups (one is sufficient). This lets deployments point the updater at a page containing a list of activities to add or update. As a side-effect, it also lets teachers quickly restore deleted activities. We dropped the group stuff because Mozilla was just starting the collections stuff. Easy to add 2) Configurable update URL (I think the old updater used a gconf key) Also easy. 3) Also add/update content bundles Not sure about this. I have lost track of the work alsroot is doing in this area. 4) Support for the olpc microformat, which is nice, simple, fast and already supported by the schoolserver. We don't want to force everyone to go through ASLO for updates. very straight forward to add a microformat parser. Some time ago, Daniel posted a longer list. On the ASLO side, we need to add one php page to output an activity collection with microformat tags in it. The already existing collectition summary page in ASLO was inadequate (can't remember why, maybe because it used pagination). Very easy task for php coder. Aslo dynamically generates the html pages in a single php script. That page could be adapted to create micro-format data. We also need to add the ability to specify exact versions of each activity in a collection, otherwise deployments will be hit by untested and possibly broken activities as they are released by the owners. Not sure about this one. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
On Sun, Jun 13, 2010 at 23:51, Bernie Innocenti ber...@codewiz.org wrote: El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. Wish I had time to help with that, but I wanted to mention that I greatly admire the work you have been doing since you arrived in Paraguay. I specially value your understanding of what is required in the field to make Sugar fulfill its mission and wish people like you had more voice in SLs as opposed to visionaries. Regards, Tomeu -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity updater
On Sun, Jun 13, 2010 at 4:51 PM, Bernie Innocenti ber...@codewiz.org wrote: El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. To give credit where credit is due, the ASLO updater is just a update of Scott's code to parse the xml ASLO dynamically creates rather than micoroformat. david For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. What missing features are important? david Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] activity updater
El Sun, 13-06-2010 a las 20:55 +0100, Gary C Martin escribió: OK, not strictly a patch but attached is an updated version of the currently malformed svg module-updater icon that's not drawing correctly in F13. Not sure who this needs to get to (could only find it in Bernie's old depreciated software update git rep). It should live in the filesystem at: /usr/share/sugar/data/icons/module-updater.svg There are two updaters: the old one written by C.Scott, which is the one in my obsolete repo and Fedora packages, and a new one written from scratch by DFarning for ASLO, which lives in the sugar repository. For the F11-0.88, we have a dilemma: the new updater is missing some crucial features that deployments were relying upon. Daniel Drake and I discussed possible solutions when he visited Paraguay. There are two equally acceptable possibilities: 1) is adding the missing features to the new codebase, which shouldn't be too hard but needs someone to do it by mid-July maximum. Anyone available? 2) The other possibility is adding the OLPC microformat support to ASLO and reverting to the old updater, which would mean less developer time but reintroduces the dependency on bitfrost which we'd rather keep away from the Sugar codebase. Or even a combination of the two. The new query protocol is very slow, so we might want to teach ASLO about the microformat anyway. When I checked the php code with Daniel, it seemed very easy to do. Alsroot and I discussed the possibility to add .xol support to ASLO. While we agree that ASLO isn't a very good fit for static content, we're going to support .xol for the utilitarian purpose of making the updater work in F11-0.88. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
On Tue, Jun 01, 2010 at 03:22:08PM -0400, Bernie Innocenti wrote: El Fri, 28-05-2010 a las 09:23 +, Aleksey Lim escribió: But what about more trivial way, just create new php generated page (like update-aslo.php) to generate page with what updater needs. In that case such script will be stored out of AMO code base and won't contain any AMO UI elements. Indeed, that would make the microformat updater slightly more efficient and less invasive. I'm planing to finish GCompris/TuxPaint/OOo4Kids(hope it won't be hard) sugarizing and will start work to provide all these blobs from ASLO (experimental activities, per arch blobs, more QA useful workflow) and can start microformat work as well. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
El Tue, 01-06-2010 a las 20:11 +, Aleksey Lim escribió: I'm planing to finish GCompris/TuxPaint/OOo4Kids(hope it won't be hard) sugarizing and will start work to provide all these blobs from ASLO (experimental activities, per arch blobs, more QA useful workflow) and can start microformat work as well. Dude, you totally rule!! Let me know if you need help testing any of this work. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
On Thu, May 27, 2010 at 12:50:10PM -0400, Bernie Innocenti wrote: El Sun, 23-05-2010 a las 14:50 -0400, Michael Stone escribió: The only purposes of the list comprehension in UpdateModel.check_updates() is to set self._bundles_to_check to a list containing the elements returned by bundleregistry.get_registry(). This purpose can be more succinctly achieved by means of the list() constructor. I'll test both patches in F11-XO1 and report back. As your eyes are already looking at this code, perhaps you may like to help with some work. yesterday dsd and I discussed the possibility to add back support for the microformat as a backend to the current activity updater. The current aslo-specific RDF protocol makes it hard for deployments to decentralize activity management to schoolservers. It's also very slow becase it does one HTTP query for each installed activity. Daniel wrote a list of desired requirements in another post not long ago. The ASLO-side of microformat support looks really trivial: we just need edit the html template for the page displaying activity collections. But what about more trivial way, just create new php generated page (like update-aslo.php) to generate page with what updater needs. In that case such script will be stored out of AMO code base and won't contain any AMO UI elements. ASLO lets any registered user create custom collections and grant other users editing rights to it. The only important feature which is missing is locking specific versions of activities. If it's a lot easier, we could restore support for the OLPC microformat and ditch the RDF protocol altogether. It won't be missed because it hasn't been used by any large deployment yet. I'm not sure can import the old code verbatim, though. Besides being very complex, it adds a dependency on bitfrost. A minimalistic backend for the current updater would be a lot more maintainable, imho. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Activity updater
El Sun, 23-05-2010 a las 14:50 -0400, Michael Stone escribió: The only purposes of the list comprehension in UpdateModel.check_updates() is to set self._bundles_to_check to a list containing the elements returned by bundleregistry.get_registry(). This purpose can be more succinctly achieved by means of the list() constructor. I'll test both patches in F11-XO1 and report back. As your eyes are already looking at this code, perhaps you may like to help with some work. yesterday dsd and I discussed the possibility to add back support for the microformat as a backend to the current activity updater. The current aslo-specific RDF protocol makes it hard for deployments to decentralize activity management to schoolservers. It's also very slow becase it does one HTTP query for each installed activity. Daniel wrote a list of desired requirements in another post not long ago. The ASLO-side of microformat support looks really trivial: we just need edit the html template for the page displaying activity collections. ASLO lets any registered user create custom collections and grant other users editing rights to it. The only important feature which is missing is locking specific versions of activities. If it's a lot easier, we could restore support for the OLPC microformat and ditch the RDF protocol altogether. It won't be missed because it hasn't been used by any large deployment yet. I'm not sure can import the old code verbatim, though. Besides being very complex, it adds a dependency on bitfrost. A minimalistic backend for the current updater would be a lot more maintainable, imho. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
On Mon, Feb 2, 2009 at 7:00 AM, Bernie Innocenti ber...@sugarlabs.org wrote: Jonas Smedegaard wrote: What Debian package? I found no mention of olpc-update anywhere in the source code for Sugar, so I guess you are talking about something OLPC-specific _below_ Sugar, right? olpc-update is the official updater for the core OS of the OLPC distribution. It is very XOOS specific so you probably don't want to package it for Debian. Not true at all, FWIW. Are you packaging up the sugar-update-control package for Debian? It's here: http://dev.laptop.org/git?p=users/cscott/sugar-update-control;a=summary (I don't know if release tarballs exist for it) gitweb provides tarballs corresponding to tagged releases. My tentative plan, to be further discussed here, is: 1. import the project in gitorious; 2. break the dependency with olpc-update and bitfrost; There's only a weak dependency on the 'inhibit-suspect' functionality in olpc-update; it's already wrapped in a try block so if olpc-update isn't installed, nothing bad happens (except on an XO, when suspend won't be properly inhibited, natch). 3. add it to jhbuild; 4. get the RPM accepted in Fedora; 5a. change the default URL to point at an Activities page on the Sugar Labs wiki. or, 5b. modify addons.sl.o to understand the OLPC microformat. The choice between 5a or 5b depends on the amount of progress we do with remora over the next few weeks. IMO, rather than worry about 5a, you should just endeavor to ensure that all sugarlabs packaged activites have an appropriate update_url that points to the sugarlabs wiki. The default is just for legacy compatibility. --scott -- ( http://cscott.net/ ) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 02, 2009 at 01:00:53PM +0100, Bernie Innocenti wrote: Jonas Smedegaard wrote: What Debian package? I found no mention of olpc-update anywhere in the source code for Sugar, so I guess you are talking about something OLPC-specific _below_ Sugar, right? olpc-update is the official updater for the core OS of the OLPC distribution. It is very XOOS specific so you probably don't want to package it for Debian. Thanks for clarifying. Are you packaging up the sugar-update-control package for Debian? It's here: http://dev.laptop.org/git?p=users/cscott/sugar-update-control;a=summary (I don't know if release tarballs exist for it) No. Might do in the future. No problem for Debian that it is distributed separately from core Sugar - - on the contrary, this makes it easier to eventually backport to older releases of Sugar. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmG4woACgkQn7DbMsAkQLjBTACghihw/44gIcTORU54RuqC6ad2 C5UAn1ZYm8sj/TsBq52ueG8OR65Kcify =w1ly -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity updater
On Mon, Feb 2, 2009 at 13:00, Bernie Innocenti ber...@sugarlabs.org wrote: Jonas Smedegaard wrote: What Debian package? I found no mention of olpc-update anywhere in the source code for Sugar, so I guess you are talking about something OLPC-specific _below_ Sugar, right? olpc-update is the official updater for the core OS of the OLPC distribution. It is very XOOS specific so you probably don't want to package it for Debian. Are you packaging up the sugar-update-control package for Debian? It's here: http://dev.laptop.org/git?p=users/cscott/sugar-update-control;a=summary (I don't know if release tarballs exist for it) My tentative plan, to be further discussed here, is: 1. import the project in gitorious; 2. break the dependency with olpc-update and bitfrost; 3. add it to jhbuild; 4. get the RPM accepted in Fedora; 5a. change the default URL to point at an Activities page on the Sugar Labs wiki. or, 5b. modify addons.sl.o to understand the OLPC microformat. The choice between 5a or 5b depends on the amount of progress we do with remora over the next few weeks. To speed up packaging, we might also integrate the updater in the main sugar package. I'd like to get help for any of these points. Actually, I will follow the mantra of doing only what nobody else is already doing. Your plan sounds good to me, ping me in #sugar when you get stuck in a Sugar weirdness. Thanks, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Activity updater
Jonas Smedegaard wrote: What Debian package? I found no mention of olpc-update anywhere in the source code for Sugar, so I guess you are talking about something OLPC-specific _below_ Sugar, right? olpc-update is the official updater for the core OS of the OLPC distribution. It is very XOOS specific so you probably don't want to package it for Debian. Are you packaging up the sugar-update-control package for Debian? It's here: http://dev.laptop.org/git?p=users/cscott/sugar-update-control;a=summary (I don't know if release tarballs exist for it) My tentative plan, to be further discussed here, is: 1. import the project in gitorious; 2. break the dependency with olpc-update and bitfrost; 3. add it to jhbuild; 4. get the RPM accepted in Fedora; 5a. change the default URL to point at an Activities page on the Sugar Labs wiki. or, 5b. modify addons.sl.o to understand the OLPC microformat. The choice between 5a or 5b depends on the amount of progress we do with remora over the next few weeks. To speed up packaging, we might also integrate the updater in the main sugar package. I'd like to get help for any of these points. Actually, I will follow the mantra of doing only what nobody else is already doing. -- // Bernie Innocenti - http://www.codewiz.org/ \X/ Sugar Labs - http://www.sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
