Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1623371

Summary:	selinux-policy build failing because of broken sepolicy manpage
Product:	[Fedora] Fedora	Reporter:	Lukas Vrabec <lvrabec>
Component:	setools	Assignee:	Chris PeBenito <cpebenito>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	alexl, caillon+fedoraproject, caolanm, cpebenito, dwalsh, john.j5live, mgrepl, plautrba, pmoore, rhughes, rstrode, sandmann, vmojzis
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	setools-4.1.1-13.fc29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-21 05:23:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Vrabec 2018-08-29 08:27:30 UTC

Description of problem:
I'm not able to build selinux-policy rpm package on rawhide and f29 branch. 


How reproducible:
Nightly builds are failing:
https://copr-be.cloud.fedoraproject.org/results/lvrabec/selinux-policy-nightly/fedora-rawhide-x86_64/00792052-selinux-policy/build.log.gz

Actual results:

+ /usr/bin/sepolicy manpage -a -p /builddir/build/BUILDROOT/selinux-policy-3.14.3-1.fc30.2.x86_64/usr/share/man/man8/ -w -r /builddir/build/BUILDROOT/selinux-policy-3.14.3-1.fc30.2.x86_64
BUILDSTDERR: Traceback (most recent call last):
BUILDSTDERR:   File "/usr/bin/sepolicy", line 27, in <module>
BUILDSTDERR:     import sepolicy
BUILDSTDERR:   File "/usr/lib/python3.7/site-packages/sepolicy/__init__.py", line 9, in <module>
BUILDSTDERR:     import setools
BUILDSTDERR:   File "/usr/lib64/python3.7/site-packages/setools/__init__.py", line 78, in <module>
BUILDSTDERR:     from .permmap import PermissionMap
BUILDSTDERR:   File "/usr/lib64/python3.7/site-packages/setools/permmap.py", line 25, in <module>
BUILDSTDERR:     import pkg_resources
BUILDSTDERR: ModuleNotFoundError: No module named 'pkg_resources'
BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.nu6Aat (%install)
RPM build errors:
BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.nu6Aat (%install)
Child return code was: 1
EXCEPTION: [Error()]
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 96, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 636, in do
    raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode)
mockbuild.exception.Error: Command failed:

Comment 1 Vit Mojzis 2018-08-29 11:06:12 UTC

https://src.fedoraproject.org/rpms/setools/pull-request/6

Comment 2 Fedora Update System 2018-08-29 12:54:55 UTC

setools-4.1.1-13.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2fe202ceb9

Comment 3 Fedora Update System 2018-08-29 19:08:07 UTC

setools-4.1.1-13.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2fe202ceb9

Comment 4 Fedora Update System 2018-08-29 23:14:45 UTC

setools-4.1.1-13.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2fe202ceb9

Comment 5 Fedora Update System 2018-09-21 05:23:09 UTC

setools-4.1.1-13.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.