Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
And finally a 1.75 image http://bender.sugarlabs.org:3000/images/xo1.75/1/ Testing on this would be appreciated because I don't have a working 1.75 with me. Now I'm going to try to get the olpc-os-builder changes upstream and setup the infrastructure bits more solidly on docky.sugarlabs.org (a vm I setup yesterday). Then I'll do builds with the fixes Martin sent. On 13 May 2014 04:27, Martin Abente wrote: > Downloading! > > > On Mon, May 12, 2014 at 8:54 PM, Daniel Narvaez wrote: > >> xo4 image finally built (untested yet) >> >> http://bender.sugarlabs.org:3000/images/xo4/2/ >> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 13 May 2014 01:49, James Cameron wrote: > > * Should we contribute the olpc-os-builder changes back to OLPC or > > fork it? I don't know if OLPC will do any active development on the > > linux side of things, if not maybe better to turn this into a > > sugarlabs thing. > > Contribute, please. In whatever way is best for you and your users; > (a) patches by mail, (b) fork and pull requests, (c) an account on > dev.laptop.org. > The non-configuration changes we have so far are here: https://github.com/dnarvaez/olpc-os-builder/compare/v7.0...v8.0 Can you review please? I can remove the dropbox change if I'm given access to rpmdropbox.laptop.org. Also, as I mentioned, I would need write access to the repo to push the configuration changes myself. I created an account on dev.laptop.org, user name is dnarvaez. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 13 May 2014 16:13, Gonzalo Odiard wrote: > > > > On Mon, May 12, 2014 at 7:12 PM, Daniel Narvaez wrote: > >> On 12 May 2014 21:07, Gonzalo Odiard wrote: >> >>> First, thanks for doing this work. >>> >>> >> Thanks for helping out. >> >> >>> I would like to take a step back and understand a bit better where we >>>> want to go with this. Some random thoughts and questions. >>>> >>>> * To really understand how much work is left I think we need some good >>>> testing, especially on the hardware related bits. I expect there will be >>>> lots of small things to fix, but it would be good to understand as early as >>>> possible if there are roadblocks. I'm a bad tester and I've never used the >>>> XO much, so I'm often not sure what is a regression and what is not... thus >>>> helping with this would be particularly appreciated. >>>> >>> >>> This is a issue. If we have a Sugar with similar functionalities >>> (settings and activities installed) we can request help from deployments >>> and volunteers. >>> >> >> Are you thinking to deployment specific settings and activities here? Or >> some kind of subset/reference that is good enough for all the interested >> deployments? >> > > Sounds good. Can you link the .ini with AU activities? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Atom shell
Yes, that's a good option too. I have not been following too closely but there seem to be a bit of a push to get it to fully work also on stock linux (rather than on the android derivative they use on phones), which would be useful for us. On 13 May 2014 13:30, Gonzalo Odiard wrote: > A few days ago, I saw a FirefoxOS cellphone. > I wonder if we can run Sugar web on that. > > Gonzalo > > > On Mon, May 12, 2014 at 11:41 AM, Daniel Narvaez wrote: > >> Yes it's basically node.js + chrome + some custom bits to integrate the >> two. It would be perfect to write an OS fully in js (dream or nightmare? >> :P). >> >> >> On 12 May 2014 16:33, Gonzalo Odiard wrote: >> >>> This use node.js too, right? >>> >>> Gonzalo >>> >>> >>> On Mon, May 12, 2014 at 11:26 AM, Daniel Narvaez wrote: >>> >>>> Hi, >>>> >>>> github recently open sourced the shell they used to build the atom >>>> editor >>>> >>>> https://github.com/atom/atom-shell >>>> >>>> It sounds like it would be a pretty cool base for a future html5 only >>>> sugar. Or event just mostly-html5, it seems like this could be easily >>>> integrated with python stuff. >>>> >>>> Also it could be a good wrapper for web activities on GNOME/OS >>>> X/Windows. >>>> >>>> -- >>>> Daniel Narvaez >>>> >>>> _______ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Software for children learning >>> >> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
xo4 image finally built (untested yet) http://bender.sugarlabs.org:3000/images/xo4/2/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 13 May 2014 00:43, Paul Fox wrote: > daniel wrote: > > * Should we contribute the olpc-os-builder changes back to OLPC or fork > it? > > > I don't know if OLPC will do any active development on the linux side > of > > > things, if not maybe better to turn this into a sugarlabs thing. > ... > > Yes. I don't really have a strong feeling one way or another. I can send > > patches for the generic parts if they are wanted. > > > > I think we also need a place where to put reference configurations. I > > initially had put them in olpc-os-builder, numbered as 14.0.0 but that > > feels wrong... since no official olpc releases are planned. I suppose I > > could edit the examples/f18-[model].ini ones instead, but I would need > > access to whatever repository we use to change those without needing > review > > every time. > > in my opinion, the value of not forking would outweigh the risk of > giving commit privs to someone from (gasp!) sugarlabs. ;-) (that really > is just an opinion, of course. it's not my call.) > I don't know... we are kind of dangerous people :P > it also seems like this problem could be well solved with branches and > tags. i haven't looked at the o-o-b tree, but i assume the current > 13.2.0 point could be frozen (branch or tag) and other work could > continue, and eventually branched or tagged itself. > Yeah, I made my changes on a branch already (v8.0). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 12 May 2014 21:07, Gonzalo Odiard wrote: > First, thanks for doing this work. > > Thanks for helping out. > I would like to take a step back and understand a bit better where we >> want to go with this. Some random thoughts and questions. >> >> * To really understand how much work is left I think we need some good >> testing, especially on the hardware related bits. I expect there will be >> lots of small things to fix, but it would be good to understand as early as >> possible if there are roadblocks. I'm a bad tester and I've never used the >> XO much, so I'm often not sure what is a regression and what is not... thus >> helping with this would be particularly appreciated. >> > > This is a issue. If we have a Sugar with similar functionalities > (settings and activities installed) we can request help from deployments > and volunteers. > Are you thinking to deployment specific settings and activities here? Or some kind of subset/reference that is good enough for all the interested deployments? * Should we contribute the olpc-os-builder changes back to OLPC or fork it? > I don't know if OLPC will do any active development on the linux side of > things, if not maybe better to turn this into a sugarlabs thing. > Probably James would know better respect of this issue. The changes we did > for AU are in a fork [1], but are not low level stuff, > just configurations. > Yes. I don't really have a strong feeling one way or another. I can send patches for the generic parts if they are wanted. I think we also need a place where to put reference configurations. I initially had put them in olpc-os-builder, numbered as 14.0.0 but that feels wrong... since no official olpc releases are planned. I suppose I could edit the examples/f18-[model].ini ones instead, but I would need access to whatever repository we use to change those without needing review every time. > * Are interested deployments using olpc-update? If I'm not mistake AU is >> not. >> > > We are not using it. I am pretty sure Nicaragua use it. > Is AU using yum? > * Do we care about maintaining the GNOME "dual boot"? I'm afraid we do, >> but I want to make sure. >> > > Yes. Is a important feature for the deployments. In the end deployments > don't ask for "Gnome", but for a standard desktop, > for some cases. If Gnome don't work without acceleration in F20, XFCE, > mate or similar can work. > I've seen screenshots of GNOME fallback in F20, so I'm hopeful it's still there. But yeah, in the worst case there are alternatives. * As I mentioned in some other thread I'm interested in setting up >> automated builds from sugar master. I have some vague plan of what it >> would look like and wrote bits of it. The basic idea is that you would push >> changes to github and get images automatically built. I think this is good >> for upstream testing but the same infrastructure could be used by >> deployments. Are people interested in using this? >> > > I am not sure if do a complete build for every sugar commit have sense, > maybe yes do weekly builds, or automatic rpms. > Yeah, weekly images and one rpm per commit was pretty much what I had in mind. (With yum based updates doing frequent builds is less important by the way). Well, it's probably good to have one image per commit to the build configurations repository, but that's different. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
Hi, to be honest I haven't even evaluated alternative distributions because I don't think we would have enough resources to do it anyway. We are making minor changes to olpc-os-builder, rewriting it for another distribution would be a lot of work. On 12 May 2014 20:11, Jon Nettleton wrote: > On Mon, May 12, 2014 at 8:02 PM, Daniel Narvaez > wrote: > > Hello, > > > > things are looking good so far, we already have all the models booting > into > > sugar 0.101 with wif apparentlyi working. I would like to take a step > back > > and understand a bit better where we want to go with this. Some random > > thoughts and questions. > > > > * To really understand how much work is left I think we need some good > > testing, especially on the hardware related bits. I expect there will be > > lots of small things to fix, but it would be good to understand as early > as > > possible if there are roadblocks. I'm a bad tester and I've never used > the > > XO much, so I'm often not sure what is a regression and what is not... > thus > > helping with this would be particularly appreciated. > > * Which deployments are planning to ship 0.102 soon and hence are > interested > > in this work? I know of AU. Maybe Uruguay? > > * Do we need to support all the XO models? > > * Should we contribute the olpc-os-builder changes back to OLPC or fork > it? > > I don't know if OLPC will do any active development on the linux side of > > things, if not maybe better to turn this into a sugarlabs thing. > > * Are interested deployments using olpc-update? If I'm not mistake AU is > > not. > > * Do we care about maintaining the GNOME "dual boot"? I'm afraid we do, > but > > I want to make sure. > > * As I mentioned in some other thread I'm interested in setting up > automated > > builds from sugar master. I have some vague plan of what it would look > like > > and wrote bits of it. The basic idea is that you would push changes to > > github and get images automatically built. I think this is good for > upstream > > testing but the same infrastructure could be used by deployments. Are > people > > interested in using this? > > Why is all this work being put into Fedora 20? The maintenance window > is limited and as of the next release they won't even support non-KMS > drivers by default. Wouldn't make sense to look into a distribution > that provides and LTS release? Resources already seem to be limited > so having to chase after Fedora every 6 months to a year seems like a > waste of resources. The GTK3 and GNOME teams obviously have their > eyes on a different class of hardware than what is being used by > deployments. > > -Jon > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
Hello, things are looking good so far, we already have all the models booting into sugar 0.101 with wif apparentlyi working. I would like to take a step back and understand a bit better where we want to go with this. Some random thoughts and questions. * To really understand how much work is left I think we need some good testing, especially on the hardware related bits. I expect there will be lots of small things to fix, but it would be good to understand as early as possible if there are roadblocks. I'm a bad tester and I've never used the XO much, so I'm often not sure what is a regression and what is not... thus helping with this would be particularly appreciated. * Which deployments are planning to ship 0.102 soon and hence are interested in this work? I know of AU. Maybe Uruguay? * Do we need to support all the XO models? * Should we contribute the olpc-os-builder changes back to OLPC or fork it? I don't know if OLPC will do any active development on the linux side of things, if not maybe better to turn this into a sugarlabs thing. * Are interested deployments using olpc-update? If I'm not mistake AU is not. * Do we care about maintaining the GNOME "dual boot"? I'm afraid we do, but I want to make sure. * As I mentioned in some other thread I'm interested in setting up automated builds from sugar master. I have some vague plan of what it would look like and wrote bits of it. The basic idea is that you would push changes to github and get images automatically built. I think this is good for upstream testing but the same infrastructure could be used by deployments. Are people interested in using this? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Atom shell
Yes it's basically node.js + chrome + some custom bits to integrate the two. It would be perfect to write an OS fully in js (dream or nightmare? :P). On 12 May 2014 16:33, Gonzalo Odiard wrote: > This use node.js too, right? > > Gonzalo > > > On Mon, May 12, 2014 at 11:26 AM, Daniel Narvaez wrote: > >> Hi, >> >> github recently open sourced the shell they used to build the atom editor >> >> https://github.com/atom/atom-shell >> >> It sounds like it would be a pretty cool base for a future html5 only >> sugar. Or event just mostly-html5, it seems like this could be easily >> integrated with python stuff. >> >> Also it could be a good wrapper for web activities on GNOME/OS X/Windows. >> >> -- >> Daniel Narvaez >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
(II) Module "i2c" already built-in > > [32.684] (II) VIA(0): I2C bus "I2C bus 1" initialized. > > [32.684] (II) VIA(0): I2C bus "I2C bus 2" initialized. > > [32.684] (II) Loading sub module "fb" > > [32.684] (II) LoadModule: "fb" > > [32.684] (II) Loading /usr/lib/xorg/modules/libfb.so > > [32.685] (II) Module fb: vendor="X.Org Foundation" > > [32.685] compiled for 1.14.4, module version = 1.0.0 > > [32.685] ABI class: X.Org ANSI C Emulation, version 0.4 > > [32.685] (II) Loading sub module "exa" > > [32.685] (II) LoadModule: "exa" > > [32.685] (II) Loading /usr/lib/xorg/modules/libexa.so > > [32.686] (II) Module exa: vendor="X.Org Foundation" > > [32.686] compiled for 1.14.4, module version = 2.6.0 > > [32.686] ABI class: X.Org Video Driver, version 14.1 > > [32.686] (II) Loading sub module "ramdac" > > [32.686] (II) LoadModule: "ramdac" > > [32.686] (II) Module "ramdac" already built-in > > [32.686] (II) Loading sub module "ddc" > > [32.686] (II) LoadModule: "ddc" > > [32.686] (II) Module "ddc" already built-in > > [32.686] (II) VIA(0): Output CRT has no monitor section > > [32.686] (II) VIA(0): Output DVI has no monitor section > > [32.686] (II) VIA(0): Output LCD using monitor section LCD > > [32.686] (**) VIA(0): Option "DIPort" "DFP_HIGHLOW,DVP1" > > [32.686] (**) VIA(0): Option "PanelSize" "1200x900" > > [32.686] (II) VIA(0): Output TV has no monitor section > > [32.686] (II) VIA(0): Output HDMI has no monitor section > > [32.686] (II) VIA(0): Output DP has no monitor section > > [32.686] (II) VIA(0): Output DP-2 has no monitor section > > [32.686] (II) VIA(0): Output LCD-2 has no monitor section > > [32.686] (II) VIA(0): Output CRT-2 has no monitor section > > [32.703] (II) VIA(0): EDID for output CRT > > [32.704] (II) VIA(0): Printing probed modes for output LCD > > [32.704] (II) VIA(0): Modeline "1200x900"x49.7 57.27 1200 1211 > 1243 > > 1264 900 901 911 912 (45.3 kHz P) > > [32.704] (II) VIA(0): Output CRT disconnected > > [32.704] (II) VIA(0): Output LCD connected > > [32.704] (II) VIA(0): Using exact sizes for initial modes > > [32.704] (II) VIA(0): Output LCD using initial mode 1200x900 +0+0 > > [32.704] (II) VIA(0): Using default gamma of (1.0, 1.0, 1.0) unless > > otherwise stated. > > [32.704] (==) VIA(0): DPI set to (96, 96) > > [32.704] (--) Depth 24 pixmap format is 32 bpp > > [32.716] (II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0 > > [32.716] (II) VIA(0): [drm] Detect H6 chipset: 0007 chipid: 5122 > > [32.806] (EE) VIA(0): DRM open error > > [32.807] drmOpenDevice: node name is /dev/dri/card0 > > [32.812] drmOpenDevice: node name is /dev/dri/card0 > > [32.849] [drm] failed to load kernel module "chrome" > > [32.849] (EE) [drm] drmOpen failed. > > [32.849] (EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI. > > [32.853] (II) VIA(0): H6 3D Engine has been initialized. > > [32.853] (II) VIA(0): VIAInternalScreenInit > > [32.854] DEBUG: maxPitchBytes 16383 > > [32.854] (II) EXA(0): Offscreen pixmap area of 60005344 bytes > > [32.854] (II) EXA(0): Driver registered support for the following > > operations: > > [32.854] (II) Solid > > [32.854] (II) Copy > > [32.854] (II) Composite (RENDER acceleration) > > [32.854] (II) VIA(0): Enable EXA Now > > [32.854] (II) VIA(0): [EXA] Trying to enable EXA acceleration. > > > > > > > > On Mon, May 12, 2014 at 11:03 AM, Daniel Narvaez > > wrote: > >> > >> I'm not quite convinced this is due to the not initialized eth0 (I'm not > >> sure what that is due too though). From the serial console are you able > to > >> see the content of /var/log/Xorg.0.log (assuming there is one)? > >> > >> > >> On 12 May 2014 15:08, Gonzalo Odiard wrote: > >>> > >>> log from xo-1.5 > >>> > >>> Looks like eth0 is not initialized and all stop there. > >>> Probably you already know that, but xo-1 and xo-1.5 have a 8686 > wireless > >>> card, different to the 8787 in the xo-4 > >>> > >>> Gonzalo > >>> > >
[Sugar-devel] Atom shell
Hi, github recently open sourced the shell they used to build the atom editor https://github.com/atom/atom-shell It sounds like it would be a pretty cool base for a future html5 only sugar. Or event just mostly-html5, it seems like this could be easily integrated with python stuff. Also it could be a good wrapper for web activities on GNOME/OS X/Windows. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
ersion 14.1 > [32.686] (II) Loading sub module "ramdac" > [32.686] (II) LoadModule: "ramdac" > [32.686] (II) Module "ramdac" already built-in > [32.686] (II) Loading sub module "ddc" > [32.686] (II) LoadModule: "ddc" > [32.686] (II) Module "ddc" already built-in > [32.686] (II) VIA(0): Output CRT has no monitor section > [32.686] (II) VIA(0): Output DVI has no monitor section > [32.686] (II) VIA(0): Output LCD using monitor section LCD > [32.686] (**) VIA(0): Option "DIPort" "DFP_HIGHLOW,DVP1" > [32.686] (**) VIA(0): Option "PanelSize" "1200x900" > [32.686] (II) VIA(0): Output TV has no monitor section > [32.686] (II) VIA(0): Output HDMI has no monitor section > [32.686] (II) VIA(0): Output DP has no monitor section > [32.686] (II) VIA(0): Output DP-2 has no monitor section > [32.686] (II) VIA(0): Output LCD-2 has no monitor section > [32.686] (II) VIA(0): Output CRT-2 has no monitor section > [32.703] (II) VIA(0): EDID for output CRT > [32.704] (II) VIA(0): Printing probed modes for output LCD > [32.704] (II) VIA(0): Modeline "1200x900"x49.7 57.27 1200 1211 1243 > 1264 900 901 911 912 (45.3 kHz P) > [32.704] (II) VIA(0): Output CRT disconnected > [32.704] (II) VIA(0): Output LCD connected > [32.704] (II) VIA(0): Using exact sizes for initial modes > [32.704] (II) VIA(0): Output LCD using initial mode 1200x900 +0+0 > [32.704] (II) VIA(0): Using default gamma of (1.0, 1.0, 1.0) unless > otherwise stated. > [32.704] (==) VIA(0): DPI set to (96, 96) > [32.704] (--) Depth 24 pixmap format is 32 bpp > [32.716] (II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0 > [32.716] (II) VIA(0): [drm] Detect H6 chipset: 0007 chipid: 5122 > [32.806] (EE) VIA(0): DRM open error > [32.807] drmOpenDevice: node name is /dev/dri/card0 > [32.812] drmOpenDevice: node name is /dev/dri/card0 > [32.849] [drm] failed to load kernel module "chrome" > [32.849] (EE) [drm] drmOpen failed. > [32.849] (EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI. > [32.853] (II) VIA(0): H6 3D Engine has been initialized. > [32.853] (II) VIA(0): VIAInternalScreenInit > [32.854] DEBUG: maxPitchBytes 16383 > [32.854] (II) EXA(0): Offscreen pixmap area of 60005344 bytes > [32.854] (II) EXA(0): Driver registered support for the following > operations: > [32.854] (II) Solid > [32.854] (II) Copy > [32.854] (II) Composite (RENDER acceleration) > [32.854] (II) VIA(0): Enable EXA Now > [32.854] (II) VIA(0): [EXA] Trying to enable EXA acceleration. > > > > On Mon, May 12, 2014 at 11:03 AM, Daniel Narvaez wrote: > >> I'm not quite convinced this is due to the not initialized eth0 (I'm not >> sure what that is due too though). From the serial console are you able to >> see the content of /var/log/Xorg.0.log (assuming there is one)? >> >> >> On 12 May 2014 15:08, Gonzalo Odiard wrote: >> >>> log from xo-1.5 >>> >>> Looks like eth0 is not initialized and all stop there. >>> Probably you already know that, but xo-1 and xo-1.5 have a 8686 wireless >>> card, different to the 8787 in the xo-4 >>> >>> Gonzalo >>> >>> >>> On Mon, May 12, 2014 at 9:36 AM, Daniel Narvaez wrote: >>> >>>> Ok, at least the partitions problem is fixed then. If Gonzalo can look >>>> at the logs with a serial port that might tell what is going on. I susoect >>>> the X driver but hard to say blindly :) >>>> >>>> >>>> On 12 May 2014 14:34, Martin Abente wrote: >>>> >>>>> Regarding XO 1.5 image, no more kernel panic, but as Gonzalo mentioned >>>>> the fading problem is still present. >>>>> >>>>> >>>>> On Mon, May 12, 2014 at 7:53 AM, Gonzalo Odiard >>>> > wrote: >>>>> >>>>>> I will attach a serial cable later and report. >>>>>> >>>>>> Gonzalo >>>>>> >>>>>> >>>>>> On Mon, May 12, 2014 at 8:51 AM, Daniel Narvaez >>>>>> wrote: >>>>>> >>>>>>> How far does it get? What are the last messages you see? >>>>>>> >>>>>>> Mostly I wonder if it's the partitions issue that tch reported >>>>>>> yesterday or if we fail when running X. >&
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
I'm not quite convinced this is due to the not initialized eth0 (I'm not sure what that is due too though). From the serial console are you able to see the content of /var/log/Xorg.0.log (assuming there is one)? On 12 May 2014 15:08, Gonzalo Odiard wrote: > log from xo-1.5 > > Looks like eth0 is not initialized and all stop there. > Probably you already know that, but xo-1 and xo-1.5 have a 8686 wireless > card, different to the 8787 in the xo-4 > > Gonzalo > > > On Mon, May 12, 2014 at 9:36 AM, Daniel Narvaez wrote: > >> Ok, at least the partitions problem is fixed then. If Gonzalo can look at >> the logs with a serial port that might tell what is going on. I susoect the >> X driver but hard to say blindly :) >> >> >> On 12 May 2014 14:34, Martin Abente wrote: >> >>> Regarding XO 1.5 image, no more kernel panic, but as Gonzalo mentioned >>> the fading problem is still present. >>> >>> >>> On Mon, May 12, 2014 at 7:53 AM, Gonzalo Odiard >>> wrote: >>> >>>> I will attach a serial cable later and report. >>>> >>>> Gonzalo >>>> >>>> >>>> On Mon, May 12, 2014 at 8:51 AM, Daniel Narvaez wrote: >>>> >>>>> How far does it get? What are the last messages you see? >>>>> >>>>> Mostly I wonder if it's the partitions issue that tch reported >>>>> yesterday or if we fail when running X. >>>>> >>>>> >>>>> On Monday, 12 May 2014, Gonzalo Odiard wrote: >>>>> >>>>>> xo-1.5 image do not boot, and show a strange gey patterns in the >>>>>> screen. >>>>>> >>>>>> Gonzalo >>>>>> >>>>>> >>>>>> On Mon, May 12, 2014 at 8:01 AM, Daniel Narvaez >>>>>> wrote: >>>>>> >>>>>> The xo1 image boots into sugar (latest from git) and wifi works. I'm >>>>>> now building xo4 images >>>>>> >>>>>> >>>>>> On 12 May 2014 02:12, Daniel Narvaez wrote: >>>>>> >>>>>> A couple more images, for xo1 and xo1.5. They have sugar packages >>>>>> built from latest sugar git. I have not tested them yet so they might not >>>>>> even boot, but if someone gives them a try please let me know how they >>>>>> works. >>>>>> >>>>>> http://146.185.144.82:3000/images/xo1/1/ >>>>>> http://146.185.144.82:3000/images/xo1.5/1/ >>>>>> >>>>>> The xo1.5 one also *attempts* to fix the issue reported by Martin. >>>>>> The problem is that I'm running the x86 build slave inside docker.io, >>>>>> which doesn't like xpart. So I patched olpc-os-builder to manually >>>>>> losetup >>>>>> the partitions, but it's sort of tricky to get right. It will work >>>>>> eventually :) >>>>>> >>>>>> I have arm packages for latest git almost built, so tomorrow I should >>>>>> be able to build xo1.75 and xo4 images too. The oob configurations and >>>>>> some >>>>>> initial bits of automated builds infra are now here >>>>>> >>>>>> https://github.com/dnarvaez/xugar >>>>>> >>>>>> >>>>>> >>>>>> On 11 May 2014 20:49, Daniel Narvaez wrote: >>>>>> >>>>>> This could be a change I made. I will investigate and let you know. >>>>>> >>>>>> >>>>>> On 11 May 2014 20:31, Martin Abente >>>>>> wrote: >>>>>> >>>>>> Hey Daniel, >>>>>> >>>>>> Could you check if this is correct? >>>>>> >>>>>> $md5sum 10001xx1.zd >>>>>> $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd >>>>>> >>>>>> >>>>>> Tested with 2 different XOs 1.5 and I am getting kernel panic errors >>>>>> very early on the boot sequence, with message: >>>>>> >>>>>> tmpfs: No value for mount option 'strictatime' >>>>>> mount: mounting on /newrun failed: invalid argument >>>>>> mount used greatest stack depth 6752 bytes left. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard < >>>>>> godi...@sugarlabs.org> wrote: >>>>>> >>>>>> Downloading... >>>>>> >>>>>> >>>>>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente < >>>>>> martin.abente.lah...@gmail.com> wrote: >>>>>> >>>>>> Downloading 10001xx1.zd , will let you know how it goes soon. >>>>>> >>>>>> >>>>>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez >>>>> > wrote: >>>>>> >>>>>> I made builds for xo1 and xo1.5 with the firmware change >>>>>> >>>>>> <http://sugarlabs.org/~dnarvaez/oob/images/> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Daniel Narvaez >>>>> >>>>> >>>> >>>> >>>> -- >>>> Gonzalo Odiard >>>> >>>> SugarLabs - Software for children learning >>>> >>> >>> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
Ok, at least the partitions problem is fixed then. If Gonzalo can look at the logs with a serial port that might tell what is going on. I susoect the X driver but hard to say blindly :) On 12 May 2014 14:34, Martin Abente wrote: > Regarding XO 1.5 image, no more kernel panic, but as Gonzalo mentioned the > fading problem is still present. > > > On Mon, May 12, 2014 at 7:53 AM, Gonzalo Odiard wrote: > >> I will attach a serial cable later and report. >> >> Gonzalo >> >> >> On Mon, May 12, 2014 at 8:51 AM, Daniel Narvaez wrote: >> >>> How far does it get? What are the last messages you see? >>> >>> Mostly I wonder if it's the partitions issue that tch reported yesterday >>> or if we fail when running X. >>> >>> >>> On Monday, 12 May 2014, Gonzalo Odiard wrote: >>> >>>> xo-1.5 image do not boot, and show a strange gey patterns in the screen. >>>> >>>> Gonzalo >>>> >>>> >>>> On Mon, May 12, 2014 at 8:01 AM, Daniel Narvaez wrote: >>>> >>>> The xo1 image boots into sugar (latest from git) and wifi works. I'm >>>> now building xo4 images >>>> >>>> >>>> On 12 May 2014 02:12, Daniel Narvaez wrote: >>>> >>>> A couple more images, for xo1 and xo1.5. They have sugar packages built >>>> from latest sugar git. I have not tested them yet so they might not even >>>> boot, but if someone gives them a try please let me know how they works. >>>> >>>> http://146.185.144.82:3000/images/xo1/1/ >>>> http://146.185.144.82:3000/images/xo1.5/1/ >>>> >>>> The xo1.5 one also *attempts* to fix the issue reported by Martin. The >>>> problem is that I'm running the x86 build slave inside docker.io, >>>> which doesn't like xpart. So I patched olpc-os-builder to manually losetup >>>> the partitions, but it's sort of tricky to get right. It will work >>>> eventually :) >>>> >>>> I have arm packages for latest git almost built, so tomorrow I should >>>> be able to build xo1.75 and xo4 images too. The oob configurations and some >>>> initial bits of automated builds infra are now here >>>> >>>> https://github.com/dnarvaez/xugar >>>> >>>> >>>> >>>> On 11 May 2014 20:49, Daniel Narvaez wrote: >>>> >>>> This could be a change I made. I will investigate and let you know. >>>> >>>> >>>> On 11 May 2014 20:31, Martin Abente wrote: >>>> >>>> Hey Daniel, >>>> >>>> Could you check if this is correct? >>>> >>>> $md5sum 10001xx1.zd >>>> $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd >>>> >>>> >>>> Tested with 2 different XOs 1.5 and I am getting kernel panic errors >>>> very early on the boot sequence, with message: >>>> >>>> tmpfs: No value for mount option 'strictatime' >>>> mount: mounting on /newrun failed: invalid argument >>>> mount used greatest stack depth 6752 bytes left. >>>> >>>> >>>> >>>> >>>> >>>> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard >>> > wrote: >>>> >>>> Downloading... >>>> >>>> >>>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente < >>>> martin.abente.lah...@gmail.com> wrote: >>>> >>>> Downloading 10001xx1.zd , will let you know how it goes soon. >>>> >>>> >>>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez >>>> wrote: >>>> >>>> I made builds for xo1 and xo1.5 with the firmware change >>>> >>>> <http://sugarlabs.org/~dnarvaez/oob/images/> >>>> >>>> >>> >>> -- >>> Daniel Narvaez >>> >>> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Software for children learning >> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
How far does it get? What are the last messages you see? Mostly I wonder if it's the partitions issue that tch reported yesterday or if we fail when running X. On Monday, 12 May 2014, Gonzalo Odiard wrote: > xo-1.5 image do not boot, and show a strange gey patterns in the screen. > > Gonzalo > > > On Mon, May 12, 2014 at 8:01 AM, Daniel Narvaez wrote: > > The xo1 image boots into sugar (latest from git) and wifi works. I'm now > building xo4 images > > > On 12 May 2014 02:12, Daniel Narvaez wrote: > > A couple more images, for xo1 and xo1.5. They have sugar packages built > from latest sugar git. I have not tested them yet so they might not even > boot, but if someone gives them a try please let me know how they works. > > http://146.185.144.82:3000/images/xo1/1/ > http://146.185.144.82:3000/images/xo1.5/1/ > > The xo1.5 one also *attempts* to fix the issue reported by Martin. The > problem is that I'm running the x86 build slave inside docker.io, which > doesn't like xpart. So I patched olpc-os-builder to manually losetup the > partitions, but it's sort of tricky to get right. It will work eventually :) > > I have arm packages for latest git almost built, so tomorrow I should be > able to build xo1.75 and xo4 images too. The oob configurations and some > initial bits of automated builds infra are now here > > https://github.com/dnarvaez/xugar > > > > On 11 May 2014 20:49, Daniel Narvaez wrote: > > This could be a change I made. I will investigate and let you know. > > > On 11 May 2014 20:31, Martin Abente wrote: > > Hey Daniel, > > Could you check if this is correct? > > $md5sum 10001xx1.zd > $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd > > > Tested with 2 different XOs 1.5 and I am getting kernel panic errors very > early on the boot sequence, with message: > > tmpfs: No value for mount option 'strictatime' > mount: mounting on /newrun failed: invalid argument > mount used greatest stack depth 6752 bytes left. > > > > > > On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard wrote: > > Downloading... > > > On Sun, May 11, 2014 at 1:31 PM, Martin Abente < > martin.abente.lah...@gmail.com> wrote: > > Downloading 10001xx1.zd , will let you know how it goes soon. > > > On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote: > > I made builds for xo1 and xo1.5 with the firmware change > > <http://sugarlabs.org/~dnarvaez/oob/images/> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error ./osbuild build
Looks like a network error, either on your side or github. I'd make sure your connection works and retry (maybe in a bit). On Monday, 12 May 2014, Athar Haque wrote: > Hello everyone, > > I was playing around with things and unfortunately had to finally setup > the development environment again but this time I got the following error > when with the command "./osbuild build". > > * Building sugar-web > > Command failed: volo -nostamp -f add > > Error: connect ECONNREFUSED > Retrying (attempt 1) in 1 minute > ^CTraceback (most recent call last): > File "/home/broot/sugar-build/build/commands/broot/run", line 12, in > > if not main.run_build(): > File > "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/main.py", > line 27, in run_build > if not build.build(): > File > "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/build.py", > line 86, in build > if not _build_module(module): > File > "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/build.py", > line 223, in _build_module > _builders[module.build_system](module) > File > "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/build.py", > line 197, in _build_grunt > command.run(["volo", "-nostamp", "-f", "add"], retry=10) > File > "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/command.py", > line 40, in run > time.sleep(60) > > > > Please help me out. > > -- > Regards, > Nazrul > irc - native93 > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
The xo1 image boots into sugar (latest from git) and wifi works. I'm now building xo4 images On 12 May 2014 02:12, Daniel Narvaez wrote: > A couple more images, for xo1 and xo1.5. They have sugar packages built > from latest sugar git. I have not tested them yet so they might not even > boot, but if someone gives them a try please let me know how they works. > > http://146.185.144.82:3000/images/xo1/1/ > http://146.185.144.82:3000/images/xo1.5/1/ > > The xo1.5 one also *attempts* to fix the issue reported by Martin. The > problem is that I'm running the x86 build slave inside docker.io, which > doesn't like xpart. So I patched olpc-os-builder to manually losetup the > partitions, but it's sort of tricky to get right. It will work eventually :) > > I have arm packages for latest git almost built, so tomorrow I should be > able to build xo1.75 and xo4 images too. The oob configurations and some > initial bits of automated builds infra are now here > > https://github.com/dnarvaez/xugar > > > > On 11 May 2014 20:49, Daniel Narvaez wrote: > >> This could be a change I made. I will investigate and let you know. >> >> >> On 11 May 2014 20:31, Martin Abente wrote: >> >>> Hey Daniel, >>> >>> Could you check if this is correct? >>> >>> $md5sum 10001xx1.zd >>> $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd >>> >>> >>> Tested with 2 different XOs 1.5 and I am getting kernel panic errors >>> very early on the boot sequence, with message: >>> >>> tmpfs: No value for mount option 'strictatime' >>> mount: mounting on /newrun failed: invalid argument >>> mount used greatest stack depth 6752 bytes left. >>> >>> >>> >>> >>> >>> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard >>> wrote: >>> >>>> Downloading... >>>> >>>> >>>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente < >>>> martin.abente.lah...@gmail.com> wrote: >>>> >>>>> Downloading 10001xx1.zd , will let you know how it goes soon. >>>>> >>>>> >>>>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez >>>>> wrote: >>>>> >>>>>> I made builds for xo1 and xo1.5 with the firmware change >>>>>> >>>>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>>>> >>>>>> The xo1 boots into sugar but there are no activities installed (I >>>>>> probably got something wrong in the ini). Testing on the xo1.5 one would >>>>>> be >>>>>> welcome, I'm curious if firmware solves the startup freeze. >>>>>> >>>>>> >>>>>> On 11 May 2014 00:24, Martin Abente >>>>>> wrote: >>>>>> >>>>>>> great!! Let me know when you have an image with this! >>>>>>> >>>>>>> >>>>>>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez >>>>>> > wrote: >>>>>>> >>>>>>>> Firmware loading works with the rebuilt systemd! I have not tested >>>>>>>> much but wifi works now. Next step, build images with latest sugar... >>>>>>>> >>>>>>>> >>>>>>>> On 10 May 2014 01:22, Daniel Narvaez wrote: >>>>>>>> >>>>>>>>> I built a xo4 image, which like 1.75 boots fine into sugar >>>>>>>>> >>>>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/ >>>>>>>>> >>>>>>>>> The main problem, as discussed, is that firmwares are not loaded. >>>>>>>>> I'm building a systemd rpm with firmware loading enabled. If we can >>>>>>>>> get >>>>>>>>> wifi working then it should be easier to play with stuff, building in >>>>>>>>> the >>>>>>>>> virtual machine takes really too long. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 9 May 2014 14:13, Daniel Narvaez wrote: >>>>>>>>> >>>>>>>>>> I built an image for 1.75 >>>>>>>>>> >>>>>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>>>>
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
A couple more images, for xo1 and xo1.5. They have sugar packages built from latest sugar git. I have not tested them yet so they might not even boot, but if someone gives them a try please let me know how they works. http://146.185.144.82:3000/images/xo1/1/ http://146.185.144.82:3000/images/xo1.5/1/ The xo1.5 one also *attempts* to fix the issue reported by Martin. The problem is that I'm running the x86 build slave inside docker.io, which doesn't like xpart. So I patched olpc-os-builder to manually losetup the partitions, but it's sort of tricky to get right. It will work eventually :) I have arm packages for latest git almost built, so tomorrow I should be able to build xo1.75 and xo4 images too. The oob configurations and some initial bits of automated builds infra are now here https://github.com/dnarvaez/xugar On 11 May 2014 20:49, Daniel Narvaez wrote: > This could be a change I made. I will investigate and let you know. > > > On 11 May 2014 20:31, Martin Abente wrote: > >> Hey Daniel, >> >> Could you check if this is correct? >> >> $md5sum 10001xx1.zd >> $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd >> >> >> Tested with 2 different XOs 1.5 and I am getting kernel panic errors very >> early on the boot sequence, with message: >> >> tmpfs: No value for mount option 'strictatime' >> mount: mounting on /newrun failed: invalid argument >> mount used greatest stack depth 6752 bytes left. >> >> >> >> >> >> On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard >> wrote: >> >>> Downloading... >>> >>> >>> On Sun, May 11, 2014 at 1:31 PM, Martin Abente < >>> martin.abente.lah...@gmail.com> wrote: >>> >>>> Downloading 10001xx1.zd , will let you know how it goes soon. >>>> >>>> >>>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez >>>> wrote: >>>> >>>>> I made builds for xo1 and xo1.5 with the firmware change >>>>> >>>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>>> >>>>> The xo1 boots into sugar but there are no activities installed (I >>>>> probably got something wrong in the ini). Testing on the xo1.5 one would >>>>> be >>>>> welcome, I'm curious if firmware solves the startup freeze. >>>>> >>>>> >>>>> On 11 May 2014 00:24, Martin Abente wrote: >>>>> >>>>>> great!! Let me know when you have an image with this! >>>>>> >>>>>> >>>>>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez >>>>>> wrote: >>>>>> >>>>>>> Firmware loading works with the rebuilt systemd! I have not tested >>>>>>> much but wifi works now. Next step, build images with latest sugar... >>>>>>> >>>>>>> >>>>>>> On 10 May 2014 01:22, Daniel Narvaez wrote: >>>>>>> >>>>>>>> I built a xo4 image, which like 1.75 boots fine into sugar >>>>>>>> >>>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/ >>>>>>>> >>>>>>>> The main problem, as discussed, is that firmwares are not loaded. >>>>>>>> I'm building a systemd rpm with firmware loading enabled. If we can get >>>>>>>> wifi working then it should be easier to play with stuff, building in >>>>>>>> the >>>>>>>> virtual machine takes really too long. >>>>>>>> >>>>>>>> >>>>>>>> On 9 May 2014 14:13, Daniel Narvaez wrote: >>>>>>>> >>>>>>>>> I built an image for 1.75 >>>>>>>>> >>>>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>>>>>>> >>>>>>>>> I've not been able to test yet. I don't have my usual usb stick >>>>>>>>> with me and having troubles finding something the XO likes. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8 May 2014 02:04, Daniel Narvaez wrote: >>>>>>>>> >>>>>>>>>> As an update, I have patched xorg-x11-drv-dove and built rpms for >>>>>>>>>> it >>>>>>>>>> >>>>>>>>>> http://s
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
This could be a change I made. I will investigate and let you know. On 11 May 2014 20:31, Martin Abente wrote: > Hey Daniel, > > Could you check if this is correct? > > $md5sum 10001xx1.zd > $0cc8f3f71d636c8dc4464ffb8bf1847b 10001xx1.zd > > > Tested with 2 different XOs 1.5 and I am getting kernel panic errors very > early on the boot sequence, with message: > > tmpfs: No value for mount option 'strictatime' > mount: mounting on /newrun failed: invalid argument > mount used greatest stack depth 6752 bytes left. > > > > > > On Sun, May 11, 2014 at 12:47 PM, Gonzalo Odiard wrote: > >> Downloading... >> >> >> On Sun, May 11, 2014 at 1:31 PM, Martin Abente < >> martin.abente.lah...@gmail.com> wrote: >> >>> Downloading 10001xx1.zd , will let you know how it goes soon. >>> >>> >>> On Sun, May 11, 2014 at 12:19 PM, Daniel Narvaez wrote: >>> >>>> I made builds for xo1 and xo1.5 with the firmware change >>>> >>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>> >>>> The xo1 boots into sugar but there are no activities installed (I >>>> probably got something wrong in the ini). Testing on the xo1.5 one would be >>>> welcome, I'm curious if firmware solves the startup freeze. >>>> >>>> >>>> On 11 May 2014 00:24, Martin Abente wrote: >>>> >>>>> great!! Let me know when you have an image with this! >>>>> >>>>> >>>>> On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez >>>>> wrote: >>>>> >>>>>> Firmware loading works with the rebuilt systemd! I have not tested >>>>>> much but wifi works now. Next step, build images with latest sugar... >>>>>> >>>>>> >>>>>> On 10 May 2014 01:22, Daniel Narvaez wrote: >>>>>> >>>>>>> I built a xo4 image, which like 1.75 boots fine into sugar >>>>>>> >>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/ >>>>>>> >>>>>>> The main problem, as discussed, is that firmwares are not loaded. >>>>>>> I'm building a systemd rpm with firmware loading enabled. If we can get >>>>>>> wifi working then it should be easier to play with stuff, building in >>>>>>> the >>>>>>> virtual machine takes really too long. >>>>>>> >>>>>>> >>>>>>> On 9 May 2014 14:13, Daniel Narvaez wrote: >>>>>>> >>>>>>>> I built an image for 1.75 >>>>>>>> >>>>>>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>>>>>> >>>>>>>> I've not been able to test yet. I don't have my usual usb stick >>>>>>>> with me and having troubles finding something the XO likes. >>>>>>>> >>>>>>>> >>>>>>>> On 8 May 2014 02:04, Daniel Narvaez wrote: >>>>>>>> >>>>>>>>> As an update, I have patched xorg-x11-drv-dove and built rpms for >>>>>>>>> it >>>>>>>>> >>>>>>>>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >>>>>>>>> >>>>>>>>> Now building an image with those. >>>>>>>>> >>>>>>>>> >>>>>>>>> On 7 May 2014 15:18, Martin Abente >>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Great! >>>>>>>>>> >>>>>>>>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing >>>>>>>>>> :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez < >>>>>>>>>> dwnarv...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> On 7 May 2014 01:44, James Cameron wrote: >>>>>>>>>>> >>>>>>>>>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>>>>>>>>> > [...] And with the XO stuck on Fedor
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
I made builds for xo1 and xo1.5 with the firmware change http://sugarlabs.org/~dnarvaez/oob/images/ The xo1 boots into sugar but there are no activities installed (I probably got something wrong in the ini). Testing on the xo1.5 one would be welcome, I'm curious if firmware solves the startup freeze. On 11 May 2014 00:24, Martin Abente wrote: > great!! Let me know when you have an image with this! > > > On Sat, May 10, 2014 at 4:36 PM, Daniel Narvaez wrote: > >> Firmware loading works with the rebuilt systemd! I have not tested much >> but wifi works now. Next step, build images with latest sugar... >> >> >> On 10 May 2014 01:22, Daniel Narvaez wrote: >> >>> I built a xo4 image, which like 1.75 boots fine into sugar >>> >>> http://sugarlabs.org/~dnarvaez/oob/images/xo4/ >>> >>> The main problem, as discussed, is that firmwares are not loaded. I'm >>> building a systemd rpm with firmware loading enabled. If we can get wifi >>> working then it should be easier to play with stuff, building in the >>> virtual machine takes really too long. >>> >>> >>> On 9 May 2014 14:13, Daniel Narvaez wrote: >>> >>>> I built an image for 1.75 >>>> >>>> http://sugarlabs.org/~dnarvaez/oob/images/ >>>> >>>> I've not been able to test yet. I don't have my usual usb stick with me >>>> and having troubles finding something the XO likes. >>>> >>>> >>>> On 8 May 2014 02:04, Daniel Narvaez wrote: >>>> >>>>> As an update, I have patched xorg-x11-drv-dove and built rpms for it >>>>> >>>>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >>>>> >>>>> Now building an image with those. >>>>> >>>>> >>>>> On 7 May 2014 15:18, Martin Abente wrote: >>>>> >>>>>> Great! >>>>>> >>>>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >>>>>> >>>>>> >>>>>> >>>>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez >>>>>> wrote: >>>>>> >>>>>>> On 7 May 2014 01:44, James Cameron wrote: >>>>>>> >>>>>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>>>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>>>>>> > enough introspection to make the port compatible with it. >>>>>>>> >>>>>>>> If anybody would like to work on moving olpc-os-builder to something >>>>>>>> more recent, feel free. It isn't something OLPC is looking at right >>>>>>>> now, but it would be helpful to the users. >>>>>>>> >>>>>>>> Not the die hard 0.98 users, of course. ;-) >>>>>>> >>>>>>> >>>>>>> I'm giving that a try. I was able to build a Fedora 20 image for XO >>>>>>> 1.5 >>>>>>> >>>>>>> https://github.com/dnarvaez/olpc-os-builder >>>>>>> >>>>>>> I don't have hardware to test that though... I'm now trying to build >>>>>>> for 1.75 which is harder but I can actually test. I need to rebuild the >>>>>>> X >>>>>>> driver but I think that will require some patching, let's see if I can >>>>>>> get >>>>>>> it to work... >>>>>>> >>>>>>> ___ >>>>>>> Devel mailing list >>>>>>> de...@lists.laptop.org >>>>>>> http://lists.laptop.org/listinfo/devel >>>>>>> >>>>>>> >>>>>> >>>>>> ___ >>>>>> Sugar-devel mailing list >>>>>> Sugar-devel@lists.sugarlabs.org >>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Daniel Narvaez >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
Firmware loading works with the rebuilt systemd! I have not tested much but wifi works now. Next step, build images with latest sugar... On 10 May 2014 01:22, Daniel Narvaez wrote: > I built a xo4 image, which like 1.75 boots fine into sugar > > http://sugarlabs.org/~dnarvaez/oob/images/xo4/ > > The main problem, as discussed, is that firmwares are not loaded. I'm > building a systemd rpm with firmware loading enabled. If we can get wifi > working then it should be easier to play with stuff, building in the > virtual machine takes really too long. > > > On 9 May 2014 14:13, Daniel Narvaez wrote: > >> I built an image for 1.75 >> >> http://sugarlabs.org/~dnarvaez/oob/images/ >> >> I've not been able to test yet. I don't have my usual usb stick with me >> and having troubles finding something the XO likes. >> >> >> On 8 May 2014 02:04, Daniel Narvaez wrote: >> >>> As an update, I have patched xorg-x11-drv-dove and built rpms for it >>> >>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >>> >>> Now building an image with those. >>> >>> >>> On 7 May 2014 15:18, Martin Abente wrote: >>> >>>> Great! >>>> >>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >>>> >>>> >>>> >>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: >>>> >>>>> On 7 May 2014 01:44, James Cameron wrote: >>>>> >>>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>>>> > enough introspection to make the port compatible with it. >>>>>> >>>>>> If anybody would like to work on moving olpc-os-builder to something >>>>>> more recent, feel free. It isn't something OLPC is looking at right >>>>>> now, but it would be helpful to the users. >>>>>> >>>>>> Not the die hard 0.98 users, of course. ;-) >>>>> >>>>> >>>>> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >>>>> >>>>> https://github.com/dnarvaez/olpc-os-builder >>>>> >>>>> I don't have hardware to test that though... I'm now trying to build >>>>> for 1.75 which is harder but I can actually test. I need to rebuild the X >>>>> driver but I think that will require some patching, let's see if I can get >>>>> it to work... >>>>> >>>>> ___ >>>>> Devel mailing list >>>>> de...@lists.laptop.org >>>>> http://lists.laptop.org/listinfo/devel >>>>> >>>>> >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Automated XO builds
Hello, I would like to setup automated XO images builds based on F20, the "official" OLPC kernel and sugar from git. I think we have most of the bits in place to do that, except for a decent ARM machine. The VM I'm using is really really too slow, it takes like 10 hours to complete an olpc-os-builder build. We either need a faster virtual machine (but I suspect we would spend a lot of server resources to be decently fast on emulation), or an always-on XO4 on a good internet connection. Any idea on how to go about this? I think automated builds for the XO would help development and testing a lot. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
By the way, I suspect the issue with small icons is something we already fixed in 0.101. As soon as we have the base system working decently I'm planning to make builds with latest sugar from git. On 10 May 2014 01:22, Daniel Narvaez wrote: > I built a xo4 image, which like 1.75 boots fine into sugar > > http://sugarlabs.org/~dnarvaez/oob/images/xo4/ > > The main problem, as discussed, is that firmwares are not loaded. I'm > building a systemd rpm with firmware loading enabled. If we can get wifi > working then it should be easier to play with stuff, building in the > virtual machine takes really too long. > > > On 9 May 2014 14:13, Daniel Narvaez wrote: > >> I built an image for 1.75 >> >> http://sugarlabs.org/~dnarvaez/oob/images/ >> >> I've not been able to test yet. I don't have my usual usb stick with me >> and having troubles finding something the XO likes. >> >> >> On 8 May 2014 02:04, Daniel Narvaez wrote: >> >>> As an update, I have patched xorg-x11-drv-dove and built rpms for it >>> >>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >>> >>> Now building an image with those. >>> >>> >>> On 7 May 2014 15:18, Martin Abente wrote: >>> >>>> Great! >>>> >>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >>>> >>>> >>>> >>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: >>>> >>>>> On 7 May 2014 01:44, James Cameron wrote: >>>>> >>>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>>>> > enough introspection to make the port compatible with it. >>>>>> >>>>>> If anybody would like to work on moving olpc-os-builder to something >>>>>> more recent, feel free. It isn't something OLPC is looking at right >>>>>> now, but it would be helpful to the users. >>>>>> >>>>>> Not the die hard 0.98 users, of course. ;-) >>>>> >>>>> >>>>> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >>>>> >>>>> https://github.com/dnarvaez/olpc-os-builder >>>>> >>>>> I don't have hardware to test that though... I'm now trying to build >>>>> for 1.75 which is harder but I can actually test. I need to rebuild the X >>>>> driver but I think that will require some patching, let's see if I can get >>>>> it to work... >>>>> >>>>> ___ >>>>> Devel mailing list >>>>> de...@lists.laptop.org >>>>> http://lists.laptop.org/listinfo/devel >>>>> >>>>> >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
I built a xo4 image, which like 1.75 boots fine into sugar http://sugarlabs.org/~dnarvaez/oob/images/xo4/ The main problem, as discussed, is that firmwares are not loaded. I'm building a systemd rpm with firmware loading enabled. If we can get wifi working then it should be easier to play with stuff, building in the virtual machine takes really too long. On 9 May 2014 14:13, Daniel Narvaez wrote: > I built an image for 1.75 > > http://sugarlabs.org/~dnarvaez/oob/images/ > > I've not been able to test yet. I don't have my usual usb stick with me > and having troubles finding something the XO likes. > > > On 8 May 2014 02:04, Daniel Narvaez wrote: > >> As an update, I have patched xorg-x11-drv-dove and built rpms for it >> >> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >> >> Now building an image with those. >> >> >> On 7 May 2014 15:18, Martin Abente wrote: >> >>> Great! >>> >>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >>> >>> >>> >>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: >>> >>>> On 7 May 2014 01:44, James Cameron wrote: >>>> >>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>>> > enough introspection to make the port compatible with it. >>>>> >>>>> If anybody would like to work on moving olpc-os-builder to something >>>>> more recent, feel free. It isn't something OLPC is looking at right >>>>> now, but it would be helpful to the users. >>>>> >>>>> Not the die hard 0.98 users, of course. ;-) >>>> >>>> >>>> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >>>> >>>> https://github.com/dnarvaez/olpc-os-builder >>>> >>>> I don't have hardware to test that though... I'm now trying to build >>>> for 1.75 which is harder but I can actually test. I need to rebuild the X >>>> driver but I think that will require some patching, let's see if I can get >>>> it to work... >>>> >>>> ___ >>>> Devel mailing list >>>> de...@lists.laptop.org >>>> http://lists.laptop.org/listinfo/devel >>>> >>>> >>> >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 9 May 2014 15:50, Peter Robinson wrote: > >>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: > >>> > [...] And with the XO stuck on Fedora 18 we might not have good > >>> > enough introspection to make the port compatible with it. > >>> > >>> If anybody would like to work on moving olpc-os-builder to something > >>> more recent, feel free. It isn't something OLPC is looking at right > >>> now, but it would be helpful to the users. > >>> > >>> Not the die hard 0.98 users, of course. ;-) > >> > >> > >> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 > >> > >> https://github.com/dnarvaez/olpc-os-builder > > > > olpc-os-builder git master also has F20 support, as of a few months > > ago. Can't remember how good the result was. > > I suspect wifi and anything that needed firmware will fail to work > because of changes in the firmware loading interface needs newer > kernels (3.4 is too old for example) > Is this the change you are referring to https://lists.fedoraproject.org/pipermail/arm/2013-June/006116.html Rebuilding systemd wouldn't be too bad if it solves it... Support of the XOs in Fedora upstream is something I've been asked > about a number of times of late by varying different people. That would be awesome of course. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 9 May 2014 14:24, Daniel Drake wrote: > On Wed, May 7, 2014 at 9:01 PM, Daniel Narvaez > wrote: > > On 7 May 2014 01:44, James Cameron wrote: > >> > >> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: > >> > [...] And with the XO stuck on Fedora 18 we might not have good > >> > enough introspection to make the port compatible with it. > >> > >> If anybody would like to work on moving olpc-os-builder to something > >> more recent, feel free. It isn't something OLPC is looking at right > >> now, but it would be helpful to the users. > >> > >> Not the die hard 0.98 users, of course. ;-) > > > > > > I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 > > > > https://github.com/dnarvaez/olpc-os-builder > > olpc-os-builder git master also has F20 support, as of a few months > ago. Can't remember how good the result was. > Does the 3.10 kernel which is used there have olpc patches applied? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
I built an image for 1.75 http://sugarlabs.org/~dnarvaez/oob/images/ I've not been able to test yet. I don't have my usual usb stick with me and having troubles finding something the XO likes. On 8 May 2014 02:04, Daniel Narvaez wrote: > As an update, I have patched xorg-x11-drv-dove and built rpms for it > > http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ > > Now building an image with those. > > > On 7 May 2014 15:18, Martin Abente wrote: > >> Great! >> >> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >> >> >> >> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: >> >>> On 7 May 2014 01:44, James Cameron wrote: >>> >>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>> > enough introspection to make the port compatible with it. >>>> >>>> If anybody would like to work on moving olpc-os-builder to something >>>> more recent, feel free. It isn't something OLPC is looking at right >>>> now, but it would be helpful to the users. >>>> >>>> Not the die hard 0.98 users, of course. ;-) >>> >>> >>> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >>> >>> https://github.com/dnarvaez/olpc-os-builder >>> >>> I don't have hardware to test that though... I'm now trying to build for >>> 1.75 which is harder but I can actually test. I need to rebuild the X >>> driver but I think that will require some patching, let's see if I can get >>> it to work... >>> >>> _______ >>> Devel mailing list >>> de...@lists.laptop.org >>> http://lists.laptop.org/listinfo/devel >>> >>> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
It would be good to start the kernel with systemd.unit=multi-user.target so that (hopefully) we just get a console instead of dcon freezing/X startup... I'm not sure how to easily pass kernel arguments on the XO though. Does anyone know? On 8 May 2014 18:55, Martin Abente wrote: > Hello Daniel, > > I built the image for XO 1.5 but it freezes during boot. > > It reaches to the stage: > > Starting Wait for Wait for Plymouth Boot Screen to Quit... > > > Right after that I see these two messages: > > > dcon_freeze_store: 1 > dcon_source_switch to DCON > > > Then the screen slowly and gradually turns gray. > > Any idea what this could be? Any suggestion for debugging it? > > Regards, > Martin. > > > > > On Thu, May 8, 2014 at 8:16 AM, Gonzalo Odiard wrote: > >> These are fantastic news! >> Thanks Daniel for working on this >> >> Gonzalo >> >> >> On Wed, May 7, 2014 at 9:04 PM, Daniel Narvaez wrote: >> >>> As an update, I have patched xorg-x11-drv-dove and built rpms for it >>> >>> http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ >>> >>> Now building an image with those. >>> >>> >>> On 7 May 2014 15:18, Martin Abente wrote: >>> >>>> Great! >>>> >>>> I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) >>>> >>>> >>>> >>>> On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: >>>> >>>>> On 7 May 2014 01:44, James Cameron wrote: >>>>> >>>>>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>>>>> > [...] And with the XO stuck on Fedora 18 we might not have good >>>>>> > enough introspection to make the port compatible with it. >>>>>> >>>>>> If anybody would like to work on moving olpc-os-builder to something >>>>>> more recent, feel free. It isn't something OLPC is looking at right >>>>>> now, but it would be helpful to the users. >>>>>> >>>>>> Not the die hard 0.98 users, of course. ;-) >>>>> >>>>> >>>>> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >>>>> >>>>> https://github.com/dnarvaez/olpc-os-builder >>>>> >>>>> I don't have hardware to test that though... I'm now trying to build >>>>> for 1.75 which is harder but I can actually test. I need to rebuild the X >>>>> driver but I think that will require some patching, let's see if I can get >>>>> it to work... >>>>> >>>>> ___ >>>>> Devel mailing list >>>>> de...@lists.laptop.org >>>>> http://lists.laptop.org/listinfo/devel >>>>> >>>>> >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Software for children learning >> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
As an update, I have patched xorg-x11-drv-dove and built rpms for it http://shell.sugarlabs.org/~dnarvaez/oob/f20-xo1.75/ Now building an image with those. On 7 May 2014 15:18, Martin Abente wrote: > Great! > > I will try your oob branch for 1.5, I do have XOs 1.5 for testing :) > > > > On Wed, May 7, 2014 at 9:01 AM, Daniel Narvaez wrote: > >> On 7 May 2014 01:44, James Cameron wrote: >> >>> On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: >>> > [...] And with the XO stuck on Fedora 18 we might not have good >>> > enough introspection to make the port compatible with it. >>> >>> If anybody would like to work on moving olpc-os-builder to something >>> more recent, feel free. It isn't something OLPC is looking at right >>> now, but it would be helpful to the users. >>> >>> Not the die hard 0.98 users, of course. ;-) >> >> >> I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 >> >> https://github.com/dnarvaez/olpc-os-builder >> >> I don't have hardware to test that though... I'm now trying to build for >> 1.75 which is harder but I can actually test. I need to rebuild the X >> driver but I think that will require some patching, let's see if I can get >> it to work... >> >> ___ >> Devel mailing list >> de...@lists.laptop.org >> http://lists.laptop.org/listinfo/devel >> >> > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
On 7 May 2014 01:44, James Cameron wrote: > On Tue, May 06, 2014 at 04:24:39PM +0200, Daniel Narvaez wrote: > > [...] And with the XO stuck on Fedora 18 we might not have good > > enough introspection to make the port compatible with it. > > If anybody would like to work on moving olpc-os-builder to something > more recent, feel free. It isn't something OLPC is looking at right > now, but it would be helpful to the users. > > Not the die hard 0.98 users, of course. ;-) I'm giving that a try. I was able to build a Fedora 20 image for XO 1.5 https://github.com/dnarvaez/olpc-os-builder I don't have hardware to test that though... I'm now trying to build for 1.75 which is harder but I can actually test. I need to rebuild the X driver but I think that will require some patching, let's see if I can get it to work... ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On 6 May 2014 13:50, kunal arora wrote: > > The amount of work needed for either strategy will be almost the same but > in my opinion a codebase compatible with both python2 and python3 will > actually be harder to maintain as whenever we change something in the core > or toolkit we'll have to write polyglot code compatible with both python2 > AND python3 . > My impression is that using a subset of python that works on both is not particularly complicated. I don't have a lot of experience with it but I ported a few small projects and the changes was trivial. Also the toolkit code doesn't really do fancy python things. My worry is mostly testing, we can't expect people to test with both when making changes. We can enforce writing unit tests though and make sure they pass with both python versions. That's going to be possible only if we have good coverage to start with and I'd say that's going to be the most time consuming part of your work... For entirely new modules we could also support python3 only probably. > Whereas if go with complete port into a new toolkit we will just have to > accomodate ourselves in writing code in python3. > What we are saying is that we don't want to obsolete the current python2 based toolkit. So if we make a new toolkit we will have to manually backport most of the patches to python2 too. It would certainly be easier to maintain only the python3 toolkit for us, but it would be bad for activities and their developers. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On 6 May 2014 12:53, Peter Robinson wrote: > > * Research and if possible port telepathy-python to introspection. Bonus > > points if testing is possible. > > I thought the whole point of introspection was to get rid of things > like telepathy-python. This was certainly the case with > gstreamer-python and number of other *-python bits that we use to use. > Ultimately it becomes a process of converting the telepathy code to > introspection not porting telepathy-python to introspection. All > telepathy-glib, t-farstream etc all support introspection now, note > sure about t-m-c currently. > That's correct. I guess the worry here is to make major changes to fragile code no one is very familiar with. And with the XO stuck on Fedora 18 we might not have good enough introspection to make the port compatible with it. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On 6 May 2014 12:28, Gonzalo Odiard wrote: > * Make core and toolkit compatible with python 2 & 3 > Does core need to be compatible with both? It seems like we could just always run it on python3. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
Obsoleting the gtk2 was an explicit decision. It's not that we don't care but we just don't have enough resources to maintain two toolkits. Completely breaking the API is really bad. It takes years for the applications to switch and many of them never do it. We have seen it with activities (and documentation) but, for example, it happened to the gtk toolkit itself, with major applications which have not been ported yet. In the gtk2->gtk3 case I think we was pretty much forced to break. The difference between the two GNOME stacks was too large, some gtk2 pieces was supposed to go away from distributions (I'm not sure if they did in practice), and introspection was a major advantage for our platform. Here we don't seem to be in the same situation. I'd expect the differences for the toolkit code to *not* be huge. The python2 ecosystem seems to be still very much alive. And I don't see the port improving our platform much. It's not a clear cut decision of course, but my feeling is that a complete API break would hurt more than it helps at this time. I should mention that supporting both python2 and python3 in sugar-toolkit-gtk3 won't come for free either because new code will have to be compatible with both. We can probably ensure that with unit tests, but it's a cost to consider. We could also allow new API to be python3 only and plan for a sugar4 toolkit with gtk4 (whenever that gets released). Seeing the diff of a quick and dirty port would help a lot to evaluate things here. On 6 May 2014 08:00, Sam Parkinson wrote: > > On May 6, 2014 9:47 AM, "Daniel Narvaez" wrote: > > > > On 1 May 2014 14:42, kunal arora wrote: > >> > >> 4)Create a new Sugar-toolkit-gtk3-python3 from the old one and also > keep the Sugar-toolkit-gtk3 for activities that haven't yet ported to > Python3 and slowly deprecate it with time as more and more activities shift > to Python3. > > > > > > This sounds like a maintenance nightmare. Can we make sugar-toolkit-gtk3 > work with both python2 and python3 instead? > > Why would we need to maintain a py2 version; we don't maintain the gtk2 > toolkit or even care to put it on GitHub. > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On 1 May 2014 14:42, kunal arora wrote: > So, I did some research and found that it would be best to port sugar in > the following way: > > 1) Resolve the dependency issue - mainly telepathy . Telepathy-python has > been deprecated , so what would be the best way to deal with this? Would it > best to just port it to python3 or something else? > > I suppose the best would be to port our code to use gobject introspection. But that assumes telepathy-glib has good enough introspection support. Also it would need to be tested very carefully, collaboration is buggy enough as is, better not introduce regressions :) Did you ask if maintainers would take patches to port to python3? Do you know if it would be trivial or a lot of work? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On 1 May 2014 14:42, kunal arora wrote: > 4)Create a new Sugar-toolkit-gtk3-python3 from the old one and also keep > the Sugar-toolkit-gtk3 for activities that haven't yet ported to Python3 > and slowly deprecate it with time as more and more activities shift to > Python3. > This sounds like a maintenance nightmare. Can we make sugar-toolkit-gtk3 work with both python2 and python3 instead? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hacking sugar-web anywhere
I pushed this because I have sugar-build changes that depends on it. Though reviews are welcome https://github.com/sugarlabs/sugar-web/pull/113 On 5 May 2014 21:03, Daniel Narvaez wrote: > Hello, > > I just sent a pull request to add a grunt build to sugar-web. It allows to > hack on sugar-web on any OS where nodejs is available. > > Rough instructions: > > 1 Install chrome and nodejs. > > 2 Run checks and unit tests > > git clone https://github.com/dnarvaez/sugar-web.git > cd sugar-web > git checkout grunt > > npm install -g grunt-cli volo > volo add -f > npm install > > grunt > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Hacking sugar-web anywhere
Hello, I just sent a pull request to add a grunt build to sugar-web. It allows to hack on sugar-web on any OS where nodejs is available. Rough instructions: 1 Install chrome and nodejs. 2 Run checks and unit tests git clone https://github.com/dnarvaez/sugar-web.git cd sugar-web git checkout grunt npm install -g grunt-cli volo volo add -f npm install grunt -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] String, UI, API freeze
Hello, I just built tarballs for 0.101.5, so we are now string, API and UI frozen. Please think of the freeze before approving patches. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A Better ASLO
What is the advantage of our own comments db? I like the idea of a static web site because it wouldn't have to be hosted etc. of course that might not really scale for long but I think it's still worth considering carefully if we need our own comments thing or we can reuse a web service for that. On Wednesday, 16 April 2014, Sam Parkinson wrote: > Hi, > > I have been working on this. It now has a git: > https://github.com/SAMdroid-apps/aslo > > I was just wondering, does activity.info have i18n? > > Also, I have used a persona login for the comments. That means we have the > email of the commenter. I think it would be cool to have a developer reply > feature (like g play), where they could talk and get follow up about > bugs... The developer would first send the message through a web interface > and not get their email unless they replied. Is that creepy? > > Sam > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Hi, issues are per github project, so that would be the component. I think people use labels for priority and bug/enh, see for example https://github.com/bower/bower/issues https://github.com/jshint/jshint/issues On Saturday, 19 April 2014, Gonzalo Odiard wrote: > Looks more than comments than tickets, right? Or I am missing something? > > For our way of work, I think we need at least component and priority, > and if is a bug or a enhancement. > > Or there are another way to categorize them? > > I see labels here https://github.com/dnarvaez/test/issues > > Gonzalo > > > On Fri, Apr 18, 2014 at 6:07 PM, Daniel Narvaez > > > wrote: > >> >> By the way, if we decide to do it I think we should do it *before* the >> meeting, so that we triage using github already and we don't risk to lose >> information (or to have a really hard time fixing the script to preserve >> it). >> >> >> On 19 April 2014 02:03, Daniel Narvaez >> >> > wrote: >> >>> I tried to do a migration using trac2github. Here is what it looks like >>> >>> https://github.com/dnarvaez/test/issues/258 >>> >>> It's missing the reporter and it's not filtering by component but these >>> should be easy to add (it's php sigh, but still...). >>> >>> >>> On 19 April 2014 01:03, Daniel Narvaez >>> >>> > wrote: >>> >>>> Something is probably worth bringing up (it has been discussed a couple >>>> of times in irc) is the possibility to migrate to github issues. >>>> Maintaining trac is becoming a bit of a burden, especially because of spam >>>> prevention. Someone (Bernie?) suggested we could keep >>>> bugs.sugarlabs.org around for a while but in read-only mode, rather >>>> than migrating. Interested in people thoughts, I have not fully considered >>>> the migration issue to be honest. >>>> >>>> >>>> On 9 April 2014 14:10, Walter Bender >>>> >>>> > wrote: >>>> >>>>> We plan to hold a triage meeting to clean up bugs.sugarlabs.org on >>>>> Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on >>>>> irc.freenode.net #sugar-meeting all day. Please join the fun. >>>>> >>>>> -- >>>>> >>>>> Tenemos la intención de celebrar una reunión de triage para limpiar >>>>> bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST >>>>> (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. >>>>> Por favor, únase a la diversión. >>>>> >>>>> >>>>> regards. >>>>> >>>>> -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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> >> ___ >> IAEP -- It's An Education Project (not a laptop project!) >> i...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/iaep >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
By the way, if we decide to do it I think we should do it *before* the meeting, so that we triage using github already and we don't risk to lose information (or to have a really hard time fixing the script to preserve it). On 19 April 2014 02:03, Daniel Narvaez wrote: > I tried to do a migration using trac2github. Here is what it looks like > > https://github.com/dnarvaez/test/issues/258 > > It's missing the reporter and it's not filtering by component but these > should be easy to add (it's php sigh, but still...). > > > On 19 April 2014 01:03, Daniel Narvaez wrote: > >> Something is probably worth bringing up (it has been discussed a couple >> of times in irc) is the possibility to migrate to github issues. >> Maintaining trac is becoming a bit of a burden, especially because of spam >> prevention. Someone (Bernie?) suggested we could keep >> bugs.sugarlabs.orgaround for a while but in read-only mode, rather than >> migrating. Interested >> in people thoughts, I have not fully considered the migration issue to be >> honest. >> >> >> On 9 April 2014 14:10, Walter Bender wrote: >> >>> We plan to hold a triage meeting to clean up bugs.sugarlabs.org on >>> Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on >>> irc.freenode.net #sugar-meeting all day. Please join the fun. >>> >>> -- >>> >>> Tenemos la intención de celebrar una reunión de triage para limpiar >>> bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST >>> (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. >>> Por favor, únase a la diversión. >>> >>> >>> regards. >>> >>> -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 >>> >> >> >> >> -- >> Daniel Narvaez >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
I tried to do a migration using trac2github. Here is what it looks like https://github.com/dnarvaez/test/issues/258 It's missing the reporter and it's not filtering by component but these should be easy to add (it's php sigh, but still...). On 19 April 2014 01:03, Daniel Narvaez wrote: > Something is probably worth bringing up (it has been discussed a couple of > times in irc) is the possibility to migrate to github issues. Maintaining > trac is becoming a bit of a burden, especially because of spam prevention. > Someone (Bernie?) suggested we could keep bugs.sugarlabs.org around for a > while but in read-only mode, rather than migrating. Interested in people > thoughts, I have not fully considered the migration issue to be honest. > > > On 9 April 2014 14:10, Walter Bender wrote: > >> We plan to hold a triage meeting to clean up bugs.sugarlabs.org on >> Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on >> irc.freenode.net #sugar-meeting all day. Please join the fun. >> >> -- >> >> Tenemos la intención de celebrar una reunión de triage para limpiar >> bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST >> (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. >> Por favor, únase a la diversión. >> >> >> regards. >> >> -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 >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Something is probably worth bringing up (it has been discussed a couple of times in irc) is the possibility to migrate to github issues. Maintaining trac is becoming a bit of a burden, especially because of spam prevention. Someone (Bernie?) suggested we could keep bugs.sugarlabs.org around for a while but in read-only mode, rather than migrating. Interested in people thoughts, I have not fully considered the migration issue to be honest. On 9 April 2014 14:10, Walter Bender wrote: > We plan to hold a triage meeting to clean up bugs.sugarlabs.org on > Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on > irc.freenode.net #sugar-meeting all day. Please join the fun. > > -- > > Tenemos la intención de celebrar una reunión de triage para limpiar > bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST > (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. > Por favor, únase a la diversión. > > > regards. > > -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 > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Ideally I think this information should be on activities.sugarlabs.org. Though given we seems stuck with an old/unmaintained codebase there, I'm favorable to this approach. And I suppose it could evolve into the new activities.sugarlabs.org at some point! I would suggest a few changes * Factor out the module list to a registry.json file that you xhr. * Cut down on the headers, a small thing at the top like we have on the other sites. The main thing should be the repository list. * Rename the module to sugar-registry. Then people can send pull requests to add to registry.json. On 12 April 2014 12:06, Sam Parkinson wrote: > Hi, > > So I have made a list of some of the main activities. You can check it out > here: http://samdroid-apps.github.io/slgio/ (Don't worry Walter, it has > less over the top web stuff than last time :P). I probably could have made > a .md, but it was fun. > > If you like it maybe we could make sugarlabs.github.io for that sort of > cool repo index? That is what they do at Google Cloud ( > https://googlecloudplatform.github.io/ ), and it looks cool for them. > > Sam > > P.S. Web has taken over sugar: http://jsfiddle.net/Tb4sR/embedded/result/ > > > On Sat, Apr 12, 2014 at 2:42 PM, Sai Vineet wrote: > >> Count me in for the website :) >> On Apr 12, 2014 9:59 AM, "Ignacio Rodríguez" wrote: >> >>> > Maybe we should put a list of major activities locations on >>> sugarlabs.github.io? >>> >>> +1 >>> >>> > I could maintain/make the site :) >>> >>> I would too :) >>> >>> >>> Ignacio Rodríguez >>> fb.com/Ignacio.Rodriguez.UY >>> @NachoDeTodos <https://twitter.com/NachoDeTodos> >>> +598 91 686 835 >>> nachoe...@gmail.com >>> >>> >>> 2014-04-12 1:26 GMT-03:00 Sam Parkinson : >>> >>>> Maybe we should put a list of major activities locations on >>>> sugarlabs.github.io? It would help as now finding an activities code >>>> is harder than searching git.sl.o (think about new-ish people). I could >>>> maintain/make the site :) >>>> >>> >>> >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Hi, to be honest when I opened this thread I thought we would put these activities under the sugarlabs github organization. Though when Ignacio and Walter used their accounts I realized that would probably be the best approach. For development I think we should take advantage of the decentralized nature of gitub. Ownership on github should follow maintainership. Putting all the activities under sugarlabs would be bad from an administrative point of view. Activity authors would have to somehow request a new repository to be created and then wait for some (overworked) admin to do it. The same thing for stuff like adding another maintainer etc. It would also be impossible to enforce consistently, people which are less connected with the core team would just put their activities under their name anyway. We could apply this only to a certain subset of vetted activities but then I'm not clear how this group would be defined. We have fructose, but I would say it's an unsuccessful attempt given that it has not been updated in ages and it's not mentioned at all these days. Of course I see the need for a central place where people can look for activities code. But I think that should be activities.sugarlabs.org, which really needs links to source code repositories. Note that there are successfull examples of similar two-layered approaches, npmjs.org being the main one. On 13 April 2014 04:26, Sai Vineet wrote: > I think official activity repos should be under the SL github org. > Otherwise they'll all be scattered. Right now it seems maintainers are > putting it under their own ids. > On Apr 13, 2014 8:48 AM, "Daniel Narvaez" wrote: > >> For sugar I meant sugar-base really, keep getting that wrong! >> >> >> On 13 April 2014 04:16, Daniel Narvaez wrote: >> >>> Update! >>> >>> Pootle and redirect: >>> >>> sugar >>> sugar-toolkit >>> pippy >>> turtleart >>> >>> Pootle, redirect, hooks: >>> >>> chat >>> log >>> >>> Mirror, pootle, redirect, hooks: >>> >>> browse >>> write >>> read >>> terminal >>> imageviewer >>> jukebox >>> >>> Hooks only: >>> >>> clock-web >>> gtd-activity >>> >>> >>> >>> On 13 April 2014 04:09, Daniel Narvaez wrote: >>> >>>> Here is what is left to do. >>>> >>>> Pootle and redirect: >>>> >>>> sugar >>>> sugar-toolkit >>>> pippy >>>> >>>> Pootle, redirect, hooks: >>>> >>>> chat >>>> log >>>> >>>> Mirror, pootle, redirect, hooks: >>>> >>>> browse >>>> write >>>> read >>>> terminal >>>> imageviewer >>>> jukebox >>>> turtleart >>>> >>> >>> >>> >>> -- >>> Daniel Narvaez >>> >> >> >> >> -- >> Daniel Narvaez >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
For sugar I meant sugar-base really, keep getting that wrong! On 13 April 2014 04:16, Daniel Narvaez wrote: > Update! > > Pootle and redirect: > > sugar > sugar-toolkit > pippy > turtleart > > Pootle, redirect, hooks: > > chat > log > > Mirror, pootle, redirect, hooks: > > browse > write > read > terminal > imageviewer > jukebox > > Hooks only: > > clock-web > gtd-activity > > > > On 13 April 2014 04:09, Daniel Narvaez wrote: > >> Here is what is left to do. >> >> Pootle and redirect: >> >> sugar >> sugar-toolkit >> pippy >> >> Pootle, redirect, hooks: >> >> chat >> log >> >> Mirror, pootle, redirect, hooks: >> >> browse >> write >> read >> terminal >> imageviewer >> jukebox >> turtleart >> > > > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Update! Pootle and redirect: sugar sugar-toolkit pippy turtleart Pootle, redirect, hooks: chat log Mirror, pootle, redirect, hooks: browse write read terminal imageviewer jukebox Hooks only: clock-web gtd-activity On 13 April 2014 04:09, Daniel Narvaez wrote: > Here is what is left to do. > > Pootle and redirect: > > sugar > sugar-toolkit > pippy > > Pootle, redirect, hooks: > > chat > log > > Mirror, pootle, redirect, hooks: > > browse > write > read > terminal > imageviewer > jukebox > turtleart > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Here is what is left to do. Pootle and redirect: sugar sugar-toolkit pippy Pootle, redirect, hooks: chat log Mirror, pootle, redirect, hooks: browse write read terminal imageviewer jukebox turtleart ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
We tested all the setup with Walter and it worked nicely for Pippy. On 13 April 2014 03:38, Daniel Narvaez wrote: > Also you need to generate a token to let the application update status on > your repository commits. This is one per owner, not one per repository > > 1 Go to your user settings, applications section > 2 Click "Generate new token" > 3 Put the description you like > 4 Delesect all, select only "repo:status" > 5 Click generate token > 6 Send it to me *off list* > > > On 13 April 2014 00:56, Daniel Narvaez wrote: > >> We need to add buildbot hooks for the modules. >> >> 1 Go to the project settings, webhooks section >> 2 Click "Add webhook" >> 3 Make Payload Url >> http://buildbot.sugarlabs.org:3000/change<https://github.com/sugarlabs/sugar/settings/hooks/2054532> >> 4 Choose "Let me select individual events" >> 5 Tick "Push" and "Pull Request". >> 6 Click "Add webook" button at the bottom. >> >> >> On 12 April 2014 03:55, Ignacio Rodríguez wrote: >> >>> Ok! >>> >>> @dnarvaez: https://github.com/sugarlabs/sugar-build/pull/27 >>> >>> Ignacio Rodríguez >>> fb.com/Ignacio.Rodriguez.UY >>> @NachoDeTodos <https://twitter.com/NachoDeTodos> >>> +598 91 686 835 >>> nachoe...@gmail.com >>> >>> >>> 2014-04-11 23:40 GMT-03:00 Ignacio Rodríguez : >>> >>> > Just wondering, is github the preference now? (Just thinking about >>>> the XO ddos) >>>> >>>> Yeah >>>> We are trying to move all modules to github asap >>>> >>>> Ignacio Rodríguez >>>> fb.com/Ignacio.Rodriguez.UY >>>> @NachoDeTodos <https://twitter.com/NachoDeTodos> >>>> +598 91 686 835 >>>> nachoe...@gmail.com >>>> >>>> >>>> 2014-04-11 23:40 GMT-03:00 Sam Parkinson : >>>> >>>> Just wondering, is github the preference now? (Just thinking about >>>>> the XO ddos) >>>>> On Apr 12, 2014 12:39 PM, "Walter Bender" >>>>> wrote: >>>>> >>>>>> and I moved Pippy >>>>>> >>>>>> -walter >>>>>> >>>>>> On Fri, Apr 11, 2014 at 10:37 PM, Ignacio Rodríguez < >>>>>> nachoe...@gmail.com> wrote: >>>>>> > Hi all :) >>>>>> > >>>>>> > I moved Chat activity and Log activity to GitHub >>>>>> > >>>>>> > https://github.com/ignaciouy/log >>>>>> > https://github.com/ignaciouy/chat >>>>>> > >>>>>> > Ignacio Rodríguez >>>>>> > fb.com/Ignacio.Rodriguez.UY >>>>>> > @NachoDeTodos >>>>>> > +598 91 686 835 >>>>>> > nachoe...@gmail.com >>>>>> > >>>>>> > >>>>>> > 2014-04-07 6:31 GMT-03:00 Daniel Narvaez : >>>>>> > >>>>>> >> Looking at my email, it sounds like Aleksey is offline for a while >>>>>> but >>>>>> >> Ignacio is co-maintainer. Adding both. >>>>>> >> >>>>>> >> >>>>>> >> On Monday, 7 April 2014, Gonzalo Odiard >>>>>> wrote: >>>>>> >>> >>>>>> >>> >>>>>> >>> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez < >>>>>> dwnarv...@gmail.com> >>>>>> >>> wrote: >>>>>> >>>> >>>>>> >>>> Gonzalo, can you confirm which of these activities you maintain >>>>>> and if >>>>>> >>>> you are fine with the move? So I can try to hunt down the >>>>>> remaining >>>>>> >>>> maintainers. >>>>>> >>>> >>>>>> >>> >>>>>> >>> I maintain: >>>>>> >>> write >>>>>> >>> read >>>>>> >>> log (with Ignacio) >>>>>> >>> jukebox >>>>>> >>> imageviewer (with Agustin) >>>>>> >>> terminal >>>>>> >>> >>>>>> >>> >>>>>> >>> Aleksey maintained >>&
Re: [Sugar-devel] Weird sugar-build crashes
Oh you need to osbuild pull first, forgot to mention that.
On 13 April 2014 03:07, Sam Parkinson wrote:
> Hi,
>
> Gdb wasn't installed inside sugar build so it didn't work. I did get
> segfault though.
>
> Thanks,
> Sam
> On Apr 13, 2014 9:49 AM, "Daniel Narvaez" wrote:
>
>> Try this
>>
>> ./sugar-build shell
>> Xephyr :100 &
>> (go back to the same terminal, press enter)
>> DISPLAY=:100 sugar
>>
>> If it's segfaulting, apply this patch to sugar
>>
>> diff --git a/bin/sugar.in b/bin/sugar.in
>> index aebb897..0a0b61f 100644
>> --- a/bin/sugar.in
>> +++ b/bin/sugar.in
>> @@ -76,4 +76,4 @@ cat > $debug_file_path << EOF
>> EOF
>> fi
>>
>> -exec python2 -m jarabe.main
>> +exec gdb --args python2 -m jarabe.main
>>
>> Then retry the same you have done above, when you get to the gdb prompt
>> type "run", if it segfaults type "bt" and post the output.
>>
>>
>>
>> On 12 April 2014 22:17, Sam Parkinson wrote:
>>
>>> Hi,
>>>
>>> My sugar build has recently started playing up. Whenever I run sugar it
>>> crashes like this:
>>>
>>> Gtk-Message: Failed to load module "pk-gtk-module"
>>>
>>> Initializing built-in extension Generic Event Extension
>>> Initializing built-in extension SHAPE
>>> Initializing built-in extension MIT-SHM
>>> Initializing built-in extension XInputExtension
>>> most recent call last):
>>> File "/home/broot/sugar-build/build/commands/broot/run", line 16, in
>>>
>>> run.run("sugar-runner")
>>> File
>>> "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/run.py",
>>> line 38, in run
>>> command.run(args, **kwargs)
>>> File
>>> "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/command.py",
>>> line 39, in run
>>> t-in extension DAMAGE
>>> alledProcessError(result, args)
>>> subprocess.CalledProcessError: Command '['sugar-runner', '--resolution',
>>> u'800x600']' returned non-zero exit status 1
>>>
>>> ! Failed to run command run
>>> Killing 4447
>>>
>>> ! Failed to run command runlizing built-in extension XVideo
>>> Initializing built-in extension XVideo-MotionCompensation
>>> Initializing built-in extension SELinux
>>> xinit: XFree86_VT property unexpectedly has 0 items instead of 1
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: Key not found in evdev+aliases(qwerty) keycodes
>>> Symbols ignored
>>> Warning: No symbols defined for (keycode 97)
>>> Warning: No symbols defined for (keycode 103)
>>> Warning: No symbols defined for (keycode 120)
>>> Warning: No symbols defined for (keycode 132)
>>> Warning: No symbols defined for (keycode 149)
>>> Warning: No symbols defined for (keycode 154)
>>> Warning: No symbols defined for (keycode 161)
>>> Warning: No symbols defined for (keycode 168)
>>> Warning: No symbols defined for (keycode 178)
>>> Warning: No symbols defined for (keycode 183)
>>> Warning:
Re: [Sugar-devel] Moving more modules to github
Also you need to generate a token to let the application update status on your repository commits. This is one per owner, not one per repository 1 Go to your user settings, applications section 2 Click "Generate new token" 3 Put the description you like 4 Delesect all, select only "repo:status" 5 Click generate token 6 Send it to me *off list* On 13 April 2014 00:56, Daniel Narvaez wrote: > We need to add buildbot hooks for the modules. > > 1 Go to the project settings, webhooks section > 2 Click "Add webhook" > 3 Make Payload Url > http://buildbot.sugarlabs.org:3000/change<https://github.com/sugarlabs/sugar/settings/hooks/2054532> > 4 Choose "Let me select individual events" > 5 Tick "Push" and "Pull Request". > 6 Click "Add webook" button at the bottom. > > > On 12 April 2014 03:55, Ignacio Rodríguez wrote: > >> Ok! >> >> @dnarvaez: https://github.com/sugarlabs/sugar-build/pull/27 >> >> Ignacio Rodríguez >> fb.com/Ignacio.Rodriguez.UY >> @NachoDeTodos <https://twitter.com/NachoDeTodos> >> +598 91 686 835 >> nachoe...@gmail.com >> >> >> 2014-04-11 23:40 GMT-03:00 Ignacio Rodríguez : >> >> > Just wondering, is github the preference now? (Just thinking about the >>> XO ddos) >>> >>> Yeah >>> We are trying to move all modules to github asap >>> >>> Ignacio Rodríguez >>> fb.com/Ignacio.Rodriguez.UY >>> @NachoDeTodos <https://twitter.com/NachoDeTodos> >>> +598 91 686 835 >>> nachoe...@gmail.com >>> >>> >>> 2014-04-11 23:40 GMT-03:00 Sam Parkinson : >>> >>> Just wondering, is github the preference now? (Just thinking about the >>>> XO ddos) >>>> On Apr 12, 2014 12:39 PM, "Walter Bender" >>>> wrote: >>>> >>>>> and I moved Pippy >>>>> >>>>> -walter >>>>> >>>>> On Fri, Apr 11, 2014 at 10:37 PM, Ignacio Rodríguez < >>>>> nachoe...@gmail.com> wrote: >>>>> > Hi all :) >>>>> > >>>>> > I moved Chat activity and Log activity to GitHub >>>>> > >>>>> > https://github.com/ignaciouy/log >>>>> > https://github.com/ignaciouy/chat >>>>> > >>>>> > Ignacio Rodríguez >>>>> > fb.com/Ignacio.Rodriguez.UY >>>>> > @NachoDeTodos >>>>> > +598 91 686 835 >>>>> > nachoe...@gmail.com >>>>> > >>>>> > >>>>> > 2014-04-07 6:31 GMT-03:00 Daniel Narvaez : >>>>> > >>>>> >> Looking at my email, it sounds like Aleksey is offline for a while >>>>> but >>>>> >> Ignacio is co-maintainer. Adding both. >>>>> >> >>>>> >> >>>>> >> On Monday, 7 April 2014, Gonzalo Odiard wrote: >>>>> >>> >>>>> >>> >>>>> >>> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez < >>>>> dwnarv...@gmail.com> >>>>> >>> wrote: >>>>> >>>> >>>>> >>>> Gonzalo, can you confirm which of these activities you maintain >>>>> and if >>>>> >>>> you are fine with the move? So I can try to hunt down the >>>>> remaining >>>>> >>>> maintainers. >>>>> >>>> >>>>> >>> >>>>> >>> I maintain: >>>>> >>> write >>>>> >>> read >>>>> >>> log (with Ignacio) >>>>> >>> jukebox >>>>> >>> imageviewer (with Agustin) >>>>> >>> terminal >>>>> >>> >>>>> >>> >>>>> >>> Aleksey maintained >>>>> >>> >>>>> >>> chat >>>>> >>> >>>>> >>> Gonzalo >>>>> >>> >>>>> >>> >>>>> >>> >>>>> >>>> >>>>> >>>> >>>>> >>>> On Friday, 4 April 2014, Daniel Narvaez >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Hello, >>>>> >>>>> >
Re: [Sugar-devel] Moving more modules to github
Manuel, can you please add the hooks for clock-web and gtd-activity which are already on github? On 13 April 2014 00:56, Daniel Narvaez wrote: > We need to add buildbot hooks for the modules. > > 1 Go to the project settings, webhooks section > 2 Click "Add webhook" > 3 Make Payload Url > http://buildbot.sugarlabs.org:3000/change<https://github.com/sugarlabs/sugar/settings/hooks/2054532> > 4 Choose "Let me select individual events" > 5 Tick "Push" and "Pull Request". > 6 Click "Add webook" button at the bottom. > > > On 12 April 2014 03:55, Ignacio Rodríguez wrote: > >> Ok! >> >> @dnarvaez: https://github.com/sugarlabs/sugar-build/pull/27 >> >> Ignacio Rodríguez >> fb.com/Ignacio.Rodriguez.UY >> @NachoDeTodos <https://twitter.com/NachoDeTodos> >> +598 91 686 835 >> nachoe...@gmail.com >> >> >> 2014-04-11 23:40 GMT-03:00 Ignacio Rodríguez : >> >> > Just wondering, is github the preference now? (Just thinking about the >>> XO ddos) >>> >>> Yeah >>> We are trying to move all modules to github asap >>> >>> Ignacio Rodríguez >>> fb.com/Ignacio.Rodriguez.UY >>> @NachoDeTodos <https://twitter.com/NachoDeTodos> >>> +598 91 686 835 >>> nachoe...@gmail.com >>> >>> >>> 2014-04-11 23:40 GMT-03:00 Sam Parkinson : >>> >>> Just wondering, is github the preference now? (Just thinking about the >>>> XO ddos) >>>> On Apr 12, 2014 12:39 PM, "Walter Bender" >>>> wrote: >>>> >>>>> and I moved Pippy >>>>> >>>>> -walter >>>>> >>>>> On Fri, Apr 11, 2014 at 10:37 PM, Ignacio Rodríguez < >>>>> nachoe...@gmail.com> wrote: >>>>> > Hi all :) >>>>> > >>>>> > I moved Chat activity and Log activity to GitHub >>>>> > >>>>> > https://github.com/ignaciouy/log >>>>> > https://github.com/ignaciouy/chat >>>>> > >>>>> > Ignacio Rodríguez >>>>> > fb.com/Ignacio.Rodriguez.UY >>>>> > @NachoDeTodos >>>>> > +598 91 686 835 >>>>> > nachoe...@gmail.com >>>>> > >>>>> > >>>>> > 2014-04-07 6:31 GMT-03:00 Daniel Narvaez : >>>>> > >>>>> >> Looking at my email, it sounds like Aleksey is offline for a while >>>>> but >>>>> >> Ignacio is co-maintainer. Adding both. >>>>> >> >>>>> >> >>>>> >> On Monday, 7 April 2014, Gonzalo Odiard wrote: >>>>> >>> >>>>> >>> >>>>> >>> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez < >>>>> dwnarv...@gmail.com> >>>>> >>> wrote: >>>>> >>>> >>>>> >>>> Gonzalo, can you confirm which of these activities you maintain >>>>> and if >>>>> >>>> you are fine with the move? So I can try to hunt down the >>>>> remaining >>>>> >>>> maintainers. >>>>> >>>> >>>>> >>> >>>>> >>> I maintain: >>>>> >>> write >>>>> >>> read >>>>> >>> log (with Ignacio) >>>>> >>> jukebox >>>>> >>> imageviewer (with Agustin) >>>>> >>> terminal >>>>> >>> >>>>> >>> >>>>> >>> Aleksey maintained >>>>> >>> >>>>> >>> chat >>>>> >>> >>>>> >>> Gonzalo >>>>> >>> >>>>> >>> >>>>> >>> >>>>> >>>> >>>>> >>>> >>>>> >>>> On Friday, 4 April 2014, Daniel Narvaez >>>>> wrote: >>>>> >>>>> >>>>> >>>>> Hello, >>>>> >>>>> >>>>> >>>>> I think we should move more of our modules to github, at least >>>>> all the >>>>> >>>>> ones we are currently building in sugar-build. >>>>> >>>>> >>>>> >&
Re: [Sugar-devel] Moving more modules to github
We need to add buildbot hooks for the modules. 1 Go to the project settings, webhooks section 2 Click "Add webhook" 3 Make Payload Url http://buildbot.sugarlabs.org:3000/change<https://github.com/sugarlabs/sugar/settings/hooks/2054532> 4 Choose "Let me select individual events" 5 Tick "Push" and "Pull Request". 6 Click "Add webook" button at the bottom. On 12 April 2014 03:55, Ignacio Rodríguez wrote: > Ok! > > @dnarvaez: https://github.com/sugarlabs/sugar-build/pull/27 > > Ignacio Rodríguez > fb.com/Ignacio.Rodriguez.UY > @NachoDeTodos <https://twitter.com/NachoDeTodos> > +598 91 686 835 > nachoe...@gmail.com > > > 2014-04-11 23:40 GMT-03:00 Ignacio Rodríguez : > > > Just wondering, is github the preference now? (Just thinking about the >> XO ddos) >> >> Yeah >> We are trying to move all modules to github asap >> >> Ignacio Rodríguez >> fb.com/Ignacio.Rodriguez.UY >> @NachoDeTodos <https://twitter.com/NachoDeTodos> >> +598 91 686 835 >> nachoe...@gmail.com >> >> >> 2014-04-11 23:40 GMT-03:00 Sam Parkinson : >> >> Just wondering, is github the preference now? (Just thinking about the >>> XO ddos) >>> On Apr 12, 2014 12:39 PM, "Walter Bender" >>> wrote: >>> >>>> and I moved Pippy >>>> >>>> -walter >>>> >>>> On Fri, Apr 11, 2014 at 10:37 PM, Ignacio Rodríguez < >>>> nachoe...@gmail.com> wrote: >>>> > Hi all :) >>>> > >>>> > I moved Chat activity and Log activity to GitHub >>>> > >>>> > https://github.com/ignaciouy/log >>>> > https://github.com/ignaciouy/chat >>>> > >>>> > Ignacio Rodríguez >>>> > fb.com/Ignacio.Rodriguez.UY >>>> > @NachoDeTodos >>>> > +598 91 686 835 >>>> > nachoe...@gmail.com >>>> > >>>> > >>>> > 2014-04-07 6:31 GMT-03:00 Daniel Narvaez : >>>> > >>>> >> Looking at my email, it sounds like Aleksey is offline for a while >>>> but >>>> >> Ignacio is co-maintainer. Adding both. >>>> >> >>>> >> >>>> >> On Monday, 7 April 2014, Gonzalo Odiard wrote: >>>> >>> >>>> >>> >>>> >>> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez >>> > >>>> >>> wrote: >>>> >>>> >>>> >>>> Gonzalo, can you confirm which of these activities you maintain >>>> and if >>>> >>>> you are fine with the move? So I can try to hunt down the remaining >>>> >>>> maintainers. >>>> >>>> >>>> >>> >>>> >>> I maintain: >>>> >>> write >>>> >>> read >>>> >>> log (with Ignacio) >>>> >>> jukebox >>>> >>> imageviewer (with Agustin) >>>> >>> terminal >>>> >>> >>>> >>> >>>> >>> Aleksey maintained >>>> >>> >>>> >>> chat >>>> >>> >>>> >>> Gonzalo >>>> >>> >>>> >>> >>>> >>> >>>> >>>> >>>> >>>> >>>> >>>> On Friday, 4 April 2014, Daniel Narvaez >>>> wrote: >>>> >>>>> >>>> >>>>> Hello, >>>> >>>>> >>>> >>>>> I think we should move more of our modules to github, at least >>>> all the >>>> >>>>> ones we are currently building in sugar-build. >>>> >>>>> >>>> >>>>> That will make it easier for contributors because they won't have >>>> to go >>>> >>>>> through two different processes to submit patches. Also gitorious >>>> lacks pr >>>> >>>>> notifications which is really bad. >>>> >>>>> >>>> >>>>> Finally, it would make it easier to detect changes to the modules >>>> in >>>> >>>>> buildbot without having to poll, which is giving issues to our >>>> server (you >>>> >>>>> could probably do the same on gitori
Re: [Sugar-devel] Weird sugar-build crashes
for group 2 redefined
> > Using new definition
> > Warning: Compat map for group 3 redefined
> > Using new definition
> > Warning: Compat map for group 4 redefined
> > Using new definition
> Errors from xkbcomp are not fatal to the X server
> xinit: connection to X server lost
>
> Traceback (most recent call last):
> File "/home/broot/sugar-build/build/commands/broot/run", line 16, in
>
> run.run("sugar-runner")
> File
> "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/run.py",
> line 38, in run
> command.run(args, **kwargs)
> File
> "/home/broot/sugar-build/build/out/sandbox-broot/install/lib/python2.7/site-packages/osbuild/command.py",
> line 39, in run
> raise subprocess.CalledProcessError(result, args)
> subprocess.CalledProcessError: Command '['sugar-runner', '--resolution',
> u'800x600']' returned non-zero exit status 1
>
> ! Failed to run command run
> Killing 4447
>
> ! Failed to run command run
>
> Also in shell.log
>
> (process:4454): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
> Window manager warning: Locale not understood by C library,
> internationalization will not work
>
> (metacity:4503): Gtk-WARNING **: Locale not supported by C library.
> Using the fallback 'C' locale.
>
> I tried removing my profile but it didn't help. Does anyone know what it
> is?
>
> Thanks, Sam
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Just checking, did you do a full mirror? https://help.github.com/articles/duplicating-a-repository On Saturday, 12 April 2014, Ignacio Rodríguez wrote: > Hi all :) > > I moved Chat activity and Log activity to GitHub > > https://github.com/ignaciouy/log > https://github.com/ignaciouy/chat > > Ignacio Rodríguez > fb.com/Ignacio.Rodriguez.UY > @NachoDeTodos <https://twitter.com/NachoDeTodos> > +598 91 686 835 > nachoe...@gmail.com > > > 2014-04-07 6:31 GMT-03:00 Daniel Narvaez > > >: > >> Looking at my email, it sounds like Aleksey is offline for a while but >> Ignacio is co-maintainer. Adding both. >> >> >> On Monday, 7 April 2014, Gonzalo Odiard >> > >> wrote: >> >>> >>> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez wrote: >>> >>>> Gonzalo, can you confirm which of these activities you maintain and if >>>> you are fine with the move? So I can try to hunt down the remaining >>>> maintainers. >>>> >>>> >>> I maintain: >>> write >>> read >>> log (with Ignacio) >>> jukebox >>> imageviewer (with Agustin) >>> terminal >>> >>> >>> Aleksey maintained >>> >>> chat >>> >>> Gonzalo >>> >>> >>> >>> >>>> >>>> On Friday, 4 April 2014, Daniel Narvaez wrote: >>>> >>>>> Hello, >>>>> >>>>> I think we should move more of our modules to github, at least all the >>>>> ones we are currently building in sugar-build. >>>>> >>>>> That will make it easier for contributors because they won't have to >>>>> go through two different processes to submit patches. Also gitorious lacks >>>>> pr notifications which is really bad. >>>>> >>>>> Finally, it would make it easier to detect changes to the modules in >>>>> buildbot without having to poll, which is giving issues to our server (you >>>>> could probably do the same on gitorious, but I'm not really looking >>>>> forward >>>>> to write and maintain that for two different services). I'm also planning >>>>> to add support for triggering builds on pr submission, so that broken ones >>>>> can be marked as such in the UI, and it would be good for all the modules >>>>> to benefit from this. >>>>> >>>>> So here are the modules I would like to move >>>>> >>>>> sugar >>>>> sugar-toolkit >>>>> browse >>>>> write >>>>> chat >>>>> read >>>>> log >>>>> terminal >>>>> pippy >>>>> imageviewer >>>>> jukebox >>>>> turtleart >>>>> >>>>> What needs to be done >>>>> >>>>> 1 Get permission from module maintainers. If you are reading this >>>>> please confirm you are fine with this. >>>>> 2 Mirror the modules on github. I can take care of that. >>>>> 3 Update sugar-build. I can take care of that. >>>>> 4 Update pootle. Gonzalo, did you volunteer? :) >>>>> 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows >>>>> who/how did it for the core modules? >>>>> >>>>> -- >>>>> Daniel Narvaez >>>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >> >> -- >> Daniel Narvaez >> >> > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About adding toolkit_type and toolkit_version options to bundles
Sam sent a pull request to fix this, reviews would be appreciated https://github.com/sugarlabs/sugar/pull/333 (You might have the honour to empty the review queue for the first time in a looong while). On 17 February 2014 12:57, Daniel Narvaez wrote: > Hello, > > parsing code to find that out is such an hack... > > Anyway, I explained in the other thread what I think is the right way to > do this in the future and I'm content with that. As long as > > - the hack is done properly (no sync file loading) > - I'm not the one having to review the patch (too complicated to make it > really solid) > - there is comment explaining that the proper way to do it would be to > look at the exec field > > Then I'm fine with it landing. > > On Monday, 17 February 2014, Gonzalo Odiard wrote: > >> This is a reply to @dnarvaez comment >> >> >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> >> The addition of a field to identify gtk2/gtk3 activities, >> was proposed as a solution to View Source issue [1] >> >> I think there are two other easier ways to solve this particular issue: >> >> * check the setup.py file >> * check the file with the startup class (view source already identify the >> file, see [2] >> >> Making changes to the activity.info file usually take a long time >> to get included in a significant number of activities, >> if we can solve it in the code is better in my opinion. >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children >> >> [1] >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> [2] >> https://github.com/sugarlabs/sugar/blob/master/src/jarabe/view/viewsource.py#L205 >> > > > -- > Daniel Narvaez > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
On 10 April 2014 22:08, Daniel Narvaez wrote: > On 10 April 2014 21:18, James Cameron wrote: > >> On Thu, Apr 10, 2014 at 01:27:09PM +0100, Daniel Narvaez wrote: >> > What I'm saying is that the "would be nice" to fix will never be >> > fixed, they will keep accumulating and we will waste triage time on >> > them over and over. Better to just wontfix them, people can always >> > send patches if they care. Plus we tell them clearly it's up to them >> > to do something if they need them fixed. >> >> I agree, if there's nobody going to work on a ticket, then close it >> wontfix. The bug tracking system is useful as a list of non-features. >> > > Not what I said. And not even funny. > My sarcasm detector was inaccurate here. Further explanation in irc, which I agree with. 21:30 < Quozl`> dnarvaez_: the existence of a ticket is a report of feature mismatch between human and software. wontfix is a policy decision of the project. policy can be set by resource constraint. it's fine, close 'em. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
On 10 April 2014 21:18, James Cameron wrote: > On Thu, Apr 10, 2014 at 01:27:09PM +0100, Daniel Narvaez wrote: > > What I'm saying is that the "would be nice" to fix will never be > > fixed, they will keep accumulating and we will waste triage time on > > them over and over. Better to just wontfix them, people can always > > send patches if they care. Plus we tell them clearly it's up to them > > to do something if they need them fixed. > > I agree, if there's nobody going to work on a ticket, then close it > wontfix. The bug tracking system is useful as a list of non-features. > Not what I said. And not even funny. > Also, it is common in triage to not process already triaged "would be > nice" tickets, so you shouldn't be wasting triage time on them over > and over. If you are, fix your triage process. > And how do you avoid the issues getting obsolete (no more relevant, already fixed etc) if not by re-triaging them? That approach has been certainly common in sugar triage until recently. The result was that we couldn't really point any new contributor to the bug tracker because most of the bugs was obsolete. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Yes, things we *want* to do are normal priority, my issue is with things that would be nice to do :) Terminology aside, I'm not saying it's bad, just expensive and IMO lower priority then a lot of other awesome things we could do... But if there are people interested in "keeping records", all the power to them! On Thursday, 10 April 2014, Gonzalo Odiard wrote: > I disagree. > > While is true manage the tickets have cost, is good have a record of > things we want to do, > even when we don't have the resources today to do it. More in the context > of a project > where we have volunteers some times more, some times less. > > Just my two cents ...of pesos :) > > Gonzalo > > > On Thu, Apr 10, 2014 at 9:27 AM, Daniel Narvaez wrote: > > What I'm saying is that the "would be nice" to fix will never be fixed, > they will keep accumulating and we will waste triage time on them over and > over. Better to just wontfix them, people can always send patches if they > care. Plus we tell them clearly it's up to them to do something if they > need them fixed. > > IMO it's really really important to aggressively close stuff we are not > realistically going to fix soon. Otherwise either we waste more time > triaging than fixing or we don't triage enough and the bug tracker becomes > useless. > > Just my two cents. We could also keep "low" for now and see if it really > grows too much to be worth retriaging over time. In my experience it's > always does but it would be nice to be proven wrong. > > On Thursday, 10 April 2014, Gonzalo Odiard wrote: > > Well, maybe call iy "normal" or "low" instead of "minor", but we need a > way > to separate the tickets we _need_ fix, the tickets we _want_ fix, > and the tickets _would_be_nice_ fix. > We have almost 250 tickets, if we can solve 50 tickets in these 2 months, > is important know what are the best candidates. > > Gonzalo > > > On Thu, Apr 10, 2014 at 3:52 AM, Daniel Narvaez wrote: > > This is probably going to be a bit controversial, but I think if something > is worth marking minor then it's probably not worth tracking. We will never > get to fix the minor but we will waste time triaging and retriaging them. > > > On Thursday, 10 April 2014, Gonzalo Odiard wrote: > > +1 to check if are enhancements or defects. > > About priorities, we can make something like: > > blocker: regressions, crashes, serious bugs > > major: bugs affecting the usability > > minor: other > > Just a idea to start to discuss. > > Gonzalo > > > > On Wed, Apr 9, 2014 at 10:24 PM, Walter Bender wrote: > > On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez > wrote: > > Something else to consider is what to do with priorities. It might make > > sense to set one when confirming bugs, it's hard to get right without > > spending a lot of time really but maybe helpful for contributors even if > not > > very accurate. > > I think we have too many categories for priorities: IMHO, either it is > a blocker or it is not. > > -walter > > > > > > On Thursday, 10 April 2014, Daniel Narvaez wrote: > >> > >> > >> > >> On Thursday, 10 April 2014, Gonzalo Odiard > wrote: > >>> > >>> > >>> > >>> > >>> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez > >>> wrote: > >>>> > >>>> On Wednesday, 9 April 2014, Gonzalo Odiard > >>>> wrote: > >>>>> > >>>>> > >>>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez > > >>>>> wrote: > >>>>>> > >>>>>> This is an interesting blog post with a paragraph about GNOME > triaging > >>>>>> > >>>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ > >>>>>> > >>>>>> Interestingly it's pretty much exactly the same approach I followed > >>>>>> with the triaging I had done with 0.100. > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
What I'm saying is that the "would be nice" to fix will never be fixed, they will keep accumulating and we will waste triage time on them over and over. Better to just wontfix them, people can always send patches if they care. Plus we tell them clearly it's up to them to do something if they need them fixed. IMO it's really really important to aggressively close stuff we are not realistically going to fix soon. Otherwise either we waste more time triaging than fixing or we don't triage enough and the bug tracker becomes useless. Just my two cents. We could also keep "low" for now and see if it really grows too much to be worth retriaging over time. In my experience it's always does but it would be nice to be proven wrong. On Thursday, 10 April 2014, Gonzalo Odiard wrote: > Well, maybe call iy "normal" or "low" instead of "minor", but we need a > way > to separate the tickets we _need_ fix, the tickets we _want_ fix, > and the tickets _would_be_nice_ fix. > We have almost 250 tickets, if we can solve 50 tickets in these 2 months, > is important know what are the best candidates. > > Gonzalo > > > On Thu, Apr 10, 2014 at 3:52 AM, Daniel Narvaez wrote: > > This is probably going to be a bit controversial, but I think if something > is worth marking minor then it's probably not worth tracking. We will never > get to fix the minor but we will waste time triaging and retriaging them. > > > On Thursday, 10 April 2014, Gonzalo Odiard wrote: > > +1 to check if are enhancements or defects. > > About priorities, we can make something like: > > blocker: regressions, crashes, serious bugs > > major: bugs affecting the usability > > minor: other > > Just a idea to start to discuss. > > Gonzalo > > > > On Wed, Apr 9, 2014 at 10:24 PM, Walter Bender wrote: > > On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez > wrote: > > Something else to consider is what to do with priorities. It might make > > sense to set one when confirming bugs, it's hard to get right without > > spending a lot of time really but maybe helpful for contributors even if > not > > very accurate. > > I think we have too many categories for priorities: IMHO, either it is > a blocker or it is not. > > -walter > > > > > > On Thursday, 10 April 2014, Daniel Narvaez wrote: > >> > >> > >> > >> On Thursday, 10 April 2014, Gonzalo Odiard > wrote: > >>> > >>> > >>> > >>> > >>> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez > >>> wrote: > >>>> > >>>> On Wednesday, 9 April 2014, Gonzalo Odiard > >>>> wrote: > >>>>> > >>>>> > >>>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez > > >>>>> wrote: > >>>>>> > >>>>>> This is an interesting blog post with a paragraph about GNOME > triaging > >>>>>> > >>>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ > >>>>>> > >>>>>> Interestingly it's pretty much exactly the same approach I followed > >>>>>> with the triaging I had done with 0.100. It would be good to have a > simple > >>>>>> set of rule like that written down before the meeting. I think the > way we > >>>>>> triage has a huge impact on lowering contribution barriers, > >>>>>> > >>>>> > >>>>> +1 > >>>>> > >>>>> We need at least verify all the "Unconfirmed" tickets. We can start > >>>>> now, don't need wait until the triage meeting. > >>>>> I assume, if the bug is confirmed, we should set: > >>>>> Milestone = 0.102 > >>>>> Status = New > >>>> > >>>> > >>>> I wonder about Milestone. It seems like it would only be useful if we > >>>> assign different milestones to tickets and I'm not sure we can do that > >>>> without being able to allocate resources to fix them. It's also a time > >>>> consuming task. > >>> > >>> > >>> True. > >>> > >>>> > >>>> > >>>>> > >>>>> or close them if are not longer present. > >>>>> > >>>>> Would be good if we can reset all the priorities to "Unassigned", > >>>>> in all the tickets with module=Sugar,the field content does not have > >>>>> any sense right now. > >>>> > >>>> > >>>> Do we want to use the field? Otherwise maybe there is a w > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
This is probably going to be a bit controversial, but I think if something is worth marking minor then it's probably not worth tracking. We will never get to fix the minor but we will waste time triaging and retriaging them. On Thursday, 10 April 2014, Gonzalo Odiard wrote: > +1 to check if are enhancements or defects. > > About priorities, we can make something like: > > blocker: regressions, crashes, serious bugs > > major: bugs affecting the usability > > minor: other > > Just a idea to start to discuss. > > Gonzalo > > > > On Wed, Apr 9, 2014 at 10:24 PM, Walter Bender wrote: > > On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez > wrote: > > Something else to consider is what to do with priorities. It might make > > sense to set one when confirming bugs, it's hard to get right without > > spending a lot of time really but maybe helpful for contributors even if > not > > very accurate. > > I think we have too many categories for priorities: IMHO, either it is > a blocker or it is not. > > -walter > > > > > > On Thursday, 10 April 2014, Daniel Narvaez wrote: > >> > >> > >> > >> On Thursday, 10 April 2014, Gonzalo Odiard > wrote: > >>> > >>> > >>> > >>> > >>> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez > >>> wrote: > >>>> > >>>> On Wednesday, 9 April 2014, Gonzalo Odiard > >>>> wrote: > >>>>> > >>>>> > >>>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez > > >>>>> wrote: > >>>>>> > >>>>>> This is an interesting blog post with a paragraph about GNOME > triaging > >>>>>> > >>>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ > >>>>>> > >>>>>> Interestingly it's pretty much exactly the same approach I followed > >>>>>> with the triaging I had done with 0.100. It would be good to have a > simple > >>>>>> set of rule like that written down before the meeting. I think the > way we > >>>>>> triage has a huge impact on lowering contribution barriers, > >>>>>> > >>>>> > >>>>> +1 > >>>>> > >>>>> We need at least verify all the "Unconfirmed" tickets. We can start > >>>>> now, don't need wait until the triage meeting. > >>>>> I assume, if the bug is confirmed, we should set: > >>>>> Milestone = 0.102 > >>>>> Status = New > >>>> > >>>> > >>>> I wonder about Milestone. It seems like it would only be useful if we > >>>> assign different milestones to tickets and I'm not sure we can do that > >>>> without being able to allocate resources to fix them. It's also a time > >>>> consuming task. > >>> > >>> > >>> True. > >>> > >>>> > >>>> > >>>>> > >>>>> or close them if are not longer present. > >>>>> > >>>>> Would be good if we can reset all the priorities to "Unassigned", > >>>>> in all the tickets with module=Sugar,the field content does not have > >>>>> any sense right now. > >>>> > >>>> > >>>> Do we want to use the field? Otherwise maybe there is a way to just > get > >>>> rid of it. > >>>> > >>>> > >>> > >>> Just to mark they have been triaged, and based in the querys used in > >>> bugs.sugarlabs.org home. > >>> Do you propose doing in another way? > >> > >> > >> The home queries uses status == unconfirmed for untriaged. The tickets I > >> set status = new (not that many left) have been confirmed. I had reset > >> everything to unconfirmed before starting to triage. > >> > >> > >> -- > >> Daniel Narvaez > >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Yes! I agree. On Thursday, 10 April 2014, Walter Bender wrote: > On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez > > > wrote: > > Something else to consider is what to do with priorities. It might make > > sense to set one when confirming bugs, it's hard to get right without > > spending a lot of time really but maybe helpful for contributors even if > not > > very accurate. > > I think we have too many categories for priorities: IMHO, either it is > a blocker or it is not. > > -walter > > > > > > On Thursday, 10 April 2014, Daniel Narvaez > > > > wrote: > >> > >> > >> > >> On Thursday, 10 April 2014, Gonzalo Odiard > >> > > wrote: > >>> > >>> > >>> > >>> > >>> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez > >>> > > > >>> wrote: > >>>> > >>>> On Wednesday, 9 April 2014, Gonzalo Odiard > >>>> > > > >>>> wrote: > >>>>> > >>>>> > >>>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez > >>>>> > > > >>>>> wrote: > >>>>>> > >>>>>> This is an interesting blog post with a paragraph about GNOME > triaging > >>>>>> > >>>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ > >>>>>> > >>>>>> Interestingly it's pretty much exactly the same approach I followed > >>>>>> with the triaging I had done with 0.100. It would be good to have a > simple > >>>>>> set of rule like that written down before the meeting. I think the > way we > >>>>>> triage has a huge impact on lowering contribution barriers, > >>>>>> > >>>>> > >>>>> +1 > >>>>> > >>>>> We need at least verify all the "Unconfirmed" tickets. We can start > >>>>> now, don't need wait until the triage meeting. > >>>>> I assume, if the bug is confirmed, we should set: > >>>>> Milestone = 0.102 > >>>>> Status = New > >>>> > >>>> > >>>> I wonder about Milestone. It seems like it would only be useful if we > >>>> assign different milestones to tickets and I'm not sure we can do that > >>>> without being able to allocate resources to fix them. It's also a time > >>>> consuming task. > >>> > >>> > >>> True. > >>> > >>>> > >>>> > >>>>> > >>>>> or close them if are not longer present. > >>>>> > >>>>> Would be good if we can reset all the priorities to "Unassigned", > >>>>> in all the tickets with module=Sugar,the field content does not have > >>>>> any sense right now. > >>>> > >>>> > >>>> Do we want to use the field? Otherwise maybe there is a way to just > get > >>>> rid of it. > >>>> > >>>> > >>> > >>> Just to mark they have been triaged, and based in the querys used in > >>> bugs.sugarlabs.org home. > >>> Do you propose doing in another way? > >> > >> > >> The home queries uses status == unconfirmed for untriaged. The tickets I > >> set status = new (not that many left) have been confirmed. I had reset > >> everything to unconfirmed before starting to triage. > >> > >> > >> -- > >> Daniel Narvaez > >> > > > > > > -- > > Daniel Narvaez > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Finally, something I think is important is to set enhancement vs defect. It doesn't take much effort and it's very useful when we are feature frozen. On Thursday, 10 April 2014, Daniel Narvaez wrote: > Something else to consider is what to do with priorities. It might make > sense to set one when confirming bugs, it's hard to get right without > spending a lot of time really but maybe helpful for contributors even if > not very accurate. > > On Thursday, 10 April 2014, Daniel Narvaez > > > wrote: > >> >> >> On Thursday, 10 April 2014, Gonzalo Odiard wrote: >> >>> >>> >>> >>> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez wrote: >>> >>>> On Wednesday, 9 April 2014, Gonzalo Odiard >>>> wrote: >>>> >>>>> >>>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez >>>>> wrote: >>>>> >>>>>> This is an interesting blog post with a paragraph about GNOME triaging >>>>>> >>>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ >>>>>> >>>>>> Interestingly it's pretty much exactly the same approach I followed >>>>>> with the triaging I had done with 0.100. It would be good to have a >>>>>> simple >>>>>> set of rule like that written down before the meeting. I think the way we >>>>>> triage has a huge impact on lowering contribution barriers, >>>>>> >>>>>> >>>>> +1 >>>>> >>>>> We need at least verify all the "Unconfirmed" tickets. We can start >>>>> now, don't need wait until the triage meeting. >>>>> I assume, if the bug is confirmed, we should set: >>>>> Milestone = 0.102 >>>>> Status = New >>>>> >>>> >>>> I wonder about Milestone. It seems like it would only be useful if we >>>> assign different milestones to tickets and I'm not sure we can do that >>>> without being able to allocate resources to fix them. It's also a time >>>> consuming task. >>>> >>> >>> True. >>> >>> >>>> >>>> >>>>> or close them if are not longer present. >>>>> >>>>> Would be good if we can reset all the priorities to "Unassigned", >>>>> in all the tickets with module=Sugar,the field content does not have >>>>> any sense right now. >>>>> >>>> >>>> Do we want to use the field? Otherwise maybe there is a way to just get >>>> rid of it. >>>> >>>> >>>> >>> Just to mark they have been triaged, and based in the querys used in >>> bugs.sugarlabs.org home. >>> Do you propose doing in another way? >>> >> >> The home queries uses status == unconfirmed for untriaged. The tickets I >> set status = new (not that many left) have been confirmed. I had reset >> everything to unconfirmed before starting to triage. >> >> >> -- >> Daniel Narvaez >> >> > > -- > Daniel Narvaez > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
Something else to consider is what to do with priorities. It might make sense to set one when confirming bugs, it's hard to get right without spending a lot of time really but maybe helpful for contributors even if not very accurate. On Thursday, 10 April 2014, Daniel Narvaez wrote: > > > On Thursday, 10 April 2014, Gonzalo Odiard > > > wrote: > >> >> >> >> On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez wrote: >> >>> On Wednesday, 9 April 2014, Gonzalo Odiard >>> wrote: >>> >>>> >>>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez wrote: >>>> >>>>> This is an interesting blog post with a paragraph about GNOME triaging >>>>> >>>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ >>>>> >>>>> Interestingly it's pretty much exactly the same approach I followed >>>>> with the triaging I had done with 0.100. It would be good to have a simple >>>>> set of rule like that written down before the meeting. I think the way we >>>>> triage has a huge impact on lowering contribution barriers, >>>>> >>>>> >>>> +1 >>>> >>>> We need at least verify all the "Unconfirmed" tickets. We can start >>>> now, don't need wait until the triage meeting. >>>> I assume, if the bug is confirmed, we should set: >>>> Milestone = 0.102 >>>> Status = New >>>> >>> >>> I wonder about Milestone. It seems like it would only be useful if we >>> assign different milestones to tickets and I'm not sure we can do that >>> without being able to allocate resources to fix them. It's also a time >>> consuming task. >>> >> >> True. >> >> >>> >>> >>>> or close them if are not longer present. >>>> >>>> Would be good if we can reset all the priorities to "Unassigned", >>>> in all the tickets with module=Sugar,the field content does not have >>>> any sense right now. >>>> >>> >>> Do we want to use the field? Otherwise maybe there is a way to just get >>> rid of it. >>> >>> >>> >> Just to mark they have been triaged, and based in the querys used in >> bugs.sugarlabs.org home. >> Do you propose doing in another way? >> > > The home queries uses status == unconfirmed for untriaged. The tickets I > set status = new (not that many left) have been confirmed. I had reset > everything to unconfirmed before starting to triage. > > > -- > Daniel Narvaez > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
On Thursday, 10 April 2014, Gonzalo Odiard wrote: > > > > On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez > > > wrote: > >> On Wednesday, 9 April 2014, Gonzalo Odiard >> > >> wrote: >> >>> >>> On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez wrote: >>> >>>> This is an interesting blog post with a paragraph about GNOME triaging >>>> >>>> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ >>>> >>>> Interestingly it's pretty much exactly the same approach I followed >>>> with the triaging I had done with 0.100. It would be good to have a simple >>>> set of rule like that written down before the meeting. I think the way we >>>> triage has a huge impact on lowering contribution barriers, >>>> >>>> >>> +1 >>> >>> We need at least verify all the "Unconfirmed" tickets. We can start >>> now, don't need wait until the triage meeting. >>> I assume, if the bug is confirmed, we should set: >>> Milestone = 0.102 >>> Status = New >>> >> >> I wonder about Milestone. It seems like it would only be useful if we >> assign different milestones to tickets and I'm not sure we can do that >> without being able to allocate resources to fix them. It's also a time >> consuming task. >> > > True. > > >> >> >>> or close them if are not longer present. >>> >>> Would be good if we can reset all the priorities to "Unassigned", >>> in all the tickets with module=Sugar,the field content does not have >>> any sense right now. >>> >> >> Do we want to use the field? Otherwise maybe there is a way to just get >> rid of it. >> >> >> > Just to mark they have been triaged, and based in the querys used in > bugs.sugarlabs.org home. > Do you propose doing in another way? > The home queries uses status == unconfirmed for untriaged. The tickets I set status = new (not that many left) have been confirmed. I had reset everything to unconfirmed before starting to triage. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Really bad web activity crashes on XO
Is the server listening on 127.0.0.1? I wonder if the server refuses the connection because of that. It wouldn't easily explain the fact that it works with chrome, but maybe libsoup and chrome handles 0.0.0.0 differently. On Wednesday, 9 April 2014, Gonzalo Odiard wrote: > I found two problems with the web activities using webkit1 > > The first can be solved with http://ur1.ca/h1lgy > > the second with http://ur1.ca/h1lh4 > > I understand the first problem, but still can't understand the second. > > Gonzalo > > > On Wed, Apr 9, 2014 at 1:44 PM, Daniel Narvaez > > > wrote: > >> Ok. Those are probably using OpenGL. I think these days support for gl >> should really be in the platform, but we should probably propose and >> discuss that explicitly. >> >> >> On Wednesday, 9 April 2014, Sam Parkinson >> wrote: >> >> I am trying to: >> * run the 2048 Activity ( >> http://activities.sugarlabs.org/en-US/sugar/addon/4738 ) >> * use the 'handwritten' (notebook) theme in sugar slides ( >> https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts >> to load so maybe that is it? >> On Apr 9, 2014 8:11 PM, "Daniel Narvaez" wrote: >> >> The sugar-build errors sounds like missing Mesa/gl bits, which >> are probably not part of the platform yet. What are you trying to do? >> >> On Wednesday, 9 April 2014, Sam Parkinson >> wrote: >> >> Hi, >> >> I was trying to run a web activity on an XO with the 102 image, but no >> matter what activity I run I just get: >> >> 1397035392.644876 ERROR root: Using port 56277 >> >> /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot >> register existing type `WebKitWebResource' >> >> g_type = info.get_g_type() >> >> /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: >> g_once_init_leave: assertion `result != 0' failed >> >> g_type = info.get_g_type() >> >> /usr/lib/python2.7/site-packages/gi/module.py:155: Warning: >> g_type_get_qdata: assertion `node != NULL' failed >> >> type_ = g_type.pytype >> >> /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: >> g_type_get_qdata: assertion `node != NULL' failed >> >> g_type.pytype = wrapper >> >> /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: >> g_type_set_qdata: assertion `node != NULL' failed >> >> g_type.pytype = wrapper >> >> >> This is a bit of an issue as every web activity crashes :( >> >> Does anyone have any ideas? It didn't crash on 100. I tested removing the >> file selector changes but it didn't fix it (yay, wasn't my fault :P). >> >> >> Thanks, Sam >> >> >> >> P.S. Does anyone know about these errors in sugar-build: >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
On Wednesday, 9 April 2014, Gonzalo Odiard wrote: > > On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez > > > wrote: > >> This is an interesting blog post with a paragraph about GNOME triaging >> >> http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ >> >> Interestingly it's pretty much exactly the same approach I followed with >> the triaging I had done with 0.100. It would be good to have a simple set >> of rule like that written down before the meeting. I think the way we >> triage has a huge impact on lowering contribution barriers, >> >> > +1 > > We need at least verify all the "Unconfirmed" tickets. We can start now, > don't need wait until the triage meeting. > I assume, if the bug is confirmed, we should set: > Milestone = 0.102 > Status = New > I wonder about Milestone. It seems like it would only be useful if we assign different milestones to tickets and I'm not sure we can do that without being able to allocate resources to fix them. It's also a time consuming task. > or close them if are not longer present. > > Would be good if we can reset all the priorities to "Unassigned", > in all the tickets with module=Sugar,the field content does not have any > sense right now. > Do we want to use the field? Otherwise maybe there is a way to just get rid of it. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Really bad web activity crashes on XO
Ok. Those are probably using OpenGL. I think these days support for gl should really be in the platform, but we should probably propose and discuss that explicitly. On Wednesday, 9 April 2014, Sam Parkinson wrote: > I am trying to: > * run the 2048 Activity ( > http://activities.sugarlabs.org/en-US/sugar/addon/4738 ) > * use the 'handwritten' (notebook) theme in sugar slides ( > https://github.com/SAMdroid-apps/sugar-slides ). That theme has 2 fonts > to load so maybe that is it? > On Apr 9, 2014 8:11 PM, "Daniel Narvaez" > > > wrote: > >> The sugar-build errors sounds like missing Mesa/gl bits, which >> are probably not part of the platform yet. What are you trying to do? >> >> On Wednesday, 9 April 2014, Sam Parkinson >> > >> wrote: >> >>> Hi, >>> >>> I was trying to run a web activity on an XO with the 102 image, but no >>> matter what activity I run I just get: >>> >>> 1397035392.644876 ERROR root: Using port 56277 >>> >>> /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot >>> register existing type `WebKitWebResource' >>> >>> g_type = info.get_g_type() >>> >>> /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: >>> g_once_init_leave: assertion `result != 0' failed >>> >>> g_type = info.get_g_type() >>> >>> /usr/lib/python2.7/site-packages/gi/module.py:155: Warning: >>> g_type_get_qdata: assertion `node != NULL' failed >>> >>> type_ = g_type.pytype >>> >>> /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: >>> g_type_get_qdata: assertion `node != NULL' failed >>> >>> g_type.pytype = wrapper >>> >>> /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: >>> g_type_set_qdata: assertion `node != NULL' failed >>> >>> g_type.pytype = wrapper >>> >>> >>> This is a bit of an issue as every web activity crashes :( >>> >>> Does anyone have any ideas? It didn't crash on 100. I tested removing >>> the file selector changes but it didn't fix it (yay, wasn't my fault :P). >>> >>> >>> Thanks, Sam >>> >>> >>> >>> P.S. Does anyone know about these errors in sugar-build: >>> >>> libEGL warning: DRI2: failed to open swrast (search paths >>> /usr/lib64/dri) >>> >>> libEGL warning: GLX: glXQueryVersion failed >>> >>> They only appear on sugar-build, not epiphany (another gtk-webkit2 >>> browser) in gnome. >>> >> >> >> -- >> Daniel Narvaez >> >> -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] triage meeting
This is an interesting blog post with a paragraph about GNOME triaging http://afaikblog.wordpress.com/2014/04/09/enabling-participation/ Interestingly it's pretty much exactly the same approach I followed with the triaging I had done with 0.100. It would be good to have a simple set of rule like that written down before the meeting. I think the way we triage has a huge impact on lowering contribution barriers, On Wednesday, 9 April 2014, Walter Bender wrote: > We plan to hold a triage meeting to clean up bugs.sugarlabs.org on > Wednesday, 23 April, beginning at 9AM EST (14 UTC). We will be on > irc.freenode.net #sugar-meeting all day. Please join the fun. > > -- > > Tenemos la intención de celebrar una reunión de triage para limpiar > bugs.sugarlabs.org el miércoles 23 de abril a partir de las 9 a.m. EST > (14 UTC). Estaremos en irc.freenode.net #sugar-meeting todo el día. > Por favor, únase a la diversión. > > > regards. > > -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 > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Really bad web activity crashes on XO
The sugar-build errors sounds like missing Mesa/gl bits, which are probably not part of the platform yet. What are you trying to do? On Wednesday, 9 April 2014, Sam Parkinson wrote: > Hi, > > I was trying to run a web activity on an XO with the 102 image, but no > matter what activity I run I just get: > > 1397035392.644876 ERROR root: Using port 56277 > > /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: cannot > register existing type `WebKitWebResource' > > g_type = info.get_g_type() > > /usr/lib/python2.7/site-packages/gi/module.py:151: Warning: > g_once_init_leave: assertion `result != 0' failed > > g_type = info.get_g_type() > > /usr/lib/python2.7/site-packages/gi/module.py:155: Warning: > g_type_get_qdata: assertion `node != NULL' failed > > type_ = g_type.pytype > > /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: > g_type_get_qdata: assertion `node != NULL' failed > > g_type.pytype = wrapper > > /usr/lib/python2.7/site-packages/gi/module.py:195: Warning: > g_type_set_qdata: assertion `node != NULL' failed > > g_type.pytype = wrapper > > > This is a bit of an issue as every web activity crashes :( > > Does anyone have any ideas? It didn't crash on 100. I tested removing the > file selector changes but it didn't fix it (yay, wasn't my fault :P). > > > Thanks, Sam > > > > P.S. Does anyone know about these errors in sugar-build: > > libEGL warning: DRI2: failed to open swrast (search paths > /usr/lib64/dri) > > libEGL warning: GLX: glXQueryVersion failed > > They only appear on sugar-build, not epiphany (another gtk-webkit2 > browser) in gnome. > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pull requests + buildbot
I probably added some confusion with my testing. Some of those emails was me opening/closing pull requests etc. I'm not completely sure, but I suspect no emails are sent at all for this, the idea being that when a reviewer looks at the pull request the status will almost certainly be there. Though for the submitter an email on failure could actually be handy, ideally to him only to avoid spamming the reviewers... Maybe let's see how it behaves exactly when someone submits a new pull request, then perhaps we can see better how to tweak it. On Monday, 7 April 2014, Gonzalo Odiard wrote: > I asked because I received the mails yesterday for every pull request, > and then when was opened and closed, > but not when a build failed. Even in "Test breaking build (#332)" > May be is only received by who sent the pr? > > Gonzalo > > > On Mon, Apr 7, 2014 at 6:23 AM, Daniel Narvaez > > > wrote: > >> Did you see the "details" link? It's the same link we receive by email. >> >> >> On Monday, 7 April 2014, Gonzalo Odiard >> > >> wrote: >> >>> Nice trick. Is possible add a comment with the build result, >>> then we receive a mail? (Or at least in the fail case) >>> >>> Gonzalo >>> >>> >>> On Sun, Apr 6, 2014 at 6:20 PM, Daniel Narvaez wrote: >>> >>>> It starts a build whenever a pr is opened or reopened, while it's >>>> building it shows that there is a build pending, then it changes the status >>>> to success/failure. It also starts a new build if commits are added or >>>> changed. >>>> >>>> >>>> On 6 April 2014 21:17, Manuel Quiñones wrote: >>>> >>>>> 2014-04-05 21:51 GMT-03:00 Daniel Narvaez : >>>>> > Hey, >>>>> > >>>>> > I have finally setup integration between pull requests and buildbot. >>>>> > >>>>> > When you push a pull request buildbot will trigger a build and >>>>> update the >>>>> > github UI to indicate success or failure. The idea is that we should >>>>> not >>>>> > normally merge a pull request unless the build was successful. >>>>> > >>>>> > You can open the build page by clicking on the "details" link. If >>>>> the build >>>>> > failed for reasons which are not related to the patches, you can use >>>>> the >>>>> > "Rebuild" button to retry it. >>>>> > >>>>> > The integration is done with a very simple node server >>>>> > https://github.com/sugarlabs/sugar-gitbot/blob/master/app.js >>>>> > I don't expect it to be particularly solid yet, so if you run into >>>>> any issue >>>>> > please let me know! >>>>> >>>>> Great work! I see it is running well. So it closes the PR while >>>>> checking and then if check succeeds reopens it again? >>>>> >>>>> -- >>>>> .. manuq .. >>>>> >>>> >>>> >>>> >>>> -- >>>> Daniel Narvaez >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Software for children learning >>> >> >> >> -- >> Daniel Narvaez >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Looking at my email, it sounds like Aleksey is offline for a while but Ignacio is co-maintainer. Adding both. On Monday, 7 April 2014, Gonzalo Odiard wrote: > > On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez > > > wrote: > >> Gonzalo, can you confirm which of these activities you maintain and if >> you are fine with the move? So I can try to hunt down the remaining >> maintainers. >> >> > I maintain: > write > read > log (with Ignacio) > jukebox > imageviewer (with Agustin) > terminal > > > Aleksey maintained > > chat > > Gonzalo > > > > >> >> On Friday, 4 April 2014, Daniel Narvaez >> > >> wrote: >> >>> Hello, >>> >>> I think we should move more of our modules to github, at least all the >>> ones we are currently building in sugar-build. >>> >>> That will make it easier for contributors because they won't have to go >>> through two different processes to submit patches. Also gitorious lacks pr >>> notifications which is really bad. >>> >>> Finally, it would make it easier to detect changes to the modules in >>> buildbot without having to poll, which is giving issues to our server (you >>> could probably do the same on gitorious, but I'm not really looking forward >>> to write and maintain that for two different services). I'm also planning >>> to add support for triggering builds on pr submission, so that broken ones >>> can be marked as such in the UI, and it would be good for all the modules >>> to benefit from this. >>> >>> So here are the modules I would like to move >>> >>> sugar >>> sugar-toolkit >>> browse >>> write >>> chat >>> read >>> log >>> terminal >>> pippy >>> imageviewer >>> jukebox >>> turtleart >>> >>> What needs to be done >>> >>> 1 Get permission from module maintainers. If you are reading this please >>> confirm you are fine with this. >>> 2 Mirror the modules on github. I can take care of that. >>> 3 Update sugar-build. I can take care of that. >>> 4 Update pootle. Gonzalo, did you volunteer? :) >>> 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows >>> who/how did it for the core modules? >>> >>> -- >>> Daniel Narvaez >>> >> >> >> -- >> Daniel Narvaez >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pull requests + buildbot
Did you see the "details" link? It's the same link we receive by email. On Monday, 7 April 2014, Gonzalo Odiard wrote: > Nice trick. Is possible add a comment with the build result, > then we receive a mail? (Or at least in the fail case) > > Gonzalo > > > On Sun, Apr 6, 2014 at 6:20 PM, Daniel Narvaez > > > wrote: > >> It starts a build whenever a pr is opened or reopened, while it's >> building it shows that there is a build pending, then it changes the status >> to success/failure. It also starts a new build if commits are added or >> changed. >> >> >> On 6 April 2014 21:17, Manuel Quiñones >> >> > wrote: >> >>> 2014-04-05 21:51 GMT-03:00 Daniel Narvaez >>> >>> >: >>> > Hey, >>> > >>> > I have finally setup integration between pull requests and buildbot. >>> > >>> > When you push a pull request buildbot will trigger a build and update >>> the >>> > github UI to indicate success or failure. The idea is that we should >>> not >>> > normally merge a pull request unless the build was successful. >>> > >>> > You can open the build page by clicking on the "details" link. If the >>> build >>> > failed for reasons which are not related to the patches, you can use >>> the >>> > "Rebuild" button to retry it. >>> > >>> > The integration is done with a very simple node server >>> > https://github.com/sugarlabs/sugar-gitbot/blob/master/app.js >>> > I don't expect it to be particularly solid yet, so if you run into any >>> issue >>> > please let me know! >>> >>> Great work! I see it is running well. So it closes the PR while >>> checking and then if check succeeds reopens it again? >>> >>> -- >>> .. manuq .. >>> >> >> >> >> -- >> Daniel Narvaez >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pull requests + buildbot
It starts a build whenever a pr is opened or reopened, while it's building it shows that there is a build pending, then it changes the status to success/failure. It also starts a new build if commits are added or changed. On 6 April 2014 21:17, Manuel Quiñones wrote: > 2014-04-05 21:51 GMT-03:00 Daniel Narvaez : > > Hey, > > > > I have finally setup integration between pull requests and buildbot. > > > > When you push a pull request buildbot will trigger a build and update the > > github UI to indicate success or failure. The idea is that we should not > > normally merge a pull request unless the build was successful. > > > > You can open the build page by clicking on the "details" link. If the > build > > failed for reasons which are not related to the patches, you can use the > > "Rebuild" button to retry it. > > > > The integration is done with a very simple node server > > https://github.com/sugarlabs/sugar-gitbot/blob/master/app.js > > I don't expect it to be particularly solid yet, so if you run into any > issue > > please let me know! > > Great work! I see it is running well. So it closes the PR while > checking and then if check succeeds reopens it again? > > -- > .. manuq .. > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About changes in pootle server config
On Sunday, 6 April 2014, Daniel Narvaez wrote: > On 4 April 2014 14:10, Gonzalo Odiard > > > wrote: > >> >> >> >> On Fri, Apr 4, 2014 at 10:06 AM, Chris Leonard >> >> > wrote: >> >>> I did not do the move to github and I do not know how to either. I am >>> going to need help to teach me how to do that. >>> >>> In fact, I am getting overwhelmed with other things and may need to >>> pull back from some of the Pootle maintenance I have been doing. >>> >>> >> Theses are but news... >> Do you know who moved sugar and sugar-toolkit-gtk3 projects? >> I remember I sent my pubkey, but I didn't had permissions in the server >> at that time. >> > > From my old emails it seems like it was alsroot. > By the way, it sounds pretty simple, we just need someone with access 2) Modify the git repository configs of sugar and sugar-toolkit-gtk3 The directories are: /var/lib/pootle/checkouts/glucose/sugar and /var/lib/pootle/checkouts/glucose/sugar-toolkit-gtk3 The new repositories are: g...@github.com:sugarlabs/sugar.git and g...@github.com:sugarlabs/sugar-toolkit-gtk3.git -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
Gonzalo, can you confirm which of these activities you maintain and if you are fine with the move? So I can try to hunt down the remaining maintainers. On Friday, 4 April 2014, Daniel Narvaez wrote: > Hello, > > I think we should move more of our modules to github, at least all the > ones we are currently building in sugar-build. > > That will make it easier for contributors because they won't have to go > through two different processes to submit patches. Also gitorious lacks pr > notifications which is really bad. > > Finally, it would make it easier to detect changes to the modules in > buildbot without having to poll, which is giving issues to our server (you > could probably do the same on gitorious, but I'm not really looking forward > to write and maintain that for two different services). I'm also planning > to add support for triggering builds on pr submission, so that broken ones > can be marked as such in the UI, and it would be good for all the modules > to benefit from this. > > So here are the modules I would like to move > > sugar > sugar-toolkit > browse > write > chat > read > log > terminal > pippy > imageviewer > jukebox > turtleart > > What needs to be done > > 1 Get permission from module maintainers. If you are reading this please > confirm you are fine with this. > 2 Mirror the modules on github. I can take care of that. > 3 Update sugar-build. I can take care of that. > 4 Update pootle. Gonzalo, did you volunteer? :) > 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows > who/how did it for the core modules? > > -- > Daniel Narvaez > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving more modules to github
On Sunday, 6 April 2014, Manuel Quiñones wrote: > Hi, > > 2014-04-04 8:18 GMT-03:00 Daniel Narvaez > >: > > Hello, > > > > I think we should move more of our modules to github, at least all the > ones > > we are currently building in sugar-build. > > > > That will make it easier for contributors because they won't have to go > > through two different processes to submit patches. Also gitorious lacks > pr > > notifications which is really bad. > > > > Finally, it would make it easier to detect changes to the modules in > > buildbot without having to poll, which is giving issues to our server > (you > > could probably do the same on gitorious, but I'm not really looking > forward > > to write and maintain that for two different services). I'm also > planning to > > add support for triggering builds on pr submission, so that broken ones > can > > be marked as such in the UI, and it would be good for all the modules to > > benefit from this. > > > > So here are the modules I would like to move > > > > sugar > > This one is already in Github. > Oops I meant sugar-base. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About changes in pootle server config
On 4 April 2014 14:10, Gonzalo Odiard wrote: > > > > On Fri, Apr 4, 2014 at 10:06 AM, Chris Leonard > wrote: > >> I did not do the move to github and I do not know how to either. I am >> going to need help to teach me how to do that. >> >> In fact, I am getting overwhelmed with other things and may need to >> pull back from some of the Pootle maintenance I have been doing. >> >> > Theses are but news... > Do you know who moved sugar and sugar-toolkit-gtk3 projects? > I remember I sent my pubkey, but I didn't had permissions in the server at > that time. > >From my old emails it seems like it was alsroot. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Pull requests + buildbot
Hey, I have finally setup integration between pull requests and buildbot. When you push a pull request buildbot will trigger a build and update the github UI to indicate success or failure. The idea is that we should not normally merge a pull request unless the build was successful. You can open the build page by clicking on the "details" link. If the build failed for reasons which are not related to the patches, you can use the "Rebuild" button to retry it. The integration is done with a very simple node server https://github.com/sugarlabs/sugar-gitbot/blob/master/app.js I don't expect it to be particularly solid yet, so if you run into any issue please let me know! -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Moving more modules to github
Hello, I think we should move more of our modules to github, at least all the ones we are currently building in sugar-build. That will make it easier for contributors because they won't have to go through two different processes to submit patches. Also gitorious lacks pr notifications which is really bad. Finally, it would make it easier to detect changes to the modules in buildbot without having to poll, which is giving issues to our server (you could probably do the same on gitorious, but I'm not really looking forward to write and maintain that for two different services). I'm also planning to add support for triggering builds on pr submission, so that broken ones can be marked as such in the UI, and it would be good for all the modules to benefit from this. So here are the modules I would like to move sugar sugar-toolkit browse write chat read log terminal pippy imageviewer jukebox turtleart What needs to be done 1 Get permission from module maintainers. If you are reading this please confirm you are fine with this. 2 Mirror the modules on github. I can take care of that. 3 Update sugar-build. I can take care of that. 4 Update pootle. Gonzalo, did you volunteer? :) 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows who/how did it for the core modules? -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] unable to launch record activity in sugar development environment
Oooh damn gtk2... This needs to be backported to sugar-toolkit commit fe192be798ac1a9bd13983d197cb5775b7da2ad5 Author: Daniel Narvaez Date: Wed Sep 11 16:36:31 2013 +0200 Add a SUGAR_HOME environment variable We should really use XDG directories but that will be a bit more complicated and require migration scripts. This is a short time solution to "expose" the dot sugar directory in sugar-build. On 4 April 2014 11:33, Gonzalo Odiard wrote: > Record is a gtk2 activity, then is using sugar.profile, not sugar3.profile, > and is not looking at the broot directory, but to .sugar/default/ > I think we discussed this issue about the compatibility with gtk2 > activities before, > but don't remember what we decided. > > Gonzalo > > > On Fri, Apr 4, 2014 at 7:26 AM, Daniel Narvaez wrote: > >> Aren't the keys supposed to be created by sugar on first start? >> >> >> On Friday, 4 April 2014, Sam Parkinson wrote: >> >>> Hi, >>> >>> Try copying your ssh keys to [dot sugar dir]/default/. You should copy >>> the id_rsa.pub to owner.key.pub >>> >>> Have a look at this for how to make ssh keys if you need to: >>> https://help.github.com/articles/generating-ssh-keys >>> >>> Hope that helps :) >>> >>> Sam >>> On Apr 4, 2014 8:15 PM, "Puneet Kaur" wrote: >>> >>>> I am unable to launch the record activity in my sugar development >>>> environment due to the following (as seen in the log): >>>> >>>> ** Message: pygobject_register_sinkfunc is deprecated (GstObject) >>>> ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) >>>> Traceback (most recent call last): >>>> File "/home/broot/sugar-build/ >>>> build/out/install/bin/sugar-activity", line 164, in >>>> main() >>>> File "/home/broot/sugar-build/build/out/install/bin/sugar-activity", >>>> line 122, in main >>>> module = __import__(module_name) >>>> File "/home/broot/sugar-build/activities/Record.activity/record.py", >>>> line 48, in >>>> from model import Model >>>> File "/home/broot/sugar-build/activities/Record.activity/model.py", >>>> line 38, in >>>> from instance import Instance >>>> File "/home/broot/sugar-build/activities/Record.activity/instance.py", >>>> line 6, in >>>> class Instance: >>>> File "/home/broot/sugar-build/activities/Record.activity/instance.py", >>>> line 8, in Instance >>>> keyHash = util.sha_data(key) >>>> File "/home/broot/sugar-build/build/out/install/lib/python2. >>>> 7/site-packages/sugar/util.py", line 48, in sha_data >>>> sha_hash.update(data) >>>> TypeError: must be string or buffer, not None >>>> Exited with status 1, pid 6433 data (None, ', mode >>>> 'w' at 0xa163cd8>, '00ff052bdf454798f5c949c07f1ec80b985eaeba') >>>> >>>> As far as I have traced the error, it is due to the null value in key >>>> in line 7 in record/instance.py which in turn is due to no os path in line >>>> 87 in >>>> sugar-build/build/out/install/lib/python2.7/site-packages/sugar/profile.py, >>>> I saw the path it was set to /home/broot/.sugar/default/owner.key.pub >>>> whereas >>>> no such path exists when I look through the terminal, the correct path >>>> where the owner.key.pub is /home/dotsugar/default/owner.key.pub , I >>>> changed the path to this in line 83 of profile.py but still the condition >>>> of *not os.path.exists(key_path)* exists is true and its returning >>>> None because of which activity not launching. Other activities are running >>>> fine. I also looked into env.py there the follows the path through line 46 >>>> to 48, that is path = None condition is true. >>>> >>>> Can somebody please tell me why am I not able to launch record activity >>>> ? why is it giving such an error.I am on ubuntu 12.04 >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >> >> -- >> Daniel Narvaez >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] unable to launch record activity in sugar development environment
Aren't the keys supposed to be created by sugar on first start? On Friday, 4 April 2014, Sam Parkinson wrote: > Hi, > > Try copying your ssh keys to [dot sugar dir]/default/. You should copy the > id_rsa.pub to owner.key.pub > > Have a look at this for how to make ssh keys if you need to: > https://help.github.com/articles/generating-ssh-keys > > Hope that helps :) > > Sam > On Apr 4, 2014 8:15 PM, "Puneet Kaur" > > > wrote: > >> I am unable to launch the record activity in my sugar development >> environment due to the following (as seen in the log): >> >> ** Message: pygobject_register_sinkfunc is deprecated (GstObject) >> ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) >> Traceback (most recent call last): >> File "/home/broot/sugar-build/ >> build/out/install/bin/sugar-activity", line 164, in >> main() >> File "/home/broot/sugar-build/build/out/install/bin/sugar-activity", >> line 122, in main >> module = __import__(module_name) >> File "/home/broot/sugar-build/activities/Record.activity/record.py", >> line 48, in >> from model import Model >> File "/home/broot/sugar-build/activities/Record.activity/model.py", >> line 38, in >> from instance import Instance >> File "/home/broot/sugar-build/activities/Record.activity/instance.py", >> line 6, in >> class Instance: >> File "/home/broot/sugar-build/activities/Record.activity/instance.py", >> line 8, in Instance >> keyHash = util.sha_data(key) >> File "/home/broot/sugar-build/build/out/install/lib/python2. >> 7/site-packages/sugar/util.py", line 48, in sha_data >> sha_hash.update(data) >> TypeError: must be string or buffer, not None >> Exited with status 1, pid 6433 data (None, ', mode >> 'w' at 0xa163cd8>, '00ff052bdf454798f5c949c07f1ec80b985eaeba') >> >> As far as I have traced the error, it is due to the null value in key in >> line 7 in record/instance.py which in turn is due to no os path in line 87 >> in >> sugar-build/build/out/install/lib/python2.7/site-packages/sugar/profile.py, >> I saw the path it was set to /home/broot/.sugar/default/owner.key.pub whereas >> no such path exists when I look through the terminal, the correct path >> where the owner.key.pub is /home/dotsugar/default/owner.key.pub , I >> changed the path to this in line 83 of profile.py but still the condition >> of *not os.path.exists(key_path)* exists is true and its returning None >> because of which activity not launching. Other activities are running fine. >> I also looked into env.py there the follows the path through line 46 to 48, >> that is path = None condition is true. >> >> Can somebody please tell me why am I not able to launch record activity ? >> why is it giving such an error.I am on ubuntu 12.04 >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] unable to launch record activity in sugar development environment
You can see the /home/broot path inside an osbuild shell, it corresponds to sugar-build/home. On Friday, 4 April 2014, Puneet Kaur wrote: > I am unable to launch the record activity in my sugar development > environment due to the following (as seen in the log): > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject) > ** Message: pygobject_register_sinkfunc is deprecated (HippoCanvasBox) > Traceback (most recent call last): > File "/home/broot/sugar-build/ > build/out/install/bin/sugar-activity", line 164, in > main() > File "/home/broot/sugar-build/build/out/install/bin/sugar-activity", > line 122, in main > module = __import__(module_name) > File "/home/broot/sugar-build/activities/Record.activity/record.py", > line 48, in > from model import Model > File "/home/broot/sugar-build/activities/Record.activity/model.py", > line 38, in > from instance import Instance > File "/home/broot/sugar-build/activities/Record.activity/instance.py", > line 6, in > class Instance: > File "/home/broot/sugar-build/activities/Record.activity/instance.py", > line 8, in Instance > keyHash = util.sha_data(key) > File "/home/broot/sugar-build/build/out/install/lib/python2. > 7/site-packages/sugar/util.py", line 48, in sha_data > sha_hash.update(data) > TypeError: must be string or buffer, not None > Exited with status 1, pid 6433 data (None, ', mode 'w' > at 0xa163cd8>, '00ff052bdf454798f5c949c07f1ec80b985eaeba') > > As far as I have traced the error, it is due to the null value in key in > line 7 in record/instance.py which in turn is due to no os path in line 87 > in sugar-build/build/out/install/lib/python2.7/site-packages/sugar/profile.py, > I saw the path it was set to /home/broot/.sugar/default/owner.key.pub whereas > no such path exists when I look through the terminal, the correct path > where the owner.key.pub is /home/dotsugar/default/owner.key.pub , I > changed the path to this in line 83 of profile.py but still the condition > of *not os.path.exists(key_path)* exists is true and its returning None > because of which activity not launching. Other activities are running fine. > I also looked into env.py there the follows the path through line 46 to 48, > that is path = None condition is true. > > Can somebody please tell me why am I not able to launch record activity ? > why is it giving such an error.I am on ubuntu 12.04 > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar 0.101.4 (unstable)
Hello, this is to announce the release of 0.101.4. We made some terrific progress, have a look to the extensive release notes (credits to Walter Bender) http://wiki.sugarlabs.org/go/0.102/Notes Thanks to everyone involved! We are now feature frozen and will focus on bug fixing. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature freeze
On 29 March 2014 11:30, Daniel Narvaez wrote: > We are not approaching 0.101.4 and the feature freeze, three days left. > There are three pull requests that I feel the freeze would apply to > > https://github.com/sugarlabs/sugar/pull/192 > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/88 > (These are probably in manuq court). > These two are still unreviewed but I will go ahead with the release anyway. It should be possible to make the patches a lot less invasive and it somewhat arguable that it is a bug fix, so I'd say it will be fine to land them before UI freeze. Was any design feedback ever given to these patches? I can help with code review once that's cleared. We really need to handle them asap, it's unacceptable to leave patches in the queue for 3 months. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] shipped languages/locales
> >> >>> > > > >> > I believe AU makes their own build with en_GB. >>> > > > >> > >>> > > > >> > cjl >>> > > > >> > >>> > > > >> > >>> > > > >> > On Wed, Mar 26, 2014 at 9:33 AM, Jerry Vonau >>> > > > >> > wrote: >>> > > > >> > > Just wondering how AU is reacting without having the correct >>> > > > >> > > spelling >>> > > > >> > > for >>> > > > >> > > 'favourites', 'neighbourhood' that comes with en_BR. This >>> is a >>> > > > >> > > regression >>> > > > >> > > from DX4 that included such support. It would be better >>> would >>> > > > >> > > really >>> > > > >> > > support en_AU thou. >>> > > > >> > > >>> > > > >> > > just my thoughts, >>> > > > >> > > >>> > > > >> > > Jerry >>> > > > >> > > >>> > > > >> > >> On March 26, 2014 at 6:59 AM Gonzalo Odiard >>> > > > >> > >> >>> > > > >> > >> wrote: >>> > > > >> > >> >>> > > > >> > >> >>> > > > >> > >> I think was done to preserve space. >>> > > > >> > >> Not sure if that is a concern now. >>> > > > >> > >> >>> > > > >> > >> Gonzalo >>> > > > >> > >> >>> > > > >> > >> >>> > > > >> > >> On Sun, Mar 9, 2014 at 8:43 PM, me wrote: >>> > > > >> > >> >>> > > > >> > >> > Hi All: >>> > > > >> > >> > >>> > > > >> > >> > I'm wondering if there is any reason why there are po >>> files >>> > > > >> > >> > generated >>> > > > >> > >> > for >>> > > > >> > >> > the source in git, these are included as .mo files in the >>> > > > >> > >> > src >>> > > > >> > >> > rpm, >>> > > > >> > >> > but >>> > > > >> > >> > not >>> > > > >> > >> > shipped in the released rpms. Compare the list in git[1] >>> > > > >> > >> > and >>> > > > >> > >> > what >>> > > > >> > >> > becomes >>> > > > >> > >> > installed in the resulting rpm through "ALL_LINGUAS="[2]. >>> > > > >> > >> > Is >>> > > > >> > >> > there >>> > > > >> > >> > any >>> > > > >> > >> > reason for this? Would it be worthwhile to ship all >>> > > > >> > >> > available >>> > > > >> > >> > translations? >>> > > > >> > >> > >>> > > > >> > >> > Jerry >>> > > > >> > >> > >>> > > > >> > >> > 1. https://github.com/sugarlabs/sugar/tree/master/po >>> > > > >> > >> > 2. >>> > > > >> > >> > >>> https://github.com/sugarlabs/sugar/blob/master/configure.ac >>> > > > >> > >> > >>> > > > >> > >> > ___ >>> > > > >> > >> > Sugar-devel mailing list >>> > > > >> > >> > Sugar-devel@lists.sugarlabs.org >>> > > > >> > >> > http://lists.sugarlabs.org/listinfo/sugar-devel >>> > > > >> > >> > >>> > > > >> > >> >>> > > > >> > >> >>> > > > >> > >> >>> > > > >> > >> -- >>> > > > >> > >> Gonzalo Odiard >>> > > > >> > >> >>> > > > >> > >> SugarLabs - Learning Software for children >>> > > > >> > >> ___ >>> > > > >> > >> 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 >>> > > > >> > >>> > > > >> >>> > > > >> >>> > > > >> >>> > > > >> -- >>> > > > >> Gonzalo Odiard >>> > > > >> >>> > > > >> SugarLabs - Learning Software for children >>> > > > ___ >>> > > > 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 >>> > > >>> > >>> > >>> > >>> > -- >>> > Gonzalo Odiard >>> > >>> > SugarLabs - Learning Software for children >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children >> > > > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Pep8 1.5.1
Hello, I just updated sugar-build to use pep8 1.5.1. Please osbuild pull asap if you are submitting patches, to avoid osbuild check errors when the code will be merged. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature freeze
We are not approaching 0.101.4 and the feature freeze, three days left. There are three pull requests that I feel the freeze would apply to https://github.com/sugarlabs/sugar/pull/192 https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/88 (These are probably in manuq court). https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/124 Is there anything else outside the review queue? On 13 March 2014 13:26, Gonzalo Odiard wrote: > > > > On Thu, Mar 13, 2014 at 9:31 AM, Daniel Narvaez wrote: > >> On 13 March 2014 08:50, Peter Robinson wrote: >> >>> Daniel would you be amicable to stretching it out by a month so we >>> have one more round of dev releases before entering freeze? >> >> >> Sorry for the delay on closing down this issue, I have been busy. I'll >> try to keep it short so that we can all go back at work asap. >> >> I think we are taking the wrong decision in the wrong way here. I have >> yet to see a rationale for proposing a delay. We are apparently trying to >> save some time for some deployment team, and I'd argue we are not even >> saving much. I don't like this kind of ad hoc decisions, as an upstream we >> should be thinking less about our own short time priorities and more about >> potential contributors. I'm not in love with time based releases, as I have >> pointed out in the past, but we should be reconsidering our release >> approach as a whole, if it's not good enough, rather than making an >> exception for not particularly good reasons. >> > > I see your point, but I think is better separate the issue of extend these > release cycle, > to start a discussion about how we will manage the release cycle in the > future. > Maybe we should define a time, after 0.102, to review our release strategy. > > > >> >> That said, I think the community consensus is pretty clear, I'm the only >> one in disagreement. So please someone send me the new release dates and >> I'll update the schedule. >> > > > After ask manuq, and reading other comments here, I propose: > > 0.101.4 - 04/01/14 - Feature Freeze > 0.101.5 - 05/01/14 - String, UI, API freeze > 0.102.0 - 06/01/14 - Final release > > Now, back to work! We need do good use of this time! > > -- > Gonzalo Odiard > > SugarLabs - Learning Software for children > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error in creating sample web activity
Try to post your code. On Monday, 24 March 2014, Gaurav Parida wrote: > Using the steps given on developers.sugarlabs.org > I have made the same activity earlier, but now on doing the same steps I > am unable to create the activity. > > This is the traceback that I get in the log > > Traceback (most recent call last): > File > "/home/broot/sugar-build/build/out/install/lib/python2.7/site-packages/sugar3/activity/webactivity.py", > line 124, in _app_scheme_cb > request.finish(Gio.File.new_for_path(path).read(None), > gi._glib.GError: Error opening file: No such file or directory > > > Thanks. > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-build, can't perform check
Unfortunately there isn't much I can do about this in sugar-build. I think sugar should use localed to set the language, I don't have time to work on it myself but it should not be too hard (backward compatibility aside, sigh). I opened a ticket about it http://bugs.sugarlabs.org/ticket/4742 On 19 March 2014 19:12, Manuel Quiñones wrote: > i can confirm that smoketest fails if Sugar is set to Spanish. > > i set it to English and the test passes now. > > 2014-03-19 15:45 GMT-03:00 Manuel Quiñones : > > attached. > > > > thanks, > > > > 2014-03-18 20:19 GMT-03:00 Daniel Narvaez : > >> Can you post the logs please? > >> > >> > >> On Tuesday, 18 March 2014, Manuel Quiñones wrote: > >>> > >>> hi, > >>> > >>> i created a fresh dev environment today, and after that ./osbuild > >>> check fails with the following output: > >>> > >>> > >>> [manuq@localhost sugar-build]$ ./osbuild check > >>> > >>> $ sudo broot run osbuild check > >>> [sudo] password for manuq: > >>> > >>> = Building = > >>> > >>> * Building sugar > >>> > >>> = Check = > >>> > >>> * Running smoke test > >>> > >>> Command failed: sugar-runner > >>> > >>> > >>> Initializing built-in extension Generic Event Extension > >>> Initializing built-in extension SHAPE > >>> Initializing built-in extension MIT-SHM > >>> Initializing built-in extension XInputExtension > >>> Initializing built-in extension XTEST > >>> Initializing built-in extension BIG-REQUESTS > >>> Initializing built-in extension SYNC > >>> Initializing built-in extension XKEYBOARD > >>> Initializing built-in extension XC-MISC > >>> Initializing built-in extension XINERAMA > >>> Initializing built-in extension XFIXES > >>> Initializing built-in extension RENDER > >>> Initializing built-in extension RANDR > >>> Initializing built-in extension COMPOSITE > >>> Initializing built-in extension DAMAGE > >>> Initializing built-in extension MIT-SCREEN-SAVER > >>> Initializing built-in extension DOUBLE-BUFFER > >>> Initializing built-in extension RECORD > >>> Initializing built-in extension DPMS > >>> Initializing built-in extension X-Resource > >>> Initializing built-in extension XVideo > >>> Initializing built-in extension XVideo-MotionCompensation > >>> Initializing built-in extension SELinux > >>> Initializing built-in extension GLX > >>> screen 0 shmid 11370507 > >>> xinit: XFree86_VT property unexpectedly has 0 items instead of 1 > >>> Xlib: extension "RANDR" missing on display ":99". > >>> gnome-keyring-daemon: insufficient process capabilities, unsecure > >>> memory might get used > >>> The XKEYBOARD keymap compiler (xkbcomp) reports: > >>> > Warning: Compat map for group 2 redefined > >>> > Using new definition > >>> > Warning: Compat map for group 3 redefined > >>> > Using new definition > >>> > Warning: Compat map for group 4 redefined > >>> > Using new definition > >>> Errors from xkbcomp are not fatal to the X server > >>> xinit: connection to X server lost > >>> > >>> > >>> ! Failed to run command check > >>> Killing 10715 > >>> > >>> ! Failed to run command check > >>> [manuq@localhost sugar-build]$ > >>> > >>> > >>> -- > >>> .. manuq .. > >>> ___ > >>> Sugar-devel mailing list > >>> Sugar-devel@lists.sugarlabs.org > >>> http://lists.sugarlabs.org/listinfo/sugar-devel > >> > >> > >> > >> -- > >> Daniel Narvaez > >> > >> > >> ___ > >> Sugar-devel mailing list > >> Sugar-devel@lists.sugarlabs.org > >> http://lists.sugarlabs.org/listinfo/sugar-devel > >> > > > > > > > > -- > > .. manuq .. > > > > -- > .. manuq .. > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [pull request] Re: Better support for running non-sugar apps under Sugar
Landed! Thanks! On 23 March 2014 02:47, Sebastian Silva wrote: > Hi, > Just updated the pull requests. > https://github.com/sugarlabs/sugar/pull/298 > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/125 > > Thanks for the reviews, > Sebastian > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] How do you save stuff in web activities?
Does it work if you do it inside domReady like gtd? I don't remember if
that's required by the API (probably not) but it might trigger a race
condition anyway.
On Sunday, 23 March 2014, Sam Parkinson wrote:
> Hi,
>
> I think this is an issue with the backend. I changed to using the
> dictstore in my activity and it works a charm in chrome; it calls my loaded
> callback. But on sugar it hangs with loading the data.
> I have no idea what is wrong, since it works for get things done activity.
>
> Sam
>
>
> On Sat, Mar 22, 2014 at 6:55 PM, Sam Parkinson
>
> > wrote:
>
>> Hi,
>>
>> I am just calling this form "define(function(require)". You can see the
>> rest of the file here
>> https://github.com/SAMdroid-apps/sugar-slides/blob/master/js/activity.coffee
>>
>> Thanks :)
>>
>>
>> On Sat, Mar 22, 2014 at 6:36 PM, Daniel Narvaez
>>
>> > wrote:
>>
>>> Where are you calling this from? You should not need to setup() manually.
>>>
>>>
>>> On Saturday, 22 March 2014, Sam Parkinson
>>> >
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm just wondering, does anyone have any code snippets for saving on
>>>> web activities?
>>>>
>>>> I'm trying to make a web activity and am having some issues. Here is my
>>>> save+load code: [CoffeeScript]
>>>>
>>>> activity.setup()
>>>> datastoreObject = activity.getDatastoreObject()
>>>> onLoaded = (error, metadata, data) ->
>>>> alert data
>>>> obj = JSON.parse data
>>>> console.log obj
>>>> container.html obj.html
>>>> $('section').each (x, ele) ->
>>>> scribe_slide_setup ele
>>>> undefined
>>>> datastoreObject.loadAsText onLoaded
>>>>
>>>> activity.write = ->
>>>> obj =
>>>> html: container.html()
>>>> jsonData = JSON.stringify obj
>>>> datastoreObject.setDataAsText jsonData
>>>> datastoreObject.save()
>>>>
>>>> Neither methods end up getting called. I'm using 0.100.0.
>>>>
>>>> Thanks,
>>>> Sam
>>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>>
>>
>
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity failed to start!
Try to run sugar-launch inside a sugar terminal, it doesn't work outside sugar. On Saturday, 22 March 2014, Kamal Kaur wrote: > Hello developers > > Can you please help me know the right way to download/install > activities in sugar? I downloaded "Etoys" and "Develop 40" from > http://activities.sugarlabs.org/en-US/sugar/ from browser activity. > Both are shown in journal. But when opened, activity icon flashes and > there is a message: "Activity failed to start" Stop [ ] ( with stop > button. > > Even I couldn't find the logs in log activity. While trying to find it > out, I reached here: > http://wiki.laptop.org/go/Python_Standard_Logging_in_Sugar > > And from the above link, I tried 'sugar-launch ' > command. Which gave the output: > > kamal@kamal:~/sugar-build$ sugar-launch Etoys > The program 'sugar-launch' can be found in the following packages: > * sugar-tools-0.84 > * sugar-tools-0.86 > * sugar-tools-0.88 > * sugar-tools-0.90 > * sugar-tools-0.96 > Try: sudo apt-get install > > So I used apt-get to install Etoys. It has downloaded 44.3MBs data. > But the same problem is there. > > What I'm doing wrong? > > > > > -- > Kamaljeet Kaur > > kamalkaur188.wordpress.com > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar build - Doesn't actually build
Weird, try "osbuild clean sugar" and then run again. On Sunday, 23 March 2014, Sam Parkinson wrote: > Hi, > > I was using sugar-build and trying to run a build but all I get is a weird > error. I have recently done an ./osbuild pull but no fix. > > [sam@f20 sugar-build]$ ./osbuild run > > $ sudo broot run osbuild run > > = Building = > > * Building sugar > > Command failed: make -j 4 > > /bin/sh ./config.status > ./config.status: line 2114: syntax error: unexpected end of file > make: *** [Makefile] Error 2 > > ! Failed to run command run > > ! Failed to run command run > > The osbuild.log file is exactly the same. > > Any ideas? :) > > Sam > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] How do you save stuff in web activities?
Where are you calling this from? You should not need to setup() manually.
On Saturday, 22 March 2014, Sam Parkinson wrote:
> Hi,
>
> I'm just wondering, does anyone have any code snippets for saving on web
> activities?
>
> I'm trying to make a web activity and am having some issues. Here is my
> save+load code: [CoffeeScript]
>
> activity.setup()
> datastoreObject = activity.getDatastoreObject()
> onLoaded = (error, metadata, data) ->
> alert data
> obj = JSON.parse data
> console.log obj
> container.html obj.html
> $('section').each (x, ele) ->
> scribe_slide_setup ele
> undefined
> datastoreObject.loadAsText onLoaded
>
> activity.write = ->
> obj =
> html: container.html()
> jsonData = JSON.stringify obj
> datastoreObject.setDataAsText jsonData
> datastoreObject.save()
>
> Neither methods end up getting called. I'm using 0.100.0.
>
> Thanks,
> Sam
>
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Build is broken
Hehe, it's not like I'm picking on that patch, but it's apparently due to it :) https://github.com/sugarlabs/sugar/commit/5641a0607b1911c787d7cb7588266b9c68d37813 On Friday, 21 March 2014, Daniel Narvaez wrote: > > http://buildbot.sugarlabs.org/builders/quick-master/builds/73/steps/shell_2/logs/stdio > > -- > Daniel Narvaez > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Build is broken
http://buildbot.sugarlabs.org/builders/quick-master/builds/73/steps/shell_2/logs/stdio -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Need your views, ASAP.
This will have to be done so that old activities keep working, so no worries :) Also I suspect python2 to python3 will be much easier than gtk2 to gtk3 for activity authors (and for the book). On Friday, 21 March 2014, James Simmons wrote: > Kamal, > > I cannot speak for the whole community but my understanding is that Python > 3 is not at all backward compatible with the Python we use now. If every > Activity we have had to be rewritten in Python 3 that would be a huge > impact. > > You may be familiar with my book: > > http://en.flossmanuals.net/make-your-own-sugar-activities/ > > I recently (like a month ago) updated the book to use GTK3 in the examples > rather than GTK2. That was a big, but necessary, effort. The current Sugar > supports both GTK2 and GTK3, so no Activities need to be rewritten. GTK3 is > supposed to give better support for tablets and touch screens and of course > we want to use the latest supported software. > > In any case, while using GTK3 over time may have a big impact in the short > term it doesn't break anything. I'm not sure we could say the same thing > about rewriting Sugar to use Python 3. > > James Simmons > > > On Thu, Mar 20, 2014 at 3:55 AM, Kamal Kaur > > > wrote: > >> Hello all members, >> >> I need help with the first question in "You and Community" section. As >> I'll be working for project "Port to python 3", I need three answers, >> one of which will I get from the mentors and other from memberss So >> the members and mentors reading this message, Please give your answer >> regarding what will be the impact after completion of my project on >> community? I need to add this answer there and it should be of 1-3 >> paragraphs. >> >> There are four outlined steps: >> Step 1. Make use of GTK3 instead of GTK2 because sugar and the apps use >> it. >> Step 2. Port the Sugar core to python3. >> Step 3. Developing a robust test suite. >> Step 4: Port an existing sugar activity to python3 and document process >> >> Please tell me what are your views about the effect on community after >> completion of this project? >> >> Thank you >> >> -- >> Kamaljeet Kaur >> >> kamalkaur188.wordpress.com >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
