Package Details: firefox-nightly 132.0a1+20240927.1+h79ef00c1355d-1

Git Clone URL: https://aur.archlinux.org/firefox-nightly.git (read-only, click to copy)
Package Base: firefox-nightly
Description: Fast, Private & Safe Web Browser (Nightly version)
Upstream URL: https://www.mozilla.org/firefox/channel/desktop/#nightly
Keywords: browser gecko web
Licenses: MPL-2.0
Submitter: None
Maintainer: heftig
Last Packager: heftig
Votes: 610
Popularity: 0.48
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-09-27 20:33 (UTC)

Sources (5)

Pinned Comments

heftig commented on 2022-07-27 22:26 (UTC)

Instead of building this yourself, please use the repository from https://bbs.archlinux.org/viewtopic.php?id=117157.

Not only do you skip the very time-consuming builds, but the published package also has debug symbols at Mozilla's crash reports service, which helps tremendously with finding or filing bugs for any crashes you get.

I consider this the canonical firefox-nightly package for Arch Linux.

[heftig]
SigLevel = Optional
Server = https://pkgbuild.com/~heftig/repo/$arch

Alternatively, download Firefox Nightly straight from Mozilla, extract it to a writable place (e.g. ~/.local/firefox-nightly) and let it update itself using the integrated updater.

Latest Comments

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

Sintan commented on 2021-06-03 18:48 (UTC)

@SimPilotAdamT For some reason, I was adding a sudo before that. That's why nothing was working. It worked. Thanks.

SimPilotAdamT commented on 2021-06-03 18:44 (UTC)

@SinTan @Adrian.Carver, what @electricprism said to do worked better than deleting and redoing the key. Just doing gpg --keyserver hkps://keys.openpgp.org --recv-keys EBE41E90F6F12F6D was enough for me.

Adrian.Carver commented on 2021-06-03 17:33 (UTC)

@SinTan, i use Kleopatra for key management. I didn't get anything through the terminal.

Sintan commented on 2021-06-03 16:49 (UTC)

@Adrian.Carver How do I do that?

electricprism commented on 2021-06-03 01:51 (UTC)

@Archange -- gpg --keyserver hkps://keys.openpgp.org --recv-keys EBE41E90F6F12F6D I guess. Worked for me assuming that's the correct procedure and security is ok.

Adrian.Carver commented on 2021-06-02 19:02 (UTC)

You need to delete the old key and import the updated Mozilla public key again. For me, simply updating the key did not help.

Sintan commented on 2021-06-02 18:59 (UTC)

Getting the error:

20210602-firefox-91.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (unknown public key EBE41E90F6F12F6D)

None of the solutions posted in the comments worked.

Archange commented on 2021-05-28 19:19 (UTC)

Regarding the current key issue, this is expected. As you can see in https://blog.mozilla.org/security/2019/06/13/updated-firefox-gpg-key/, the current key was set to expire on 2021-05-29 UTC, so they rotated to a new key a bit before as every two years. But… the new subkey is not available currently on most keyservers I have tried, so for now the only way to retrieve it I have found is this: gpg --keyserver hkps://keys.openpgp.org --recv-keys 14F26682D0916CDD81E37B6D61B7B526D98F0353. After that you should be able to upgrade without troubles.

<deleted-account> commented on 2021-05-28 17:35 (UTC)

I am getting ==> Verifying source file signatures with gpg... 20210528-firefox-90.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (unknown public key EBE41E90F6F12F6D)

I have read the pinned comments and did the first comment. I still receive the error. Happened yesterday too (5-27-2021) and is happening still today.

ToadKing commented on 2021-05-16 17:47 (UTC) (edited on 2021-05-22 16:17 (UTC) by ToadKing)

I saw someone made a similar tool a while back but the link seems dead: Here's a script for detecting when a new nightly build is available.

https://gist.github.com/ToadKing/006dd0eaa5f2cdc26b88bfb2d08b0e15

It returns a 0 exit code when an update is available and a non-zero one if you're already on the latest version or the script fails somewhere. It can be used like this:

firefox-nightly-needs-update.sh && yay -S firefox-nightly

Just replace yay with your favorite AUR helper/makepkg/etc. It can't detect major version changes but the PKGBUILD needs updating for those anyway.

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