Package Details: firefox-always-nightly 99.0a1-14

Git Clone URL: (read-only)
Package Base: firefox-always-nightly
Description: Standalone web browser from, nightly build, always updating
Upstream URL:
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Conflicts: firefox-nightly
Provides: firefox-nightly
Submitter: passcod
Maintainer: passcod
Last Packager: passcod
Votes: 22
Popularity: 4.178538
First Submitted: 2014-01-21 22:05
Last Updated: 2017-07-19 10:52

Pinned Comments

passcod commented on 2016-06-13 02:42

That's why it's called "always-nightly" and why the version is 99.0a1, and not 56.0a1 or whatever Nightly is at right now.

With this package, every system upgrade with an AUR-aware pacman wrapper WILL try to fetch the latest Nightly, even if there is no new build. This is not a bug.
Caching wrappers like pacaur will cache properly, though, so those won't download the same file twice.

Thus, please DO NOT flag this package out of date if:
- it seems it's not been updated (it doesn't need to), or
- the version seems wrong (that's intentional).

However, please DO flag out of date if:
- the build process fails in a way that did not happen on a prior run, or
- the way Firefox Nightly is released changed.

For other issues or suggestions, please do comment.

The Firefox Nightly Release process currently has a bug!

It causes checksum generation to be delayed.

That may cause integrity validation to fail during some hours of the day.
In this case, you can use `yaourt --m-arg "--skipchecksums" -Sb firefox-always-nightly` (or equivalent) to install the package while skipping the checks.

Latest Comments

passcod commented on 2017-10-09 10:51

@timofonic I don't know — ask pacaur. Or just retry later. In my experience the checksums sync again after 4 to 6 hours. Or try the firefox-nightly AUR package instead.

timofonic commented on 2017-10-09 08:49

@passcod I don't use yaourt, it gave me too many system issues. Why can't this be done with pacaur? I'm able to remove the cache, so that's not the problem at all.

passcod commented on 2017-10-05 19:20

@timofonic Please read the pinned comment. Especially take care to scroll right down and see the description of the known issue you hit which is an *upstream* bug (under the **WARNING** header). Additionally, you CAN run ANY two (or more) Firefoxes side-by-side by using the --new-instance flag.

timofonic commented on 2017-10-05 14:26

Some kind of feature request: Could you make Firefox Nightly be able to run along with other Firefox versions like ESR? Please consider it, it would be a very nice feature for me. I need ESR for some nasty stuff that requires Java plugins, for example.

timofonic commented on 2017-10-05 14:23

I removed the cache, the same error happens too. I tried without "--noconfirm" and "--noedit" too, same error

$ rm -rf ~/.cache/pacaur/firefox-always-nightly/

$ pacaur --noconfirm --noedit -S firefox-always-nightly
:: Package firefox-always-nightly not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...
:: firefox-always-nightly latest revision -- fetching

AUR Packages (1) firefox-always-nightly-latest

:: Proceed with installation? [Y/n]
:: Retrieving package(s)...
Cloning into 'firefox-always-nightly'...
remote: Counting objects: 7, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 7 (delta 1), reused 1 (delta 0)
Unpacking objects: 100% (7/7), done.
[sudo] password for timofonic:
:: Checking firefox-always-nightly integrity...
==> Making package: firefox-always-nightly 99.0a1-14 (Thu Oct 5 16:29:07 CEST 2
==> Retrieving sources...
-> Downloading firefox-always-nightly-58.0a1.20171004220309.tar.bz2...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 61.1M 100 61.1M 0 0 3477k 0 0:00:18 0:00:18 --:--:-- 3466k
-> Found firefox-nightly.desktop
-> Found firefox-nightly-safe.desktop
-> Found vendor.js
==> Validating source files with sha512sums...
firefox-always-nightly-58.0a1.20171004220309.tar.bz2 ... FAILED
firefox-nightly.desktop ... Passed
firefox-nightly-safe.desktop ... Passed
vendor.js ... Passed
==> ERROR: One or more files did not pass the validity check!
:: Preparing firefox-always-nightly...
==> Making package: firefox-always-nightly 99.0a1-14 (Thu Oct 5 16:29:27 CEST 2017)
==> WARNING: Skipping dependency checks.
==> Retrieving sources...
-> Found firefox-always-nightly-58.0a1.20171004220309.tar.bz2
-> Found firefox-nightly.desktop
-> Found firefox-nightly-safe.desktop
-> Found vendor.js
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
-> Extracting firefox-always-nightly-58.0a1.20171004220309.tar.bz2 with bsdtar
==> Starting pkgver()...
==> Updated version: firefox-always-nightly 58.0a1.20171004220309-1
==> Sources are ready.
:: failed to verify integrity or prepare firefox-always-nightly package

passcod commented on 2017-10-02 03:42

@darkgeek I've just gotten the same error on a different package, and it stemmed from a bad pacaur cache. `rm -rf ~/.cache/pacaur/package-name` does the trick.

passcod commented on 2017-09-24 20:24

@darkgeek: I can't reproduce, even with the latest pacaur from git, and it has worked with pacaur since mid-July. Are you using unusual pacaur flags or custom makepkg config? Otherwise it might be an intermittent issue to do with the releng checksums issue (still not fixed at Firefox's end!).

@lumn: Can't reproduce that. I've got Firefox and Nightly installed, and both programs have their own icon. Removing the WMClass line causes issues, see NTAuthority's comment on 2016-11-21 23:35.

darkgeek commented on 2017-09-24 14:29

Hi, I failed to install this package via pacaur with the following errors:

:: firefox-always-nightly package(s) failed to install.
:: ensure package version does not mismatch between .SRCINFO and PKGBUILD
:: ensure package name has a VCS suffix if this is a devel package

lumn commented on 2017-08-29 11:46

Could you please fix the issue, that normal Firefox uses Nightly icon on gnome desktop.
I believe it may be related with "StartupWMClass=Firefox" line in .desktop file.

passcod commented on 2017-08-11 06:39

Nowadays, yes. Originally I think I wrote this because the firefox-nightly package at one point didn't get updated for a time. So this was an experiment to remove the need for a maintainer to run a daily script that updates the package, and remove the dependency of the package's users on that maintainer's / script's continued presence.

It's actually only fairly recently that more people have been using it. For a long time I think it was just me, and maybe a couple others? Hard to tell.

From a perspective of "how successful has the experiment been?" I think it's gone and is going pretty good! With the exception of that Firefox RelEng checksum bug, I've only *had* to change the PKGBUILD a few times, for minor bugs and on two occurrences, because the upstream RelEng output changed.

All comments