XS-Python-Version: current fix (was: Re: RFS: deejayd (updated package))
Hi, The current version of my package does not launch in unstable following the switch of the current python version. I think it is because of the current keyword in the XS-Python-Version tag. A rebuild fixes the problem. Is this appropriate fix? -XS-Python-Version: current, = 2.4 +XS-Python-Version: = 2.4, 3.0 Or should I remove the line to get the defaults? Or should I drop the 3.0 which is implied? How do I fix this? Upload new fixed version and seek a sponsor? Request a rebuild in some way (is that possible for arch: all packages?)? Thanks in advance for your advices. Alex On Tue, Apr 6, 2010 at 19:27, Alexandre Rossi alexandre.ro...@gmail.com wrote: Dear mentors, I am looking for a sponsor for the new version 0.10.0-1 of my package deejayd. It builds these binary packages: deejayd - Network controllable media player daemon deejayd-client - Client library and command line tool to access the deejayd server deejayd-gstreamer - Deejayd GStreamer backend deejayd-webui - Web interface for deejayd deejayd-webui-extension - Deejayd web user interface Iceweasel extension deejayd-xine - Deejayd XINE backend The package appears to be lintian clean. The upload would fix these bugs: 575118 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/deejayd - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/deejayd/deejayd_0.10.0-1.dsc I would be glad if someone uploaded this package for me and to address any issues you would find with the package. Kind regards Alexandre Rossi -- 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/aanlktilphm0nnjh-7tgf10v4dpcq0wfdsxtlu-r0t...@mail.gmail.com
Re: XS-Python-Version: current fix (was: Re: RFS: deejayd (updated package))
* Alexandre Rossi alexandre.ro...@gmail.com, 2010-06-23, 10:53: The current version of my package does not launch in unstable following the switch of the current python version. I think it is because of the current keyword in the XS-Python-Version tag. A rebuild fixes the problem. Is this appropriate fix? -XS-Python-Version: current, = 2.4 +XS-Python-Version: = 2.4, 3.0 Please don't add 3.0. While we didn't agree yet how to specify 3.0 version, there's consensus that is should be explicit, i.e. = 2.4 will continue to contain only 2.* series. While current is frowned upon[0], this is not what caused your package breakage. The culprit it that scripts have #!/usr/bin/pythonX.Y shebangs - if they were unversioned, the package would continue to work with new Python. How do I fix this? Upload new fixed version and seek a sponsor? Yes. Request a rebuild in some way (is that possible for arch: all packages?)? No, it's not possible. [0] Either your Python modules are intended for general use - then they should be bytecompiled with all supported version; or they are not - then they should be put into a private directory. -- Jakub Wilk signature.asc Description: Digital signature
Re: XS-Python-Version: current fix (was: Re: RFS: deejayd (updated package))
Alexandre Rossi alexandre.ro...@gmail.com wrote: Hi, The current version of my package does not launch in unstable following the switch of the current python version. I think it is because of the current keyword in the XS-Python-Version tag. A rebuild fixes the problem. Is this appropriate fix? -XS-Python-Version: current, = 2.4 +XS-Python-Version: = 2.4, 3.0 Or should I remove the line to get the defaults? Or should I drop the 3.0 which is implied? How do I fix this? Upload new fixed version and seek a sponsor? Request a rebuild in some way (is that possible for arch: all packages?)? Thanks in advance for your advices. It will take a new upload to change this. The 3.0 is not needed. Scott K -- 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/cafa233a-055d-4ac2-9674-e43c08197...@email.android.com
Re: XS-Python-Version: current fix (was: Re: RFS: deejayd (updated package))
While current is frowned upon[0], this is not what caused your package breakage. The culprit it that scripts have #!/usr/bin/pythonX.Y shebangs - if they were unversioned, the package would continue to work with new Python. Those are changed by python distutils, that's why a rebuild fixes the problem. My debian/rules is too complicated because I do not need to build python modules for all python versions. The following construct (from pycentral howto) is useless in my case : PYVERS=$(shell pyversions -vr) install: build $(PYVERS:%=install-python%) install-python%: python$* setup.py install --root $(CURDIR)/debian/python-foo Because setup.py is used with python$*, it replaces the shebang line with python$*. Anyway when squeeze is frozen, I won't need a lenny backport and I'll switch to a much simpler debian/rules. I'll fix the breakage in the next upload. Thanks a lot for your input. Alex -- 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/aanlktik73ubba6sxrlinfgzazh27epokiihzpb6is...@mail.gmail.com
