Package Details: firefox-nightly 57.0a1.20170802-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: 502
Popularity: 17.210482
First Submitted: 2008-09-10 14:23
Last Updated: 2017-08-02 22:34

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)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build firefox-nightly.

Please read this:

Short answer:
gpg --recv-key 0x61B7B526D98F0353

Latest Comments

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.

Alittlemurkling 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...

vijaygopal1234 commented on 2017-08-29 13:28

20170829-firefox-57.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (bad signature from public key BBBEBDBB24C6F355)

This is a different public key than usual? Installation failing today.

Getting this when I try to import the key again

$ 24 signatures not checked due to missing keys

grawlinson commented on 2017-08-25 22:38

Quick question, given the recent desktop icon changes (red bird, original logo, doge logo, etc), it should have reverted back to the original logo by now.

Mine hasn't, anyone know how to force a refresh of this? Thanks. :)

ArchangeGabriel commented on 2017-08-19 16:06

They are even several new versions per day. And yes, you can automatize the process on your side, they are a lot of different tools for this job. Read the man of your favourite AUR helper or change to another one if yours do not support updating VCS-like packages.

deathye commented on 2017-08-19 15:44

There's no way to automatize the process of daily update the AUR package?

All comments