[Debian-pan-maintainers] Packaging pytango 9.2.0

[Bodó-Merle Sándor]

OK - thx. I wanted to address the lintian stuff after your feedback. I'll try to take care of them today.

On the other hand - do you know a way to configure ccache which works with pybuild (apparently it disregards the PATH)?

Regarding the c++ warnings, most of them seem to come from the upstream tango includes (specifically zmq).
I want to check the tango sources - but having it still in SVN is a major drawback - at least for my motivation ...
And i guess i'll have to subscribe to the debian-python :) (this is my first python package i have to deal with)

Sandor

________________________________________
From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca at synchrotron-soleil.fr>
Sent: Tuesday, August 30, 2016 8:58 AM
To: Bodó-Merle Sándor; debian-pan-maintainers at lists.alioth.debian.org
Subject: RE:Packaging pytango 9.2.0

during the build I have this

reading sources... [100%] utilities

/<<PKGBUILDDIR>>/doc/client_api/green.rst:18: WARNING: autodoc: failed to import function u'DeviceProxy' from module u'tango.futures'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in import_object
    __import__(self.modname)
  File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/tango/futures.py", line 35, in <module>
    check_requirements()
  File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/tango/futures.py", line 30, in check_requirements
    raise ImportError("No module named concurrent. You need to " \
ImportError: No module named concurrent. You need to install the futures backport module to have access to PyTango futures green mode
/<<PKGBUILDDIR>>/doc/client_api/green.rst:20: WARNING: autodoc: failed to import function u'DeviceProxy' from module u'tango.gevent'; the following exception was raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in import_object
    __import__(self.modname)
  File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/tango/gevent.py", line 43, in <module>
    check_requirements()
  File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/tango/gevent.py", line 30, in check_requirements
    raise ImportError("No module named gevent. You need to install " \
ImportError: No module named gevent. You need to install gevent module to have access to PyTango gevent green mode. Consider using the futures green mode instead
looking for now-outdated files... none found


so it seems that the documentaion need python-gevent in orde to build fluently :))


It seems that there is plenty of waning in the c++ code, can you report this to the upstream ?
unused variables, sign unsigned comparison, deprecated, etc...



in the rules files you have

#!/usr/bin/make -f

> export PYBUILD_NAME=tango
> export PYBUILD_INSTALL_ARGS_python2=--install-html=$(CURDIR)/debian/python-tango-doc/usr/share/doc/python-tango-doc/html

> %:
>       dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
>
>override_dh_auto_install: $(PYTHON3:%=install-python%)

remove the  $(PYTHON3:%=install-python%)

>       dh_auto_install -O--buildsystem=pybuild
>       dh_numpy
>       dh_numpy3

>override_dh_installdocs:
>       dh_installdocs
>ifneq (,$(filter python-tango-doc, $(shell dh_listpackages)))
>       # add the - for backport where dh_sphinxdoc is not available
>       -dh_sphinxdoc -ppython-tango-doc
>endif

you can remove all this section, it was used only for wheezy

>override_dh_auto_clean:
>       dh_auto_clean
>       rm -rf build
>       rm -rf *.egg-info

ok



Cheers

Fred
________________________________

A jelen email útján megküldött vélemény vagy információ kizárólag a küldő személyéhez kapcsolódik és nem feltétlenül jeleníti meg az ELI-HU Nonprofit Kft. álláspontját is. Társaságunk nem vállal felelősséget az email tartalmáért, ide értve különösen, de nem kizárólagosan kötelezettségvállalást jogi kötő erővel bíró szerződések létrehozásáért, módosításáért vagy megszűntetéséért, valamint az átadott információ alapján indult eljárásokért mindaddig, amíg az adott információt utólag és írásban a megfelelően meghatalmazott vagy az ELI-HU Nonprofit Kft. képviseleti jogával felruházott személy meg nem erősíti. Az email bizalmas vagy jogilag védett információt tartalmazhat, amelyet kizárólag a címzett személy vagy szervezet, illetve az általuk felhatalmazottak használhatnak fel. Amennyiben Ön nem az üzenet címzettje, kérjük, értesítse erről az üzenet küldőjét és törölje az üzenetet rendszeréből. A jelen email tartalmának nem a címzett általi bármilyen formában történő illetéktelen közzététele, terjesztése, másolása, illetve felhasználása vagy alkalmazása szigorúan tilos és jogszabályba ütközhet.


Please note that any information or opinions presented in this email are solely those of the sender and do not necessarily represent those of ELI-HU Nonprofit Ltd. Our Company accepts no liability or responsibility for the content of this email, especially, but not limited to commitment for establishing, modifying or terminating legally binding contracts, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing by a person duly authorized or endowed with the right of representation of ELI-HU Nonprofit Ltd. This email may contain confidential or legally protected information, and is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you are not the intended recipient of this email, please inform the sender immediately and delete it from your system. Any unauthorized disclosure, dissemination, copying or use of or reliance upon the content of this email by anyone other than the intended recipient is strictly prohibited and may be unlawful.