[07:26] <m4n1sh> in .install file, I have a bunch of files under python2.7 directory
[07:26] <m4n1sh> I am putting in install file
[07:26] <m4n1sh> usr/lib/python2*/* usr/lib/python3*/
[07:26] <dholbach> good morning
[07:27] <m4n1sh> hoping those folders to be copied inside all the python3 python3.3 folders
[07:27] <m4n1sh> but it isnt
[07:27] <m4n1sh> do I need to hardcode paths usr/lib/python2*/* usr/lib/python3.3/
[07:29] <geser> what are you trying to do?
[07:30] <m4n1sh> I have a package which has a bunch of python files which installs in python2.7 location
[07:30] <m4n1sh> I need them to also have in python3.x directory
[07:31] <m4n1sh> geser: check python-zeitgeist package, I want to have python3-zeitgeist package too which installs in python3 dist-packages for ubuntu
[07:35] <geser> m4n1sh: I guess you need to use dh_python3 and let setup.py run with python3 to install it to the right directories (most can be done with dh if you tell it to build for python3 too)
[07:38] <m4n1sh> geser: it uses automake
[07:38] <m4n1sh> python-zeitgeist is a part of bigger package
[07:39] <geser> does it work with python3?
[07:40] <m4n1sh> geser: noes. when running with python3, it cannot import packages
[07:41] <geser> does upstream support to run it with python3 or does it need some porting first to be able to run with python2 and python3?
[07:43] <m4n1sh> geser: upstream doesn't support. Most probably due to an unknown technical restriction http://stackoverflow.com/questions/17541207/am-path-python-for-python2-and-python3
[07:44] <m4n1sh> because automake's AM_PATH_PYTHON cannot handle two python version at a time, or there is a way around which I am not aware of
[07:48] <geser> you might need to have to build it twice then, once for python2 and once for python3 (if upstreams allows to set python to python3)
[07:49] <geser> perhaps barry has some more ideas what needed to get a python3 package for it too
[07:52] <m4n1sh> geser: you mean to say another source package?
[07:52] <m4n1sh> or in the debian/rules change it in such a way that it builds twice?
[07:53] <geser> m4n1sh: the later
[07:54] <m4n1sh> geser: well, I have no idea how that has to be done, but AFAIK the python2.7 version can also work for python3.3 without any change
[07:55] <geser> google knows about a lp:~ev/zeitgeist/python3 branch, perhaps ask ev in #ubuntu-devel about the status of it
[08:00] <tumbleweed> if this is a pure-python package and the same source works with python & python3, you can use .pyinstall files or dh_install to install it for python3
[08:04] <m4n1sh> tumbleweed: yes. it is pure python package
[08:05] <m4n1sh> you mean no seperate python3-zeitgeist package?
[08:05] <m4n1sh> python-zeitgeist will install in python2.7 and python3.3 both?
[08:07] <tumbleweed> one source building multiple binary packages
[08:07] <tumbleweed> we always have python and python3 in separate binary packages
[08:08] <geser> tumbleweed: I didn't look at the package but I assume it's python bindings for a C library (build from the same source)
[08:08] <tumbleweed> I'd assume so too, if it's using autotools
[08:09] <m4n1sh> geser: it isn't a binding over C, it is a pure python package which wraps over dbus interface
[08:09] <m4n1sh> C bindings too wrap over dbus interface
[08:09] <tumbleweed> also, fyi, the source package is zeitgeist not python-zeitgeist
[08:10] <tumbleweed> anyway, it contains a bunch of C
[08:10] <m4n1sh> yeah. python-zeitgeist is a binary package of source package
[08:10] <m4n1sh> source package zeitgeist contains C library package named libzeitgeist-2.0 and python library/module package named python-zeitgeist which is right now installing in python2.7
[08:12] <tumbleweed> it looks entirely plausible that this python works unmodified under python3. have you tested it?
[08:13] <m4n1sh> not very exhaustively, but yes, it works
[08:14] <tumbleweed> then some hacky dh_install ing is probably the easiest
[08:15] <m4n1sh> wont putting this in .install file work?
[08:15] <m4n1sh> usr/lib/python2*/* usr/lib/python3/
[08:16] <tumbleweed> should do
[08:18] <m4n1sh> should it be specifically python3 or python3.3?
[08:19] <tumbleweed> python3
[08:20] <m4n1sh> thanks
[09:00] <Noskcaj10> Is it possible to directly add apt-fast? the debian bug has halted
[17:44] <dkessel> good evening dholbach :)
[17:45] <dholbach> hi dkessel