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: 16
Popularity: 4.461975
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-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.

ibrokemypie commented on 2017-08-11 06:18

What is the actual benefit of using this version over the firefox-nightly package? Is it just more immediate updates?

passcod commented on 2017-08-10 23:34

Version bumps are every "5 to 8 weeks" [1], let's pick the midpoint at 6.5, (100-57)*6.5/52 = 5.375. But yes, whichever way you figure it, it's in quite a few years, and bumping it early or right on time doesn't particularly matter in terms of user experience.

Is there something you were wondering about related to that, or was it just curiosity?


Det commented on 2017-08-10 13:33

I calculated it's 6... so....

passcod commented on 2017-08-10 13:00

I'll bump the version up another hundred I suppose. If it's still here. v100 is in about five years, that's quite a bit of time.

Det commented on 2017-08-10 03:54

What happens when trunk gets bumped to 100.0a1?

passcod commented on 2017-07-19 10:57

Right, I updated the dependencies and recommendations from the upstream PKGBUILD. I also revised the build so it works with pacaur. It works fine without skipping checksums nowadays, but the RelEng bug hasn't been closed so I can't promise it won't break sometimes until that happens ;)

jtojnar commented on 2017-04-21 00:09

Seems to work even without gtk2.

passcod commented on 2017-03-17 00:38

Right, so, the problem is definetly not with this package... it's with the checksums mozilla provides us. For some reason*, the checksums file we depend on to check downloads gets out of sync with the actual files available. So half the time there's a checksum error, and then if you retry it a few hours to a day later, it will work. Or not. It depends on if the checksums file is up-to-date.

The entire point of checksums is to check integrity or downloaded, so running mksrcinfo in pkgver() would completely defeat the purpose: we'd be checking that files we downloaded match the checksum we compute from those files we downloaded.

*I say "for some reason"… the reason is this: Due to high load in the build servers, the checksum-computing jobs are lagging behind, so we're getting new builds with yesterday's checksums.

Until that bug is resolved, you do need to --skipchecksum… but check back regularly to figure out when you can omit that option.

Smile4ever commented on 2017-03-16 19:28

To install this package you need
yaourt --m-arg "--skipchecksums" -Sb firefox-always-nightly

All comments