Package Details: firefox-aurora 52.0a2.20170123004004-1

Git Clone URL: (read-only)
Package Base: firefox-aurora
Description: Firefox Aurora channel - Nightly build
Upstream URL:
Keywords: firefox mozilla
Licenses: GPL, MPL, LGPL
Submitter: L42y
Maintainer: AlexTalker
Last Packager: AlexTalker
Votes: 313
Popularity: 1.926994
First Submitted: 2011-04-13 19:15
Last Updated: 2017-01-23 16:28

Latest Comments

kahnpro commented on 2016-11-23 01:38

Which day's build did you look at? Today's checksums are right, but at the time of writing I was using the Nov 19th build. I'm not using any custom PKGBUILD, I took it from a fresh clone of the git repo linked above. Steps to reproduce:

git clone
git checkout ff7f628b33632f775c3a2d58626f862c82b3ceb6
cd firefox-aurora
makepkg PKGBUILD

It seems like the Nov 20-22 builds are fine, but you might want to look into why it broke for that day's build.

AlexTalker commented on 2016-11-21 21:00

As always, check sums are right. IDK what is your problem but will appreciate if next time u show me PKGBUILD on which your building goes wrong.

kahnpro commented on 2016-11-20 16:55

Seems like the latest package has bad signatures. Won't install from pacaur after clearing cache... downloading the snapshot tar.gz and running makepkg from inside the folder also fails.

macheath commented on 2016-11-16 06:35

Sound stopped working without pulseaudio. Anyone has workwaround using alsa?

kahnpro commented on 2016-11-13 03:52

@evotopid You're absolutely right, I'm using pacaur and it's caching stuff in $HOME/.cache/pacaur/firefox-aurora. Removed this now it's able to verify and build the package. Thanks!

AlexTalker commented on 2016-11-12 18:16

@evotopid is right, I will think about integrate buildid in tarball name, but as I remember this could cause problems with obs. Will check soon.

evotopid commented on 2016-11-11 21:09

@kahnpro: Are you by any chance trying to update the package using an AUR helper which keeps the files around after building a package? In that case make sure the file is deleted when updating the package. I guess you should be able to configure such behavior in your AUR helper but you can also delete such a directory manually.

The PKGBUILD could also be updated to save the source file to a version dependent name. This fixes the problem for many users – though this is mostly about fixing a flaw in AUR helpers., some AUR helpers will accumulate quite some mass of files over time (I just checked mine and it's 3.9GB of files I don't need).

kahnpro commented on 2016-11-11 19:19

It still doesn't work.

==> Validating source_x86_64 files with sha512sums...
firefox-51.0a2.en-US.linux-x86_64.tar.bz2 ... FAILED
==> ERROR: One or more files did not pass the validity check!

AlexTalker commented on 2016-10-28 10:05

@evotopid I rewrite generator for this package with simple traversal starting from to daily release. No more broken hashsums :)))

AlexTalker commented on 2016-10-27 11:16

@evotopid Hello, thank you, I never thought about that :(
You script seems very clear to me and I think I'll find some time on holiday to fix mine that way.
By the way, I think a bit that add `git commit` and such things in PKGBUILD update generator is not very clear(since if ppl want to use it, the'll not need it usually). I cut that logic away in few shell scripts which keep abstraction around the whole updating, that's why only makes new PKGBUILD by template. But, that's question of code style and architecture more.
Thanks again for giving me the tip.
Also, u can use hashsums from the same directory as tarball, just one more request.

All comments