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.63
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2024-12-11 14:29 (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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 56 Next › Last »

SimPilotAdamT commented on 2021-02-25 16:27 (UTC)

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 (UTC) (edited on 2021-02-18 19:03 (UTC) by drugo)

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 (UTC)

@Archange oh sorry i didn't know that

Archange commented on 2021-02-14 09:48 (UTC)

@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 (UTC)

@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 https://pkgbuild.com/~heftig/packages/firefox-nightly/.

pmarreck commented on 2021-01-15 17:56 (UTC) (edited on 2021-01-15 17:58 (UTC) by pmarreck)

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 (UTC)

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 (UTC)

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

Archange commented on 2020-12-22 19:05 (UTC)

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.

sperg512 commented on 2020-12-22 19:01 (UTC)

that's weird, how does that even work?

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