You are not logged in.
Good morning.
So, as you could have guessed from the title, Firefox Aurora, and, likely, other Firefox versions as well, are unable to to updated via in-build Firefox updater if they were installed through Arch User Repository, being stuck on "Connecting to the update server", as depicted below:
http://i.imgur.com/7HbtUYi.png
Tool that was used to install the package is yaourt, no PKGBUILD or firefox.conf modifications were made.
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by VladimirVilimaitis (2014-08-18 15:36:12)
Offline
Can the versions from the official repository update themselves?
Offline
Aurora is in one of the unofficial repos.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I feel rather silly, the version I have installed comes from local repository, not AUR.
Furthermore, for some reason, now PacmanXG that Firefox version is indeed 33.0a2. How can this be true, though, if the installer obviously haven't updated anything, and pacman -Syu did not output Firefox as an updated package? Now I am more curious as to why the issue was caused initially, since it is no longer present.
Offline
Firefox is currently at 31.0-1 and Aurora is at 33.0a2. What local repository are you using?
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Check pacman's log to see when these packages when last updated.
Offline
Check pacman's log to see when these packages when last updated.
[2014-08-18 02:57] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-linux/PKGDEST.2r4/firefox-aurora-33.0a2.20140817004001-1-i686.pkg.tar.xz'
[2014-08-18 02:57] [PACMAN] installed firefox-aurora (33.0a2.20140817004001-1)Weird, so the version I have installed initially was, in fact, 33.0a2.
Why the hell then I was offered to perform an update which would not update my system, then? Anyone had similar issues? Is it a bug which should be reported to Firefox team?
Last edited by VladimirVilimaitis (2014-08-18 21:10:41)
Offline
And apparently I am still getting them, what the hell:
-- Stop posting oversized screenshots.
-- Read the link I edited into your first post. I'm not your mother; make some sort of effort so that I don't have to keep following you around cleaning up after you.
Last edited by jasonwryan (2014-08-18 22:03:56)
Offline
karol wrote:Check pacman's log to see when these packages when last updated.
[2014-08-18 02:57] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-linux/PKGDEST.2r4/firefox-aurora-33.0a2.20140817004001-1-i686.pkg.tar.xz' [2014-08-18 02:57] [PACMAN] installed firefox-aurora (33.0a2.20140817004001-1)Weird, so the version I have installed initially was, in fact, 33.0a2.
Why the hell then I was offered to perform an update which would not update my system, then? Anyone had similar issues? Is it a bug which should be reported to Firefox team?
You used AUR by using yaourt.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
The internal updater is for the case where you manually download a build from mozilla.org and unpack it into your home dir. The other option is a distro-provided build that's installed system-wide and updated via the package manager (such a build will have the internal updater disabled at compile-time).
What you did, have the package manger download a mozilla.org build and install it system-wide, gives you conflicting update mechanisms. What the PKGBUILDs in AUR should do is disable the internal updater by creating a ${pkgdir}/opt/firefox/browser/defaults/preferences/archlinux.js that contains
pref("app.update.auto", false);
pref("app.update.enabled", false);Offline
Maybe it wants to install today's build? I don't know how aurora updates work. If the internal update is still broken for you, update it with pacman.
heftig provides nightly builds in his unofficial repository.
Offline
The internal updater is for the case where you manually download a build from mozilla.org and unpack it into your home dir. The other option is a distro-provided build that's installed system-wide and updated via the package manager (such a build will have the internal updater disabled at compile-time).
What you did, have the package manger download a mozilla.org build and install it system-wide, gives you conflicting update mechanisms. What the PKGBUILDs in AUR should do is disable the internal updater by creating a ${pkgdir}/opt/firefox/browser/defaults/preferences/archlinux.js that contains
pref("app.update.auto", false); pref("app.update.enabled", false);
Thanks, done it.
This ends the thread, I assume.
I think that it would be wonderful if package maintainers on AUR implemented this so no other user would have similar errors, but I am not explicitly concerned about it.
Offline