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.41
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-09-27 20:33 (UTC)

Required by (97)

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 .. 17 18 19 20 21 22 23 24 25 26 27 .. 56 Next › Last »

grawlinson commented on 2017-08-25 22:38 (UTC)

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. :)

Archange commented on 2017-08-19 16:06 (UTC)

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.

lockeanarchist commented on 2017-08-19 15:44 (UTC)

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

akrai commented on 2017-08-16 19:10 (UTC)

please STOP FLAGGING THIS as out of date, you get the latest version of firefox nightly every time you install it, there is literally no need to update DAILY the pkgbuild just to change the date of the package, just have in mind that every day there is a new build, if you want it just reinstall the package

Archange commented on 2017-08-13 17:37 (UTC)

@ChoromPotro What are you trying to say with this OOD flag?

NdranC commented on 2017-08-09 13:40 (UTC)

I managed to install the key manually. I don't know why I'm not able to fetch any public key remotely as far as I can tell. Searching for this issue the last couple hours seems to have been futile. Thanks for your help.

Archange commented on 2017-08-09 08:53 (UTC)

Are you able to retrieve any other key? If not, take a look at fixing your gnupg setup.

NdranC commented on 2017-08-09 02:09 (UTC) (edited on 2017-08-09 02:11 (UTC) by NdranC)

I have tried every single command linked in the last 10 comments and none of them worked for me. The error I get with every single one of them is: gpg: keyserver receive failed: Server indicated a failure Any ideas on why it works for some people and it doesn't for others? I can't even update my firefox-beta either because of a similar "integrity checking" issue. EDIT: Don't know if it matters but the exact error I get when I try to install firefox-nightly doesn't mention exfalso. Here it is: ==> Verifying source file signatures with gpg... 20170808-firefox-57.0a1.en-US.linux-x86_64.tar.bz2 ... FAILED (unknown public key BBBEBDBB24C6F355) ==> ERROR: One or more PGP signatures could not be verified! :: failed to verify firefox-nightly integrity

repo commented on 2017-08-08 16:09 (UTC)

gpg --delete-key 0x61B7B526D98F0353 gpg --recv-key 0x61B7B526D98F0353 Worked for me.

Archange commented on 2017-08-08 10:01 (UTC)

Once again, they didn’t change their key, only a sub key, so refreshing you’re existing one should work. The master key you’re looking for is 0x61B7B526D98F0353: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x61B7B526D98F0353 You can see the former subkey that expired (1C69C4E55E9905DB) and the new one that is now used (BBBEBDBB24C6F355). Can you try `gpg --recv-keys --keyserver hkp://pgp.mit.edu 0xBBBEBDBB24C6F355` or `gpg --recv-keys --keyserver hkp://pgp.mit.edu 0x61B7B526D98F0353`? And please be more specific with “does not work”, they are a lot of possibles issues.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 56 Next › Last »