Re: RFS: openshot
Paul, Thanks for the feedback! I will try and resolve the issues you have pointed out. python-mlt is not available in Debian or Ubuntu, best remove it from the depends. python-mlt2 is now included in the libmlt2 source package, in Debian unstable: http://packages.debian.org/sid/libmlt2 Will you also be packaging openshot-docs? Yes, but I'm trying to focus on the openshot package first. If I knew what I was doing, I suppose I would somehow package them together. =) Your Standards-Version is out of date, please read the upgrading-checklist.txt.gz from debian-policy to find out what you need to change to upgrade it. Not sure what this is, so I'll do some research and try and fix it. Please install the latest version of lintian from Debian sid, build your package and run this command on the resulting .changes file: lintian --info --display-info --display-experimental --pedantic --show-overrides --checksums --color auto foo.changes Will do. Thanks. You are installing the desktop file and icon in the wrong locations, please use /usr/share/applications and /usr/share/pixmaps or the appropriate directory; /usr/share/icons/hicolor/res/apps/. Will do. I have the feeling you are doing something very wrong with the maintainer scripts, can you describe what they are for? These were created by someone else, who was trying to help me package openshot. I will remove them, if they have no purpose. Your orig.tar.gz ships with some binary *.pyc files, it should not do that. I think using ./setup.py sdist would do the right thing here, please use it in future. Will do. The Glade format and library is obsolete, please switch to GtkBuilder. IIRC you can do this by opening the files in glade-3 and saving them as GtkBuilder format. I am in the process of replacing Glade with GtkBuilder at the moment. Should be done soon. Hopefully. There are a lot of images and architecture-independent files, you should probably split them out into a -common or -data package. In fact, the entire source tree is architecture independent. Why are you shipping precompiled .mo files in a source package? The .po files should be present at the very least and probably the .mo file should not be present. The gettext library needs the MO files, which is why I compiled the PO files in the first place. i suppose I could compile them on the fly, and only package the PO files. I'll look into this. If you are using any embedded code copies, please remove them and package them separately. Not that I am aware of. Thanks so much for your suggestions. You are the first person who has offered any real advice to me. Now, if I can just find a Debian sponsor. =) -Jonathan On Fri, Jan 22, 2010 at 1:40 AM, Paul Wise p...@debian.org wrote: On Thu, Jan 21, 2010 at 11:49 AM, Jonathan Thomas jonathan.oo...@gmail.com wrote: I am looking for a sponsor for my package openshot. I reviewed this package recently and concluded that it needs work: http://lists.debian.org/debian-mentors/2010/01/msg00254.html -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: openshot
Dear mentors, I am looking for a sponsor for my package openshot. * Package name: openshot Version : 1.0.0-1 Upstream Author : Jonathan Thomas jonathan.oo...@gmail.com * URL : http://www.openshotvideo.com * License : GPLv3 Section : video It builds these binary packages: openshot - Non Linear Video Editor using Python and MLT The package appears to be lintian clean. The upload would fix these bugs: 564945 My motivation for maintaining this package is: I am the upstream author, and have already packaged openshot for my LaunchPad PPA. I would love to have openshot included in Debian. =) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/o/openshot - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/openshot/openshot_1.0.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Jonathan Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Python Bindings for MLT
I solved this problem also. I needed to change my setup.py to include a mlt folder, not a mlt-python folder. Also, I modified the __init__.py to include the following code: from mlt import * Now when I install the package, python-support puts everything in the /usr/lib/pymodules/ folder, which is in the python path, and then my mlt folder and the customized __init__.py file work great. Now I am able to import the mlt library as expected: import mlt Sorry for so many stupid questions. I tried to explain my solutions so they are documented for the next person with my questions. =) Thanks, -Jonathan On Mon, Dec 28, 2009 at 4:24 PM, Jonathan Thomas jonathan.oo...@gmail.comwrote: I have figured out the answer to my question. Python-support correctly adds my folder and files to the Python path. This changes the way I need to import the python module from import mlt to import mlt-python.mlt However, mlt-python does not appear to be a valid module name for Python. It does not like the - character. Is there a way to tell python-support what the name of the folder should be? For example, Instead of this folder: /usr/lib/pymodules/python2.6/mlt-python/ Use this folder: /usr/lib/pymodules/python2.6/mlt/ Thanks in advance! -Jonathan Thomas On Mon, Dec 28, 2009 at 2:48 PM, Jonathan Thomas jonathan.oo...@gmail.com wrote: Jakub, Thanks for the advice. I have removed the postinst script and the DEB_PYTHON_INSTALL_ARGS_ALL line. I have also contacted the MLT packagers, but I'm not confident they will include the Python bindings in their packages. Here is a dumb question. After installing the DEB file, it moves all of the correct files to /usr/lib/pymodules/python2.6/mlt-python. However, when I fire up python, it is unable to import mlt. For example: *import mlt* Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named ml If I launch the Python interpreter from /usr/lib/pymodules/python2.6/mlt-python, it works just fine. It is acting like my public Python module is not in the sys.path. I assumed because /usr/lib/pymodules/python2.6/ was in the sys.path, that this would work. Am I missing something? Thanks, -Jonathan On Thu, Dec 17, 2009 at 6:38 AM, Jakub Wilk uba...@users.sf.net wrote: Hello, * Jonathan Thomas jonathan.oo...@gmail.com, 2009-12-15, 13:16: I have done my best to package the MLT Python bindings (which were generated using Swig), and I have published to my own PPAhttps://launchpad.net/%7Ejonoomph/+archive/openshot-edge(hosted on LaunchPad). I am fairly certain that my build script needs to be improved. For example, I never could figure out how to copy the MLT Python bindings to the /site-packages/ folder, so I created a postinst file... which can't be the best way. Right, that's not event an acceptable way. Those files don't need to be installed into /site-packages/, python-support should take care to put them in the right place once you remove maintainer scripts and the DEB_PYTHON_INSTALL_ARGS_ALL line from debian/rules. Anyway, these bindings should not have a separate source package. Just ask mlt maintainers (preferably via a bug report) to build binary package with Python bindings out of their source. -- Jakub Wilk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJLKiYwAAoJEC1Os6YBVHX1ve4P/3661p1kp2xbF2j/LtQ0oA1o 4goSpI+rg2Fl+zHi4e4VOexhSXrvw2WaaHEXofzVFvcoC3Osgz/H2iLzm6DkL3PI 5MrlLcAYU/ZP4ahRA20HHiQhvXcZMWgrN+2uLzu4l8tMAexMtNfQ/xPiceKV3kL9 KDHS3X6Rk7jG6vsnPVI7uGztgjprSr6MG3Ks6NoLICgPCk8SUQ1P+okaP99H/Q0f 6+pbDYiK5g5/v4dw/iIXIJHMsaawh6F+zphvEg7TMVJuWJ9zGPORmDNMon0z3+h0 Q4xTD2qemnL3ybleKVvcF40p/po4HGk+IYaaqM4HQ0DudH8gSkKoFp0Hzx12ZQ34 XMxHL8dNAnYPqlvubgxjQqctmAVm660dqExKQDjPMQytpjntyVPAKQGJdEOBCPwY Chj5nn36/dAUH9HTd4f2583nRfcCX5BbPdhFbADPAoen8Fbehl4GBGYSoUsJ7COT sjvXpRKkMxSUhXGXt6k4Gs63YrQ80rZwJPhYM/vtaKzBeLyq/5Acc7n2Ba8CIU1Y h42OQgG5bhyAFUGdiomUd1eweSfUZ04FZSXHfaVwqUuWeeOYZacQiUj111ygdMTS vbZ4EU/MR+xc5p6mJNqyJTBI9TrqV1eHfsgjLXTi9J8e3IFDkEt7Nhdweuoid4Gp hFNHiCz04pdpj/8HWWrS =kneW -END PGP SIGNATURE-
Re: Python Bindings for MLT
Jakub, Thanks for the advice. I have removed the postinst script and the DEB_PYTHON_INSTALL_ARGS_ALL line. I have also contacted the MLT packagers, but I'm not confident they will include the Python bindings in their packages. Here is a dumb question. After installing the DEB file, it moves all of the correct files to /usr/lib/pymodules/python2.6/mlt-python. However, when I fire up python, it is unable to import mlt. For example: *import mlt* Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named ml If I launch the Python interpreter from /usr/lib/pymodules/python2.6/mlt-python, it works just fine. It is acting like my public Python module is not in the sys.path. I assumed because /usr/lib/pymodules/python2.6/ was in the sys.path, that this would work. Am I missing something? Thanks, -Jonathan On Thu, Dec 17, 2009 at 6:38 AM, Jakub Wilk uba...@users.sf.net wrote: Hello, * Jonathan Thomas jonathan.oo...@gmail.com, 2009-12-15, 13:16: I have done my best to package the MLT Python bindings (which were generated using Swig), and I have published to my own PPAhttps://launchpad.net/%7Ejonoomph/+archive/openshot-edge(hosted on LaunchPad). I am fairly certain that my build script needs to be improved. For example, I never could figure out how to copy the MLT Python bindings to the /site-packages/ folder, so I created a postinst file... which can't be the best way. Right, that's not event an acceptable way. Those files don't need to be installed into /site-packages/, python-support should take care to put them in the right place once you remove maintainer scripts and the DEB_PYTHON_INSTALL_ARGS_ALL line from debian/rules. Anyway, these bindings should not have a separate source package. Just ask mlt maintainers (preferably via a bug report) to build binary package with Python bindings out of their source. -- Jakub Wilk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJLKiYwAAoJEC1Os6YBVHX1ve4P/3661p1kp2xbF2j/LtQ0oA1o 4goSpI+rg2Fl+zHi4e4VOexhSXrvw2WaaHEXofzVFvcoC3Osgz/H2iLzm6DkL3PI 5MrlLcAYU/ZP4ahRA20HHiQhvXcZMWgrN+2uLzu4l8tMAexMtNfQ/xPiceKV3kL9 KDHS3X6Rk7jG6vsnPVI7uGztgjprSr6MG3Ks6NoLICgPCk8SUQ1P+okaP99H/Q0f 6+pbDYiK5g5/v4dw/iIXIJHMsaawh6F+zphvEg7TMVJuWJ9zGPORmDNMon0z3+h0 Q4xTD2qemnL3ybleKVvcF40p/po4HGk+IYaaqM4HQ0DudH8gSkKoFp0Hzx12ZQ34 XMxHL8dNAnYPqlvubgxjQqctmAVm660dqExKQDjPMQytpjntyVPAKQGJdEOBCPwY Chj5nn36/dAUH9HTd4f2583nRfcCX5BbPdhFbADPAoen8Fbehl4GBGYSoUsJ7COT sjvXpRKkMxSUhXGXt6k4Gs63YrQ80rZwJPhYM/vtaKzBeLyq/5Acc7n2Ba8CIU1Y h42OQgG5bhyAFUGdiomUd1eweSfUZ04FZSXHfaVwqUuWeeOYZacQiUj111ygdMTS vbZ4EU/MR+xc5p6mJNqyJTBI9TrqV1eHfsgjLXTi9J8e3IFDkEt7Nhdweuoid4Gp hFNHiCz04pdpj/8HWWrS =kneW -END PGP SIGNATURE-
Re: Python Bindings for MLT
I have figured out the answer to my question. Python-support correctly adds my folder and files to the Python path. This changes the way I need to import the python module from import mlt to import mlt-python.mlt However, mlt-python does not appear to be a valid module name for Python. It does not like the - character. Is there a way to tell python-support what the name of the folder should be? For example, Instead of this folder: /usr/lib/pymodules/python2.6/mlt-python/ Use this folder: /usr/lib/pymodules/python2.6/mlt/ Thanks in advance! -Jonathan Thomas On Mon, Dec 28, 2009 at 2:48 PM, Jonathan Thomas jonathan.oo...@gmail.comwrote: Jakub, Thanks for the advice. I have removed the postinst script and the DEB_PYTHON_INSTALL_ARGS_ALL line. I have also contacted the MLT packagers, but I'm not confident they will include the Python bindings in their packages. Here is a dumb question. After installing the DEB file, it moves all of the correct files to /usr/lib/pymodules/python2.6/mlt-python. However, when I fire up python, it is unable to import mlt. For example: *import mlt* Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named ml If I launch the Python interpreter from /usr/lib/pymodules/python2.6/mlt-python, it works just fine. It is acting like my public Python module is not in the sys.path. I assumed because /usr/lib/pymodules/python2.6/ was in the sys.path, that this would work. Am I missing something? Thanks, -Jonathan On Thu, Dec 17, 2009 at 6:38 AM, Jakub Wilk uba...@users.sf.net wrote: Hello, * Jonathan Thomas jonathan.oo...@gmail.com, 2009-12-15, 13:16: I have done my best to package the MLT Python bindings (which were generated using Swig), and I have published to my own PPAhttps://launchpad.net/%7Ejonoomph/+archive/openshot-edge(hosted on LaunchPad). I am fairly certain that my build script needs to be improved. For example, I never could figure out how to copy the MLT Python bindings to the /site-packages/ folder, so I created a postinst file... which can't be the best way. Right, that's not event an acceptable way. Those files don't need to be installed into /site-packages/, python-support should take care to put them in the right place once you remove maintainer scripts and the DEB_PYTHON_INSTALL_ARGS_ALL line from debian/rules. Anyway, these bindings should not have a separate source package. Just ask mlt maintainers (preferably via a bug report) to build binary package with Python bindings out of their source. -- Jakub Wilk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJLKiYwAAoJEC1Os6YBVHX1ve4P/3661p1kp2xbF2j/LtQ0oA1o 4goSpI+rg2Fl+zHi4e4VOexhSXrvw2WaaHEXofzVFvcoC3Osgz/H2iLzm6DkL3PI 5MrlLcAYU/ZP4ahRA20HHiQhvXcZMWgrN+2uLzu4l8tMAexMtNfQ/xPiceKV3kL9 KDHS3X6Rk7jG6vsnPVI7uGztgjprSr6MG3Ks6NoLICgPCk8SUQ1P+okaP99H/Q0f 6+pbDYiK5g5/v4dw/iIXIJHMsaawh6F+zphvEg7TMVJuWJ9zGPORmDNMon0z3+h0 Q4xTD2qemnL3ybleKVvcF40p/po4HGk+IYaaqM4HQ0DudH8gSkKoFp0Hzx12ZQ34 XMxHL8dNAnYPqlvubgxjQqctmAVm660dqExKQDjPMQytpjntyVPAKQGJdEOBCPwY Chj5nn36/dAUH9HTd4f2583nRfcCX5BbPdhFbADPAoen8Fbehl4GBGYSoUsJ7COT sjvXpRKkMxSUhXGXt6k4Gs63YrQ80rZwJPhYM/vtaKzBeLyq/5Acc7n2Ba8CIU1Y h42OQgG5bhyAFUGdiomUd1eweSfUZ04FZSXHfaVwqUuWeeOYZacQiUj111ygdMTS vbZ4EU/MR+xc5p6mJNqyJTBI9TrqV1eHfsgjLXTi9J8e3IFDkEt7Nhdweuoid4Gp hFNHiCz04pdpj/8HWWrS =kneW -END PGP SIGNATURE-
