Red Hat Bugzilla – Bug 225755
Merge Review: firefox
Last modified: 2016-12-20 06:56:38 EST
Fedora Merge Review: firefox http://cvs.fedora.redhat.com/viewcvs/devel/firefox/ Initial Owner: caillon@redhat.com
I assume this was closed by accident as I don't see any package review here. If not, please provide a reason for closing.
What is a reason for this bug? More accurately, what do you expect? From some specific reasons Firefox does not comply to all Fedora packaging guidelines (like embeded libraries) so technically it can't get package review...
Anyway, rpmlint seems to be quite happy: $rpmlint firefox.spec firefox.spec:104: W: unversioned-explicit-provides webclient firefox.spec: W: invalid-url Source1: firefox-langpacks-24.0-20130913.tar.xz
Hi Martin, About Merge Reviews, please see https://fedoraproject.org/wiki/Merge_Reviews These have to be treated (almost) like regular package reviews. There are still ~50-60 outstanding Merge Reviews https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW%2CNEEDINFO%2CMODIFIED&component=Package%20Review&field0-0-0=flagtypes.name&list_id=1819664&order=bugs.bug_id%20desc&product=Fedora&query_format=advanced&type0-0-0=notsubstring&value0-0-0=fedora-review rpmlint output for the SPEC file is only one of the many things to check during a package review. Please wait for (or search for) a reviewer before closing this bug. Thanks.
Mass reassigning all merge reviews to their component. For more details, see this FESCO ticket: https://fedorahosted.org/fesco/ticket/1269 If you don't know what merge reviews are about, please see: https://fedoraproject.org/wiki/Merge_Reviews How to handle this bug is left to the discretion of the package maintainer.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Hasn't this been fixed for a long time?
(In reply to Christian Stadelmann from comment #7) > Hasn't this been fixed for a long time? No. Feel free to take it and attach a patch here. Even a particular one can help. Thanks!
I should have read comment #4 before posting. Sorry for the noise.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.