1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
|
%global _empty_manifest_terminate_build 0
Name: python-selinux-please-lie-to-me
Version: 1.0.1
Release: 1
Summary: Fake selinux module that always says SELinux is off
License: MIT
URL: https://github.com/goneri/selinux_please_lie_to_me
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/66/db/210919df4457f5822b8e6a9e0238b9cf64fb6076014d274351fe41991398/selinux_please_lie_to_me-1.0.1.tar.gz
BuildArch: noarch
%description
# SELinux: please lie to me! ðŸ˜
This package provides a fake `selinux` module. This package mocked `selinux` module and
will always pretend SELinux is not enabled on the system.
## But why? 😕
If your system runs SELinux and run Ansible in a virtualenv you will probably
face this error:
Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!
## But what about the regular [selinux package from Pypi](https://pypi.org/project/selinux/)?
You system comes with a `python3-libselinux` package that was built using on specific Python version.
For instance, on Fedora 34 it's Python 3.9. The same binary package may work fine with another Python
version, but it's not always the case.
### Example with the selinux shim from pypi
In this example on Fedora 34, we cannot use the `selinux` shim package because Python 3.6 cannot load the system `selinux` binary for Python 3.9:
```
$ virtualenv -p python3.6 ~/tmp/my-venv-py36
(...)
$ ~/tmp/my-venv-py36/bin/pip install selinux
Collecting selinux
Using cached selinux-0.2.1-py2.py3-none-any.whl (4.3 kB)
Requirement already satisfied: setuptools>=39.0 in ./tmp/my-venv-py36/lib/python3.6/site-packages (from selinux) (53.0.0)
Collecting distro>=1.3.0
Using cached distro-1.5.0-py2.py3-none-any.whl (18 kB)
Installing collected packages: distro, selinux
Successfully installed distro-1.5.0 selinux-0.2.1
WARNING: You are using pip version 21.0.1; however, version 21.1.3 is available.
You should consider upgrading via the '/home/goneri/tmp/my-venv-py36/bin/python -m pip install --upgrade pip' command.
$ ~/tmp/my-venv-py36/bin/python -m selinux
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib64/python3.6/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib64/python3.6/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 104, in <module>
check_system_sitepackages()
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 95, in check_system_sitepackages
success = add_location(candidate)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 65, in add_location
reload(sys.modules["selinux"])
File "/usr/lib64/python3.6/importlib/__init__.py", line 166, in reload
_bootstrap._exec(spec, module)
File "/usr/lib64/python3.9/site-packages/selinux/__init__.py", line 13, in <module>
from . import _selinux
ImportError: cannot import name '_selinux'
```
## Example with selinux_please_lie_to_me
$ virtualenv -p python3.6 venv
$ source venv/bin/active
$ pip install selinux_please_lie_to_me
$ python3 -c 'import selinux; print(f"SELinux is enabled: {selinux.is_selinux_enabled()}, (which is probably a lie 🤫)")'
SELinux is enabled: False, (which is probably a lie 🤫)
## What does this break?
Since, we pretend selinux is disabled, we won't do any SELinux specific operation.
%package -n python3-selinux-please-lie-to-me
Summary: Fake selinux module that always says SELinux is off
Provides: python-selinux-please-lie-to-me
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-selinux-please-lie-to-me
# SELinux: please lie to me! ðŸ˜
This package provides a fake `selinux` module. This package mocked `selinux` module and
will always pretend SELinux is not enabled on the system.
## But why? 😕
If your system runs SELinux and run Ansible in a virtualenv you will probably
face this error:
Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!
## But what about the regular [selinux package from Pypi](https://pypi.org/project/selinux/)?
You system comes with a `python3-libselinux` package that was built using on specific Python version.
For instance, on Fedora 34 it's Python 3.9. The same binary package may work fine with another Python
version, but it's not always the case.
### Example with the selinux shim from pypi
In this example on Fedora 34, we cannot use the `selinux` shim package because Python 3.6 cannot load the system `selinux` binary for Python 3.9:
```
$ virtualenv -p python3.6 ~/tmp/my-venv-py36
(...)
$ ~/tmp/my-venv-py36/bin/pip install selinux
Collecting selinux
Using cached selinux-0.2.1-py2.py3-none-any.whl (4.3 kB)
Requirement already satisfied: setuptools>=39.0 in ./tmp/my-venv-py36/lib/python3.6/site-packages (from selinux) (53.0.0)
Collecting distro>=1.3.0
Using cached distro-1.5.0-py2.py3-none-any.whl (18 kB)
Installing collected packages: distro, selinux
Successfully installed distro-1.5.0 selinux-0.2.1
WARNING: You are using pip version 21.0.1; however, version 21.1.3 is available.
You should consider upgrading via the '/home/goneri/tmp/my-venv-py36/bin/python -m pip install --upgrade pip' command.
$ ~/tmp/my-venv-py36/bin/python -m selinux
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib64/python3.6/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib64/python3.6/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 104, in <module>
check_system_sitepackages()
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 95, in check_system_sitepackages
success = add_location(candidate)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 65, in add_location
reload(sys.modules["selinux"])
File "/usr/lib64/python3.6/importlib/__init__.py", line 166, in reload
_bootstrap._exec(spec, module)
File "/usr/lib64/python3.9/site-packages/selinux/__init__.py", line 13, in <module>
from . import _selinux
ImportError: cannot import name '_selinux'
```
## Example with selinux_please_lie_to_me
$ virtualenv -p python3.6 venv
$ source venv/bin/active
$ pip install selinux_please_lie_to_me
$ python3 -c 'import selinux; print(f"SELinux is enabled: {selinux.is_selinux_enabled()}, (which is probably a lie 🤫)")'
SELinux is enabled: False, (which is probably a lie 🤫)
## What does this break?
Since, we pretend selinux is disabled, we won't do any SELinux specific operation.
%package help
Summary: Development documents and examples for selinux-please-lie-to-me
Provides: python3-selinux-please-lie-to-me-doc
%description help
# SELinux: please lie to me! ðŸ˜
This package provides a fake `selinux` module. This package mocked `selinux` module and
will always pretend SELinux is not enabled on the system.
## But why? 😕
If your system runs SELinux and run Ansible in a virtualenv you will probably
face this error:
Aborting, target uses selinux but python bindings (libselinux-python) aren't installed!
## But what about the regular [selinux package from Pypi](https://pypi.org/project/selinux/)?
You system comes with a `python3-libselinux` package that was built using on specific Python version.
For instance, on Fedora 34 it's Python 3.9. The same binary package may work fine with another Python
version, but it's not always the case.
### Example with the selinux shim from pypi
In this example on Fedora 34, we cannot use the `selinux` shim package because Python 3.6 cannot load the system `selinux` binary for Python 3.9:
```
$ virtualenv -p python3.6 ~/tmp/my-venv-py36
(...)
$ ~/tmp/my-venv-py36/bin/pip install selinux
Collecting selinux
Using cached selinux-0.2.1-py2.py3-none-any.whl (4.3 kB)
Requirement already satisfied: setuptools>=39.0 in ./tmp/my-venv-py36/lib/python3.6/site-packages (from selinux) (53.0.0)
Collecting distro>=1.3.0
Using cached distro-1.5.0-py2.py3-none-any.whl (18 kB)
Installing collected packages: distro, selinux
Successfully installed distro-1.5.0 selinux-0.2.1
WARNING: You are using pip version 21.0.1; however, version 21.1.3 is available.
You should consider upgrading via the '/home/goneri/tmp/my-venv-py36/bin/python -m pip install --upgrade pip' command.
$ ~/tmp/my-venv-py36/bin/python -m selinux
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib64/python3.6/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
File "/usr/lib64/python3.6/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 104, in <module>
check_system_sitepackages()
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 95, in check_system_sitepackages
success = add_location(candidate)
File "/home/goneri/tmp/my-venv-py36/lib/python3.6/site-packages/selinux/__init__.py", line 65, in add_location
reload(sys.modules["selinux"])
File "/usr/lib64/python3.6/importlib/__init__.py", line 166, in reload
_bootstrap._exec(spec, module)
File "/usr/lib64/python3.9/site-packages/selinux/__init__.py", line 13, in <module>
from . import _selinux
ImportError: cannot import name '_selinux'
```
## Example with selinux_please_lie_to_me
$ virtualenv -p python3.6 venv
$ source venv/bin/active
$ pip install selinux_please_lie_to_me
$ python3 -c 'import selinux; print(f"SELinux is enabled: {selinux.is_selinux_enabled()}, (which is probably a lie 🤫)")'
SELinux is enabled: False, (which is probably a lie 🤫)
## What does this break?
Since, we pretend selinux is disabled, we won't do any SELinux specific operation.
%prep
%autosetup -n selinux-please-lie-to-me-1.0.1
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-selinux-please-lie-to-me -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.1-1
- Package Spec generated
|