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: 1.40
First Submitted: 2008-09-10 14:23 (UTC)
Last Updated: 2025-02-13 07:59 (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 .. 40 41 42 43 44 45 46 47 48 49 50 .. 56 Next › Last »

<deleted-account> commented on 2012-02-10 04:09 (UTC)

@eruo I use xfce and here's what I did: For me it was asking how to handle "file links" regardless of the application type Choosing thunar opened the filetypes I tested in the right apps I used (zip files in file-roller, images in gthumb for me) If it works for you, check "remember my choice for file links"

xenom commented on 2012-02-02 08:15 (UTC)

No need to add a comment for update when package is already marked as "Out of date". You just need to change the pkgver, it's the same thing at every new version. Package will be updated today, after my day of work.

Det commented on 2012-02-01 20:05 (UTC)

If it's obvious why does it need saying?

<deleted-account> commented on 2012-02-01 19:28 (UTC)

For now, just change pkgver from 12.a1 to 13.a1 (obviously)

Det commented on 2012-02-01 17:54 (UTC)

Yes?

<deleted-account> commented on 2012-02-01 15:08 (UTC)

Shouldn't this be updated for firefox 13 ?

<deleted-account> commented on 2011-12-27 22:55 (UTC)

Any way to get the file/application associations working with this

Det commented on 2011-12-27 22:35 (UTC)

Whatever. Just saying.

xenom commented on 2011-12-27 21:58 (UTC)

Thanks for the answer and the work. I like to update the pkgrel for every change (exept. for description,url,...) to show a change in the PKGBUILD, even when it is a minor change like this. Maybe people do not have the necessary dependencies, or have installed packages as dependencies only for this program.

Det commented on 2011-12-27 19:09 (UTC)

Well, usually you could either: 1) Remove the dependency and try to start the program with it or 2) Start the program and use 'lsof' to find the files the process is using (`lsof -p [pid]`) But in this case it's not required. The binary "update-desktop-database" used in [extra]'s firefox's .install file is provided by 'desktop-file-utils'. That's why it's required there. Also verifying for every [extra]'s firefox dependency is not required. I already did that. Finally, I don't get why is it so important for some people to bump the pkgrel upon every single change. Eg. in this case nothing is actually changed: only dependencies people already _have_ are being added/removed (of course decluding those who upon clean install install like only this thing).