Hello, Your package depends on a utility from policycoreutils-python. The utilities have been moved to a new package, policycoreutils-python-utils. Please, apply the provided patch to fix your package as soon as possible because on Tuesday, July 28, there is an Alpha Freeze and Change Freeze for Fedora 23. Thank you very much, Tomas Radej
Created attachment 1055828 [details] Patch for SPEC file
Upstream ticket: https://fedorahosted.org/389/ticket/48229
Fedora build for f23 fails. I've never seen this error. Is this related to python update? Thanks. ======================================================= Building 389-ds-base-1.3.4.2-1.fc23 for f23-candidate Created task: 10489794 Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=10489794 Watching tasks (this may be safely interrupted)... 10489794 build (f23-candidate, /389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123): open (buildvm-11.phx2.fedoraproject.org) 10489795 buildSRPMFromSCM (/389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123): free 10489795 buildSRPMFromSCM (/389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123): free -> open (arm04-builder18.arm.fedoraproject.org) 10489795 buildSRPMFromSCM (/389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123): open (arm04-builder18.arm.fedoraproject.org) -> FAILED: BuildError: error retrieving sources, mock exited with status 23; see root.log for more information 0 free 1 open 0 done 1 failed 10489794 build (f23-candidate, /389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123): open (buildvm-11.phx2.fedoraproject.org) -> FAILED: BuildError: error retrieving sources, mock exited with status 23; see root.log for more information 0 free 0 open 0 done 2 failed 10489794 build (f23-candidate, /389-ds-base:d4386f996a84bd01c87591721f48a5d1feb97123) failed ======================================================= Snippet of root.log: DEBUG util.py:378: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0Warning: Failed to create the file ./: Is a directory DEBUG util.py:378: curl: (23) Failed writing body (0 != 8001) DEBUG util.py:489: Child return code was: 23
Please note that building 389-ds-base on f22 was successfully done. http://koji.fedoraproject.org/koji/taskinfo?taskID=10489840 where the spec file patch in the comment #1 is not applied.
I doubt it's related. Building version 389-ds-base-1.3.4.1-2.fc23 (only with Python 3 patch, not updated to newer version) succeeds: http://koji.fedoraproject.org/koji/taskinfo?taskID=10491726 I believe it's updating to 1.3.4.2 in the following commit that breaks the build.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.