Stevo wrote:New stable update to 34.0.5 now in the test CR, along with updated language packs. . . .

Stevo,
I usually do not have the testing repo enabled; to get this package I did enable it in Synaptic, reloaded and the latest (actually the only) version I'm seeing for Firefox is
28.0~mozillabinaries-1mcr120+1 (mepis)

GPG error: http://main.mepis-deb.org mepis12cr Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CA321713B07EE13GPG error: http://main.mepis-deb.org mepis12cr Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CA321713B07EE13Failed to fetch http://main.mepis-deb.org/mepiscr/testrepo/dists/mepis12cr/testrepo/binary-i386/Packages 404 Not Found
Some index files failed to download. They have been ignored, or old ones used instead.

I know about the public key, that's not relevent.
So: is the problem due to

Right you are, Mr. M!
I had the relevant wiki page before me, but in my dotage apparently failed to notice the text change (compared to the default WW put in) on the last word in the repo list.
Thanks! FF 3 has installed faultlessly, picking up all my Iceweasel prefs & even the open tabs from my current/previous session before the install.

One potential problem: the FF install killed my "iceweasel." This was not my fault, and if the "Arctic Environmental Wildlife Defense Army" comes after me, I'm shifting the blame!!

I was somewhat surprised that the MX Package Manager would remove Iceweasel. I usually install Firefox using the kmathern script. It installs it in /opt (from memory) and it would leave Iceweasel if memory serves. I couldn't use both at the same time so it wasn't a 'feature' that I needed. I have Iceweasel still installed but I've never got Firefox closed to see if it'd work. I should go ahead an remove it. But I don't care about the space, and there's the possibility that Preferences would be lost. Anyone know for sure?

I installed Firefox manually this time. I'd used the MX Package Manager in a test install. So I knew what to expect. Things like disabling the back-ports repository before doing an upgrade. But needing it enabled to do some of the things that I wanted to do. Easy enough to change. I've made it a habit to check Settings/Preferences and Settings/Repositories when I open Synaptic. Saves a lot of problems as I know exactly what's going to be looked at and made available.
(When I'm testing I put /var/cache/apt/Archives on a FlashDrive. Saves a lot of downloading when testing.)

Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

lucky9 wrote:I was somewhat surprised that the MX Package Manager would remove Iceweasel. I usually install Firefox using the kmathern script. It installs it in /opt (from memory) and it would leave Iceweasel if memory serves. ...

The CR firefox package removes iceweasel because of the way the dependencies are in the control file:

Per m_pav's recommendation, we decided to put the new releases straight into the main CR, after the packager tests for installation and usability. After all, this is what you'd get if you did the straight upgrade from Mozilla from the nag screen.