This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1500488,1500489 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
Closing, as Fedora 26 is EOL (no update is possible); F27 and F28 have fixed rubygems. Please open a new bug in case you encounter an issue.
Lets avoid using EOL resolution to avoid confusion with auto-closed bug.
Actually, the last ruby version in F26 was 2.4.4, which includes fixed rubygems 2.6.14. It seems to have been in ruby since 2.4.3. There's also separate rubygems component at version 2.6.13. Is there still need to have it in Fedora?
Actually, this bug is against rubygems component, that - as noted in comment 6 above - has not been fixed in any Fedora. 2.6.13 is still the latest version. This should have limited impact, as rubygems RPM from rubygems SRPM has lower NVR than rubygems RPM from ruby SRPM which was fixed in F26 (see bug 1500654). If we don't need the rubygems component in Fedora any more, it should be removed.
(In reply to Tomas Hoger from comment #7) > Actually, this bug is against rubygems component, that - as noted in comment > 6 above - has not been fixed in any Fedora. 2.6.13 is still the latest > version. Right, I missed that, sorry. > This should have limited impact, as rubygems RPM from rubygems SRPM has > lower NVR than rubygems RPM from ruby SRPM which was fixed in F26 (see bug > 1500654). Yes, the rubygems subpackage from ruby package is used. I've considered that a fix. > If we don't need the rubygems component in Fedora any more, it should be > removed. Actually, we use it occasionally to update rubygems separately. Let me discuss this with my collegue when he gets back from PTO.
Hello, we concluded that rubygems package is needed/useful for our work and we should update rubygems package more often. (Bugs are for some reason not automatically created by release monitoring[1].) I'll rebase it (only) in rawhide then. Thanks for investigating this. [1] https://release-monitoring.org/project/13487/
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 should be resolved now. The rubygems were retired for a short while and therefore removed from F31+F32, now the package is restored in F33.