RPM .spec template renderer
Go to file
Javier Pena 10dba17495 Fix _pymod2pkg_translate when skip_pyversion is None
[1] ensured proper order for py_vers when using pymod2pkg, however
it did not consider the chance that skip_pyversion is None. In this
case, it failed with:

TypeError: argument of type 'NoneType' is not iterable

This patch ensures that it works even when skip_pyversion is None.

[1] - https://review.opendev.org/662719

Change-Id: Iac7dda35b44edf4a7af31129d9055280aa37df01
2019-06-06 11:50:07 +02:00
doc Follow opendev rebranding 2019-05-23 01:44:16 +02:00
renderspec Fix _pymod2pkg_translate when skip_pyversion is None 2019-06-06 11:50:07 +02:00
.gitignore Switch to stestr 2018-11-23 01:42:49 +01:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:17 +00:00
.stestr.conf Switch to stestr 2018-11-23 01:42:49 +01:00
.zuul.yaml Switch to stestr 2018-11-23 01:42:49 +01:00
LICENSE Initial version of renderspec 2015-10-05 08:40:44 +02:00
README.rst Follow opendev rebranding 2019-05-23 01:44:16 +02:00
requirements.txt Switch to stestr 2018-11-23 01:42:49 +01:00
setup.cfg Update home-page 2019-01-12 09:53:20 +00:00
setup.py Updated from global requirements 2017-03-02 11:55:41 +00:00
test-requirements.txt Switch to openstackdocstheme 2019-05-21 09:19:42 +02:00
tests.py Add option to skip certain python version 2017-09-29 22:33:17 +02:00
tox.ini Switch to TOX_CONSTRAINTS_FILE 2019-05-23 21:41:06 +02:00

Team and repository tags

image

renderspec

renderspec is a tool to convert a .spec.j2 Jinja2 template to a rpm .spec file which is usable for different distributions and follow their policies and processes.

Documentation for renderspec can be found at

https://docs.openstack.org/renderspec/latest/

For more information about the OpenStack rpm packaging initiative, please follow the link to the wiki page:

https://wiki.openstack.org/wiki/Rpm-packaging

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:

https://bugs.launchpad.net/renderspec

Developers wishing to work on renderspec should always base their work on the latest code, available from the master GIT repository at:

https://opendev.org/openstack/renderspec

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

or join the IRC channel on

http://webchat.freenode.net/?channels=openstack-rpm-packaging