Your package resiprocate failed to build from source in current F28. https://koji.fedoraproject.org/koji/taskinfo?taskID=24888068 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Created attachment 1442909 [details] build.log
Created attachment 1442910 [details] root.log
Created attachment 1442911 [details] state.log
Dear Maintainer, your package has not been built successfully in F28. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://fedoraproject.org/wiki/Fails_to_build_from_source#Package_Removal_for_Long-standing_FTBFS_bugs
Let's orphan this package.
there is a new upstream release coming, it will fix build issues on Fedora If anybody is interested and has time to test you are welcome to communicate with us through the reSIProcate mailing list. Personally, I have Fedora and CentOS environments for testing during the upstream release process before a final tag is made.
Any update about the new release that fixes the build issues? This package still requires ambiguous python and was not rebuilt since Fedora 24.
The build errors appear to be OpenSSL related: $ grep -i error: build.log ssl/OpenSSLInit.cxx:69:2: error: 'CRYPTO_malloc_debug_init' was not declared in this scope ssl/OpenSSLInit.cxx:70:31: error: 'V_CRYPTO_MDEBUG_ALL' was not declared in this scope ssl/OpenSSLInit.cxx:70:2: error: 'CRYPTO_set_mem_debug_options' was not declared in this scope error: Bad exit status from /var/tmp/rpm-tmp.dTeOQi (%build) mockbuild.exception.Error: Command failed. See logs for output. There have been improvements to the OpenSSL 1.1 support upstream, another patch just came in today: https://github.com/resiprocate/resiprocate/pull/127 After merging, I'll copy the latest 1.12.x code into Fedora rawhide and see if it builds.
Please also clarify what you mean about "This package still requires ambiguous python" and what you suggest I tweak
Looks like the OpenSSL errors were fixed by this commit, included in the 1.12.x code: https://github.com/resiprocate/resiprocate/commit/b74d77e6e792dfda33fa3c543cb6b5378e55b28b
(In reply to Daniel Pocock from comment #10) > Please also clarify what you mean about "This package still requires > ambiguous python" and what you suggest I tweak $ dnf repoquery --repo=rawhide --requires resiprocate-turn-server-psql | grep python Nepodařilo se načíst plugin: py3query Poslední kontrola metadat: před 8:25:43, Út 16. dubna 2019, 10:47:47 CEST. /usr/bin/python python-psycopg2 Is this Python 2 or Python 3? It's ambiguous. If this package can work with Python 3, use /usr/bin/python3 and python3-psycopg2. If this package can only work with Python 2, use /usr/bin/python2 and python2-psycopg2.
More info: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_multiple_python_runtimes
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.