rpmbuild 在 %install 部分失败

Question

这是我的规范文件

#
# spec file for package python-nassl
#
# Copyright (c) 2017 root.
#

Name:           python-nassl
Version:        0.16.3
Release:        0
Url:            https://github.com/nabla-c0d3/nassl
Summary:        Experimental OpenSSL wrapper for Python 2.7 / 3.3+ and SSLyze.
License:        UNKNOWN (FIXME:No SPDX)
Group:          Development/Languages/Python
Source:         https://files.pythonhosted.org/packages/source/n/nassl/nassl-%{version}.zip
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  python-devel

%description
nassl
=====


[![Build Status](https://travis-ci.org/nabla-c0d3/nassl.svg?branch=master)](https://travis-ci.org/nabla-c0d3/nassl)
[![PyPI version](https://badge.fury.io/py/nassl.svg)](https://badge.fury.io/py/nassl)

Experimental OpenSSL wrapper for Python 2.7 / 3.3+ and SSLyze. **Do NOT use for anything serious**. This code has not
been properly tested/reviewed and is absolutely not production ready.

Quick Start
-----------

Nassl can be installed directly via pip:

    pip install nassl

On OS X and Linux, it is also easy to directly clone the repository, build the `_nassl` C extension and then run the
sample client:

    git clone https://github.com/nabla-c0d3/nassl.git
    cd nassl
    pip install -r requirements.txt --target ./lib
    python setup.py build_ext -i
    python sample_client.py


Building the C extension
------------------------

Nassl relies on a C extension to call into OpenSSL; the extension can be directly built using the pre-compiled OpenSSL
binaries available in ./bin, by running the following command:

    python setup.py build_ext -i

On Windows, a "Platform Wheel" can be built using:

    python setup.py bdist_wheel

If you do not want to use the pre-compiled binaries, compiling the C extension requires successively building:

* [Zlib 1.2.11](http://zlib.net/zlib-1.2.11.tar.gz)
* A [special fork of OpenSSL 1.0.2](https://github.com/PeterMosmans/openssl) which enables additional features (such as
the ChaCha20 cipher suites), or the official OpenSSL 1.0.2e.
* The `_nassl` C extension itself

The whole build process is all taken care of by the _build\_from\_scratch.py_ script:

    git clone https://github.com/nabla-c0d3/nassl.git
    cd nassl
    pip install -r requirements.txt --target ./lib
    wget http://zlib.net/zlib-1.2.11.tar.gz
    tar xvfz  zlib-1.2.11.tar.gz
    git clone https://github.com/PeterMosmans/openssl
    python build_from_scratch.py

For Windows builds, Visual Studio is expected to be installed at the default location.

The build script was tested on the following platforms: Windows 7 (32 and 64 bits), Debian 7 (32 and 64 bits),
macOS Sierra. It will build the C extension for the interpreter and platform that was used to run the script
(ie. no cross-compiling).


Project structure
-----------------

### nassl/

Classes implemented in Python are part of the `nassl` namespace; they are designed to provide a simpler, higher-level
interface to perform SSL connections.


### nassl/_nassl/

Classes implemented in C are part of the `nassl._nassl` namespace; they try to stay as close as possible to OpenSSL's
API. In most cases, Python methods of such objects directly match the OpenSSL function with same name. For example the
`_nassl.SSL.read()` Python method matches OpenSSL's `SSL_read()` function.

These classes should be considered internal.


Why another SSL library?
------------------------

I'm the author of [SSLyze](https://github.com/nabla-c0d3/sslyze), an SSL scanner written in Python. Scanning SSL servers
requires access to low-level SSL functions within the OpenSSL API, for example to test for things like insecure
renegotiation or session resumption.

None of the existing OpenSSL wrappers for Python (including ssl, M2Crypto and pyOpenSSL) expose the APIs that I need for
SSLyze, so I had to write my own wrapper.


License
-------

Licensed under the GPLv2; see ./LICENSE

Please contact me if this license doesn't work for you.


Author
------

Alban Diquet - @nabla_c0d3 - https://nabla-c0d3.github.io


%prep
%setup -q -n nassl-%{version}

%build
python setup.py build

%install
python setup.py install --prefix=%{_prefix} --root=%{buildroot}

%clean
rm -rf %{buildroot}

%files
%defattr(-,root,root,-)
%{python_sitelib}/*

%changelog

现在，当我尝试构建 rpm 时，我在 %install 部分遇到错误

rpmbuild -bi python-nassl.spec

The error is

Processing files: python-nassl-0.16.3-0.x86_64
error: File not found by glob: /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib/python2.7/site-packages/*


RPM build errors:
    File not found by glob: /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib/python2.7/site-packages/*

当我尝试列表检查时，我遇到了同样的错误。

[root@localhost SPECS]# rpmbuild -bl python-nassl.spec 
Processing files: python-nassl-0.16.3-0.x86_64
error: File not found by glob: /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib/python2.7/site-packages/*


RPM build errors:
    File not found by glob: /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib/python2.7/site-packages/*
[root@localhost SPECS]#

检查 /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64 目录时，我发现文件实际上位于 /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib64，而不是 /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64/usr/lib。

是否有任何 rpmbuild 宏我可以调整以使其在 /root/rpmbuild/BUILDROOT/python-nassl-0.16.3-0.x86_64 目录中显示？

Answer 1

我能够通过修改 %files 部分来解决问题。

%{python_sitelib} 扩展到 /usr/lib/python2.7/site-packages

[root@localhost SPECS]# rpm --eval '%{python_sitelib}'
/usr/lib/python2.7/site-packages
[root@localhost SPECS]#

我将其替换为 %{python_sitearch}，扩展为 /usr/lib64/python2.7/site-packages

rpmbuild 在 %install 部分失败

rpmbuild fails during %install section

rpm

rpmbuild

rpm-spec