Package Details: firefox-nightly 135.0a1+20241211.2+h2b2422cd05b9-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: 613
Popularity: 2.43
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-12-11 14:29 (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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 56 Next › Last »

Archange commented on 2017-07-20 13:04 (UTC)

@fightcookie: I’ve tried to hack something, let’s see whether it works. You might only build once a day without cleaning, so if you build before the daily nightly is published, you’ll end with the version from the day before. Note that nightlies are now produced twice per day though, and anyway the $pkgver is not suited for this. And I don’t think it’s an huge issue to miss one everyday.

xuiqzy commented on 2017-07-19 17:45 (UTC)

is it possible to add a date to the downloaded file in the packagebuild so one doesn't have to remove the previous file everytime when upgrading, to force it tot redownload it? :)

Archange commented on 2017-07-07 22:35 (UTC)

Mozilla cycled their keys, you must run `gpg --refresh-keys` before building (else you will get an unknown key error again). And please don’t flag OOD for this kind of errors.

zwindl commented on 2017-06-15 14:52 (UTC)

@ArchangeGabriel Thanks for your answer, it solved, after I refresh that key. And I still don't know why it happened, anyway, it works.

Archange commented on 2017-06-15 12:42 (UTC) (edited on 2017-12-24 18:40 (UTC) by Archange)

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.

Archange commented on 2017-06-15 12:39 (UTC)

@zwindl: What kind of problem? Can you paste the log somewhere and link it here? @rican-linux and @fredmorcos: Sorry, I missed your posts. I’m pinning a comment about GPG handling.

zwindl commented on 2017-06-15 12:37 (UTC)

I got a gpgkey problem, and it says can't verify package with sha512sums. What should I provide or what should I do to solve that problem?

fredmorcos commented on 2017-05-29 08:56 (UTC)

@rican-linux care to share what you did? i added the keys but it still does not work for me. same gpg error.

p4block commented on 2017-05-28 13:41 (UTC) (edited on 2017-05-28 14:17 (UTC) by p4block)

@ArchangeGabriel: I always got the same version as the one available, and appending --needed would skip the package although it was listed as upgradeable. Somehow the issue solved itself today though. That was weird. Will report if it happens again. EDIT: happened on another PC. There was a version mismatch (*16 vs *18) but pacaur was upgrading to the old package all the time for some reason. Manual rebuild of the package managed to finally upgrade the thing.

rican-linux commented on 2017-05-27 20:49 (UTC)

I am getting a gpg error when I try to build. I needed to add the mozilla software release key. Should there be a comment letting users know this or people should just know when they see the error to add the key?

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 56 Next › Last »