Re: [Sugar-devel] [Sugar Devel] Sugar-datastore build problem
Nope, I am still getting the error , even after cleaning the cache. On Thu, Aug 14, 2014 at 1:19 AM, Gonzalo Odiard wrote: > Then I don't know. > > Can you do a "make clean" to be sure is not something cached? > > Gonzalo > > > On Wed, Aug 13, 2014 at 4:44 PM, kunal arora > wrote: > >> Yeah, I just changed: >> >> PYTHON=python2 >> AM_PATH_PYTHON([2.5]) >> >> to >> >> PYTHON=python3 >> AM_PATH_PYTHON([3.1]) >> >> >> On Thu, Aug 14, 2014 at 1:10 AM, Gonzalo Odiard >> wrote: >> >>> Did you modified configure.ac ? >>> >>> Gonzalo >>> >>> >>> On Wed, Aug 13, 2014 at 4:36 PM, kunal arora >>> wrote: >>> >>>> Hi >>>> >>>> While building sugar-datastore module using Python3 , i seem to be >>>> getting this error: >>>> >>>> *checking for headers required to compile python extensions... not >>>> found* >>>> *configure: error: could not find Python headers* >>>> >>>> Searching it on google, I found out that python3-devel needs to be >>>> installed. >>>> I already installed python3-devel on my machine and the >>>> sugar-build-broot , I also included python3-devel in root.json but i am >>>> still getting the same error. >>>> Am I missing something here? >>>> Any help would be appreciated. >>>> >>>> I have attached my osbuild.log (ignore all the poop) >>>> Here's my sugar-build branch: >>>> https://github.com/curiousguy13/sugar-build/tree/sandbox1 >>>> >>>> Thanks >>>> Kunal Arora >>>> (IRC-curiousguy13) >>>> >>>> >>>> >>>> >>>> ___ >>>> Sugar-devel mailing list >>>> Sugar-devel@lists.sugarlabs.org >>>> http://lists.sugarlabs.org/listinfo/sugar-devel >>>> >>>> >>> >>> >>> -- >>> Gonzalo Odiard >>> >>> SugarLabs - Software for children learning >>> >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sugar Devel] Sugar-datastore build problem
Yeah, I just changed: PYTHON=python2 AM_PATH_PYTHON([2.5]) to PYTHON=python3 AM_PATH_PYTHON([3.1]) On Thu, Aug 14, 2014 at 1:10 AM, Gonzalo Odiard wrote: > Did you modified configure.ac ? > > Gonzalo > > > On Wed, Aug 13, 2014 at 4:36 PM, kunal arora > wrote: > >> Hi >> >> While building sugar-datastore module using Python3 , i seem to be >> getting this error: >> >> *checking for headers required to compile python extensions... not found* >> *configure: error: could not find Python headers* >> >> Searching it on google, I found out that python3-devel needs to be >> installed. >> I already installed python3-devel on my machine and the sugar-build-broot >> , I also included python3-devel in root.json but i am still getting the >> same error. >> Am I missing something here? >> Any help would be appreciated. >> >> I have attached my osbuild.log (ignore all the poop) >> Here's my sugar-build branch: >> https://github.com/curiousguy13/sugar-build/tree/sandbox1 >> >> Thanks >> Kunal Arora >> (IRC-curiousguy13) >> >> >> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Sugar Devel] Sugar-datastore build problem
Hi While building sugar-datastore module using Python3 , i seem to be getting this error: *checking for headers required to compile python extensions... not found* *configure: error: could not find Python headers* Searching it on google, I found out that python3-devel needs to be installed. I already installed python3-devel on my machine and the sugar-build-broot , I also included python3-devel in root.json but i am still getting the same error. Am I missing something here? Any help would be appreciated. I have attached my osbuild.log (ignore all the poop) Here's my sugar-build branch: https://github.com/curiousguy13/sugar-build/tree/sandbox1 Thanks Kunal Arora (IRC-curiousguy13) INFO:root:#poop:osbuild/build.py:_build_module1 INFO:root:#poop:osbuild/build.py:_build_module2 INFO:root:#poop:osbuild/build.py:_build_module3 INFO:root:#poop:osbuild/build.py:_build_module4 INFO:root:Running command make -j 16 INFO:root:Running: make -j 16 INFO:root:#poop:plog/__init.py:wait1 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/__init.py:wait2a INFO:root:/bin/sh ./config.status --recheck INFO:root:running CONFIG_SHELL=/bin/sh /bin/sh /home/broot/sugar-build/sugar-datastore/configure --enable-maintainer-mode --prefix /home/broot/sugar-build/build/out/install --libdir /home/broot/sugar-build/build/out/install/lib64 CC=ccache gcc --no-create --no-recursion INFO:root:checking for a BSD-compatible install... /bin/install -c INFO:root:checking whether build environment is sane... yes INFO:root:checking for a thread-safe mkdir -p... /bin/mkdir -p INFO:root:checking for gawk... gawk INFO:root:#poop:plog/__init.py:wait4 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/__init.py:wait2a INFO:root:checking whether make sets $(MAKE)... yes INFO:root:checking whether make supports nested variables... yes INFO:root:checking whether to enable maintainer-specific portions of Makefiles... yes INFO:root:checking build system type... x86_64-unknown-linux-gnu INFO:root:checking host system type... x86_64-unknown-linux-gnu INFO:root:checking how to print strings... printf INFO:root:checking for style of include used by make... GNU INFO:root:checking for gcc... ccache gcc INFO:root:checking whether the C compiler works... yes INFO:root:checking for C compiler default output file name... a.out INFO:root:#poop:plog/__init.py:wait4 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/__init.py:wait2a INFO:root:checking for suffix of executables... INFO:root:checking whether we are cross compiling... no INFO:root:checking for suffix of object files... o INFO:root:checking whether we are using the GNU C compiler... yes INFO:root:checking whether ccache gcc accepts -g... yes INFO:root:checking for ccache gcc option to accept ISO C89... none needed INFO:root:checking dependency style of ccache gcc... gcc3 INFO:root:checking for a sed that does not truncate output... /bin/sed INFO:root:checking for grep that handles long lines and -e... /bin/grep INFO:root:checking for egrep... /bin/grep -E INFO:root:#poop:plog/__init.py:wait4 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/__init.py:wait2a INFO:root:checking for fgrep... /bin/grep -F INFO:root:checking for ld used by ccache gcc... /bin/ld INFO:root:checking if the linker (/bin/ld) is GNU ld... yes INFO:root:checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B INFO:root:checking the name lister (/bin/nm -B) interface... BSD nm INFO:root:checking whether ln -s works... yes INFO:root:checking the maximum length of command line arguments... 1572864 INFO:root:checking whether the shell understands some XSI constructs... yes INFO:root:checking whether the shell understands "+="... yes INFO:root:checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop INFO:root:checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop INFO:root:checking for /bin/ld option to reload object files... -r INFO:root:checking for objdump... objdump INFO:root:checking how to recognize dependent libraries... pass_all INFO:root:checking for dlltool... no INFO:root:checking how to associate runtime and link libraries... printf %s\n INFO:root:checking for ar... ar INFO:root:checking for archiver @FILE support... @ INFO:root:checking for strip... strip INFO:root:checking for ranlib... ranlib INFO:root:checking command to parse /bin/nm -B output from ccache gcc object... ok INFO:root:checking for sysroot... no INFO:root:checking for mt... no INFO:root:checking if : is a manifest tool... no INFO:root:#poop:plog/__init.py:wait4 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/__init.py:wait2a INFO:root:checking how to run the C preprocessor... ccache gcc -E INFO:root:checking for ANSI C header files... yes INFO:root:checking for sys/types.h... yes INFO:root:#poop:plog/__init.py:wait4 INFO:root:#poop:plog/__init.py:wait2 INFO:root:#poop:plog/_
[Sugar-devel] Porting Sugar To Python3 Progress
I couldn't attend the GSOC meeting yesterday due to unforeseen circumstances, so here is the update on what I did this week: Most of this week was spent on debugging an issue I am having while building sugar, the issue is that when i try to build the sugar module , everything seems to go perfectly as expected but after all the code is executed , it gets stuck somewhere and continues printing empty lines in osbuild.log file . The problem might be with sugar or the plog module , I still haven't figured it out yet. Other than that i ported sugar-artwork and sugar-datastore to Python3 and also side by side I am trying to increase the test coverage of sugar module. I guess that's it. Thanks Kunal Arora (IRC-curiousguy13) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] unable to disable chroot
Hi,
i tried disabling chroot by placing the prefs.json file in sugar-build
which contained:
{
"use_broot": false
}
but i seem to be getting an error.
here is the error log:
http://fpaste.org/112786/03644557/
and the pip.log file mentioned in the error above is attached
can someone help?
/home/curiousguy13/sugar-build/build/out/sandbox/install/bin/pip run on Wed Jun 25 02:49:06 2014
Downloading/unpacking git+https://github.com/dnarvaez/osbuild
Cloning https://github.com/dnarvaez/osbuild to /tmp/pip-iFadLS-build
Found command 'git' at '/usr/bin/git'
Running command /usr/bin/git clone -q https://github.com/dnarvaez/osbuild /tmp/pip-iFadLS-build
Running setup.py (path:/tmp/pip-iFadLS-build/setup.py) egg_info for package from git+https://github.com/dnarvaez/osbuild
running egg_info
creating pip-egg-info/osbuild.egg-info
writing dependency_links to pip-egg-info/osbuild.egg-info/dependency_links.txt
writing requirements to pip-egg-info/osbuild.egg-info/requires.txt
writing pip-egg-info/osbuild.egg-info/PKG-INFO
writing top-level names to pip-egg-info/osbuild.egg-info/top_level.txt
writing manifest file 'pip-egg-info/osbuild.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
reading manifest file 'pip-egg-info/osbuild.egg-info/SOURCES.txt'
writing manifest file 'pip-egg-info/osbuild.egg-info/SOURCES.txt'
Source in /tmp/pip-iFadLS-build has version 0.33, which satisfies requirement osbuild==0.33 from git+https://github.com/dnarvaez/osbuild
Downloading/unpacking sourcestamp
Getting page https://pypi.python.org/simple/sourcestamp/
URLs to search for versions for sourcestamp:
* https://pypi.python.org/simple/sourcestamp/
Analyzing links from page https://pypi.python.org/simple/sourcestamp/
Found link https://pypi.python.org/packages/source/s/sourcestamp/sourcestamp-0.1.tar.gz#md5=505bc518505e593582109abf21f8dc10 (from https://pypi.python.org/simple/sourcestamp/), version: 0.1
Using download cache from /home/curiousguy13/sugar-build/build/out/sandbox/cache/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fs%2Fsourcestamp%2Fsourcestamp-0.1.tar.gz
Running setup.py (path:/home/curiousguy13/sugar-build/build/out/sandbox/install/build/sourcestamp/setup.py) egg_info for package sourcestamp
running egg_info
creating pip-egg-info/sourcestamp.egg-info
writing dependency_links to pip-egg-info/sourcestamp.egg-info/dependency_links.txt
writing pip-egg-info/sourcestamp.egg-info/PKG-INFO
writing top-level names to pip-egg-info/sourcestamp.egg-info/top_level.txt
writing manifest file 'pip-egg-info/sourcestamp.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
reading manifest file 'pip-egg-info/sourcestamp.egg-info/SOURCES.txt'
writing manifest file 'pip-egg-info/sourcestamp.egg-info/SOURCES.txt'
Source in ./build/out/sandbox/install/build/sourcestamp has version 0.1, which satisfies requirement sourcestamp
Requirement already satisfied (use --upgrade to upgrade): plog==0.16 in /usr/lib/python2.7/site-packages (from osbuild==0.33)
Downloading/unpacking json-format==0.1 (from osbuild==0.33)
Getting page https://pypi.python.org/simple/json-format/
URLs to search for versions for json-format==0.1 (from osbuild==0.33):
* https://pypi.python.org/simple/json-format/0.1
* https://pypi.python.org/simple/json-format/
Getting page https://pypi.python.org/simple/json-format/0.1
Could not fetch URL https://pypi.python.org/simple/json-format/0.1: 404 Client Error: Not Found
Will skip URL https://pypi.python.org/simple/json-format/0.1 when looking for download links for json-format==0.1 (from osbuild==0.33)
Analyzing links from page https://pypi.python.org/simple/json-format/
Found link https://pypi.python.org/packages/source/j/json-format/json-format-0.1.tar.gz#md5=526ee73934b6cf9b5e125daa513a4495 (from https://pypi.python.org/simple/json-format/), version: 0.1
Using download cache from /home/curiousguy13/sugar-build/build/out/sandbox/cache/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fj%2Fjson-format%2Fjson-format-0.1.tar.gz
Running setup.py (path:/home/curiousguy13/sugar-build/build/out/sandbox/install/build/json-format/setup.py) egg_info for package json-format
running egg_info
creating pip-egg-info/json_format.egg-info
writing dependency_links to pip-egg-info/json_format.egg-info/dependency_links.txt
writing pip-egg-info/json_format.egg-info/PKG-INFO
writing top-level names to pip-egg-info/json_format.egg-info/top_level.txt
writing manifest file 'pip-egg-info/json_format.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
reading manifest file 'pip-egg-info/json_format.egg-info/SOURCES.txt'
writing manifest file 'pip-egg-info/json_format.egg-info/SOURCES.txt'
Source in ./build/out/sandbox/install/build/json-format h
[Sugar-devel] chroot python3.3 problem
Hey, can anyone tell me what this command from root.py in /site-packeages/broot does: *chroot --userspec 1000:1000 /var/lib/broot/sugar-build-3xlQJ /usr/bin/env -i PATH=/bin:/usr/bin:/usr/sbin BROOT=yes XAUTHORITY=/home/broot/.Xauthority DISPLAY=:0 HOME=/home/broot LANG=C TERM=xterm-256color /bin/bash -lc "/home/broot/sugar-build/osbuild build"* because i keep getting */usr/bin/env: python3.3: No such file or directory* error when i run it using python3.3 which basically means that it cannot find the python3.3 directory in the new chroot jail , so if that is the problem, how can i add python3.3 in the chroot jail. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
On Tue, May 6, 2014 at 5:43 PM, Gonzalo Odiard wrote: > These links can be useful: > > https://docs.python.org/3/howto/pyporting.html > > > http://stackoverflow.com/questions/11372190/python-2-and-python-3-dual-development > > https://pythonhosted.org/six/ > > Gonzalo > > > On Tue, May 6, 2014 at 8:50 AM, 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 . Whereas if go with complete port into a new toolkit we will >> just have to accomodate ourselves in writing code in python3. >> But if you guys think maintaining another toolkit will be harder, then we >> can port sugar core and toolkit to python2 and python3 compatible code and >> follow the strategy mentioned above by Gonzalo. >> >> Kunal >> > > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > Thanks for the links. :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] Porting To Python3
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 . Whereas if go with complete port into a new toolkit we will just have to accomodate ourselves in writing code in python3. But if you guys think maintaining another toolkit will be harder, then we can port sugar core and toolkit to python2 and python3 compatible code and follow the strategy mentioned above by Gonzalo. Kunal ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [GSoC] Porting To Python3
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? 2)Port sugar-build to Python3 3)Port Sugar-shell to Python3 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. How the porting would be done: 1) Choose a single module. 2)Port the tests carefully and if there is not full test coverage , write some additional tests. 3) Update the code carefully to pass the tests. These links were and will be helpful as we can draw on the experience of organisations who have already ported their codebase to python3. http://twistedmatrix.com/trac/wiki/Plan/Python3 https://wiki.openstack.org/wiki/Python3#Port_Python_2_code_to_Python_3 Is there any other strategy which would be better? Any feedback/comments are welcome. Kunal (IRC- curiousguy13) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Porting sugar to Python3
Hey Everyone, Everyone seems to have a slightly different opinion of how to port sugar to Python3. So lets play a game. Pure port to Python3: Pros: 1) Relatively easier to implement. (Writing code in only one language) Cons: 1)Will have to deal with telepathy and any other non-ported dependency 2)We will have to maintain another sugar-toolkit-gtk3 (python3) Python 2/3 compatible port: Pros: 1) We will have to maintain only one toolkit. (It will be a slow transition to Python3 in order to support python2 activities) Cons: 1)Relatively difficult to implement and maintain. (Writing polyglot code compatible with Python 2/3) Rules of the game: Correct if me or anyone else is wrong in any point. Add any other points to the pros and cons list. I'll add more points if anything else come to my knowledge. And this game will end when we will reach a consensus over the better method. Let the game and discussion begin. :) Regards, Kunal (IRC- curiousguy13) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design]
On Mon, Mar 17, 2014 at 10:08 PM, Gonzalo Odiard wrote: > Note there are already patches implementing this > > http://www.google-melange.com/gci/task/view/google/gci2013/5402267310096384 > > We need agree in the design part, do we really want show all that > directories to the user? > Can be configured for specific cases? > > I also think that although this is an essential functionality, displaying all the folders may not be the best way to go from the design perspective. Some of the options that can be considered are: 1) We could choose from the settings, which folders to display. It would provide an option of customizability. 2) We could just display one Browse option which would display all the folders and files of the computer the person could choose from them (I don't know how it would be implemented right now though). Maybe the design team could weigh in and provide a better alternative. I also have a few other ideas and questions regarding this which i will discuss with you on IRC when you come back. My nickname on IRC: curiousguy13 Regards, Kunal ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Design]
Regarding ticket #3856 https://bugs.sugarlabs.org/ticket/3856 It seems like a valid design enhancement to me, and wanted to work on it. Just wanted to discuss here first. Any comments/feedback ? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
