Netrunner Repo Holding Back Firefox

On a freshly upgraded 14.1 Netrunner:

apt-cache policy firefox
  Installed: 34.0+build2-0ubuntu0.14.04.2~ppa2~trusty1
  Candidate: 34.0+build2-0ubuntu0.14.04.2~ppa2~trusty1
  Version table:
     35.0.1+build1-0ubuntu0.14.04.1 0
        500 trusty-updates/main i386 Packages
        500 trusty-security/main i386 Packages
 *** 34.0+build2-0ubuntu0.14.04.2~ppa2~trusty1 0
        700 trusty/main i386 Packages
        100 /var/lib/dpkg/status
     28.0+build2-0ubuntu2 0
        500 trusty/main i386 Packages

Is this intended? Perhaps a regression in FF35 I’m not aware of?


No regression, Firefox 35.0.1 should be showing, the problem is on your end:

Hi skyliner,

did you do a
sudo apt-get update
in yakuake or terminal and then try a
sudo apt-get upgrade again?

Yes, many times. Nevertheless I checked the repository causing the problem manually, just to make sure it wasn’t a cache problem on my end or something. The version listed is the same 34.0+build2 showing on my system.

Here you can see for yourself:

I checked other architectures too. The only ones that have a Firefox package are AMD64 and i386. The rest only mention a package called kmozillahelper which depends on firefox-kde-support.

Your right, the standard firefox is 34.0, remember this is a LTS release.

For Firefox-plasma 35.0.1 and Thunderbird-plasma 31.4.0, the Netrunner announcement tells you to add a repository:

sudo add-apt-repository ppa:moz-plasma/releases sudo apt-get update sudo apt-get install firefox-plasma sudo apt-get install thunderbird-plasma

Thanks, I didn’t know about the announcement. I added the PPA and installed Firefox.

One thing to note is that it is necessary to specify this PPA as the target or change the repo’s apt-pin priority before trying to install/upgrade FF; because the netrunner repo has a pin priority of 700 and the new ppa gets added with the default priority of 500. If you don’t do this you get a dependency error as the ppa tries to pull FF35 but the version in the stable repo gets precedence.

Um, the package name your supposed to install is different, would that not allow you to upgrade in and of itself?
firefox —> firefox-plasma

It’s different compared to Rolling: as with Launchpad, it didn’t work to have two versions of the same program with different names. So firefox-plasma is a meta-package that pulls in the patched firefox, which unfortunately is still also called firefox.

Ah, OK Then. :slight_smile:

Could you elaborate a little? How do you do that?

Did you try installing firefox-plasma already ? It should pull in the necessary packages.

I did and I got this message:

you are about to add the following PPA to your system:
 Mozilla stable releases

The firefox-plasma package should install patched firefox version and firefox-kde-support helper package automatically and keep them pinned.

sudo add-apt-repository ppa:moz-plasma/releases
sudo apt-get update
sudo apt-get install firefox-plasma thunderbird-plasma

and down the road this is how it ends:

sudo apt-get install firefox-plasma
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package firefox-plasma

So, how does skyliner force the system to look for the right package in the right place ?

Hmm did you ran apt-get update after enabling the ppa?

yes and this is the result:

The following packages have unmet dependencies:
 firefox-plasma : Depends: firefox (= 1000~35.0.1+build1-0ubuntu1~20150130.2144) but 34.0+build2-0ubuntu0.14.04.2~ppa2~trusty1 is to be installed
E: Unable to correct problems, you have held broken packages.

Then try installing firefox like so

sudo apt-get install firefox=1000~35.0.1+build1-0ubuntu1~20150130.2144 

Thanks! This time it works. 35.1 at last!
Future updates should show up in Muon Update Manager from now on? They seem to do so with Thunderbird 31.4 so far.

Yes they will come from that repo now.