Package Details: firefox-nightly 137.0a1+20250213.1+h67ec343f7371-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: 615
Popularity: 0.83
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2025-02-13 07:59 (UTC)

Dependencies (57)

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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 56 Next › Last »

di72nn commented on 2018-08-16 18:33 (UTC)

@Lindhe I may be wrong, but it seems that pacaur's --devel option is what you're looking for.

Lindhe commented on 2018-08-16 17:22 (UTC)

I just realized that this package automatically pulls the latest version from Mozilla, even if the version number of the packet is not changed. Would it be possible to have some automated build process to update that, because right now my nightly will not be found by pacaur as a program that can be updated...

Archange commented on 2018-08-16 15:37 (UTC)

@SamWhited Can you confirm this is happening even with the policies.json in place?

Archange commented on 2018-08-15 17:47 (UTC)

There is a way to fix this, I just need to check whether it would be acceptable with fellow TUs.

ratcheer commented on 2018-08-07 12:45 (UTC)

I get the "FAILED (bad signature from public key" almost every time I try to make this package, no matter how long I wait. Is there a more reliable way to do this?

akrai commented on 2018-07-22 11:03 (UTC)

thanks fiji-flo, done in the es-es package

fiji-flo commented on 2018-07-19 18:43 (UTC)

Disabling auto update via vendor.js is not working anymore: https://bugzilla.mozilla.org/show_bug.cgi?id=1420514

adding a policies.json with the following content:

{ "policies": { "DisableAppUpdate": true } }

and then installing it via

install -Dm644 "${srcdir}"/policies.json -t "${pkgdir}"/${OPT_PATH}/distribution

should solve this.

ux3w5r9xb commented on 2018-07-10 16:38 (UTC) (edited on 2018-07-10 16:40 (UTC) by ux3w5r9xb)

This package doesn't seem to get updated daily, only when major version is changed (e.g. 61 -> 62). I believe this is due to package signature isn't updated on daily basis.

dryya commented on 2018-06-29 01:38 (UTC)

I'm getting a PGP signature verification failure when trying to update to 63. I've tried the solutions suggested in the pinned comment.

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 56 Next › Last »