Package Details: firefox-nightly 71.0a1.20190904-1

Git Clone URL: (read-only)
Package Base: firefox-nightly
Description: Standalone Web Browser from Mozilla — Nightly build (en-US)
Upstream URL:
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Submitter: None
Maintainer: ArchangeGabriel
Last Packager: ArchangeGabriel
Votes: 560
Popularity: 1.940396
First Submitted: 2008-09-10 14:23
Last Updated: 2019-09-04 19:29

Required by (1)

Sources (8)

Pinned Comments

ArchangeGabriel commented on 2017-06-15 12:42

If you face this:

==> Verifying source file signatures with gpg... yyyymmdd-firefox-xx.0a1.en-US.linux-${CARCH}.tar.bz2 ... FAILED (unknown public key BBBEBDBB24C6F355)

Please read this.

Short answer:

gpg --recv-key 0x61B7B526D98F0353

If you face this:

==> Verifying source file signatures with gpg... yyyymmdd-firefox-xx.0a1.en-US.linux-${CARCH}.tar.bz2 ... FAILED (bad signature from public key BBBEBDBB24C6F355)

Then just retry later (~1h), this is a CDN caching issue.

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

ArchangeGabriel commented on 2017-10-07 10:23

If you get bad signatures, retry a bit after (like 1 h). The download is handled by CDN, so the .sig file and the tarball might actually differ because of not being cached at the same time. The TTL was set to 1 h instead of 24 h to mitigate this, but you might still fall into a window where a new build has been published and one of the two files is still cached from previous build.

bemeurer commented on 2017-10-07 06:18

I second saghm's issue. I get `FAILED (bad signature from public key BBBEBDBB24C6F355)` as well, independent of having the correct keys imported.

saghm commented on 2017-09-25 18:32

I'm getting a "bad signature from public key" error when trying updating to 58.0a1. (I tried reimporting the key with gpg just in case, but it reported it as unchanged).

z3ntu commented on 2017-09-22 06:12

58.0a1 files are available!

ArchangeGabriel commented on 2017-09-08 12:30

Regarding signature checking errors, this is a CDN issue. The thing is that the signature file and the tarball may not be cached simultaneously, and at some point one of the two files can be updated while the other isn’t. In such cases, just retry ~1 h after (the cache is set to expire after 1 h).

@Horo: Why don’t you just install the package corresponding to your locale? firefox-nightly is for en users, firefox-nightly-${lang} for ${lang} users. ;)

Horo commented on 2017-09-08 09:16

May you add "pref("intl.locale.matchOS", true);" to vendor.js so that firefox-nightly can auto detect language after install language pack ?

jhartz commented on 2017-09-03 02:09

Seems like the verification issues are due to an issue with Mozilla's buildserver (someone in firefox-always-nightly investigated a bit:

pmlamotte commented on 2017-08-29 17:00

This has failed the signature check a lot for me too, but it doesn't seem to actually be a key error. I think it only happens while a nightly build is in progress, if I clean out my pacaur cache and try again an hour or so later it works. Trying to build before that continues to give the signature error.

11backslashes commented on 2017-08-29 13:57

This fails to pass verification after purging and reimporting the key for me as well, regardless of the keyserver I use.

EDIT: Strange. What worked for me was reimporting with: `gpg --recv-key 0x61B7B526D98F0353` on top of the key (without deleting it first).

cgirard commented on 2017-08-29 13:37

@vijaygopal1234: or you could read the comments...