[Fedora-packaging] Issue packaging python lib into RPM due to conflicting __init__.py

Braddock braddock at braddock.com
Sun Jul 7 16:20:47 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,
I'm attempting to make an RPM of the Python package backports.lzma for
a One Laptop Per Child project using bdist_rpm.

tar xzf backports.lzma-0.0.2.tar.gz
cd backports.lzma-0.0.2
python setup.py bdist_rpm

My problem is that more than one python library wants to live under
the "backports" directory, resulting in a backports/__init__.py file
conflict on SOME platforms as each RPM attempts to create the
backports/__init__.py file in its parent directory.

For example, backports.lzma RPM conflicts with
python-backports-ssl_match_hostname

file /usr/lib/python2.7/site-packages/backports/__init__.py from
install of backports.lzma-0.0.2-1.armv7hl conflicts with file from
package python-backports-ssl_match_hostname-3.2-0.3.a3.fc18.noarch

I am uncertain how to resolve this.  Is there a way for an RPM to only
create the backports/__init__.py file if it does not already exist?
There are a number of packages which would want to live under the
backports/ module.

Any advice appreciated.

Thanks,
Braddock Gaskill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJR2ZVfAAoJEHWLR/DQzlZuh/wH/R8Mj/+O4uMpNhC205TPWSx7
Ure0MAten13uALy7IVfwPS/IdtfWQhj5vdgXkv/BZLjHk26DerIZP2Wwyo/IKMw9
ZEYmouf10CF9uaDBNXmWEgXCrmgknMDqLdHYZvAuQmwrai95BUy4zTrj9PoFzKuT
h6Hx56UfpLFDeQsGaU5o2k9sR/aW356LQoQ26jNYOfUQuaWx3eJ4n64nFtfH5oPu
PDVTrWtWoCilOnLR/kerHcBWZoNxuHtOANZafyF7se0hQP4aQs1DF6Bqv6mChCOM
w/zM5wEjBb+nwUJE+/cEMJTuxMQv67rIjo+yYn8cSg06NpOUtD1Q4Azz2bmSx80=
=Gpvi
-----END PGP SIGNATURE-----


More information about the packaging mailing list