[Distutils] bdist_rpm fails - how to change what's included in hard linking?

Andy Theuninck gohanman at gmail.com
Sat Aug 16 04:42:52 CEST 2008


I'm trying to create an rpm package using bdist_rpm and it's failing.
I can see exactly why it's failing, but I can't coax google into
telling me how to fix it. First I see python create a tarball to put
in the rpm's SOURCES:

creating python-sybase-0.39
making hard links in python-sybase-0.39...
hard linking Sybase.py -> python-sybase-0.39
hard linking blk.c -> python-sybase-0.39
hard linking cmd.c -> python-sybase-0.39
hard linking conn.c -> python-sybase-0.39
hard linking ctx.c -> python-sybase-0.39
hard linking databuf.c -> python-sybase-0.39
hard linking datafmt.c -> python-sybase-0.39
hard linking date.c -> python-sybase-0.39
hard linking datetime.c -> python-sybase-0.39
hard linking iodesc.c -> python-sybase-0.39
hard linking locale.c -> python-sybase-0.39
hard linking money.c -> python-sybase-0.39
hard linking msgs.c -> python-sybase-0.39
hard linking numeric.c -> python-sybase-0.39
hard linking setup.py -> python-sybase-0.39
hard linking sybasect.c -> python-sybase-0.39
tar -cf dist/python-sybase-0.39.tar python-sybase-0.39
gzip -f9 dist/python-sybase-0.39.tar
removing 'python-sybase-0.39' (and everything under it)
copying dist/python-sybase-0.39.tar.gz -> build/bdist.linux-i686/rpm/SOURCES

One of the files required by setup.py (ez_setup.py) isn't getting hard
linked. Thus, when rpmbuild unpacks the above tarball into the rpm
BUILD directory and runs setup.py, it crashes with an ImportError.

How do I adjust what files get hard linked into that tarball?


More information about the Distutils-SIG mailing list