Your package expatpp failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=12814674 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
Created attachment 1124534 [details] build.log
Created attachment 1124535 [details] root.log
Created attachment 1124536 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This FTBFS is caused by the package still using "fgets", a function which has long been deprecated and finally was removed from c++14. This patch would make this package buildable again, but ... diff -Naur expatpp.orig/test/testexpatpp.cpp expatpp/test/testexpatpp.cpp --- expatpp.orig/test/testexpatpp.cpp 2016-03-18 13:34:09.834408700 +0100 +++ expatpp/test/testexpatpp.cpp 2016-03-18 13:40:50.457310799 +0100 @@ -82,7 +82,7 @@ int depth = 0; puts("\n\nXML test: enter filename"); - gets(filename); + fgets(filename,80,stdin); if (strlen(filename)==0) break; ... due to the facts, - nothing in Fedora seems to depend on this package - its Fedora maintainer (mrceresa) seemingly is AWOL According to http://koji.fedoraproject.org/koji/userinfo?userID=1229 no packaging activity since 2015-04-08 - its upstream appears dead. I propose to drop this package from f24 and rawhide. @mrceresa: Please consider to be part of an AWOL process and respond to this BZ. I will file a formal AWOL ticket against you with FESCO, otherwise.
Hi Ralf, thanks for your mail. I'm okay to retire it. However, do you know how to check if nobody else is using this package? I tried: dnf repoquery --whatrequires expatpp but I'm not sure if it is giving the correct information, especially considered that, for instance, I use gdcm as build-require InsightToolkit but it does not appear in the list. Best, Mario
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
peter's expatpp-0-11.20121019gitd8c1bf8.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=924881
expatpp-0-11.20121019gitd8c1bf8.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-54ebfef817
expatpp-0-11.20121019gitd8c1bf8.fc26 has been pushed to the Fedora 26 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-2017-54ebfef817
fweimer's expatpp-0-12.20121019gitd8c1bf8.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=942190
expatpp-0-11.20121019gitd8c1bf8.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.