FF 36.0 is causing a hang for me when I load a page with Firebug or the built-in debugger open. On Windows, the FF updater almost immediately allowed me to directly download FF 36.0.1 which seemed to fix that issue, but here it is more than 2.5 weeks after that and OpenSUSE isn’t pushing that update through apper/Software Update. Why?
36.0.4 is in -test so I’m guessing they’ll release it “soon”.
I just prefer to use the mozilla repo myself since they seem to take their time before releasing updates in the “stable update” repo.
Because they really don’t care about their users.
Critical security vulnerabilities were disclosed to Mozilla and fixed immediately, but here we wait.
Meanwhile my Kubuntu has already updated.
On Tue, 24 Mar 2015 20:16:02 +0000, CountBakula wrote:
> Why?
You’d have to ask the maintainer, but chances are that the maintainer has
other things that they do besides package and test Firefox, so it’s
probably a question of workload.
You can be sure that it’s not because they think users are entertained by
waiting. They’ll push it into the channel when they feel it’s ready.
I’m sure you wouldn’t want them to just throw it out there and have it
break other stuff.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
You can always install it from the Mozilla repo.
Kubuntu in general relies much less on modular repositories than SUSE does.
On Wed, 25 Mar 2015 16:36:01 +0000, rafter22 wrote:
> Because they really don’t care about their users.
>
> Critical security vulnerabilities were disclosed to Mozilla and fixed
> immediately, but here we wait.
>
> Meanwhile my Kubuntu has already updated.
Apples and oranges with different distros. If you’re not going to
contribute anything useful to the discussion, you’re welcome to find
another forum.
Trolling like this (and it is trolling) is not acceptable here.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
https://en.opensuse.org/Additional_package_repositories#Mozilla
You can add the repo and update to the newest version of Firefox.
To add the repo on 13.2:
zypper ar -f http://download.opensuse.org/repositories/mozilla/openSUSE_13.2/ Mozilla
The output should be
zypper ar -f http://download.opensuse.org/repositories/mozilla/openSUSE_13.2/ Mozilla
Adding repository ‘Mozilla’ …[done]
Repository ‘Mozilla’ successfully added
Enabled : Yes
Autorefresh : Yes
GPG check : Yes
URI : http://download.opensuse.org/repositories/mozilla/openSUSE_13.2/
Then refresh your repository list with
zypper ref
and accept the Key.
zypper ref
Retrieving repository ‘Mozilla’ metadata ----------------------------------------------------------------------------------]
New repository or package signing key received:
Repository: Mozilla
Key Name: mozilla OBS Project <mozilla@build.opensuse.org>
Key Fingerprint: AAA53190 5D829BDC BE4D5169 026B47F3 766DA614
Key Created: Thu Dec 18 10:12:55 2014
Key Expires: Sat Feb 25 09:12:55 2017
Rpm Name: gpg-pubkey-766da614-5492c4c7Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a
Retrieving repository ‘Mozilla’ metadata …[done]
Building repository ‘Mozilla’ cache …[done]
Repository ‘Main Repository (OSS)’ is up to date.
Repository ‘Main Update Repository’ is up to date.
Repository ‘openSUSE-13.2-0’ is up to date.
Repository ‘packman’ is up to date.
Repository ‘security’ is up to date.
All repositories have been refreshed.
Once that’s done, go to YaST -> Software Management. Search for “Firefox”, click on it once, and then click the tab called “Versions”. Select the latest version available at the Mozilla repo. Here’s a reference Image:
http://s1.postimg.org/tji77buzj/snapshot1.png
Then Click ACCEPT. Note that you’ll be prompted to switch vendors for “mozilla-nspr”. Don’t panic, just select the option to switch vendors, from openSUSE to Mozilla.
http://s17.postimg.org/588uz5clb/snapshot2.png
You can see now that I have the latest Firefox
http://s23.postimg.org/7upsk8tiz/snapshot3.png
Regards,
Junior
MozillaFirefox-36.0.4 was released today (or yesterday, I didn’t check when my rsync picked it up)
I just finished installing it.
My opinion: I have no problem with the opensuse updating. I figure that the delay is used for testing to make sure that everything still works. I do not run firefox as root, so the risks of delay seem small.
Prompt update is more important for the Windows world where many people run as Administrator. But I have not updated my Windows system either (I login there as a limited user, except when I need to do Admin stuff).
First, i know about the different repos and the handling to test before
to release. Therefore i have no problems with it but i think there be
some points to be worth to think about it.
-
I use Firefox at work under windows too and since some versions
there is a problem that early after a x.0 version you get a x.1 or x.2
because they have bugs (sometimes only under windows). So from my view
if the version jump from at example 35.x to 36.0 than i enjoy very
much that the opensuse team take his time to test it
-
36.0.4 get released at 21-Mar-2015 in the mozilla repo and i got it
at 26-Mar-2015. Perhaps i could be a nice idea for updates as from 36.0
to 36.0.4 to reduce the time. But only if it is possible. -
There is a cosmetic problem with using the mozilla repo because
the package number is even lower as in the normal repo (normal repo:
36.0.4-18.1 / mozilla repo: 36.0.4-1.1). It would be nice if the
mozilla repo could have the same or higher numbers. But again only if
it is possible.
The numbers you’re talking about are revision numbers. A higher revision number doesn’t mean a newer version of the program.
At the time I responded to this thread the default Firefox was 36.0.1, while the one at Mozilla’s repo was 36.0.4. Although I don’t use Mozilla’s repo myself, I’d recommend people to stick with it if they REALLY need something that’s not being pushed to the main OSS repo (which from my perspective is very rare).
On Sat, 28 Mar 2015 15:26:01 GMT Junior s2 Camila wrote:
> The numbers you’re talking about are revision numbers. A higher
> revision number doesn’t mean a newer version of the program.
Sure that is why i called it cosmetic und this happens to me because i
used a lower priority for the mozilla repo. Therefore i see a info about
this situation in the first lines of a “zypper lu” oder a “zypper up”
if both repos have the same version but with different revision
numbers. I know this is nothing bad