Package Details: icecat-bin 60.7.0-2

Git Clone URL: (read-only)
Package Base: icecat-bin
Description: Binary build of the GNU version of the Mozilla Firefox browser
Upstream URL:
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Conflicts: icecat
Provides: icecat
Replaces: icecat
Submitter: jfigueras
Maintainer: figue (figuepluto, jfigueras)
Last Packager: figuepluto
Votes: 40
Popularity: 1.343257
First Submitted: 2016-01-03 12:11
Last Updated: 2019-06-03 20:06

Latest Comments

1 2 3 4 Next › Last »

figue commented on 2019-07-19 15:53

@aluizioneto you have to trust in Ruben's gpg key. Just execute this in a shell:

gpg --recv-keys D7BEFC2F89D03EFC

aluizioneto commented on 2019-07-19 12:40

I'm having the issue bellow:

==> Verifying source file signatures with gpg... icecat-60.7.0.en-US.gnulinux-x86_64.tar.bz2 ... FAILED (unknown public key D7BEFC2F89D03EFC) ==> ERROR: One or more PGP signatures could not be verified!

Read Jezza's comment but didn't quite understand what is going on. Can someone help me to clear this? GPG is not able to verify the signatures and Jezza is suggesting changing them on the PKGBUILD, right? Is that a safe procedure? What would be a reliable source for the correct keys?


jezza commented on 2019-06-04 03:06

Re Ruben Rodriguez' key verification: In the PKGBUILD, insert his other key: 'gpg --recv-keys D7E04784' (or find it in Enigmail), check that you got the right one, and then replace the validpgpkeys line of the PKGBUILD with the fingerprint: validpgpkeys=(A57369A8BABC2542B5A0368C3C76EED7D7E04784) # Ruben Rodriguez (GNU IceCat releases key) That worked for me.

qwer1234 commented on 2019-06-03 19:02

==> Verifying source file signatures with gpg... icecat-60.7.0.en-US.gnulinux-x86_64.tar.bz2 ... FAILED (unknown public key D7BEFC2F89D03EFC)

figue commented on 2019-05-11 19:02

Binary packages of IceCat are not released yet. Please be patient.

misaka00251 commented on 2019-04-11 04:28

What about *.xpi themes? Can't use the method provided by @lolisamurai.

lolisamurai commented on 2019-01-13 20:46

it appears to be a problem specific to icecat on extensions without an id in their manifest:

current workaround is to extract the xpi and repack it with a manifest id

figue commented on 2019-01-08 15:06

@azx07 @lolisamurai I'm not sure if this kind of issues are related to packaging method or is an upstream issue. I've tried with Icecat compiled from source and the same happens. Please, report upstream:

lolisamurai commented on 2019-01-08 14:27

@azx07 same here with , no idea what could be the cause

azx07 commented on 2018-12-11 23:57

hello, I am having problems with installing some extensions to icecat.

For instance:

it gives the error that the extension seems to be corrupt. I also tried to instal via download and then install locally from file with the same error. The above extensions can be installed to firefox without a problem.

Here are some extension that can be added to icecat without a problem:

It seems to me that the problem must be icecat specific since exactly the same bug appears also on android icecat.

Could somebody confirm these bugs on their system? Anybody has an idea what could be the problem