2017/02/10 update: I’ve discovered a better solution (using an updated version of setuptools) and have updated the post below.
To add additional data files to python installation files — such as service files in /etc/init.d for RH-based distros — all the docs tell you to simply add a data_files line to your setup.py file, like:
If you do this, however, might get this lovely error when attempting to create the RPM:
$ python setup.py bdist_rpm < snip > running install_data error: can't copy 'init.d/service_name': doesn't exist or not a regular file error: Bad exit status from /var/tmp/rpm-tmp.DRsp99 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.DRsp99 (%install) error: command 'rpmbuild' failed with exit status 1
This will perplex you for ages considering the file clearly exists in the path relative to setup.py, per the instructions:
$ ls -l setup.py -rw-rw-r--. 1 cpeel cpeel 1233 Mar 9 14:37 setup.py $ ls -l init.d/service_name -rw-rw-r--. 1 cpeel cpeel 1242 Mar 9 14:40 init.d/service_name
The problem is that there are (at least) two different flavors of setup() functions and they are not completely alike. Both distutils and setuptools provide a setup() function and both packages have changed over time. See this StackOverflow example discussing the python setup tools landscape as of January 2017.
I don’t know what version of distutils I was using when I wrote this blog post, but it was probably some version with python 2.6. The version of distutils bundled with python 2.7.12, and presumably later, does not generate the RPM build error.
I also get the above RPM build error when using setup() from older versions of setuptools (at least 20.1.1). Updating to the most recent version of setuptools (34.1.1 as of February 2017) resolves the issue.
It appears that the general internet consensus, and official Python Packaging User Guide, is to use setuptools which can be updated independently of the python version you are using, so just be sure you’re using the latest version.
If you’re stuck on an older version of setuptools or distutils, the missing piece that took me hours to discover, is that even with data_files in setup.py, you need a MANIFEST.in file that tells them to include the files in the package:
$ cat MANIFEST.in recursive-include init.d *
One thought on “Secret sauce to including data_files in python bdist_rpm”
Thank you so much. I was already claiming myself dump, not finding the difference between two files where one copys and the other didn’t. It was just on bdist_rpm, while sdist or bdist all worked fine. Even if it was exact the same file testwise, the strace drove me crazy. Misleading aF.
Your post made my day!
LikeLiked by 1 person