Package Details: firefox-developer 54.0a2.20170402-1

Git Clone URL: https://aur.archlinux.org/firefox-developer.git (read-only)
Package Base: firefox-developer
Description: Standalone web browser from mozilla.org, developer build
Upstream URL: http://www.mozilla.org/firefox/developer
Licenses: GPL, MPL, LGPL
Submitter: jnbek
Maintainer: jnbek
Last Packager: jnbek
Votes: 370
Popularity: 9.543243
First Submitted: 2015-11-26 17:14
Last Updated: 2017-04-16 00:24

Pinned Comments

ArchangeGabriel commented on 2017-04-04 00:37

For PGP errors: it’s a CDN issue. See https://bugzilla.mozilla.org/show_bug.cgi?id=1336732 (and eventually upvote it if you already have an account there — but don’t create one just for this).

Latest Comments

4nduril commented on 2017-04-26 08:31

I have read the solution for the PGP error but the verfication process says that the public key 1C69C4E55E9905DB is unknown (so not a bad signature). What do I have to do?

EDIT: Nevermind. My trustdb had some issue. I tried to import the missing key with gpg --receive-keys and then it told me there was an issue and how to repair it.

ArchangeGabriel commented on 2017-04-24 18:43

@undu: What issue do you have with the current .SRCINFO? If it’s pacaur, there is nothing that can be done here.

Regarding the update of the pkgver daily, this is non-sensical. It’s on the user end that should be decided how often to update VCS-like packages on their system. They are tools on the AUR to help you update automatically such packages at given (an individual if you want) frequency.

undu commented on 2017-04-24 09:36

Can at least a new revision with an updated, working .SRCINFO be released?

And about "It does not make sense to run around 5 times a day to manually update the pkgver()."

You're right, but there are automated ways of doing it. That's why an alternative package, "firefox-dev" appeared.

ArchangeGabriel commented on 2017-04-19 23:41

Anyway, things might be moving here as of today: https://www.ghacks.net/2017/04/16/firefox-aurora-end/

jnbek commented on 2017-04-19 21:35

@denvit, please stop marking this out of date, the pkgbuild only needs to be marked out of date when a new Major version is released... As in... as of today, the major version is 54, it becomes out of date with the major version becomes 55. The GPG checks and pkgver() function take care of ensuring that the build date is updated in the text file, makepkg sets that version for the resulting package. It does not make sense to run around 5 times a day to manually update the pkgver(). If, when 55.0a2 releases and I haven't yet updated the pkgbuild, then and only then is it appropriate to mark it out of date. Thank you for your cooperation.

r3b311i0n commented on 2017-04-19 17:44

@Firefoxic see the workaround posted by ArchangeGabriel below.

Firefoxic commented on 2017-04-19 17:13

I still do not understand what I need to do when PGP error.

TheWarden commented on 2017-04-18 13:35

Installing package returns the following "firefox-developer package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD".

The ".SRCINFO" file was not updated with the correct packaged version.
Update .SRCINFO file as follows.

pkgver = 54.0a2.20170418

Rebuild package and install the updated package.

ArchangeGabriel commented on 2017-04-15 18:24

Hum indeed, this is because of a remaining ${_pkgname} in the command icon.

sgtpep commented on 2017-04-13 18:37

Icon names are mangled:
firefox-developer /usr/share/icons/hicolor/16x16/apps/.png
firefox-developer /usr/share/icons/hicolor/32x32/apps/.png
firefox-developer /usr/share/icons/hicolor/48x48/apps/.png

All comments