[opensuse-packaging] Packaging python noarch project with SLES_11
I have a problem packaging the new fail2ban version vor SLES 11: All python modules are installed to /usr/lib64/python2.6/site-packages instead of /usr/lib/python2.6/site-packages. How can I force python to install to the correct location? You can check the build at https://build.opensuse.org/package/show/home:weberho:branches:security/fail2... Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On May 8, 2015, at 7:49 AM, Johannes Weberhofer <jweberhofer@weberhofer.at> wrote:
I have a problem packaging the new fail2ban version vor SLES 11: All python modules are installed to /usr/lib64/python2.6/site-packages instead of /usr/lib/python2.6/site-packages. How can I force python to install to the correct location?
You can check the build at https://build.opensuse.org/package/show/home:weberho:branches:security/fail2...
This is correct behavior for SLES 11 (suse_version=1110), which still used binary packages (not noarch) and /usr/lib64/python2.6/site-packages. Your spec file already has the correct noarch check, so everything is fine. There’s this documentation: https://en.opensuse.org/openSUSE:Packaging_Python#Compatibility_with_older_d... although I don’t think it’s 100% correct, since the sitelib/sitearch macros are defined exactly the same (in /usr/lib/rpm/macros), identical to the Wiki, on both SLES 11 SP3 and openSUSE 13.2, so there’s no need to put them in your spec file. (The difference is that on SLES 11 both sitelib and sitearch output the lib64 dir, whereas on newer opensuse they output lib and lib64 resp.)
participants (2)
-
Andrew Daugherity
-
Johannes Weberhofer