rubyforge.org was shut down, hence this package has lost its purpose. The only package which depends on this one is rubygem-echoe. I already asked upstream to drop the rubyforge support [1]. There is also rubygem-ci_reporter, which has BR on rubygem-rubyforge, but that is maintainer commission, since upstream already dropped the rubyforge support in 1.9.2 [2]. [1] https://github.com/evan/echoe/issues/18 [2] https://github.com/ci-reporter/ci_reporter/commit/ea428e096ff8196dc4c9184beaeace9c2775738d
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
This was not done yet and should be done IMO.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
Ping?
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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.
I still think this is useless.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
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.
It would be nice to remove this unneeded package.
I now did "fedpkg retire" on master, let's see how it goes.
(In reply to Mamoru TASAKA from comment #11) > I now did "fedpkg retire" on master, let's see how it goes. Looking at yesterday compose report [1], it was not removed yet. Not sure if the retirement was correctly processed, because there were problems [2]. But may be I am just impatient and it will be all right in next compose :) [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HX27LTJVFSWRHT3BLJPHDTJMHIV4LUGM/ [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/6OPZRCTCJIEK6SK2ICIHJUW547ERAHQN/
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DXNM2XDVXVYOOC7JK6EAKR3PZUPUQYST/ https://koji.fedoraproject.org/koji/packageinfo?packageID=6154