I’m much given to wondering why Firefox is being held back.
I trust there is enough information from my humble rig to help me out with a feasible explanation.
# zypper up
Loading repository data...
Reading installed packages...
The following 6 package updates will NOT be installed:
MozillaFirefox MozillaFirefox-translations-common dragonplayer kgpg konsole konsole-part
zypper if MozillaFirefox
Loading repository data...
Reading installed packages...
Information for package MozillaFirefox:
---------------------------------------
Repository: openSUSE-Leap-42.1-Update
Name: MozillaFirefox
Version: 42.0-3.5
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: out-of-date (version 41.0.2-1.2 installed)
Installed Size: 96.0 MiB
Summary: Mozilla Firefox Web Browser
Description:
Mozilla Firefox is a standalone web browser, designed for standards
compliance and performance. Its functionality can be enhanced via a
plethora of extensions.
A fresh install? Installed from dvd a couple of weeks ago. Oh I know what, do you mean have I upgraded from 13.1 to 13.2 to Leap? No.
A strange thing is happening now with your suggestion to use zypper up MozillaFirefox:
# zypper up MozillaFirefox
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 6 NEW packages are going to be installed:
gstreamer-fluendo-mp3 java-1_7_0-openjdk java-1_7_0-openjdk-headless java-1_7_0-openjdk-plugin lcms2 timezone-java
The following 2 packages are going to be upgraded:
MozillaFirefox MozillaFirefox-translations-common
2 packages to upgrade, 6 new.
Overall download size: 91.8 MiB. Already cached: 1.9 MiB. After the operation, additional 85.3 MiB will be used.
Continue? [y/n/? shows all options] (y):
I mean to say - new packages? These were not mentioned during todays zypper ref, zypper lu and finally zypper up.
I can think of two reasons. Vendor change (this is known to happen in the past with updates, at least in TW) and optional update. As explicit installation works, I tend to think this update is marked as optional.
I think that’s the way that the Gnome update applet works. It downloads updates in the background, but doesn’t install them until you say so.
As for the new packages – those are actually part of a standard install, except that they are not on the install DVD. So they are intended to be installed later, such as when you do updates or install something from the repos.
However, I’m not sure why Firefox did not update initially. I did not run into that problem here.