Description of problem: sepolicy manpage fails during policy build Version-Release number of selected component (if applicable): latest rawhide How reproducible: sometimes Steps to Reproduce: 1. Initiate a selinux-policy build Actual results: + /usr/bin/sepolicy manpage -a -p /__w/selinux-policy/selinux-policy/rpmbuild/BUILDROOT/selinux-policy-38.2-1.20221212_150123.2b2c45d.fc38.x86_64/usr/share/man/man8/ -w -r /__w/selinux-policy/selinux-policy/rpmbuild/BUILDROOT/selinux-policy-38.2-1.20221212_150123.2b2c45d.fc38.x86_64 FileExistsError: [Errno 17] File exists: '/__w/selinux-policy/selinux-policy/rpmbuild/BUILDROOT/selinux-policy-38.2-1.20221212_150123.2b2c45d.fc38.x86_64/usr/share/man/man8/' error: Bad exit status from /var/tmp/rpm-tmp.WY9sgI (%install) Bad exit status from /var/tmp/rpm-tmp.WY9sgI (%install) RPM build errors: Error: Process completed with exit code 1. Expected results: no error Additional info: https://github.com/fedora-selinux/selinux-policy/actions/runs/3676994136/jobs/6218369540
modified python/sepolicy/sepolicy/manpage.py @@ -376,8 +376,7 @@ class ManPage: self.fcdict = sepolicy.get_fcdict(self.fcpath) - if not os.path.exists(path): - os.makedirs(path) + os.makedirs(path, exist_ok=True) self.path = path
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
FEDORA-2023-568a3be5b8 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-568a3be5b8
FEDORA-2023-568a3be5b8 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-568a3be5b8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-568a3be5b8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-568a3be5b8 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.