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: 559
Popularity: 1.924755
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

1 2 3 4 5 6 ... Next › Last »

toyarchery commented on 2019-06-14 08:18

I had to use "gpg --keyserver --recv-key 0xF1A6668FBB7D572E"

lnicola commented on 2019-06-14 07:47

Fix for "unknown public key": gpg --keyserver --refresh-keys

lnicola commented on 2019-06-14 05:48

Possibly related:

DuKol commented on 2019-06-13 08:59

Actually a new unknown key... FAILED (unknown public key F1A6668FBB7D572E) on 20190613-firefox-69.0a1.en-US.linux-x86_64.tar.bz2

ArchangeGabriel commented on 2019-06-02 17:28

Known and intentional. pacaur is (or at least was) an AUR helper that knew how to handle this, just like any other -git or VCS package for instance.

leo_sk commented on 2019-06-02 15:52

@ArchangeGabriel:I asked because because pamac (using yaourt backend) was showing the latest version to be 69.0a1.20190521-1 for almost a week without any update. However on manually installing it again today, nightly updated to 69.0a1.20190602-1. Now my installed version is 69.0a1.20190602-1 but pamac still shows the latest version is 69.0a1.20190521-1 and that i am using outdated version. On updating however, I still get the 2nd June's build. Is this behaviour known and intentional, or is it a bug specific to me?

ArchangeGabriel commented on 2019-06-01 21:43

@leo_sk: It is updated at the frequency you update it (at most once per day). The PKGBUILD automatically download the latest tarballs from upstream. So at any given time, if you build the PKGBUILD you are at most 1 day behind (if you already tried to build on the same day, before new tarballs were uploaded upstream).

leo_sk commented on 2019-06-01 20:58

Just wanted to know how frequently this package is updated and how up to date is it with latest nightly?

SamWhited commented on 2019-03-26 15:11

FWIW, I no longer have this problem and assume that it had been fixed. Are you sure it's still happening if you try to update again?

CoolOppo commented on 2019-03-26 15:04

I'm having the exact same issue as @SamWhited.