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.
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.
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.
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 ?
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.