Package Details: firefox-nightly 88.0a1.20210227-1

Git Clone URL: (read-only, click to copy)
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: Archange
Last Packager: Archange
Votes: 586
Popularity: 3.76
First Submitted: 2008-09-10 14:23
Last Updated: 2021-02-28 13:52

Required by (95)

Sources (8)

Pinned Comments

Archange 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 »

nrayamjhee commented on 2021-02-26 21:51

@SimPilotAdamT Just change the _version = 88.0a1 and pkgver = 88.0a1.20210226 in PKGBUILD and rebuild the package for now. @Archange is probably going to update that and .SRCINFO sometime soon. Just did that so that I can get the update with doge firefox logo :D

SimPilotAdamT commented on 2021-02-25 16:27

Any news on when the AUR version of Nightly is going to be updated? I am currently on 88.0a1, while AUR is still 87.0a1.

drugo commented on 2021-02-18 14:24

Hello, it is failing for me with a key error, but because of a bad signature instead of a missing key.

==> Verifying source file signatures with gpg...
    20210218-firefox-87.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (bad signature from public key F1A6668FBB7D572E)

The key was imported automatically during installation, and deleting and manually importing it leads to the same behaviour. Issue on their side?

EDIT: this happened with yay, cloning and installing manually worked (same check was made but passed for some reason)

masih commented on 2021-02-14 18:37

@Archange oh sorry i didn't know that

Archange commented on 2021-02-14 09:48

@masih Please stop flagging out-of-date, this PKGBUILD auto-update at build time unless the major version number changed (which won’t be the case before another two weeks at least).

Archange commented on 2021-01-27 09:33

@pmarreck: This package does not build from source, it downloads prebuild artifacts from Mozilla. Those are only provided for i686 and x86_64. No one ever wanted to push a firefox-nightly source build, because you would have to rebuild constantly and it takes hour each time.

That being said there is a source package (with nightly builds, that I’ve been using for a long time now instead of this AUR package) on heftig repo at

pmarreck commented on 2021-01-15 17:56

So I'm trying to build this on manjaro-aarch64. I added aarch64 to the allowed build architectures in PKGBUILD (because this usually works, I've built things from source before this way, although am generally new to Manjaro). I am erroring inside the package() function on the copy step: "cp: cannot stat 'firefox': No such file or directory" I added some debug commands prior to the error (pwd, ls -al etc.) and reran the build and yep, there's no "firefox" in there, which means... a previous step failed, but didn't error, or something? I'm not sure.

DuKol commented on 2021-01-15 08:11

Dear all, last two days I see the following error: ==> Updated version: firefox-nightly 86.0a1.20210114-1 ==> ERROR: A package has already been built. (use -f to overwrite) Even if I downloaded a new package and, for me, it is actually 2021-01-15: Extracting 20210115-firefox-86.0a1.en-US.linux-x86_64.tar.bz2 with bsdtar

The other days it was the same just different dates. Even if I delete everything and build a package, after installation it does not work correctly - it must be killed.

sperg512 commented on 2020-12-22 19:06

oh, I see. that's pretty odd but thanks

Archange commented on 2020-12-22 19:05

The latest version is retrieved by checking a particular text file upstream. Checksums are embedded in the PGP signature file, so they are retrieved with it, and verified using gpg.