Hello! It seems like the IceCat project is not dead. There have been some version bumps since IceCat removal from Portage. Maybe it is worth returning it back again? The IceCat v.13.0.1 is available now, which is more or less new. Regards, Vladimir Reproducible: Always
Since I was the former icecat maintainer I gonna assign this but to me. To be honest I am still not convinced that icecat rose back from the dead. If they manage to release icecat-14/-15 I will consider adding it back to portage. Meanwhile I will try to add icecat to the mozilla- and/or poly-c overlay depending on decision by the mozilla herd to let this package belong to mozilla team again.
(In reply to comment #1) > Since I was the former icecat maintainer I gonna assign this but to me. > To be honest I am still not convinced that icecat rose back from the dead. > If they manage to release icecat-14/-15 I will consider adding it back to > portage. Meanwhile I will try to add icecat to the mozilla- and/or poly-c > overlay depending on decision by the mozilla herd to let this package belong > to mozilla team again. I am not convinced they can keep up with security releases, 14.0 was already released which addressed a few critical security issues.
Just FYI, Icecat 14.0.1 was released on 21 Aug 2012. http://ftp.gnu.org/gnu/gnuzilla/14.0 http://lists.gnu.org/archive/html/bug-gnuzilla/2012-08/msg00002.html +1
They're still lacking behind badly. I'm still not convinced that it would be a good idea to reintroduce icecat into portage.
(In reply to comment #4) > They're still lacking behind badly. I'm still not convinced that it would be > a good idea to reintroduce icecat into portage. What's wrong about lagging behind?
Hello! It looks like GNU IceCat 17 is out: http://ftp.gnu.org.ua/gnu/gnuzilla/17.0/ So, maybe it is alive enough to get back into Portage? Thanks!
*** Bug 466072 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > They're still lacking behind badly. I'm still not convinced that it would be > a good idea to reintroduce icecat into portage. +1
There's still no reliable upstream release cycle and I just don't want to put a browser full of security bugs into portage without any expectation of getting these security bugs fixed by upstream (which is GNU in this case, not mozilla) in a reasonable timeframe. Feel free to reopen this bug once upstream becomes reliable again.
GNU released IceCat v60.3.0 two days ago, based on currently latest Firefox ESR (v60.3.0): https://lists.gnu.org/archive/html/bug-gnuzilla/2018-11/msg00000.html How about reopening this bug?
Yes reopening this issue would be a good idea seeing as Icecat is very much not dead. You can even see that this project is being actively maintained by the developers and kept up to date with the latest version of ESR (68.11.0 at the time of writing): https://git.savannah.gnu.org/cgit/gnuzilla.git/log/?h=68 GNU Icecat is still one of my favorite flavors of Firefox, and having to rely on a thirdparty overlay when it used to be in Gentoos official repository is a bit annoying.
IceCat 78 released https://git.savannah.gnu.org/cgit/gnuzilla.git/commit/?id=bcfe407570cae32d00dd33a268de0e0593166f7b
I think gnu icecat is the only trustworthy browser so I would really appreciate if this issue was reopened. It seems that gnu icecat is doing a much better job at following firefox esr: https://git.savannah.gnu.org/cgit/gnuzilla.git/commit/?id=a43514623e93d4f3fe6d61f5b2f82c5ef29bf518 Release 78.6.0 from icecat released December 14th and firefox released 78.6.0 on December 15th: https://www.mozilla.org/en-US/firefox/78.6.0/releasenotes/ (In reply to Armin Karic from comment #11) > Yes reopening this issue would be a good idea seeing as Icecat is very much > not dead. > You can even see that this project is being actively maintained by the > developers and kept up to date with the latest version of ESR (68.11.0 at > the time of writing): > https://git.savannah.gnu.org/cgit/gnuzilla.git/log/?h=68 > GNU Icecat is still one of my favorite flavors of Firefox, and having to > rely on a thirdparty overlay when it used to be in Gentoos official > repository is a bit annoying. Can you please share the overlay you are using? The only one I could find was out of date (using icecat 68.*)
It seems the reason this bug was closed is not relevant anymore. The only active overlay with icecat is lagging behind the new version for 2 months already. Makes sense to reopen.
(In reply to Lars Wendler (Polynomial-C) from comment #9) > There's still no reliable upstream release cycle and I just don't want to > put a browser full of security bugs into portage without any expectation of > getting these security bugs fixed by upstream (which is GNU in this case, > not mozilla) in a reasonable timeframe. > > Feel free to reopen this bug once upstream becomes reliable again. Hi! Icecat git repo is close to esr updates and is updated regularly. I think upstream is getting reliable again. It looks like regular users don't have the option to reopen this bug.
I've reassigned and reopened given no reply for now.
Icecat is now 115.20.0 which is current. One should reconsider including an Icecat ebuild because Mozilla recently changed Firefox' user license in order to sidechannel its users' data which is generally considered an inevitable move towards commercialization.
