Package Details: firefox-aurora 51.0a2.20161026004014-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: 311
Popularity: 1.493330
First Submitted: 2011-04-13 19:15
Last Updated: 2016-10-27 10:14

Latest Comments

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.

evotopid commented on 2016-10-27 11:07

@AlexTalker : On the Mozilla FTP server there are archive directories for the individual release versions so the kind of hash conflicts won't happen if you link to them instead of the binary that is updated daily. However updating the package gets a bit more tricky. Many Arch users (me included) don't want to add more repos to their system than they need.

You might want to check out my package "firefox-developer-de". I have a ruby script in the repo that I launch using a cron job that determines the most recent release and updates the PKGBUILD accordingly with the new hash. Caveat: so far it doesn't check signatures of the fetched file and just calculates the hash by downloading the file, I guess before wider deployment this might have to be fixed. (If you need further info you can write me an email.)

AlexTalker commented on 2016-10-27 10:20

What's wrong with u, folks?
I didn't said I wouldn't maintain this one. I just said I try to automatize it.

Sorry, I've got a little trouble, has to erase 'Template' package use by update script. Very sorry.

Yes, I wanna say that its better to use package from OpenSUSE build system than build manually 'cause here's will always be wrong hashes for some people 'cause I update the package around 4am, but new releases comes around 10am of local time. My laptop is usually offline all the day so I probably can't update to release as soon as it comes. I'll try to minimize that but most likely there's nothing to do. I just updated the package, sorry for interrupt.

Gharial commented on 2016-10-24 09:40

Please update the checksum for the 51.02.x86_64 tar in the PKGBUILD.

kahnpro commented on 2016-10-23 20:07

@AlexTalker I'm seconding this, the package right now does not build. If you no longer intend on maintaining this package then please orphan it and let someone else take over.

archaurwiki commented on 2016-10-02 22:02

@AlexTalker please orphan this package if you no longer intend to maintain it. @LA-MJ is also correct.

ianks commented on 2016-10-02 19:41

@AlexTalker, so we should not use this AUR package anymore? I think the firefox page should be updated as such if this is the case.

AlexTalker commented on 2016-10-01 16:14

Hello, folks!

It was long time for me till my patch for Open Build System was applied on finally, so now I moved building of the package to there.

So, if u used my previous repo, you can easily use new one

SigLevel = Never
Server =$arch

Web view to project is here:

Now I hope will no more broken hashsums and mess in logs since I rewrite my scripts to automatic update this and few other packages to use OBS instead of building locally and push to my own old repo.

I hope u enjoy this improvement.

Also git of the package now contains 2 files, & PKGBUILD.template which I use to generate PKGBUILD using fresh information from vendor sites. U can as well use it yourself, just run

Have a lucky day!

LA-MJ commented on 2016-10-01 10:11

what's with the horrific mess that is the latest commits to this package?

AlexTalker commented on 2016-09-25 13:04

@growler sad, AFAIK .SRCINFO is updated right after successful building of package with makepkg(i did automatize the process), so I really don't know what could mismatch... and you show error output, please?

All comments