Your package rubygem-riot failed to build from source in current F28. https://koji.fedoraproject.org/koji/taskinfo?taskID=24891903 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
Let's try to investigate if upstream is responsive. There seems to be some incompatibility, probably because update Ruby to 2.5 (or earlier). ``` DEBUG: A kind_of assertion macro :fail when not a kind of String DEBUG: + asserts failure is equal to :fail DEBUG: - asserts failure message: expected "expected kind of String, not Fixnum", not "expected kind of String, not Integer" DEBUG: An AssertionMacro instance receiving #new_message DEBUG: + asserts that it is a kind of Riot::Message DEBUG: - asserts to_s: expected "\"hope\"", not "hope" kind of? Riot::Message send :to_s DEBUG: An AssertionMacro instance receiving #expected_message DEBUG: + asserts that it is a kind of Riot::Message DEBUG: - asserts to_s: expected "expected \"hope\"", not expected "hope" kind of? Riot::Message send :to_s ```
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
Giving it a second look, this can also be caused by Rails dependency update. Should be easy enought to fix the tests. But as I do not have any use for this package anymore, I've orphaned it. Feel free to pick it up if you need it.
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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.