f74f393218
This is a mechanically generated patch to ensure unit testing is in place for all of the Tested Runtimes for Train. See the Train python3-updates goal document for details: https://governance.openstack.org/tc/goals/train/python3-updates.html Change-Id: Iec17f01beed324e1481391204533eeafaf6253e3 Story: #2005924 Task: #34235 |
||
|---|---|---|
| doc | ||
| renderspec | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests.py | ||
| tox.ini | ||
Team and repository tags
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
For more information about the OpenStack rpm packaging initiative, please follow the link to the wiki page:
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:
Developers wishing to work on renderspec should always base their work on the latest code, available from the master GIT repository at:
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