Re: Please add me to the team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Jakub! On 12/08/12 15:10, Jakub Wilk wrote: > * Andreas Tille , 2012-08-10, 13:45: >> I personally don't mind very much about the team - the main point is that >> there is any team behind a package that really cares. As far as I >> can tell you are welcome on any Debian mailing list to ask for advise about >> packaging issues if it is on topic and having the code for >> packaging in the according repository is not mandatory. > > Of course! :) Everyone is welcome to ask here for advice or for a review of > his package, even when they are not members of any Python packaging > team. > > From a quick look at librcsb-core-wrapper, it doesn't seem to fit DPMT. As > far as I understand it, it's a library package that just happens to > have Python bindings. Hmm, I thought libraries with bindings were modules just as well as - I don't know - 'native' modules? For the Perl team, this makes no difference at all (or at least so far no one there told me). Perhaps this could be made clearer on DPMT [1] as well, because to me it does not read like "it doesn't seem to fit the DPMT". > > That is not meant to say that Laszlo is not welcome to join the team; it's > just I don't see a reason to do it right now. (This is my own > opinion; opinions of other team admins may vary.) Ok, yes, I see and I agree with you fully: there is no reason for me to join the team right now. But I would like to, indeed, seek advice with librcsb-core-wrapper, to be kept at the Deb Med team. Best regards, Laszlo > [1] http://wiki.debian.org/Teams/PythonModulesTeam/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQKLrVAAoJEJvS1kCaDFL6zJkP/27F5lBZDcA6xzOdm7A7Axx3 i0Ggf+PQj47HahOM/QU44YltPqm4pSMk5H2UM1abBQWUXHGE0WGeRageYYKPmesV 2nR6TJHrw0MxIEZxS5VEstiUdL9zNQYyCh+iAgOwlS0GGRQEKamgfLJjk9gvEPwY vN3/VJrScEs4uU+OjXhI4nvLCVy4qb1HxfdzYWufaKE8pbNThHYpYi77ywsjmTh2 UGFcHdgjE4ffO9dVXEnUgwyuw3relDoqM+mNZqrhprxeVChKP57HdQYeHp6ZdIh9 3FWsp2RpR9dow79JSwux6yZqItRmEOAqn7kt472WbzNMebOl0X65+he66UcwsFJW +c4L2HyCipWLZ/O7OtByhWdAoh5tkhQZa8UbTznyE5i3IKa+SVeQB3xvUyTy+u+t 3Na3QDFueRF4LNs6Abzx+UBRxzXdMD2AiPPU4844HPIdUREXzO75eedKUuSj3eV8 KzA/AleGZGAA6E2ZO3DgSBrYlr0N7jceVmaJQaEcDhpeGHv/L43BFWttginNdxIE Ldk46kyqpCa7FBOpShr93GbvIbSG//L++7WBRBsuslQ9ARaapJ0LM/6Nw05jv9um AMnqGarV2uhw4zjAnjKhrpLaQzMtfoqLJUU0yBGxSfDHkOoZ1yjHvSSeSHzi7Uvu 5UK24pknUuIXv8pkg4fJ =l8KX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5028bad5.30...@rostlab.org
Re: Please add me to the team
* Laszlo Kajan , 2012-08-13, 10:29: From a quick look at librcsb-core-wrapper, it doesn't seem to fit DPMT. As far as I understand it, it's a library package that just happens to have Python bindings. Hmm, I thought libraries with bindings were modules just as well as - I don't know - 'native' modules? For the Perl team, this makes no difference at all (or at least so far no one there told me). The are called “extension modules” (or simply: “extensions”) in Python world. And yes, we package them too. If libfoo and python-foo are separate packages, then DPMT would be the correct team to (co-)maintain python-foo. But if libfoo and python-foo are built from the same source package, then it's not really our business anymore. (Is my point clear now?) But I would like to, indeed, seek advice with librcsb-core-wrapper, to be kept at the Deb Med team. debian/patches/pythonwrapper and debian/patches/objectfiles worry me a bit. They both hardcode Python versions. This should be normally avoided. (Worse, the latter harcodes 2.5, which we've removed over a year ago.) The package currently FTBFS: make[2]: Entering directory `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000/common' libtool --mode=compile g++ -O -fPIC -ansi -Werror -Wall -Wno-deprecated -DHAVE_STRCASECMP -DINCL_TEMPLATE_SRC -DHAVE_PLACEMENT_NEW -I./include -I../include -c src/RcsbPlatform.C -o ./obj/RcsbPlatform.o make[2]: libtool: Command not found make[2]: *** [RcsbPlatform.o] Error 127 make[2]: Leaving directory `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000/common' make[1]: *** [lib/librcsb-core-wrapper.la] Error 1 make[1]: Leaving directory `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 After adding libtool, bison and flex to Build-Depends, it still FTBFS: cp: cannot stat `./wrapper/lib/CorePyWrap.so': No such file or directory make[1]: *** [install] Error 1 make[1]: Leaving directory `/build/librcsb-core-wrapper-moPRXb/librcsb-core-wrapper-1.000' dh_auto_install: make -j1 install DESTDIR=/build/librcsb-core-wrapper-moPRXb/librcsb-core-wrapper-1.000/debian/tmp AM_UPDATE_INFO_DIR=no returned exit code 2 make: *** [binary] Error 29 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813164114.ga4...@jwilk.net
Re: Please add me to the team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Jakub! On 13/08/12 18:41, Jakub Wilk wrote: > * Laszlo Kajan , 2012-08-13, 10:29: >>> From a quick look at librcsb-core-wrapper, it doesn't seem to fit DPMT. As >>> far as I understand it, it's a library package that just happens >>> to have Python bindings. >> Hmm, I thought libraries with bindings were modules just as well as - I >> don't know - 'native' modules? For the Perl team, this makes no >> difference at all (or at least so far no one there told me). > > The are called “extension modules” (or simply: “extensions”) in Python world. > And yes, we package them too. > > If libfoo and python-foo are separate packages, then DPMT would be the > correct team to (co-)maintain python-foo. > > But if libfoo and python-foo are built from the same source package, then > it's not really our business anymore. > > (Is my point clear now?) Yes, thanks a lot, clear now. > >> But I would like to, indeed, seek advice with librcsb-core-wrapper, to be >> kept at the Deb Med team. > > debian/patches/pythonwrapper and debian/patches/objectfiles worry me a bit. > They both hardcode Python versions. This should be normally avoided. > (Worse, the latter harcodes 2.5, which we've removed over a year ago.) > > The package currently FTBFS: > > make[2]: Entering directory > `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000/common' > libtool --mode=compile g++ -O -fPIC -ansi -Werror -Wall -Wno-deprecated > -DHAVE_STRCASECMP -DINCL_TEMPLATE_SRC -DHAVE_PLACEMENT_NEW > -I./include -I../include -c src/RcsbPlatform.C -o ./obj/RcsbPlatform.o > make[2]: libtool: Command not found > make[2]: *** [RcsbPlatform.o] Error 127 > make[2]: Leaving directory > `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000/common' > make[1]: *** [lib/librcsb-core-wrapper.la] Error 1 > make[1]: Leaving directory > `/build/librcsb-core-wrapper-CQ0jkK/librcsb-core-wrapper-1.000' > dh_auto_build: make -j1 returned exit code 2 > make: *** [build] Error 2 > > After adding libtool, bison and flex to Build-Depends, it still FTBFS: > > cp: cannot stat `./wrapper/lib/CorePyWrap.so': No such file or directory > make[1]: *** [install] Error 1 > make[1]: Leaving directory > `/build/librcsb-core-wrapper-moPRXb/librcsb-core-wrapper-1.000' > dh_auto_install: make -j1 install > DESTDIR=/build/librcsb-core-wrapper-moPRXb/librcsb-core-wrapper-1.000/debian/tmp > AM_UPDATE_INFO_DIR=no > returned exit code 2 > make: *** [binary] Error 29 > Ah thanks a lot for these! I am very much working on it now... that was a very early attempt. By now it builds much better (for the usual set of python versions)! Let me polish this a bit more, and then I am going to ask you to have a look, OK? - so that you do not waste your time on half-baked in-progress versions I happen to commit. Best regards, Laszlo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQKTIRAAoJEJvS1kCaDFL6JUwP/iSTlF0FpnB+FXEU0FKLbJUx qn3iR0Azs5wG53AlgXcEtlkqogsHNu5p+FyBnr17j8dLkUmrxLLOwULocLxoLE/S anLYzryL1x6W97pfNPTxnxZ5NnbcAnPglnZzgzia8cvMdhPUBIaEzwcCjJ7VDN2m 0f+fspjRJyW4KYkYQ20yP9qSs7EcAukiEJGLQzUuJOhOk3XUZGjOt84lH2rP3pqU Ejjs+9Jy4albu4yV/ZPGWKNZtZK1RZ9NpY3toEN7v6h9mPQE8DSmH/lCclGrJpRE WPrFxOYZqVKmvgthma9qbpa+9emkRPXuXJ/tUXw4+92kX61Un08EP5AbkH8EDnU+ 7aOKnNQBegYtxNOe7yfL4o4Z8NveVXf2tVJ5ItK6OeYPTNrhgEkNz4vJbEgqRu9Q quGIZmimc4GsjBO1f9rhAIzh6A+a9+nqApU7CWuhg+AHmuw+yS5oEcNZyuv3txfa WRkACo5efkDiydiZL4vRDnlnerDbe7Z67v0pbtslAy9LpvFHAvoak9/h/je6TH19 uIxA3BfqUHI2iwX4mXmwZNTepr/3Gii0D9ftGiUAtYk+O4AFsz4CPde8D+AkeSy7 O066E3nvgmdlosOM/Af/phflTV5CXgaXjKPa53wUHlWtzh+NhuaZHGrnc32Tsgs2 INesxT+PAEP3Yy5fwr6S =cXk/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50293212.8000...@rostlab.org
Re: Please add me to the team
* Laszlo Kajan , 2012-08-13, 18:57: Let me polish this a bit more, and then I am going to ask you to have a look, OK? Sure. :) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120813170503.ga...@jwilk.net
