Bug 1765805 - Update Request for GNUzilla IceCat
Summary: Update Request for GNUzilla IceCat
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: icecat
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio T. (sagitter)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-26 07:43 UTC by Ali Reza
Modified: 2019-11-12 02:20 UTC (History)
2 users (show)

Fixed In Version: icecat-68.2.0-1.gnu1.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-12 02:20:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ali Reza 2019-10-26 07:43:32 UTC
Description of problem:

GNU IceCat is not updated on Fedora repositories. Current version we're using is 60.9.0 but there's newer versions of IceCat available. I want to request updates.

Comment 1 Antonio T. (sagitter) 2019-10-26 10:50:13 UTC
IceCat-68.2.0 is still not entirely ready for stable releases: some
features like personalized "about:icecat" homepage and privacy
protection addons are not properly working/recognized yet.

Comment 2 Ali Reza 2019-10-26 11:20:14 UTC
(In reply to Antonio from comment #1)
> IceCat-68.2.0 is still not entirely ready for stable releases: some
> features like personalized "about:icecat" homepage and privacy
> protection addons are not properly working/recognized yet.

How's the progress? Will it be shipped with Firefox 70 as new version of Firefox released days ago?

Comment 3 Antonio T. (sagitter) 2019-10-26 16:38:13 UTC
(In reply to Alireza from comment #2)
> (In reply to Antonio from comment #1)
> > IceCat-68.2.0 is still not entirely ready for stable releases: some
> > features like personalized "about:icecat" homepage and privacy
> > protection addons are not properly working/recognized yet.
> 
> How's the progress?

This is a question for upstream.

> Will it be shipped with Firefox 70 as new version of
> Firefox released days ago?

No. IceCat is based on Firefox ESR, next releases will be all 68.*

Comment 4 Ben Cotton 2019-10-31 18:44:04 UTC
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.

Comment 5 Fedora Update System 2019-11-02 07:58:32 UTC
FEDORA-2019-64eea68baf has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-64eea68baf

Comment 6 Fedora Update System 2019-11-04 02:18:17 UTC
icecat-68.2.0-1.gnu1.fc31 has been pushed to the Fedora 31 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-2019-64eea68baf

Comment 7 Fedora Update System 2019-11-12 02:20:49 UTC
icecat-68.2.0-1.gnu1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.