Install The Newest Firefox ppa with command "add-apt-repository" (9.10 & above)

[lovinglinux]

OMG Opera :-(

I must admit I never really gave Opera any attention and I was unaware of it's capabilities. But since Opera 11 supports extensions, I decided to give it a try and port some of my extensions to it. After a month using it for real, I must admit is a great browser and I'm really enjoying it. I still miss some Firefox extensions tho, because Opera extension framework is similar to Chrome and thus not very powerful like Firefox. But after exploring Opera, I was able to configure it to my liking and my workflow is going really well with it. Plus, it looks gorgeous with the theme I'm using.

I'm still using Firefox for development tho. At least I'm not using Chrome, otherwise people could think I went nuts :). However, I'm also porting extension to Chrome, because they are very similar to Opera and don't require much work to make them compatible.


I was once tempted to try it on my HTC Desire but the EULA is execrable.

Reading through it I came to the conclusion they would own the soul of my first male born heir, among other things...

And its proprietary.

Well, being proprietary is one of the major drawbacks. However, extensions can be released as open source, which is the most important factor for me.

The EULA looks like standard proprietary software license agreement or am I missing something?

[Enigmapond]

Just as a short testimonial, I really LUV the new FF! It's quick and has a few great features and the tab placement it just wonderful. The only problem is with some extensions but that will be sorted out when it's released, I guess. Thanks for all the work on this. :D

[hawthornso23]

Looks like there have been some nasty regressions in firefoxb8pre over the last few days. I'm seeing frequent orphaned processes that have to be killed with killall firefox-4.0-bin,sudden crashes for no apparent reason, and a bizarre bug whereby each click of the launcher would open two minefield instances. And if you try to report the issues via the help menu you get a snarky message telling you to update to firefox 4.0b7 first. Not useful when you are already running b8pre.

It was stable and nice. But a couple days back somebody broke something bigtime and they still havn't got it fixed. A shame - I was enjoying the HTML5 on youtube. Now I've had to switch back to Namoroka because Minefield is just too frustrating to use.

[SilverWave]

I...
Well, being proprietary is one of the major drawbacks. However, extensions can be released as open source, which is the most important factor for me.

The EULA looks like standard proprietary software license agreement or am I missing something?

Well it has been the first one I have actually read for some time tbh... but the stuff regarding 3rd party use of your info was a no-no for me.

In Mozilla I trust.

[SilverWave]

Just as a short testimonial, I really LUV the new FF! It's quick and has a few great features and the tab placement it just wonderful. The only problem is with some extensions but that will be sorted out when it's released, I guess. Thanks for all the work on this. :D

Yeah I am starting to like it as well.... it took some time as so much is changing.

I run 4 and 3.6 at the same time and I have changed 3.6 to more of a "4" look and feel.

Day to day most of my browsing is in 3.6 but gmail and Shelvelogger log I view in 4 with no problem.

As more extensions start working on 4 I will move more of my browsing and hopefully swap to mainly browsing with 4 sometime next year :-)

[SilverWave]

Looks like there have been some nasty regressions in firefoxb8pre over the last few days. I'm seeing frequent orphaned processes that have to be killed with killall firefox-4.0-bin,sudden crashes for no apparent reason, and a bizarre bug whereby each click of the launcher would open two minefield instances. And if you try to report the issues via the help menu you get a snarky message telling you to update to firefox 4.0b7 first. Not useful when you are already running b8pre.

It was stable and nice. But a couple days back somebody broke something bigtime and they still havn't got it fixed. A shame - I was enjoying the HTML5 on youtube. Now I've had to switch back to Namoroka because Minefield is just too frustrating to use.

Hmm have you tried the one I have in my Weekly testing PPA?

4.0~b8~hg20101127r58302+nobinonly-0ubuntu1~umd1~lucid

I am using that and I have no problems.

One Daily A Week #0 - Lucid (https://launchpad.net/%7Esilverwave/+archive/testing0)

sudo add-apt-repository ppa:silverwave/testing0

[SilverWave]

... However, there are still some blocking issues (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0:beta8+) and I haven't received any words about making my extensions compatible with beta 9 or RC yet, which usually happens a couple of days before the release. But I think the most important clue is that there aren't any candidates in the nightly ftp directory (ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/).


Mozilla (http://www.mozilla.org/) Project has confirmed that it plans to ship the eighth beta for version 4 of its open source Firefox web browser on Tuesday, the 7th of December. It looks as if they have only sipped a week, nice to see them back on track.

http://www.h-online.com/open/news/item/Mozilla-Firefox-4-Beta-8-coming-next-Tuesday-1145550.html

P.S.

"Mozilla says that Firefox 4 Beta 8 will ship at the same time as Firefox 4 Beta 3 for Mobile devices"

Excellent.

[SilverWave]

Changes for the versions:
3.6.14~hg20101125r34782+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20101203r34803+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b8~hg20101127r58302+nobinonly-0ubuntu1~umd1~lucid
4.0~b8~hg20101204r58593+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

Changes for the versions:
3.6.14~hg20101203r34803+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b8~hg20101204r58593+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

Changes for the versions:
3.6.14~hg20101203r34803+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20101210r34811+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b8~hg20101204r58593+nobinonly-0ubuntu1~umd1~lucid
4.0~b8~hg20101210r59052+nobinonly-0ubuntu1~umd1~lucid

The beta8 has been delayed again now probably sometime in December.

[SilverWave]

The latest FF4b8pre updates your back end sync data (held on Mozilla servers).

The problem is that any FF3.6 machines still on 1.5.1 cant read the new format yet.

So you wont be able to sync with your FF3.6 machines until they release an update.

Joy :sad:

__________________


Upon upgrading to Sync 1.5.1, sync suddenly
refuses to sync (“Error While Syncing”) and demands to upgrade to the latest version (“You need to update Firefox Sync to continue syncing your data”). Problem is, 1.5.1 ***IS*** the latest version!!!

Latest version of sync demands to be upgraded to latest version... WTF?? (https://groups.google.com/group/mozilla-labs-weave/browse_thread/thread/10cbe6e6bf96ee63?hide_quotes=no)



Mike Connor
First off, I'm sorry this has been confusing for you and your friends.
Storage format changes, while rare, are occasionally necessary, and
sometimes are incompatible. This is something that used to happen
with every version released, but we've only changed things twice since
February, and this is anticipated to be the final incompatible change
we make to Sync. The plan is to release stable builds at the same
time for all affected products. Unfortunately, we did not communicate
this well to users of nightly and/or developer builds, who would hit
this sooner, and in less of a controlled fashion.

To clarify what you're seeing here, I suspect that at least one of
your clients is running a nightly build of Firefox, or a developer
channel version of Firefox Sync (1.6b2), which would include the
newest version of sync, which uses a simpler and more performant
crypto component, as well as some internal changes necessary to
support some near-future performance work. Again, this is expected to
be the last compatibility-breaking change, but it was expected (and,
indeed, the clients check for this type of change before syncing).

[SilverWave]

hmm found this but not tested yet!

Latest Update: Firefox Sync 1.6b4 (December 11, 2010) (https://services.mozilla.com/sync/updated/?version=1.5&channel=dev)

time to take a backup me thinks ;-)

Recent changes (https://services.mozilla.com/sync/updated/changelog.html)



(1.6b4) Fix reliability issues in crypto procedures and key caching
(1.6b3) Better error handling and recovery for various key errors
(1.6b3) Fix HKDF implementation in crypto
(1.6b2) Performance and correctness fixes
(1.6b1) Employ a simpler crypto infrastructure. This provides a newer storage format and requires that all computers connected to the account are upgraded to this verfsion of Firefox Sync or higher.
(1.6b1) Several performance improvements.
(1.6b1) Improved preference sync.
(1.5.1b3) Overlong wizard page titles (in translations) are now wrapped over multiple lines
(1.5.1b2) Re-enable locales, not all strings are translated, so you may see en-US equivalents
(1.5.1b2) History sync now ignores invalid entries that sometimes appear
(1.5b7) Fixed a bug that prevented some form data generated by Firefox 4 from being synced.
(1.5b7) Fixed several UI warts in the setup wizard.
(1.5b7) Make use of plural forms where appropriate.
(1.5b6) Implement a newer storage format. Note: This requires all computers connected to the account are upgraded to this version of Firefox Sync or higher.
(1.5b6) Show a strength meter for custom Sync Keys
(1.5b6) Removed option to email the Sync Key
(1.5b6) Improved localization of the quota dialog
(1.5b5) Updated the Fennec UI to support email address based accounts and dashed Sync Keys
(1.5b5) Provide explanatory text for the Sync Key artifact and email
(1.5b5) Fixed an issue that prevented users from signing up
(1.5b4) Fixed UI issues in the setup wizard
(1.5b3) Sync no longer asks for a user name on sign up, just an email address
(1.5b3) Sync now syncs which engines are enabled across all clients
(1.5b3) Added support for server-side quota
(1.5b3) Improved default client name on mobile devices
(1.5b3) Fixed UI issues caused by the changes to the setup wizard
(1.5b2) Improved setup wizard
(1.5b1) Enable bookmark and tabs sync on Seamonkey
(1.5b1) Memory and performance improvements

[SilverWave]

hmm found this but not tested yet!

Latest Update: Firefox Sync 1.6b4 (December 11, 2010) (https://services.mozilla.com/sync/updated/?version=1.5&channel=dev)

time to take a backup me thinks ;-)

Well the install worked but then I received: Wrong Sync Key error... OK WTF!

The key here is not to panic ;-) looking at my working FF4.0b8 I knew I had a key just how to find it!

What's happened is that they have changed your sync key without telling you!

Oh bad Mozilla, bad Mozilla, no biscuit for you!

Anyway I did what you always do in a case like this and Googled it... here we go:

Your old Firefox Sync key is no good! (http://tech.mahesha.com/2010/12/07/your-old-firefox-sync-key-is-no-good/)


Once I figured that the Wrong Sync Key error was not because of broken Minefield, but because Minefield indeed changed my key, I could quickly bring all the other installations of Firefox in sync again.
All that needs to be done is, grab your new key like so:


Open Minefield (or Firefox) button → Options → Options (Which is Minefield (or Firefox) button → Preferences → Preferences in Linux).
Go to the Sync tab
Expand the Manage Account group
Click on the My Sync Key item
Copy/Print/Write down/Passpack your Sync Key displayed in the dialog that shows up

Then in the installation of Firefox where you get the Wrong Sync Key error, update the Sync Key with the new key. This pretty much involves resetting Sync information and setting it up anew, like so:


Open Minefield (or Firefox) button → Options → Options (Which is Minefield (or Firefox) button → Preferences → Preferences in Linux).
Go to the Sync tab




Go to the Wrong Sync key item and correct it.


WHOOT! Sync has now completed on my ff3.6.14pre!

[SilverWave]

Well this explains quite a lot about the key change.
[... (https://groups.google.com/group/mozilla-labs-weave/browse_thread/thread/10cbe6e6bf96ee63?hide_quotes=no)]the passphrase was previously used with PBKDF2 to generate an AES key.
Generating even stronger secrets was actually unnecessary, since we were converting to an AES key.
For new users, we now generate a 128-bit AES key directly, and existing users will have their passphrases converted as a one-off.
This is the same end level of security, since any extra entropy was lost in the conversion in the previous scheme.
In the future, the standard setup path will use J-PAKE to securely transfer credentials to new clients, rather than manually entering keys, so we feel the added length for all users is not a major problem. And this is the plan for J-PAKE:


Explore using J-PAKE to securely pass credentials to another device. (https://wiki.mozilla.org/Services/Sync/SyncKey/J-PAKE)

User Requirements



Setting up a new mobile device should only involve entering a short code on the desktop device
Secondary request, not a hard requirement, is that if the user has a mobile device, and is setting up a desktop device, that the flow is similar and still involves entering the key on the desktop

Desired User Flow



User chooses "quick setup" on new device
Device displays a setup key that contains both the initial secret and a channel ID
On a device that is authenticated, user chooses "add another device" and is prompted for that key
The two devices exchange messages to build the secure tunnel
The already-authenticated device passes all credentials (username/password/passphrase) to the new device
New device completes setup and starts syncing

[SilverWave]

Linux has the Firefox button in the nightly builds.
(http://forums.mozillazine.org/viewtopic.php?f=23&t=1951751&start=338) It has been there for at least a week now.
It IS very rough right now (It needs a lot of polish and styling), but it works well.
I think the initial plan for the Firefox button on Linux was to make it movable, but currently it isn't movable.

The Fx button is placed in the tabbar when you uncheck "Menubar" after a right-click.
The Title of the page is still displayed on Linux because firefox still uses your window manager's window decorations.
Linux will still display the page's title in Firefox 4 and their are no plans to change it.Heh I had missed this! Excelent :-)

It is easy to miss! It looks like a tab and its called Minefield.

[SilverWave]

[UPDATE] this is out of date go here instead:

Installing old extensions for use with Firefox: Addon Compatibility Reporter (http://ubuntuforums.org/showpost.php?p=10253879&postcount=291)
__________________


With FF4.0b8pre I think things are really starting to come together.

With this in mind I have started to look at small hacks to workaround compatibility issues with existing key Add-ons.

So that other users of the Latest Firefox can benefit I will add them to this post.

Warning: Use the attached Add-ons at your own risk, I have had no issues but YMMV. :-)
__________________

Using Minefield?
To allows extensions at AMO to be installed:

in about:config
Set:
general.useragent.compatMode.firefox
To true.
__________________

Working Add-ons List



Adblock Plus 1.3.2



Barlesque 1.14

Note: Collapses the wide grey add-on bar into a neat set of add-on buttons





Download Statusbar 0.9.7.2



Link Target Display 1.7

Note: Bottom Left alternative to it being jammed into the right of the address bar..





Make Link 10.8



NewTabURL 2.2.0

Config: Set to https://encrypted.google.com/webhp?complete=1&hl=en





OptimizeGoogle 0.78.2



Places’ Full Titles 3.2.4

It will work for the bookmarks menu but not for the bookmarks toolbar (which is where I keep my RSS feeds). You will need to adjust the code manually - but it's not difficult. Inside your Firefox profile, navigate to extensions\{7bf7c1c3-d8e7-4020-ab38-a829c76693d5}\chrome\placesfulltitles\skin and open placesfulltitles.css in a text editor. Do a find-and-replace: replace all instances of bookmarksBarContent with PlacesToolbar and then close the file and restart Firefox. Great fix by Bas (https://addons.mozilla.org/en-US/firefox/user/61629/).





Reliby 1.5.0



RequestPolicy 0.5.16

Note: The Toolbar button is not working, use the Add-on Bar Button instead.





Stay-Open Menu 1.5.6



Tab Counter 1.8.7



Toolbar Buttons 0.6.0.8



Tree Style Tab 0.11.2010120903

Only the first style "Metal" is readable for me under Linux.
Right Click Menu over tabs seems not to be working, but a Right Click on the grey below the tabs, or on the "New Tab Plus", works OK.



__________________

Hacked Add-ons List



Locationbar² 1.0.5

maxVersion bumped to 4.*
Date: 2010.12.12
Notes: the new link URL-on-hover feature isn’t supported (so use Link Target Display).
Config: Double-click selects all; Grey Directories and file name; strong; on top.
Shows bread crumbs regardless of preferences.





Menu Editor 1.2.6

maxVersion bumped to 4.*
Date: 2010.12.12
CTRL+SHIFT+S brings up the Menu Editor Options dialogue.
I use this to hide a lot of the Main Context Menu(right click menu) items - you just toggle hide/unhide.
But there are 2 things I use it for that I cant do without.

Add a "Close tab" item just above "Back" in the right click menu.

Note that the "Close tab" that works is from the File Menu.


Add an "Undo Close Tab" item just below "Stop" in the right click menu.







nosquint-2.0.5

maxVersion bumped to 4.*
Date: 2010.12.12





Readability 1.2

maxVersion bumped to 4.*
Date: 2010.12.12





Shelve 1.22

maxVersion bumped to 4.*
Date: 2010.12.12



Built from source at GitHub.



__________________

Add-ons built-in to FF4.0



BarTab (https://philikon.wordpress.com/2010/11/10/firefox-4-0b7-updates/) 2.0 (Now a Built-in feature of FF)

To duplicate BarTab behaviour alter the following setting:
about:config







browser.sessionstore.max_concurrent_tabs
set
value = 0


Fission 1.0.9 (Waiting for this feature to land).

__________________

Non-Working Add-ons List



Boox 2.6 (Developer will update when he has time).



Informational Tab 0.3.2010062901 (Will be a built-in to Firefox, if not Developer will probably update).



Platypus 0.81 (Developer no longer maintaining this Add-on).

Save the Platypus script in FF3.6 and then export to FF4.0 until a fix is found.



__________________

Add-ons Awaiting Testing List



DownThemAll! (http://downthemall.net/) 1.1.10
Greasemonkey (http://www.greasespot.net/) 0.8.20100408.6
HTTPS-Everywhere (https://www.eff.org/https-everywhere) 0.9.2
Image Zoom (http://imagezoom.yellowgorilla.net/) 0.4.4
Linkification (http://yellow5.us/firefox/linkification/) 1.3.8
Pronounce (http://www.netgents.com/) 1.4
repagination (http://andreineculau.com/blog/2008/06/repagination/) 2006.4.5.1
SQLite Manager (http://sqlite-manager.googlecode.com/) 0.6.5

__________________

Tips

Web Console short cut:
CTRL+SHIFT+K and CTRL+R

https://arantius.com/misc/gm-nightly/
__________________

[libssd]

I have gone through this twice, to confirm the behavior I'm reporting with Ubuntu 10.04.

1. Added http://ppa.launchpad.net/ubuntu-mozi...ily/ppa/ubuntu to software sources
2. Installed Firefox 4.08b from this repository
3. The next time I applied software updates, Firefox 3.6.13 was replaced by Namaroka
4. Uninstalled Namaroka
5. De-activateed http://ppa.launchpad.net/ubuntu-mozi...ily/ppa/ubuntu (Synaptic)
6. Activate http://ppa.launchpad.net/silverwave/...month-1/ubuntu (Synaptic)
7. Uninstall firefox-4.0(Synaptic)
8. sudo apt-get update (terminal)
9. sudo apt-get install firefox-4.0 (terminal or synaptic, dependency errors):

firefox-4.0:
Depends: firefox-4.0-core (=4.0~b8~hg20101204r58593+nobinonly-0ubuntu1~umd1~lucid) but 4.0~b8~hg20101213r59154+nobinonly-0ubuntu1~umd1~lucid is to be installed

It's not that hard to re-install firefox-4.0 from the daily PPA, or to uninstall Namaroka and re-install firefox 3.6.13, just annoying, and subject to operator error if I don't watch updates closely.

[SilverWave]

I have gone through this twice, to confirm the behavior I'm reporting with Ubuntu 10.04.

1. Added http://ppa.launchpad.net/ubuntu-mozi...ily/ppa/ubuntu to software sources
2. Installed Firefox 4.08b from this repository
3. The next time I applied software updates, Firefox 3.6.13 was replaced by Namaroka
4. Uninstalled Namaroka
5. De-activateed http://ppa.launchpad.net/ubuntu-mozi...ily/ppa/ubuntu (Synaptic)
6. Activate http://ppa.launchpad.net/silverwave/...month-1/ubuntu (Synaptic)
7. Uninstall firefox-4.0(Synaptic)
8. sudo apt-get update (terminal)
9. sudo apt-get install firefox-4.0 (terminal or synaptic, dependency errors):

firefox-4.0:
Depends: firefox-4.0-core (=4.0~b8~hg20101204r58593+nobinonly-0ubuntu1~umd1~lucid) but 4.0~b8~hg20101213r59154+nobinonly-0ubuntu1~umd1~lucid is to be installed

It's not that hard to re-install firefox-4.0 from the daily PPA, or to uninstall Namaroka and re-install firefox 3.6.13, just annoying, and subject to operator error if I don't watch updates closely.

Hmm before #5, I would have uninstalled the Firefox 4.08b that you installed in #2. Then with things back to normal... I would have done #6 and then installed Firefox 4.08b from the silverwave PPA. [If that makes sense ;-)]

On your second point, with so many packages included in the ubuntu-mozilla-daily (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa?field.series_filter=) ppa it is way to easy to accidentally update the wrong one as you have found to your cost.
Hence why I created single package ppa's like silverwave/one-daily-a-month-1 in the first place, the same had thing had happened to me :-(.
Conversely with Firefox-4.0 - One Daily A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1) you can set it and forget it.

[libssd]

Hmm before #5, I would have uninstalled the Firefox 4.08b that you installed in #2. Then with things back to normal... I would have done #6 and then installed Firefox 4.08b from the silverwave PPA. [If that makes sense ;-)]
It makes sense, so I just tried that sequence of steps, but ended up with the same outcome.


On your second point, with so many packages included in the ubuntu-mozilla-daily (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa?field.series_filter=) ppa it is way to easy to accidentally update the wrong one as you have found to your cost.
Hence why I created single package ppa's like silverwave/one-daily-a-month-1 in the first place, the same had thing had happened to me :-(.
Yup. Been there, done that (more than once), which is why I'm trying to install from the silverwave PPA.


Conversely with Firefox-4.0 - One Daily A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1) you can set it and forget it.
That is my goal.

[SilverWave]

It makes sense, so I just tried that sequence of steps, but ended up with the same outcome.


Yup. Been there, done that (more than once), which is why I'm trying to install from the silverwave PPA.


That is my goal.

So if that didn't work... I would be tempted to uninstall any thing related to ff4.0 and then have a look through your software sources to ensure that nothing is still remaining.

Then:


sudo add-apt-repository ppa:silverwave/one-daily-a-month-1Followed by:


sudo apt-get update
sudo apt-get install firefox-4.0Best of luck.

P.S.

This command can be useful in trouble shooting as well...


apt-cache policy firefox-4.0

apt-cache policy firefox-4.0-core

[libssd]

So if that didn't work... I would be tempted to uninstall any thing related to ff4.0 and then have a look through your software sources to ensure that nothing is still remaining.

Then:


sudo add-apt-repository ppa:silverwave/one-daily-a-month-1Followed by:


sudo apt-get update
sudo apt-get install firefox-4.0Best of luck.

P.S.

This command can be useful in trouble shooting as well...


apt-cache policy firefox-4.0

apt-cache policy firefox-4.0-core

So if that didn't work... I would be tempted to uninstall any thing related to ff4.0 and then have a look through your software sources to ensure that nothing is still remaining.

I'm pretty sure that the first thing I did upon encountering the dependency error was to do a complete uninstall of firefox-4.0, followed by what you suggest; no dice.

I'm assuming that production firefox-4.0 will be released in the near future (less than 3 months), so I'm just going to let things ride until then. Both versions are functional, and I have both PPAs de-activated at the moment. Once a week or so I'll re-activate the firefox daily PPA, check for updates, and make sure to uncheck any FF 3 updates before applying them. This is more of an intellectual puzzle than a roadblock, and at the moment I'm tired of beating my head against the wall over this minor problem. ](*,)

Thanks again for all your suggestions.

[SilverWave]

I'm pretty sure that the first thing I did upon encountering the dependency error was to do a complete uninstall of firefox-4.0, followed by what you suggest; no dice.

I'm assuming that production firefox-4.0 will be released in the near future (less than 3 months), so I'm just going to let things ride until then. Both versions are functional, and I have both PPAs de-activated at the moment. Once a week or so I'll re-activate the firefox daily PPA, check for updates, and make sure to uncheck any FF 3 updates before applying them. This is more of an intellectual puzzle than a roadblock, and at the moment I'm tired of beating my head against the wall over this minor problem. ](*,)

Thanks again for all your suggestions.


Well as you say everything is working :-)

One thing that I have remembered that may help if you ever have an issue like this again is being able to Force a Version in Synaptic.

Note: I have Show packaging properties in the main window enabled (Edit > Preferences > General).
Also in "Columns and Fonts" you may find it helpfull to enable some more Columns.

How to Force a Version in Synaptic.

Select "firefox-4.0-core" in Synaptic

Click on the "Versions" tab to see the multible versions on offfer. There is a Note displayed at the botton of the screen:
"To install a version different from the default one, choose Package -> Force Version... from the menu."

This pops a dialogue box up which allows you to choose. :-)

[libssd]

Well as you say everything is working :-)

One thing that I have remembered that may help if you ever have an issue like this again is being able to Force a Version in Synaptic.

Note: I have Show packaging properties in the main window enabled (Edit > Preferences > General).
Also in "Columns and Fonts" you may find it helpful to enable some more Columns.

How to Force a Version in Synaptic.

Select "firefox-4.0-core" in Synaptic

Click on the "Versions" tab to see the multible versions on offfer. There is a Note displayed at the botton of the screen:
"To install a version different from the default one, choose Package -> Force Version... from the menu."

This pops a dialogue box up which allows you to choose. :-)
Thanks for another useful tip. I'm guessing you are referring to Synaptic in a release other than Lucid, as I am seeing a slightly different path to this option.

Mark package for installation > Package menu > Force Version

However, I noted this caution in the Synaptic help:


If you force a different version from the default one, errors in the dependency handling can occur.
But, while reading the help (what a novel idea: RTFM) I noted another option on that menu: Lock Version

Would this prevent Namaroka from being installed? "Debian only" in Synaptic help suggests not:


3.10. To Lock a Package to the Current Version (Debian only)

To lock a package to the current version follow these steps:

1. Select the package that you want to lock in the package list.

2. Choose Package ▸ Lock Version.

The Synaptic Package Manager will reload the package information.
You should now see that the menu item Package ▸ Lock Version is checked.

Update: Ah hah! "Lock Version" appears to do the trick. After locking Firefox 3.6, I re-activated the daily PPA, checked for updates, and none were offered for firefox, but were for firefox-4.0; ran the updates, and Namaroka was not installed.

Great discussion!

[SilverWave]

Thanks for another useful tip. I'm guessing you are referring to Synaptic in a release other than Lucid, as I am seeing a slightly different path to this option.

Mark package for installation > Package menu > Force Version

However, I noted this caution in the Synaptic help:


But, while reading the help (what a novel idea: RTFM) I noted another option on that menu: Lock Version

Would this prevent Namaroka from being installed? "Debian only" in Synaptic help suggests not:



Update: Ah hah! "Lock Version" appears to do the trick. After locking Firefox 3.6, I re-activated the daily PPA, checked for updates, and none were offered for firefox, but were for firefox-4.0; ran the updates, and Namaroka was not installed.

Great discussion!

Result! I think I was reluctant to use that option as I was sure I would forget which packages I had locked. ;-)

Great to see that you have found a solution. :-)

[SilverWave]

hmm found this but not tested yet!

Latest Update: Firefox Sync 1.6b4 (December 11, 2010) (https://services.mozilla.com/sync/updated/?version=1.5&channel=dev)

time to take a backup me thinks ;-)

Latest Update: Firefox Sync 1.6b5 (December 14, 2010)

Recent changes



(1.6b5) Backward-compatibility fix for old Sync Keys




(1.6b4) Fix reliability issues in crypto procedures and key caching
(1.6b3) Better error handling and recovery for various key errors
(1.6b3) Fix HKDF implementation in crypto
(1.6b2) Performance and correctness fixes
(1.6b1) Employ a simpler crypto infrastructure. This provides a newer storage format and requires that all computers connected to the account are upgraded to this verfsion of Firefox Sync or higher.
(1.6b1) Several performance improvements.
(1.6b1) Improved preference sync.

[SilverWave]

Download Firefox 4.0 Beta 8 Preview (http://news.softpedia.com/news/Download-Firefox-4-0-Beta-8-Preview-172892.shtml)


Early adopters can grab the Firefox 4.0 Beta 8 Candidate bits from Mozilla’s FTP servers (ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/) and test drive the release to get an idea of what’s coming in the Beta.

I'm updating the one-daily-a-week ppa's with the new ff-4.0b9pre's as we speak :D

[libssd]

Got it, and my strategy of checking the "don't update" box for ff 3.6+ worked -- no Namaroka. Unfortunately 4.09b breaks Adblock Plus 3.1.2, Better Privacy 1.48.3, and Blacksheep 1.5. The perils of a beta release.

[SilverWave]

Got it, and my strategy of checking the "don't update" box for ff 3.6+ worked -- no Namaroka. Unfortunately 4.09b breaks Adblock Plus 3.1.2, Better Privacy 1.48.3, and Blacksheep 1.5. The perils of a beta release.

Yes all looks OK in my testing on Lucid but as you say most add-on are reporting as non compatible... hmm I'll see what our options are.

[SilverWave]

Changes for the versions:
3.6.14~hg20101210r34811+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20101214r34821+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b8~hg20101210r59052+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20101215r59188+nobinonly-0ubuntu1~umd1~lucid

As FF4.0b8 is on its way to release here is the first Firefox 4.0b9pre!

[SilverWave]

3.6.14~hg20101214r34821+nobinonly-0ubuntu1~umd1~lucid

4.0~b9~hg20101215r59188+nobinonly-0ubuntu1~umd1~lucid

Have fun :-)

The FF4.0 development is getting to a stage where it is almost possible to use it day-today ;-)

[SilverWave]

...Unfortunately 4.09b breaks Adblock Plus 3.1.2, Better Privacy 1.48.3, and Blacksheep 1.5. The perils of a beta release.

All the big hitters are starting to be be updated as compatible... Adblock Plus is now OK.

This should help with the rest:

Add-on Compatibility Reporter 0.7 (https://addons.mozilla.org/en-US/firefox/addon/15003/?src=discovery-pane)

[lovinglinux]

All the big hitters are starting to be be updated as compatible... Adblock Plus is now OK.

Updating extensions already compatible with b8pre at this point (feature freeze) is just a matter of visiting the developer hub and changing the compatibility of the extension to the new version available in mozilla-central, in this case b9pre. However, Mozilla needs to add that version to the list, so we developers can apply the update. They only did that a couple of hours ago, so some extensions are still showing as compatible with b8pre. I just updated my extensions, but they still show as b8pre compatible because of the site cache. So you can expect that most popular extensions will be compatible later today.



Add-on Compatibility Reporter 0.7 (https://addons.mozilla.org/en-US/firefox/addon/15003/?src=discovery-pane)

That solves the problem for all extensions that are already compatible with beta 7. Be careful tho, with extensions that are only compatible with Firefox 3.6, because they can break things really bad, since Firefox 4 has major changes in the extension API. Launch the "Error Console" (CTRL+SHIFT+J) to check if any extension produces errors.

[SilverWave]

If you are using FF4.0b9 the changes to the statusbar can be a wrench...

After a lot of research I recommend these add-ons:



Barlesque (https://addons.mozilla.org/en-US/firefox/addon/259879/) 1.14

Collapses the wide grey add-on bar into a neat set of add-on buttons.
Can minimise to only an arrow until needed.


https://addons.mozilla.org/img/uploads/previews/full/51/51462.png?modified=1291322880
(Note: Barlesque is very new and so it could be regarded as possibly a little more risky than the others).



Link Target Display (https://addons.mozilla.org/en-US/firefox/addon/55724/) 1.7

Bottom Left alternative to it being jammed into the right of the Locationbar, only shows when needed.


https://addons.mozilla.org/img/uploads/previews/full/40/40370.png?modified=1262553214



Oh and I use Locationbar² (https://addons.mozilla.org/en-US/firefox/addon/4014/) 1.0.5

This turns off the Link in the Locationbar and puts emphasis on the domain to reduce spoofing risk.




https://addons.mozilla.org/img/uploads/previews/full/21/21090.png?modified=1211739738

Observations

I do agree with the the creation of an Add-on Bar, but it is too big as it stands.
Luckily I can use Barlesque to makes it perfect.

I cannot say I agree with the Link Target being jammed into the right of the Locationbar.
Again thanks to an Add-on we can avoid this problem until the devs correct it or change the implementation.
[update] WHOOT! Sanity has prevailed! The Devs have dumped this brain-dead idea.
Bug 541656 - Display hyperlink URLs at bottom of window (instead of right side of location bar) (https://bugzilla.mozilla.org/show_bug.cgi?id=541656)

[lovinglinux]

If you are using FF4.0b9 the changes to the statusbar can be a wrench...

After a lot of research I recommend these add-ons:



Barlesque (https://addons.mozilla.org/en-US/firefox/addon/259879/) 1.14
[LIST]
Collapses the wide grey add-on bar into a neat set of add-on buttons.
Can minimise to only an arrow until needed.


Awesome.

I also recommend Status-4-Evar (https://addons.mozilla.org/en-US/firefox/addon/235283/). Don't how it would behave with Barlesque tho.

[SilverWave]

Sometime soon after the beta 8 code freeze, the Places team will be merging the Places branch into mozilla-central. There are a lot of changes we’ve been working on, the most important of which is some major re-architecting how we store datahttp://shawnwilsher.com/archives/473

This just struck me as being a big change rather late in the day...

Under the hood speed-ups so maybe that explains it.

I suppose we are still in beta and this would not be a GUI change... so interesting.

[SilverWave]

Someone asked me if Firefox was still relevant and my take on the Firefox 4.0 changes... here is my response:



Firefox is an amazing browser but it was in danger of being eclipsed by chrome. I am particularly impressed by the way Mozilla have not shrank from taking the hard choices that were needed to meet this challenge.

1. A large part of Firefox's success is because of it extensions but the old system was causing some drag and would be an increasing burden in the future... so they have created a new architecture "JetPack" that will solve this. It addresses the main problem of extensions needing updating after each new Firefox version by providing a separate api and a new way of assigning permissions that looks to be very scalable.

2. Firefox Sync. This is the killer app atm for Firefox and enormously extends its relevance and usefulness working hand-in-hand with Firefox Mobile.

3. Firefox Mobile, basing it on 4.0 code and running it as a native application under Android is a master stroke and will pay huge dividends in the future. An incredibly ballsy move, bravo Mozilla.

4. Speed audits and rewrites of bottlenecks in the code. Some of this is yet to land IIRC e.g. the Places storage code.

5. HTML 5 support.

So yes Chrome was a disruptive change but Mozilla have used it a driver for renewing Firefox's direction and rearchitecturing the fundamentals that it is based on.

They will not reap all the rewards immediately, JetPack for instance is a more long term play, but Mozilla are punching well above their weight and serving their users and the open web well.

[SilverWave]

Well this is interesting...

Visualizing Firefox Plugins (http://eaves.ca/2010/12/17/visualizing-firefox-plugins-memory-consumption/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EavescaMozilla+%28eaves.ca+%C 2%BB+mozilla%29)

Presently, if you run Firefox you can go to the Plugin Check page (http://www.mozilla.com/en-US/plugincheck/) to see if your plugins are up to date. We thought: Wouldn't it be great if that page ALSO showed you memory consumption rates? Maybe something like this (note the Memory Consumption column, it doesn't exist on the real webpage [...] Please understand (and we are quite proud of this). All of the data in this mockup is real. Memory consumptions are estimates we derived by analyzing the Test Pilot data.So I already disable Java... do I use DivX? hmmm...

http://eaves.ca/wp-content/uploads/2010/Firefox%20data%20visualization.png

[libssd]

Well stated summary of "Why Firefox". Chrome (among other things) seems to have shaken up the Firefox developers in a positive way. I had more or less consigned Firefox 3+ to irrelevancy, except for the few extensions it ran that had unique functionality. Now, I'm back as a regular user

[SilverWave]

As I was getting toolbar issues* on upgrating my previous profile from FF4.0b7 to FF4.0b8, I have pulled in a later daily build... 4.0~b9~hg20101218r59459, which does not display this issue.

*The toolbar was being reset to the default.

Changes for the versions:
4.0~b9~hg20101215r59188+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20101218r59459+nobinonly-0ubuntu1~umd1~lucid

While I was on I updated FF3.6 as well.

Changes for the versions:
3.6.14~hg20101214r34821+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20101218r34829+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

As I was getting toolbar issues* on upgrating my previous profile from FF4.0b7 to FF4.0b8, I have pulled in a later daily build... 4.0~b9~hg20101218r59459, which does not display this issue.

*The toolbar was being reset to the default.

Changes for the versions:
4.0~b9~hg20101215r59188+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20101218r59459+nobinonly-0ubuntu1~umd1~lucid

While I was on I updated FF3.6 as well.

Changes for the versions:
3.6.14~hg20101214r34821+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20101218r34829+nobinonly-0ubuntu1~umd1~lucid

As there was an issue with the previous daily I have updated the Monthly PPA's as well.

[SilverWave]

With the new 4.0b9pre release I decided to try using the Add-on Compatibility Reporter (https://addons.mozilla.org/en-US/firefox/addon/15003/) again and this time it worked fine.

It also allowed me to advise the developers that most of my Add-ons worked OK as well, which was the cherry on top :-)

__________________

Note: With previous unofficial compatibility add-ons, the procedure was to individually select the add-on to be forced to be compatible.

With this official one its all or nothing.

__________________

With the Add-on Compatibility Reporter you need to do the following:


Install the Add-on Compatibility Reporter (https://addons.mozilla.org/en-US/firefox/addon/15003/) and restart Firefox.



Go to Add-ons > Extensions, there should be a note at the top saying:
"Add-on compatibility checking is disabled. You may have incompatible add-ons."



There will be an "Enable" link to the right. Do not click this! Its a trap. ;-)




None of your old Extensions will work at this point!



Restart Firefox again (No I'm not kidding).



Now your old Extensions will be enabled and may be working.

Optional


Go to Add-ons > Extensions. This time use the "Compatibility" button to report if the add-on is working or not.

Your add-ons will still display a warning that it is "incompatible with 4.0b9pre".
If you have reported that it still works then the "Compatibility" button turns in to a green tick with the words "Works properly."

Observations

It works... so thats great but I have to say that I found it very unintuitive.

[SilverWave]

Latest Update: Firefox Sync 1.6 (December 22, 2010)

Recent changes



(1.6) Accept old-style 20 character Sync Keys in dashed form
(1.6b5) Backward-compatibility fix for old Sync Keys
(1.6b4) Fix reliability issues in crypto procedures and key caching
(1.6b3) Better error handling and recovery for various key errors
(1.6b3) Fix HKDF implementation in crypto
(1.6b2) Performance and correctness fixes
(1.6b1) Employ a simpler crypto infrastructure. This provides a newer storage format and requires that all computers connected to the account are upgraded to this verfsion of Firefox Sync or higher.
(1.6b1) Several performance improvements.
(1.6b1) Improved preference sync.


Works fine in 3.6 but still not showing "Add Device", which does show in FF4.0b9pre

Firefox Mobile Beta3 Sync worked like a dream - All you do is connect and you are presented with a code to input on your desktop PC browser. That's it all done :-)

[SilverWave]

Any one interested in Sync and Security may wish to watch this bug:

Bug 592772 - Fennec should offer to use master password (https://bugzilla.mozilla.org/show_bug.cgi?id=592772)

This comment sums things up nicely:


Quote: Michael Coates 2010-11-10 14:05:18 PST

I'd like to reopen the discussion on this issue. I understand we may not be
willing to block fennec for the master password. However, I think we do need to
carefully make a few design decisions in the interest of security.

Current Sync Deployment:
1. Any sync'ed passwords (from desktops/other devices) will be sync'ed to the
mobile
2. Passwords on the mobile are stored in clear text
3. A phone without builtin encryption (e.g. most of them) provides zero defense
from an attacker inspecting and removing the passwords (either via running
script or forensic inspection)
4. Mobile phones are much more likely to be lost or stolen then laptop/desktop
computers which increases the risk of unencrypted stored passwords.

Possible Solutions
1. Master password (as discussed)
2. Default to not sync passwords to mobile devices at all
3. Idea #2 by default plus user option to enable password sync with a huge
warning message on the risk they're about to accept

We need to adopt some sort of solution to mitigate this risk before we launch
fennec with sync. Otherwise our users will be caught of guard by the large
security risk they've unknowingly assumed.I also fear we will receive
significant backlash from media/security/privacy groups. Mobile banking apps
are already receiving bad press for poor security practices on mobile devices
and hackers are definitely targeting mobile devices.You have been warned :-)

[SilverWave]

Changes for the versions:
4.0~b9~hg20101218r59459+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20101227r59681+nobinonly-0ubuntu1~umd1~lucid

[lovinglinux]

I just got the greenlight to make extensions compatible with Firefox 4.0 instead of 4.0b9. That doesn't mean the next version will be 4.0 final, but means we are closer to the final release and no more compatibility breaking changes are expected.

:guitar:

[SilverWave]

I just got the greenlight to make extensions compatible with Firefox 4.0 instead of 4.0b9. That doesn't mean the next version will be 4.0 final, but means we are closer to the final release and no more compatibility breaking changes are expected.

:guitar:

Well that's great news!

Firefox 4.0 is looking good :-)

[lovinglinux]

Well that's great news!

Firefox 4.0 is looking good :-)

Looks like beta 9 is scheduled for release on January 13th.

[SilverWave]

Changes for the versions:
3.6.14~hg20101218r34829+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20110104r34855+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b9~hg20101227r59681+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20110104r59999+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

Changes for the versions:
3.6.14~hg20101218r34829+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20110104r34855+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b9~hg20101227r59681+nobinonly-0ubuntu1~umd1~lucid
4.0~b9~hg20110104r59999+nobinonly-0ubuntu1~umd1~lucid

This will be the last updates until Firefox 4.0b9 is released, probably next week.

[SilverWave]

Any one interested in Sync and Security may wish to watch this bug:

Bug 592772 - Fennec should offer to use master password (https://bugzilla.mozilla.org/show_bug.cgi?id=592772)

You have been warned :-)

A patch has been landed for this bug...


Comment 17 silverwav 2010-12-23 22:55:53 PST
Created attachment 499633 (https://bugzilla.mozilla.org/attachment.cgi?id=499633) [details] (https://bugzilla.mozilla.org/attachment.cgi?id=499633&action=edit)
unlock addition to master-password-question.png

>how long does that "unlock" last, especially in a world where the user might leave Firefox running for days in the background?

How about:

Ask again in; 1 Hour; 2 Hours; 3 Hours; 4 Hours; 1 Day.


Comment 18 Vivien Nicolas (:vingtetun) 2010-12-27 07:16:28 PST
I think adding duration for asking the master password again is an other bug,
this one is about adding a master password UI to mobile-browser.
Feel free to open a new one depending on this bug, or to create an addon to
experiment with the provided concept of master password "session"

Comment 19 Vivien Nicolas (:vingtetun) 2010-12-27 07:57:02 PST
Created attachment 499830 (https://bugzilla.mozilla.org/attachment.cgi?id=499830&action=diff) [details] (https://bugzilla.mozilla.org/attachment.cgi?id=499830&action=edit)
Patch - updated on the trunk

The patch is updated to work on trunk, the UI is the same as the previous
screenshot except that the style is the new one.
Nice to see that this is being sorted :-)

This is why I love Firefox and Mozilla, decision making transparency and that they take security seriously.

[SilverWave]

A patch has been landed for this bug...

Bug 592772 - Fennec should offer to use master password (https://bugzilla.mozilla.org/show_bug.cgi?id=592772)

Nice to see that this is being sorted :-)

This is why I love Firefox and Mozilla, decision making transparency and that they take security seriously.

Here is a add-on to test the patch from Matt:


Matt Brubeck (:mbrubeck) (mbrubeck@mozilla.com) 2011-01-07 11:16:15 PST I took Vivien's patch and made it into an add-on, with essentially no
modifications:
https://addons.mozilla.org/en-US/mobile/addon/270907/

Please try out this add-on if you would like to have Master Password support.
Any feedback or bug reports on the add-on will help when we incorporate the
feature into the browser itself.Thanks to Matt and Vivien you ppl are stars :-)

[SilverWave]

Notices / Schedule

Firefox 4
Beta 9 has been built and handed off to QA (based on this revision (http://hg.mozilla.org/mozilla-central/rev/badef0f336d2)) Here we go!

Unfortunately the automated builds failed so we will have to wait until tomorrow.

[SilverWave]

Changes for the versions:
3.6.14~hg20110104r34855+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20110112r34868+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b9~hg20110104r59999+nobinonly-0ubuntu1~umd1~lucid
4.0~b10~hg20110114r60482+nobinonly-0ubuntu1~umd1~lucid

So this the first working Firefox 4.0b10pre daily :-)

[SilverWave]

Changes for the versions:
3.6.14~hg20110104r34855+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20110112r34868+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b9~hg20110104r59999+nobinonly-0ubuntu1~umd1~lucid
4.0~b10~hg20110114r60482+nobinonly-0ubuntu1~umd1~lucid

So this the first working Firefox 4.0b10pre daily :-)

Seemed to be OK in limited testing on Lucid 64bit so I have loaded to the Monthly PPA's as well.

[SilverWave]

Let me check out some demos! (http://blog.vlad1.com/2010/12/21/webgl-in-firefox-4-beta-8/)

http://webglsamples.googlecode.com/hg/aquarium/aquarium.html

http://blog.vlad1.com/wp-content/uploads/2010/12/aquarium.png

http://videos.mozilla.org/serv/mozhacks/flight-of-the-navigator/

http://blog.vlad1.com/wp-content/uploads/2010/12/fotn.pnghttp://blog.vlad1.com/wp-content/uploads/2010/12/fotn.png

http://bodybrowser.googlelabs.com/body.html#

http://blog.vlad1.com/wp-content/uploads/2010/12/bodybrowser.png

well... at least if you have a NVIDIA GeForce 8600 GTS :-)

Why Firefox On Linux Is Not Accelerated (http://weblogs.mozillazine.org/gerv/archives/2011/01/why_firefox_on_linux_is_not_accelerated.html?utm_s ource=feedburner&utm_medium=feed&utm_campaign=Feed%3A+HackingForChrist+%28Hacking+f or+Christ%29)

[SilverWave]

Recent Firefox betas replaced the menu bar with a Firefox button. Under Linux, this is not enabled by default, but right-clicking on the menu bar allows to disable the menu bar, which enables the Firefox button.

The button is not exactly very appealing, and takes quite a lot of horizontal space on the tab bar. But with a few lines of CSS, this can fortunately be changed. Edit the chrome/userChrome.css file under your user profile, and add the following lines:Replacing the Firefox button with an icon (http://glandium.org/blog/?p=1547)

#appmenu-toolbar-button {
list-style-image: url("chrome://branding/content/icon16.png");
}
#appmenu-toolbar-button > .toolbarbutton-text,
#appmenu-toolbar-button > .toolbarbutton-menu-dropmarker {
display: none !important;
}Well that worked... but I had to copy the chrome/userChrome.css from my ff3.6 profile.

That is I had no chrome/ folder... weird.

[SilverWave]

How to use feed auto-discovery in Firefox 4 (http://decafbad.com/blog/2011/01/15/how-to-use-feed-auto-discovery-in-firefox-4)


Customize which buttons and controls appear on the toolbar.

If you scroll down in the panel, you’ll see a “Subscribe” button. Drag that from the panel to a position in the toolbar.
http://decafbad.com/blog/wp-content/uploads/2011/01/feed-sub-04.png
Note1:
If you actually used RSS you would, unlike this author of the above screen shot, have the bookmarks bar viable and have all your RSS feeds showing on it for ease of access ;-)

Note2:
I think Mozilla missed fully exploiting RRS in Firefox after a great start with LiveBookMarks...

You can fix it like I did with some small add-ons...

I use Boox with Places Full Tiles and Stay-Open Menu.

RSS nirvana :-)

Boox is still at 3.6 and I cant move to FF 4.0 only until its updated.

[SilverWave]

Changes for the versions:
3.6.14~hg20110112r34868+nobinonly-0ubuntu1~umd1~lucid
3.6.14~hg20110119r34882+nobinonly-0ubuntu1~umd1~lucid


Changes for the versions:
4.0~b10~hg20110114r60482+nobinonly-0ubuntu1~umd1~lucid
4.0~b10~hg20110120r60909+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

Firefox 4 beta logistics (http://christian.legnitto.com/blog/2011/01/20/firefox-4-beta-logistics/)


Summary



We’ll take the most recent green changeset from mozilla-central this Friday, 2011-01-21 at 2:00 pm PST and call that beta 10

The tree will close for < 15 minutes for this (if at all)
We’ll freeze nightly updates at or around the changeset we branched from (likely only for the weekend)
Any problems with the beta will be dealt with on the relbranch


We will release beta 10 as soon as possible during the week of the 24th
We’ll take the most recent green changeset from mozilla-cental on Friday, 2011-01-28 at 2:00 pm PST (or sooner if the remaining betaN hardblockers (https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=anywordssubstr&query_format=advanced&value0-1-0=[hardblocker]&field0-1-0=status_whiteboard&field0-0-0=cf_blocking_20&type0-0-0=anywordssubstr&value0-0-0=beta&resolution=---) are finished) and call that beta 11

The tree will close for < 15 minutes for this (if at all)
We’ll freeze nightly updates at or around the changeset we branched from (likely only for the weekend)
Any problems with the beta will be dealt with on the relbranch


We will release beta 11 as soon as possible during the week of the 31st



Well that's interesting!

[SilverWave]

Latest Update: Firefox Sync 1.6.2 (January 20, 2010)

Recent changes (https://services.mozilla.com/sync/updated/changelog.html)



(1.6.2) Fix bookmark reordering and duplication issues on upgrade
(1.6.2) Fix history and form sync compatibility issues
(1.6.2) Network reliability fixes



This may help if you have had some issues lately.

[SilverWave]

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-4.0 - 4.0~b11~hg20110126r61302+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1474079/+listing-archive-extra)

Oh well we will keep checking but its not that long until the next beta!

[SilverWave]

After a week of build failures

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-4.0 - 4.0~b11~hg20110129r61581+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1477854/+listing-archive-extra)

Looks the business.

Testing as we speak :-)

[SilverWave]

Changes for the versions:
3.6.14~hg20110119r34882+nobinonly-0ubuntu1~umd1~lucid
3.6.15~hg20110129r34899+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b10~hg20110120r60909+nobinonly-0ubuntu1~umd1~lucid
4.0~b11~hg20110129r61581+nobinonly-0ubuntu1~umd1~lucid

So that means you have all the 4.0b10 stuff plus all the code for 4.0b11 that's landed to date.

[SilverWave]

Changes for the versions:
3.6.14~hg20110119r34882+nobinonly-0ubuntu1~umd1~lucid
3.6.15~hg20110129r34899+nobinonly-0ubuntu1~umd1~lucid

Changes for the versions:
4.0~b10~hg20110120r60909+nobinonly-0ubuntu1~umd1~lucid
4.0~b11~hg20110129r61581+nobinonly-0ubuntu1~umd1~lucid

So that means you have all the 4.0b10 stuff plus all the code for 4.0b11 that's landed to date.

Updated the monthly PPA's as well.

Well done Mozilla! Firfox 4.0 is almost done :-)

[SilverWave]

Changes for the versions:
3.6.15~hg20110129r34899+nobinonly-0ubuntu1~umd1~lucid
3.6.15~hg20110202r34916+nobinonly-0ubuntu1~umd1~lucid


Changes for the versions:
4.0~b11~hg20110129r61581+nobinonly-0ubuntu1~umd1~lucid
4.0~b12~hg20110203r61824+nobinonly-0ubuntu1~umd1~lucid


So that means you have all the 4.0b11 stuff plus all the code for 4.0b12 that's landed to date.

[SilverWave]

Changes for the versions:
4.0~b11~hg20110129r61581+nobinonly-0ubuntu1~umd1~lucid
4.0~b12~hg20110203r61824+nobinonly-0ubuntu1~umd1~lucid


So that means you have all the 4.0b11 stuff plus all the code for 4.0b12 that's landed to date.

Updated the monthly PPA's as well.

The tempo is getting faster... the B12pre followed on very quickly :smile:

[SilverWave]

Boox 3 alpha 1 for Firefox 4 is Available! (http://joliclic.free.fr/blog/index.php?post/2011/01/22/Boox-3-alpha-1-for-Firefox-4&pub=1#pr)


Yes!!!!!!!!!!!!!!!
My Deepest Thanks :-)
OK... it works! WHOOT!
I think I can now move over to FF4.0 fulltime :-D

[SilverWave]

Boox 3 alpha 1 for Firefox 4 is Available! (http://joliclic.free.fr/blog/index.php?post/2011/01/22/Boox-3-alpha-1-for-Firefox-4&pub=1#pr)


Tab Utilities 1.0 (https://addons.mozilla.org/en-US/firefox/addon/tab-utilities/) is a great find... it does the job of various different add-ons while it also allows a lot of tab related fine control.

So far I have uninstalled: NewTabUrl TabCounter and Stay Open Menu. :-)

To enable middle clicking to allow you to open multiple items from the LiveBookMarks feed in Boox do this:

Add-ons > Preferences > Mouse > M-Click >
On Bookmarks > Stay menu open

[SilverWave]

Works with FF4.0b12pre so that's good :-)
Was able to just copy all my 3.6 scripts over to my 4.0 profile.
The new scripts show in Add-ons under User Scripts.

The ability to easily add www.example.com* (http://www.example.com*) from the manager has been lost though :-(

Its going to be a pain but I will keep FF3.6 around so I can create the script from Platypus and save in the old Greasemonkey. Then I can use the old manager to update includes.

I may just provide a link to my FF3.6 profile actually hmm will have to investigate if that will work correctly under Ubuntu.
Anyway nasty workaround or not this was one of the last "must have" add-ons that were stopping me moving to FF4.0 full-time. so worth the aggravation ;-)


Not happy with the new manager but as I can only use Platypus with FF3.6 I was going to have to do something similar in any case.

And I was really missing my 60 scripts!



Note:
FF3.6 had updated Greasemonkey so I had to uninstall and reinstall with the Version 0.8.20100408.6 (https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/versions/) from April 8 2010.

[SilverWave]

How to Block Distracting Animated Favicons (http://lifehacker.com/5036881/how-to-block-distracting-animated-favicons)



Lifehacker: Blocking for a Single Site

If there's a single site that is giving you trouble, you can use the Adblock Plus Firefox extension (http://adblockplus.org/en/) to block the offending favicon. Just open up Blockable items, find the favicon in the list and choose "Block this item" to get rid of it. Here is an example:

http://news.softpedia.com/cat/Science/

How annoying is that!

I blocked ||s2.softpedia-static.com/favicon_a.gif

[SilverWave]

Changes for the versions:
4.0~b12~hg20110203r61824+nobinonly-0ubuntu1~umd1~lucid
4.0~b12~hg20110210r62284+nobinonly-0ubuntu1~umd1~lucid

This change is not from a source that supports changelogs.

[SilverWave]

WHOOT! Sanity has prevailed!

Bug 541656 - Display hyperlink URLs at bottom of window (instead of right side of location bar) (https://bugzilla.mozilla.org/show_bug.cgi?id=541656)

Devs have dumped the brain-dead idea of displaying hyperlink URLs in the location bar.

Which had to be the worst UI design decision of all time.

Now just doing the same as chrome... thank god.

[SilverWave]

Changes for the versions:
4.0~b12~hg20110214r62499+nobinonly-0ubuntu1~umd1~lucid
4.0~b12~hg20110217r62724+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

So that means 4.0b12 is done :-)

Changes for the versions:
4.0~b12~hg20110223r62975+nobinonly-0ubuntu1~umd1~lucid
4.0~b13~hg20110224r63035+nobinonly-0ubuntu1~umd1~lucid

Ever closer to the Final release of 4.0!

[SilverWave]

So that means 4.0b12 is done :-)

Changes for the versions:
4.0~b13~hg20110224r63035+nobinonly-0ubuntu1~umd1~lucid

Ever closer to the Final release of 4.0!

Nice.

[SilverWave]

Changes for the versions:
4.0~b13~hg20110303r63299+nobinonly-0ubuntu1~umd1~lucid
4.0~b13~hg20110305r63332+nobinonly-0ubuntu1~umd1~lucid

Obviously this will be the next RC.

[SilverWave]

Updated Monthly and Weekly PPA's as there were a lot of security fixes.

firefox - 3.6.16~hg20110303r34968+nobinonly-0ubuntu1~umd1~karmic

[SilverWave]

Oh oh! Looks like chrisccoulson is annoyed at Ubuntuzilla :-)


[ Fabien Tassin ] -- Fabien Tassin <fta@ubuntu.com (https://launchpad.net/%7Efta)> Sat, 12 Mar 2011 05:00:57 +0100
Fix up the mess left by Ubuntuzilla rather than leaving our official package in a broken and inconsistent state, which ends up with users reporting bugs to Launchpad and giving us a bad reputation. If /usr/bin/firefox has been diverted and there is no /usr/bin/firefox provided on the system, just do the job of whatever package it was that broke the users install and remove the diversion for them. This should hopefully stop the frequently reported bugs we get from Ubuntuzilla users about /usr/bin/firefox being missing - update debian/firefox.postinst.in - Fixes LP: #512937 (https://launchpad.net/bugs/512937), LP: #529136 (https://launchpad.net/bugs/529136), LP: #552919 (https://launchpad.net/bugs/552919), LP: #572733 (https://launchpad.net/bugs/572733), LP: #574111 (https://launchpad.net/bugs/574111), LP: #599978 (https://launchpad.net/bugs/599978), LP: #600271 (https://launchpad.net/bugs/600271), LP: #610522 (https://launchpad.net/bugs/610522), LP: #610756 (https://launchpad.net/bugs/610756), LP: #610907 (https://launchpad.net/bugs/610907), LP: #612162 (https://launchpad.net/bugs/612162), LP: #620400 (https://launchpad.net/bugs/620400), LP: #623980 (https://launchpad.net/bugs/623980), LP: #625014 (https://launchpad.net/bugs/625014), LP: #630643 (https://launchpad.net/bugs/630643), LP: #635166 (https://launchpad.net/bugs/635166), LP: #638342 (https://launchpad.net/bugs/638342), LP: #641838 (https://launchpad.net/bugs/641838), LP: #658828 (https://launchpad.net/bugs/658828), LP: #668809 (https://launchpad.net/bugs/668809), LP: #672282 (https://launchpad.net/bugs/672282), LP: #676239 (https://launchpad.net/bugs/676239), LP: #707704 (https://launchpad.net/bugs/707704), LP: #724090 (https://launchpad.net/bugs/724090) * Don't allow users to report bugs with apport-bug when /usr/bin/firefox has been diverted - update debian/firefox.py.in

Update:

No, that was actually me. Fabien's name is in the changelog because he runs the nightly builds, but that change was actually committed by me

Fixed :-D

[chrisccoulson]

Oh oh! Looks like Fabien is annoyed at Ubuntuzilla :-)

No, that was actually me. Fabien's name is in the changelog because he runs the nightly builds, but that change was actually committed by me

[SilverWave]

No, that was actually me. Fabien's name is in the changelog because he runs the nightly builds, but that change was actually committed by me

Fixed :-D

[SilverWave]

Changes for the versions:
4.0~b13~hg20110308r63349+nobinonly-0ubuntu1~umd1~lucid
4.0~b13~hg20110312r63396+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

Well it looks like this could be very useful for a lot of people who want the latest official release but not a nightly build.
https://launchpad.net/~mozillateam/+archive/firefox-next


This PPA will contain Milestone builds of the next version of Firefox (alpha, beta, RC)


Add a Firefox 4.0 PPA:


sudo add-apt-repository ppa:mozillateam/firefox-next
Update & Install


sudo apt-get update
sudo apt-get install firefox-4.0

[SilverWave]

________________________________________

One Daily A Week (from ubuntu-mozilla-daily).
The latest firefox without the update hassle.


One ppa per Ubuntu Version (containing both Firefox 4.0 & Firefox 3.6).
Updated at the start of each Week.

________________________________________

Note that I'm dropping Firefox 3.6 from the "One Daily A Week" PPA's

[SilverWave]

Mozilla outlines 16-week Firefox development cycle (http://arstechnica.com/open-source/news/2011/03/mozilla-outlines-16-week-firefox-development-cycle.ars?utm_source=rss&utm_medium=rss&utm_campaign=rss)

Mozilla Firefox: Development Process (http://people.mozilla.com/%7Esayrer/2011/temp/process.html)

Well this is great news!

It will be interesting to see how the Ubuntu Mozilla Team respond :-)

Although Firefox-Next is a good start.

[SilverWave]

firefox-4.0 - 4.0~rc1+build1+nobinonly-0ubuntu1~mfn~lucid1 (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1/+sourcepub/1559106/+listing-archive-extra)

Now that we have the Firefox-Next PPA the need for a "One Daily A Month" PPA for Firefox 4 is questionable...

...Short term I am just going to mirror Firefox-Next.

Pity we don't have usage figures on our PPA's as this would allow me to see if I could close them down without affecting to many ppl.

So to summarise:

"One Daily A Week" PPA's for Firefox 4.0 are still going to be updated from the daily builds.

"One Daily A Month" PPA's for Firefox 4.0 are going to mirror Firefox-Next.
"One Daily A Month" PPA's for Firefox 3.6 are still going to be updated from the daily builds.

[lovinglinux]

Mozilla outlines 16-week Firefox development cycle (http://arstechnica.com/open-source/news/2011/03/mozilla-outlines-16-week-firefox-development-cycle.ars?utm_source=rss&utm_medium=rss&utm_campaign=rss)

Mozilla Firefox: Development Process (http://people.mozilla.com/%7Esayrer/2011/temp/process.html)

Well this is great news!

It will be interesting to see how the Ubuntu Mozilla Team respond :-)

Although Firefox-Next is a good start.

This will be great for extension developers

[SilverWave]

This will be great for extension developers

From Ars:


Arguably the biggest challenge for faster iteration is going to be the question of extension compatibility. The proposal document acknowledges that the problem exists but doesn't provide any suggested solutions. It's an area where Mozilla is going to have to do some serious problem-solving.

Interesting.

[SilverWave]

This will be the landing page for anyone who needs the "One Daily A Month" instructions.

One Daily A Month PPAs for Firefox 4.0 are now just mirrors of Firefox-Next

One Daily A Month PPAs for Firefox 3.6 are the same as normal but moving details here as they will have diminishing relevance.
________________________________________

One Daily A Month (from ubuntu-mozilla-daily).
The latest firefox without the update hassle.


One ppa for each Firefox.
Updated at the start of each month.

________________________________________

Add a Firefox 4.0 PPA:

Firefox-4.0 - One Daily A Month #5 - Maverick (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-5)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-5Firefox-4.0 - One Daily A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-1Firefox-4.0 - One Daily A Month #3 - Karmic (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-3)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-3Add a Firefox 3.6 PPA:

Firefox-3.6 - One Daily A Month #4 - Maverick (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-4)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-4Firefox-3.6 - One Daily A Month #0 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-0)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-0Firefox-3.6 - One Daily A Month #2 - Karmic (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-2)

sudo add-apt-repository ppa:silverwave/one-daily-a-month-2Update & Install

sudo apt-get update
sudo apt-get install firefox
sudo apt-get install firefox-4.0Applications > Internet.
FF3.6 is called "Namoroka Web Browser" (Firefox pre-release).
FF4.0 is called "Minefield 4.0 Web Browser" (Browse the Bleeding Edge).

________________________________________

:)

[SilverWave]

Changes for the versions:
3.6.16~hg20110308r34972+nobinonly-0ubuntu1~umd1~lucid
3.6.17~hg20110319r35006+nobinonly-0ubuntu1~umd1~lucid

[SilverWave]

http://mozcom-cdn.mozilla.net/img/firefox/beta/4/firstrun/illustration-rc.jpg

Testing out the new PPA:

Changes for the versions:
4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid
4.0~rc1+build1+nobinonly-0ubuntu1~mfn~lucid1

As you can see the RC1 trumps the daily build.

2 days to go for the full release :-)

Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20110310 Firefox/4.0 Firefox/4.0 ID:20110310030225

[Update]

After updating my add-ons I needed to uninstall/reinstall the Add-on Compatibility Reporter to get it working again.

[SilverWave]

Testing out the new PPA:

Changes for the versions:
4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid
4.0~rc1+build1+nobinonly-0ubuntu1~mfn~lucid1

As you can see the RC1 trumps the daily build.

2 days to go for the full release :-)

Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20110310 Firefox/4.0 Firefox/4.0 ID:20110310030225

[Update]

After updating my add-ons I needed to uninstall/reinstall the Add-on Compatibility Reporter to get it working again.

Issues with "Add-on Compatibility Reporter" forgetting it should be enabled after a reboot...

Don't have the time to troubleshoot so:

Uninstalled 4.0~rc1+build1+nobinonly-0ubuntu1~mfn~lucid1

Disabled the Firefox-next PPA in Software Sources.

Installed Firefox-4.0 from my One Daily A Week (https://launchpad.net/%7Esilverwave/+archive/testing0) PPA.

4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid

___

Cant beat backups ;-)

[lovinglinux]

Lots of things going on. The new ppa, Ubuntuzilla ceasing operations and all that stuff you have been posting. :shock:

I also have decided to cease the development of FoxTester. Now I am recommending the new Mozilla's profile Manager for managing multiple versions and profiles.


Issues with "Add-on Compatibility Reporter" forgetting it should be enabled after a reboot...

Don't have the time to troubleshoot so:

Uninstalled 4.0~rc1+build1+nobinonly-0ubuntu1~mfn~lucid1

Disabled the Firefox-next PPA in Software Sources.

Installed Firefox-4.0 from my One Daily A Week (https://launchpad.net/%7Esilverwave/+archive/testing0) PPA.

4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid
__

Cant beat backups ;-)

I am not experiencing such issue.

[SilverWave]

Lots of things going on.


Very true!


The new ppa,Yeah long overdue IMHO :-)


Ubuntuzilla ceasing operationsWow I missed that, but it makes sense as its really not needed any more.


and all that stuff you have been posting. :shock:Yes Firefox-Next was just what I wanted (easy installs of Firefox betas, RC's etc., for all Ubuntu users).
Particularly as Mozilla are upping the tempo of releases.
Its going to pretty much match what I was trying to accomplish with my One Daily A Month PPA's.

One less thing I need to worry about :D (Although it did necessitate a major rewrite of the How to).


I also have decided to cease the development of FoxTester. Now I am recommending the new Mozilla's profile Manager for managing multiple versions and profiles.Oh I will have to have a look into it, thanks for the tip.



I am not experiencing such issue [re Add-on Compatibility Reporter].
Good! that means its probably either my profile or on of my many add-ons ;-)

Although... everything works with the daily I swapped the RC1 out for... hmm interesting!

[lovinglinux]

Oh I will have to have a look into it, thanks for the tip.

Here is the link:

https://developer.mozilla.org/en/Profile_Manager

Is pretty good and can also do profile backups.

[SilverWave]

https://launchpad.net/~mozillateam/+archive/firefox-stable

Add a Firefox 4.0 PPA:


sudo add-apt-repository ppa:mozillateam/firefox-stable
Update & Install


sudo apt-get update
sudo apt-get install firefox

[SilverWave]

Warning!

Just tested and bear in mind that this will upgrade your Firefox 3.6 to 4.0...

That is you will no longer have access to Firefox 3.6!



https://launchpad.net/~mozillateam/+archive/firefox-stable (https://launchpad.net/%7Emozillateam/+archive/firefox-stable)

Add a Firefox 4.0 PPA:


sudo add-apt-repository ppa:mozillateam/firefox-stable
Update & Install


sudo apt-get update
sudo apt-get install firefox

[SilverWave]

Warning!

Just tested and bear in mind that this will upgrade your Firefox 3.6 to 4.0...

That is you will no longer have access to Firefox 3.6!

If you need to undo the upgrade and put Firefox 3.6 back as it was:

(Hopefully you have a backup of your Firefox folder :-|)

Uninstall Firefox from Package Manager.

Optional: Replace you Firefox folder with your saved backup copy.
In Software sources remove the entry for Firefox-stable.
Via Package Manager install Firefox. (Version should be 3.6)

You are now sorted! :-)

[jquest71]

Sweet! I was really excited about fx4 when I put the RC on my Win7 netbook, but now that I'm running Ubuntu it's running even better. Thanks for posting the instructions on how to get the stable update. Now, is there an easy way to uninstall the Minefield developer preview version?

Thanks!

JQ



https://launchpad.net/~mozillateam/+archive/firefox-stable (https://launchpad.net/%7Emozillateam/+archive/firefox-stable)

Add a Firefox 4.0 PPA:


sudo add-apt-repository ppa:mozillateam/firefox-stable
Update & Install


sudo apt-get update
sudo apt-get install firefox

[SilverWave]

Sweet! I was really excited about fx4 when I put the RC on my Win7 netbook, but now that I'm running Ubuntu it's running even better. Thanks for posting the instructions on how to get the stable update. Now, is there an easy way to uninstall the Minefield developer preview version?

Thanks!

JQ

Hi,

Uninstall firefox-4.0
Then remove firefox-next from your "Software Sources"

That should do it as the firefox-stable package is "firefox".

Cheers.

[SilverWave]

Changes for the versions:
4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid
4.0~b13~hg20110321r63449+nobinonly-0ubuntu1~umd1~lucid

[vagrale13]

Hi,

Uninstall firefox-4.0
Then remove firefox-net from your "Software Sources"

That should do it as the firefox-stable package is "firefox".

Cheers.
One safe way to back Firefox 3.6*
go System - Administration - Software sources -
and other software category uncheck
for Ubuntu 10.10 => ppa.launchpad.net/mozillateam/firefox-stable/ubuntu maverick main
for Ubuntu 10.04 => ppa.launchpad.net/mozillateam/firefox-stable/ubuntu lucid main
Close and in the question Reload.
Then close Firefox, open terminal and run the following commands

sudo apt-get remove firefox ubufox xul-ext-ubufox
sudo apt-get updatethen run

sudo apt-get install firefox firefox-gnome-supportand then

sudo apt-get update && sudo apt-get upgradeAfter just open Firefox, and you have again the old version Firexox 3.6*

[SilverWave]

Originally Posted by jquest71 http://ubuntuforums.org/images/buttons/viewpost.gif (http://ubuntuforums.org/showthread.php?p=10589477#post10589477)
Sweet! I was really excited about fx4 when I put the RC on my Win7 netbook, but now that I'm running Ubuntu it's running even better. Thanks for posting the instructions on how to get the stable update. Now, is there an easy way to uninstall the Minefield developer preview version?

Thanks!

JQ


Hi,

Uninstall firefox-4.0
Then remove firefox-next from your "Software Sources"

That should do it as the firefox-stable package is "firefox".

Cheers.


One safe way to back Firefox 3.6*
go System - Administration - Software sources -
and other software category uncheck
for Ubuntu 10.10 => ppa.launchpad.net/mozillateam/firefox-stable/ubuntu maverick main
for Ubuntu 10.04 => ppa.launchpad.net/mozillateam/firefox-stable/ubuntu lucid main
Close and in the question Reload.
Then close Firefox, open terminal and run the following commands

sudo apt-get remove firefox ubufox xul-ext-ubufox
sudo apt-get updatethen run

sudo apt-get install firefox firefox-gnome-supportand then

sudo apt-get update && sudo apt-get upgradeAfter just open Firefox, and you have again the old version Firexox 3.6*



hmm I think he needed the Firefox-4.0 RC1 Milestone removed...

[vagrale13]

hmm I think he needed the Firefox-4.0 RC1 Milestone removed...
I think you have right. This is for mozillateam/firefox-stable PPA.

Thanks for PPA :popcorn:

[SilverWave]

Changes for the versions:
3.6.17~hg20110319r35006+nobinonly-0ubuntu1~umd1~lucid
3.6.17~hg20110324r35011+nobinonly-0ubuntu1~umd1~lucid

___

Separate XULRunner update:

Changes for the versions:
1.9.2.15+build1+nobinonly-0ubuntu0.10.04.1
1.9.2.16+build1+nobinonly-0ubuntu0.10.04.1

Version 1.9.2.16+build1+nobinonly-0ubuntu0.10.04.1:

* New upstream release v1.9.2.16 (FIREFOX_3_6_16_BUILD1)
- see USN-1091-1
___

[SilverWave]

You've been updated to the latest version of Firefox Sync!

Latest Update: Firefox Sync 1.7 (March 9, 2011)
Recent changes

* (1.7) Performance improvements
* (1.6.3) Better handling of smart bookmarks
* (1.6.3) Handle restoring bookmarks from backup better
* (1.6.2) Fix bookmark reordering and duplication issues on upgrade
* (1.6.2) Fix history and form sync compatibility issues
* (1.6.2) Network reliability fixes
* (1.6.1) Provide the "Add a Device" link under Sync Options for Firefox 3.5/3.6
* (1.6) Accept old-style 20 character Sync Keys in dashed from
* (1.6b5) Backward-compatibility fix for old Sync Keys
* (1.6b4) Fix reliability issues in crypto procedures and key caching
* (1.6b3) Better error handling and recovery for various key errors
* (1.6b3) Fix HKDF implementation in crypto
* (1.6b2) Performance and correctness fixes
* (1.6b1) Employ a simpler crypto infrastructure. This provides a newer storage format and requires that all computers connected to the account are upgraded to this verfsion of Firefox Sync or higher.
* (1.6b1) Several performance improvements.
* (1.6b1) Improved preference sync.

[SilverWave]

Source Uploader Published Status Series Section Build Status
https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-4.0 - 4.0~b13~hg20110323r63531+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1562732/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-4.0_4.0%7Eb13%7Ehg20110323r63531%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes) fta (https://launchpad.net/%7Efta) 2011-03-23 Published Lucid Web https://launchpad.net/@@/no [/URL]
[URL="https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2338800"] (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2338799)https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-4.0 - 4.0~b13~hg20110321r63449+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1560946/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-4.0_4.0%7Eb13%7Ehg20110321r63449%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes) fta (https://launchpad.net/%7Efta) 2011-03-22 Superseded Lucid Web https://launchpad.net/@@/yes
https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-4.0 - 4.0~b13~hg20110319r63446+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1557591/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-4.0_4.0%7Eb13%7Ehg20110319r63446%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes) fta (https://launchpad.net/%7Efta) 2011-03-19 Superseded Lucid Web What's next?

Cant see any new builds since the 23rd of March 2011, and that failed...

[SilverWave]

OK I think its time to move on... so I am prepared to dump 3.6 and upgrade Firefox to 4.0 (Stable PPA).

So if I am going to do it, lets do it right, yes its time for a clean profile :-D

After updating I still have a separate Firefox 4.0 folder.
I have deleted the contents of the Firefox folder and a new profile is created automatically on running Firefox.

[SilverWave]

OK I think its time to move on... so I am prepared to dump 3.6 and upgrade Firefox to 4.0 (Stable PPA).

So if I am going to do it, lets do it right, yes its time for a clean profile :grin:

After updating I still have a separate Firefox 4.0 folder.
I have deleted the contents of the Firefox folder and a new profile is created automatically on running Firefox.

Set-up a master password first.

I have set-up sync by authorising Another Device via my Minfield Firefox 4.0 package (from the dailies), all done in under 5min :-)

If you wait a few minutes all your passwords and history is pulled across :-D

Heh even your Persona's Cool!

I am closing Firefox down and saving an archive from time to time in case I screw-up, as I don't want to have to start from the beginning :-|

[SilverWave]

First issue

Firefox crashes with XML Parsing Error (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/677815)


Binary package hint: firefox
The newest version of Firefox installed from the Natty repositories crashes on startup with the following message:
XML Parsing Error: undefined entity
Location: chrome://browser/content/browser.xul
Line Number 232, Column 5: <key id="key_openAddons" key="&addons.commandkey;" command="Tools:Addons" modifiers="accel,shift"/>Here is the workaround:



Gabriel de Perthuis (https://launchpad.net/%7Eg2p) wrote on 2011-03-25: #13 (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/677815/comments/13) It was working when running firefox-4.0 from ubuntu-mozilla-daily/ppa which has the betas and nightlies, and quit working with mozillateam/firefox-stable which has the final firefox 4. This is because the language packs are in /usr/lib/firefox-addons/extensions/ and not /usr/lib/firefox-4.0-addons/extensions/ .
Here is a workaround: `firefox -uilocale en`, go to the addons manager, open the language pack pane, disable language packs.
I filed a bug over there: https://bugzilla.mozilla.org/show_bug.cgi?id=644933

Note1: I only experienced this issue one I added Add-on Compatibility Reporter. (https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/)
Note2: I went back to a previous backup and disabled the 3.6 GB Language Pack.

Working fine now :-)

[SilverWave]

OK now installing all my extensions (this should be part of Sync IMNSHO), but its not too bad.

The search feature of the new Add-ons Manager is fantastic!

You no longer need to visit AMO to search and download your extensions.

Instead you can do it all from within the Add-ons Manager :-)

Impressed!

[SilverWave]

Copied my greasemonkey scripts:

/home/silverwave/.mozilla/firefox-4.0/lkj9c9k1.default/gm_scripts

...to the firefox folder.

They imported fine :-D

[SilverWave]

OK nearly Done ;-)

Disabled all the plugins except Shockwave and VLC

[SilverWave]

History There is the updating history and the list of known problems.

0.11.2011032401

Fixed: On Firefox 4, toolbar buttons in the tab bar were unexpectedly hidden.
Fixed: On Firefox 4, switching of tab groups broke tree of tabs.
Fixed: Works with Locationbar2 (https://addons.mozilla.org/firefox/addon/locationbar%C2%B2/) correctly.

0.11.2011031901

Fixed: Flexible toolbar items (like search bar) were wrongly shrunken and hidden if there were too many tabs.
Fixed: Clicking on an extra toolbar item in the tab bar wrongly selected overflow-ed tabs behind the toolbar item.
Fixed: In secondary browser window, bookmarks couldn't be opened after the primary browser window was closed.
Fixed: Toolbar customization unexpectedly moved toolbar items before tabs, to the place after tabs.
Fixed: Extra toolbar items in the tab bar can be removed by dragging correctly.
Fixed: Clicks on extra toolbar items were wrongly ignored.
Fixed: Tree Style Tab freezed Firefox itself when you close a last tree of tabs in the tab bar.
Fixed: Pinned tabs never accept dropping of tabs.
Fixed: Pinned tabs were sometimes wrongly positioned.
Fixed: Tree view was unexpectedly disabled by Personal Titlebar (https://addons.mozilla.org/ja/firefox/addon/personal-titlebar/).
Fixed: Broken appearance of pinned tabs with Tab Mix Plus gone.
Fixed: Misplaced favicons in pinned tabs with Tab Mix Plus gone.
Improved: A new secret preference to control collapsed/expanded state of restored tabs, "extensions.treestyletab.collapseExpandSubtree.sess ionRestore". -1 restores the last state, 0 collapses all of restored trees, 1 expands all of them.
German locale was updated by Andy Pillip.

0.11.2011021901

Fixed: TST wrongly handled drag and drop actions on the tab bar even if it is fired in the toolbar customization.
Fixed: Pinned tabs are shown with highlighted background correctly when their titles are changed.
Fixed: Better compatibility with TotalToolbar (http://totaltoolbar.mozdev.org/).

0.11.2011021601

Improved: Buttons in the information bar to confirm how restore other closed tabs in the tree (it is shown when you do "undo close tab" for a tab which was in a tree) now have their suitable accesskey.
Improved: Focusring is shown in tabs if tabs are focusable by userChrome.css.
Improved: On Firefox 3.6 or olders, the background of the transparent tab bar is no longer drawn if the secret pref "extensions.treestyletab.tabbar.transparent.partial Transparency" has a value equals to or larger than "1".
Improved: An alternative drop-marker for drag and drop onto the vertical tab bar is available, for the "Default" skin.
Fixed: On Minefield, closing of the current tab didn't back the focus to the owner tab.
Fixed: Tearing off of multiple tabs was failed unexpectedly when Multiple Tab Handler (http://piro.sakura.ne.jp/xul/_multipletab.html.en) is installed.
Fixed: Needless blank window was wrongly opened when a tab was teared off from the window by drag-and-drop.
Fixed: On Minefield, dragging on the grippy in the splitter for the tab bar failed to resize the tab bar.
Fixed: Restored tab from "Undo Close Tab" was unexpectedly opened in a collapsed tree, when BarTab (https://addons.mozilla.org/firefox/addon/bartab/) is installed.
Fixed: On Minefield, the appearance of the tab bar was unexpectedly broken if RequestPolicy (https://addons.mozilla.org/firefox/addon/requestpolicy/) is installed.
zh-CN locale is updated by hzhbest. Thanks!
es-ES locale is updated by Tito Bouzout. Thanks!
sv-SE (Swedish) locale is available, translated by Mikael Hiort af Ornäs. Thanks!

0.11.2011020402

Fixed: An error in the initialization process disappeared.

0.11.2011020401

Modified: The status panel on Minefield is shown in the another side by default, for vertical tab bar.
Fixed: The API "TreeStyleTabService.position" didn't work.

0.11.2011020301

Improved: Now you can open a new blank tab in existing tree.
Improved: Tabs restored from about:sessionrestore become children of the tab.
Improved: Works with DragNDrop Toolbars (https://addons.mozilla.org/firefox/addon/dragndrop-toolbars/).
Fixed: The status panel (https://bugzilla.mozilla.org/show_bug.cgi?id=628654) is repositioned for bottom tab bar.
Fixed: Tabs in a moved tree were expanded wrongly, if the tree was collapsed.
Fixed: Tabs can't be dragged if there is Tab Mix Plus.
Modified: The transparency of the tab bar (for auto-hide mode) is fixed. It is no longer customizable.

0.11.2011012302

Fixed: pl locale was broken.

0.11.2011012301

Improved: The tab bar can be moved to another place with Peronal Titlebar (https://addons.mozilla.org/irefox/addon/personal-titlebar/) (or otehr addons provide customizability of the tab bar). If the tab bar is moved to another toolbar, then whole the toolbar becomes "tab bar" for Tree Style Tab.
Improved: In bookmark group tabs (about:treestyletab-group), the existing text in the text field is automatically selected when you click the title.
Modified: TreeStyleTabService.currentTabbarPosition was renamed to TreeStyleTabService.position. For backward compatibility, the old name is still available.
Fixed: Tooltip on tabs were not updated after it was shown on a twisty of a tab.
Fixed: Icons of tabs were unexpectedly stretched if Tab Mix Plus is installed.
Fixed: The drop position indicator for horizontal tab bar was unexpectedly shown even if the tab bar was vertical.
Fixed: When TreeStyleTabService.treeViewEnabled becomes "false", then stacked tabs in horizontal tab bar are correctly unstacked.

0.11.2011011301The final issue was with Tree Style Tabs, the developer has updated the extension a lot but I couldn't update as the StatusPanel was positioning itself on the right instead of the left in the new versions!

It was driving me nuts :-|

I had a look at his blog and I identified that he would call this setting "StatusPanel".

I did a search in about.config and found it!!!

Set "extensions.treestyletab.autoRepositionStatusPanel" to false and it displays correctly on the left again. :-)

[SilverWave]

All the following extensions are installed and working :-)


*Aardvark 3.0
Adblock Plus 1.3.5
Add-on Compatibility Reporter 0.8.2
Barlesque 1.15
Boox 3.0a1
Download Statusbar 0.9.8
Greasemonkey 0.9.1
Image Zoom 0.4.6
Locationbar² 1.0.6
Make Link 11.03
Menu Editor 1.2.7
Nightly Tester Tools 3.1.2
NoSquint 2.1
OptimizeGoogle 0.78.2
Places’ Full Titles 4
Re-Pagination 2011.03.24
Readability 1.3
Reliby 1.5.0
RequestPolicy 0.5.20
Shelve 1.23
Tab Utilities 1.0.2
Toolbar Buttons 1.0
Tree Style Tab 0.11.2011032401

*Officially incompatible with Firefox 4.0... but works anyway ;-)
The amazing thing is that all bar one are fully compatible with Firefox 4.0!

This is a fantastic result for Mozilla, as incompatible key extensions can hold ppl back from updating Firefox.
e.g. Boox is not 100% yet but I wouldn't be updating if the developer hadn't found time to release this alpha.

I remember that compatibility was much worse with Firefox 3.0 and Firefox 3.5.

[SilverWave]

Do you want to stop using this account?
This will reset all of your Sync account information and preferences.

[Cancel] [Reset All information]


Hi, the Firefox 4 desktop option "Deactivate this device" will only disconnect your desktop browser from Firefox Sync. Your existing data (bookmarks, history, passwords, etc.) will remain intact, both on your desktop and also on the Firefox Sync servers.


I can confirm that this works as advertised (in spite of the scary message, which I think is a little misleading).

__________________

The reason I was looking into this was as follows...

I had successfully created a new clean profile using the Stable Firefox 4.0 package (profile in /home/silverwave/.mozilla/firefox) and I wanted to repurpose it for use with the Minefield Firefox 4.0 package (profile in /home/silverwave/.mozilla/firefox4.0).

But if I did that both profiles would be using the same Sync client ID... which would be bad ;-)

Using "Deactivate this device" on the copied profile did the trick allowing me to re authorise it via "Add A Device" on the original profile.

Heh Sync is loads and loads of fun :-D

__________________

Note:
Prior to all of this I used the old Minefield Firefox 4.0 profile to authorise the new clean profile I had created with Stable Firefox 4.0.

Round and round we go ;-)

[SilverWave]

Boox 3 alpha 1 for Firefox 4 is Available! (http://joliclic.free.fr/blog/index.php?post/2011/01/22/Boox-3-alpha-1-for-Firefox-4&pub=1#pr)

Yes!!!!!!!!!!!!!!!
My Deepest Thanks :smile:
OK... it works! WHOOT!
I think I can now move over to FF4.0 fulltime :grin:


Workaround for "Mark as read." issue.

Set History to "Boox History" and Restart.
Right Click the feed and then click "Mark as read"
Click one of the feed items to update the feed status from bold.

[SilverWave]

Here is a list of the adjustments I make to the default profile:

The usual voodoo:
browser.display.show_image_placeholders: False
network.http.max-connections: 48
network.http.max-connections-per-server: 32
network.http.max-connections-per-proxy: 16
network.http.max-persistent-connections-per-server : 32
network.http.pipelining: True
network.http.pipelining.maxrequests: 8 (Hard-coded Limit)
network.http.proxy.pipelining: True

ui.submenuDelay: 0


Specials:
browser.sessionstore.max_concurrent_tabs: 0

[lovinglinux]

Check this out:

https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/

[SilverWave]

Check this out:

https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/


Wow a true Watershed moment in Firefox development!

So lets save the whole thing for posterity:


New development channels and repositories for rapid releases (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/)

Recently we announced additional details (http://mozilla.github.com/process-releases/draft/development_specifics/) about the channels for the new Firefox development and release process. We are confident this process will enable us to ship quality Firefox releases to users at a faster cadence and ask for your patience as we hammer out the final remaining items.
Reasoning behind the new update channel and repositories

Firefox currently has three update channels, all of which contain updates built out of the same code repository:


Nightly – builds created out of the mozilla-central repository every night. These are not qualified by QA
Beta – builds created out of the mozilla-central repository, qualified by QA as being of sufficient quality to release to beta users
Release – builds created out of the mozilla-central repository, qualified by QA as being of sufficient quality to release to hundreds of millions of people

Because the updates we put on the Nightly channel aren’t tested before they are offered to users, we use a different icon and name (“Minefield”) to indicate they are risky and not the stable Firefox most users expect:
http://christian.legnitto.com/blog/wp-content/uploads/2011/04/minefield.png (http://christian.legnitto.com/blog/wp-content/uploads/2011/04/minefield.png)
While this approach has treated us well we feel there are some issues inherent in the current structure:


The quality expectation for updates on the Beta channel is vastly higher than the updates on the Nightly channel
Users on the Beta channel may not even know they are running pre-release (but hopefully decent) versions of Firefox
Due to #1 above, development on the mozilla-central repository is frozen while we stabilize for an update to the Beta channel. This causes a huge backlog of patches and adds additional risk for the next beta
3rd parties must track Firefox development closely to know when a milestone they care about (such as feature complete, API freeze, or string freeze) is reached
For developers, the tree rules are constantly changing on mozilla-central depending on when we last shipped an update from it

Because of these issues we came up with a modified process:
http://mozilla.github.com/process-releases/draft/development_specifics/img/channels.png


Nightly – builds created out of the mozilla-central repository every night. These are not qualified by QA
Aurora – builds created out of the mozilla-aurora repository, which is synced from mozilla-central every 6 weeks1 (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/#6_weeks). There is a small amount of QA at the start of the 6 week1 (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/#6_weeks) period before the updates are offered
Beta – builds created out of the mozilla-beta repository, qualified by QA as being of sufficient quality to release to beta users
Release – builds created out of the mozilla-release repository, qualified by QA as being of sufficient quality to release to hundreds of millions of people

With the new structure, all these issues go away:


The quality expectation for updates on the Beta channel is vastly higher than the updates on the Nightly channel.
We address this by creating the Aurora channel. This channel has higher expectations of quality than the Nightly channel but lower expectations than Beta. At the start of the 6 week1 (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/#6_weeks) Aurora period for a particular release, the quality will be closer to the Nightly channel. At the end of the 6 week Aurora period quality will have converged to match the Beta channel
Users on the Beta channel may not even know they are running pre-release (but hopefully decent) versions of Firefox.
To fix this issue we are branding builds from individual channels with new icons. This should allow users to know at a glance what channel they are on and set stability expectations accordingly
Due to #1 above, development on the mozilla-central repository is frozen while we stabilize for an update to the Beta channel. This causes a huge backlog of patches and adds additional risk for the next beta.
Because we are using a repo-per-channel model, mozilla-central development (and thus the updates on the Nightly channel) never have to freeze…quality convergence takes place on other repositories while Firefox development continues on mozilla-central unaffected by the release process
3rd parties must track Firefox development closely to know when a milestone they care about (such as feature complete, API freeze, or string freeze) is reached.
With the new process what happens where and when is a lot more explicit and consistent. No longer will 3rd parties need to know that beta 8 was API complete while beta 9 was string frozen. Instead we can make assurances such as “no new en-US strings will be added through updates on the Aurora channel” and “no extension API changes will be delivered to users via the Beta channel”. This allows 3rd parties to accurately plan and encourages sticking to the rules and schedule
For developers, the tree rules are constantly changing on mozilla-central depending on when we last shipped an update from it.
Lastly, the new repositories (which map to the channels) allow developers to do what they do best—develop. No longer should a developer need to know we are in blocker-only mode for a particular release. Instead, they will be allowed to land their fixes on mozilla-central at any time provided they stick to the mozilla-central tree rules. The mozilla-aurora repository will have different rules, and mozilla-beta will have different (and stricter) rules still. The rules for each of these repositories will not change over time or from release to release, which should help alleviate a lot of developer confusion and annoyance

Repository and channel mechanics

The repository and channel mechanics can get very specific and involved. Most developers won’t care about the specifics and will instead just focus on landing their fixes on mozilla-central. If you do care about the specifics, please take a look at the previously posted process specifics document (http://mozilla.github.com/process-releases/draft/development_specifics/). The document is where we are collecting the decisions about how to best handle the nuts and bolts of releases.
Feedback

As with most Mozilla process changes, questions and comments from the community are highly encouraged. The best place to ask questions is the mozilla-dev-planning newsgroup (https://groups.google.com/group/mozilla.dev.planning/topics). Please be sure to read the previous threads to make sure your question hasn’t already been answered as there have already been some great discussions taking place.
Feedback and changes to the process specifics document (http://mozilla.github.com/process-releases/draft/development_specifics/) can be submitted directly as pull requests on GitHub (https://github.com/mozilla/process-releases). You can also use the history view to see the iterations the process document has already gone through.
Finally, I understand there are a lot of details in the specifics document and sometimes it is easier to just talk to someone directly. I am available via email (clegnitto@mozilla.com) and IRC (LegNeato on irc.mozilla.org) for any community members with questions or comments.

1 Please see the process specifics document (http://mozilla.github.com/process-releases/draft/development_specifics/) for reasons why the steps for Firefox 5 are not in 6 week increments
This entry was posted by Christian Legnitto on Thursday, April 7th, 2011 at 3:26 pm and is filed under General (https://developer.mozilla.org/devnews/index.php/categories/1/).

[SilverWave]

Wow a true Watershed moment in Firefox development!

https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/

So lets save the whole thing for posterity:



Aurora – builds created out of the mozilla-aurora repository, which is synced from mozilla-central every 6 weeks1 (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/#6_weeks). There is a small amount of QA at the start of the 6 week1 (https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/#6_weeks) period before the updates are offeredThis is probably the one most ppl will find most useful, some QA so it will at least work. :-)

But the latest and greatest every 6 weeks!

Cool.

[SilverWave]

What's next?

Cant see any new builds since the 23rd of March 2011, and that failed...

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 4.2~a1~hg20110407r67597+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1635874/+listing-archive-extra) fta (https://launchpad.net/%7Efta)
5 hours ago Published Lucid Web https://launchpad.net/@@/no amd64 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2433556) i386 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2433557)

Hmm pity it failed but nice to see we are moving on :-)

[SilverWave]

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 4.2~a1~hg20110407r67597+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1635874/+listing-archive-extra) fta (https://launchpad.net/%7Efta)
5 hours ago Published Lucid Web https://launchpad.net/@@/no amd64 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2433556) i386 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2433557)

Hmm pity it failed but nice to see we are moving on :-)

The Lucid build failed again:

firefox-trunk - 4.2~a1~hg20110408r67700+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1637409/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-trunk_4.2%7Ea1%7Ehg20110408r67700%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes)
fta (https://launchpad.net/%7Efta) 5 hours ago Published Lucid Web https://launchpad.net/@@/no amd64 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2436162) i386 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2436163)

As did Karmic and Hardy.

Maverick looks OK.

firefox-trunk - 4.2~a1~hg20110408r67700+nobinonly-0ubuntu1~umd1~maverick (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1637408/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-trunk_4.2%7Ea1%7Ehg20110408r67700%2Bnobinonly-0ubuntu1%7Eumd1%7Emaverick_source.changes)
fta (https://launchpad.net/%7Efta) 5 hours ago Published Maverick Web https://launchpad.net/@@/yes

[SilverWave]

Mozilla shoots for June 21 release of Firefox 5 (http://www.computerworld.com/s/article/9215660/Mozilla_shoots_for_June_21_release_of_Firefox_5?so urce=rss_news&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+computerworld%2Fnews%2Ffeed+% 28Latest+from+Computerworld%29)

Wow!

[Update]

This Firefox/Features/UX Priorities (https://wiki.mozilla.org/Firefox/Projects/UX_Priorities) is a bit of a goldmine for information on what is coming next :-)

(https://wiki.mozilla.org/Firefox/Projects/UX_Priorities)

[SilverWave]

firefox-trunk - 6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1643001/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-trunk_6.0%7Ea1%7Ehg20110413r68036%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes) fta (https://launchpad.net/%7Efta) 27 minutes ago Published Lucid Web https://launchpad.net/@@/no amd64 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2444496) i386 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2444497)

Maverick looks OK...

Oh well with so much new happening it was possible that it could take some time to get Lucid to build...

Pity though as I would like to play as well :-)

[lovinglinux]

firefox-trunk - 6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1643001/+listing-archive-extra) (changes file) (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+files/firefox-trunk_6.0%7Ea1%7Ehg20110413r68036%2Bnobinonly-0ubuntu1%7Eumd1%7Elucid_source.changes) fta (https://launchpad.net/%7Efta) 27 minutes ago Published Lucid Web https://launchpad.net/@@/no amd64 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2444496) i386 (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+buildjob/2444497)

Maverick looks OK...

Oh well with so much new happening it was possible that it could take some time to get Lucid to build...

Pity though as I would like to play as well :-)

I am working like crazy to keep up :-)

Just released a new version of FoxTester with support for the new aurora and beta repositories.

[SilverWave]

I am working like crazy to keep up :-)

Just released a new version of FoxTester with support for the new aurora and beta repositories.

Here we go first working 6.0A1 for Lucid :D

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1/+sourcepub/1666101/+listing-archive-extra)

That's all for now but lots more later... once I have updated everything.

[SilverWave]

Here we go first working 6.0A1 for Lucid :D

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1/+sourcepub/1666101/+listing-archive-extra)

That's all for now but lots more later... once I have updated everything.


OK that went surprisingly well :-)

Here are the gory details:


firefox-4.0
Changes for the versions:
4.0~b13~hg20110321r63449+nobinonly-0ubuntu1~umd1~lucid
6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid

This change is not from a source that supports changelogs.
(This is a transitional package to ensure that upgrades work correctly. It can be safely removed).

firefox-4.0-globalmenu
Changes for the versions:
4.0~b13~hg20110321r63449+nobinonly-0ubuntu1~umd1~lucid
6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid

This change is not from a source that supports changelogs.
(This is a transitional package to ensure that upgrades work correctly. It can be safely removed).

firefox-trunk (New install)
Changes for the versions:
None
6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid

This change is not from a source that supports changelogs.
(Firefox delivers safe, easy web browsing. A familiar user interface, enhanced security features including protection from online identity theft, and integrated search let you get the most out of the web).


firefox-4.0-globalmenu (New install)
Changes for the versions:
None
6.0~a1~hg20110413r68036+nobinonly-0ubuntu1~umd1~lucid

This change is not from a source that supports changelogs.
(This package provides an extension which adds support for the Unity appmenu to Firefox).

[SilverWave]

OK that went surprisingly well :-)

Here are the gory details:

What happens is that your firefox folder is copied across to firefox-trunk and you also get a cool new icon:


Home (http://www.mozilla.org/) /
http://www.mozilla.org/images/projects/nightly_logo.jpg Firefox Nightlies

Thank you for trying a nightly build and helping improve future versions of Firefox. Learn more about how you can get involved with our testing and developer community.
Getting Started

Use these links to find and report issues.


Submit crash reports (http://support.mozilla.com/en-US/kb/Mozilla%20Crash%20Reporter)
Run test cases in Litmus (https://litmus.mozilla.org/)
Report bugs in Bugzilla (https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox)
Subscribe to Nightly-Testers mailing list (https://mail.mozilla.org/listinfo/nightly-testers)

On start-up I upgraded Add-ons Compatibility reporter and after a reboot all my add-on look to be working!

Before sync'ing I changed the Sync name and reset Sync to pull in all new data from the cloud copy.

This took a while but worked fine... I did reboot it a few times to help the process along a bit.

The only pref that I noticed hasn't replicated yet is all the No-Squint stuff.

So... in shot things are going well and I am writing this from 6.0a1!!!

How cool is that!

[SilverWave]

Yep that's right none of my PPA's will carry Firefox 3.6.
Also Karmic will no longer be supported either.

Most of the old Karmic PPa's are being re-purposed for the new upcoming Natty :-)

Personal package archives

One Daily A Month #0 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-0)
Firefox-trunk - One Daily A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1)
One Daily A Month #2 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-2)
Firefox-trunk - One Daily A Month #3 - Natty (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-3)
One Daily A Month #4 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-4)
Firefox-trunk - One Daily A Month #5 - Maverick (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-5)
One Daily A Week #0 - Lucid (https://launchpad.net/%7Esilverwave/+archive/testing0)
One Daily A Week #1 - Natty (https://launchpad.net/%7Esilverwave/+archive/testing1)
One Daily A Week #2 - Maverick (https://launchpad.net/%7Esilverwave/+archive/testing2)

Any more changes will depend on there being "Aurora" packages made available.

[SilverWave]

Ignore this post LOL

Deleting the following text from the main page as it looks to be no longer relevant.
(Just making a note in case I need to add it back at a later time).


Firefox-Next from the Mozilla Team (https://launchpad.net/%7Emozillateam/+archive/firefox-next)

This PPA contains Milestone builds of the next version of Firefox (alpha, beta, RC).

High safety, easy install. Milestone packages have undergone quality assurance.
Take notice of the version (alpha, beta, RC) for a measure of stability.

Add The Firefox Next PPA:


sudo add-apt-repository ppa:mozillateam/firefox-next
Update & Install


sudo apt-get update
sudo apt-get install firefox-4.0Note that this is best option for most users as:
This PPA only contains Firefox.
You will not be swamped with updates.
Milestone builds are quite polished.

[Jinx13]

Just want to say thanks very much for this all this information helps n00bs like me :D

[SilverWave]

Just want to say thanks very much for this all this information helps n00bs like me :D

Thank you for saying so.

I am pleased you find it useful.

:-)

[SilverWave]

...Most of the old Karmic PPa's are being re-purposed for the new upcoming Natty :-)


Personal package archives

One Daily A Month #0 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-0)
Firefox-trunk - One Daily A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1)
One Daily A Month #2 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-2)
Firefox-trunk - One Daily A Month #3 - Natty (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-3)
One Daily A Month #4 - Not in use (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-4)
Firefox-trunk - One Daily A Month #5 - Maverick (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-5)
One Daily A Week #0 - Lucid (https://launchpad.net/%7Esilverwave/+archive/testing0)
One Daily A Week #1 - Natty (https://launchpad.net/%7Esilverwave/+archive/testing1)
One Daily A Week #2 - Maverick (https://launchpad.net/%7Esilverwave/+archive/testing2)

Updated Natty PPA's with latest firefox-trunk 6.0a1

[SilverWave]

Just a note in case anyone else is having the same problems...

It looked as if FF was trying to sync but, when I checked it hadn't been successful for 4 days.

I tried various strategies but in the end went back to my ff4.0 backup from Monday last (7 days ago).

All is working again thank goodness :-)

As a precaution I have wiped the contents of my FF6.0a1 profile (just leaving the empty firefox-trunk folder) and let ff create a new one on start-up.

This seems to be working OK and I have used Sync on FF4.0 to authorise it (ff6.0a1) successfully.

Was getting a little worried there... I had went back through 4 different backups before I found one that would Sync!

Now I just need to add the extensions back in one at a time for my new ff6.0a1 - oh joy :-( LOL

[SilverWave]

...I tried various strategies but in the end went back to my ff4.0 backup from Monday last (7 days ago).

All is working again thank goodness :-)
...

I have done a little more trouble shooting...
I originally thought it could be a new beta2 of Boox that I had just installed but I no longer think that Boox is the cause.

I think it may be related to my history settings or the size of my sync data.

I have set Firefox to use "custom settings for history" with most of the setting enabled.

I don't see a "specific number of days to remember" setting that was an option in previous ff's.

I will continue to test and report back but for now sync is working again.

[SilverWave]

I have done a little more trouble shooting...
I think it may be related to my history settings or the size of my sync data.

I have set Firefox to use "custom settings for history" with most of the setting enabled...

I have cleared active logins as a test on my ff6.0a1 and that seems to have done the trick.

Prior to that I was getting Sync encountered an unknown error.

[lovinglinux]

I just wanted to let you know that Mozilla is working on a new compatibility workflow for add-ons (http://blog.mozilla.com/addons/2011/04/19/add-on-compatibility-rapid-releases/). Basically add-ons compatible with the latest release will be automatically marked as compatible when a new Firefox version is released, instead of requiring all add-ons authors to bump the compatibility themselves. They will implement automatic tests to prevent bumping compatibility of those add-ons flagged with incompatibilities. This new scheme should be ready for Firefox 5 beta.

[SilverWave]

I just wanted to let you know that Mozilla is working on a new compatibility workflow for add-ons (http://blog.mozilla.com/addons/2011/04/19/add-on-compatibility-rapid-releases/) ...


Well that is simply amazing :-)

[lovinglinux]

Well that is simply amazing :-)

Indeed. That will save add-ons developers a lot of time and will reduce the wait for compatibility patches considerably.

[SilverWave]

Not happy with the new manager but as I can only use Platypus with FF3.6 I was going to have to do something similar in any case.

And I was really missing my 60 scripts!



Note:
FF3.6 had updated Greasemonkey so I had to uninstall and reinstall with the Version 0.8.20100408.6 (https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/versions/) from April 8 2010.

OK it seems to be a time of radical decisions so here is mine:

I have uninstalled Greasemonkey.

I am completley replacing it with Stylish 1.1.2 (https://addons.mozilla.org/en-US/firefox/addon/stylish/) and the DOM Inspector. (https://addons.mozilla.org/en-US/firefox/addon/dom-inspector-6622/)

:o

[SilverWave]

OK it seems to be a time of radical decisions so here is mine:

I have uninstalled Greasemonkey.

I am completely replacing it with Stylish 1.1.2 (https://addons.mozilla.org/en-US/firefox/addon/stylish/) and the DOM Inspector. (https://addons.mozilla.org/en-US/firefox/addon/dom-inspector-6622/)

:o

I originally used Greasemonkey and Platypus to allow me to clean up websites that were cluttered.

But first Platypus was abandoned and then changes were made to the way Greasemonkey scripts were managed.

So I did my first serious test of Stylish for years and found a surprisingly professional product.

Better than Greasemonkey for my uses in the following areas:
1. Speed, Stylish appears to be instantaneous, whereas Greasemonkey slowed page loads appreciably.

2. CSS not JS so no security issues.

3. A huge number of great ready made styles at http://userstyles.org/ presented in a nice clean manor.

4. Fantastic extra tools to help you such as the DOM Inspector (https://addons.mozilla.org/en-US/firefox/addon/dom-inspector-6622/) and the Stylish-Custom (https://addons.mozilla.org/en-US/firefox/addon/stylish-custom/?src=collection&collection_id=aa7d5fd9-1937-8e54-58ee-dffc9bc63499) add-ons for example.

5. Great developer support for both the main add-on and the extra tools.
TBH now that I look at it I cant see how it took me so long to move :-)

That said the main issue with Stylish was a lack of an easy how to... more on that next.

[SilverWave]

... That said the main issue with Stylish was a lack of an easy how to... more on that next.

From the stylish statusbar icon:

Left Click > Write new style

Name:

Ubuntu Forums. Big Edit.CSS:

@namespace url(http://www.w3.org/1999/xhtml); (http://www.w3.org/1999/xhtml%29;)

@-moz-document url-prefix(http://ubuntuforums.org/editpost.php), url-prefix(http://ubuntuforums.org/newreply.php){

DIV[align="left"][style="width:640px"] {width:1000px!important}
#vB_Editor_001_iframe { width: 1000px!important; height: 650px!important; }

}
There you go sorted :-D

__________________

On the web its a one click install here:

http://userstyles.org/styles/47039/silverwave-ubuntuforums-big-edit

Or, from the stylish statusbar icon > Left Click > Find styles for this site...

__________________

Notes:

The trick to using Stylish is finding out what the elements, that you want to alter, are called.

e.g. how to find the names:

#vB_Editor_001_iframe
DIV[align="left"][style="width:640px"]

That will be the subject of the next post on the DOM Inspector (https://addons.mozilla.org/en-US/firefox/addon/dom-inspector-6622/) but the quick answer is right click > "Copy Selector".

[SilverWave]

Install Stylish (https://addons.mozilla.org/en-US/firefox/addon/stylish/)
Install the DOM Inspector (https://addons.mozilla.org/en-US/firefox/addon/dom-inspector-6622/)

From the stylish statusbar icon:

Left Click > Write new style > For bbc.co.uk...

Add the code below:


@namespace url(http://www.w3.org/1999/xhtml); (http://www.w3.org/1999/xhtml%29;)

@-moz-document domain("bbc.co.uk") {

.layout-block-b { display: none !important; }
.layout-block-a { width: 100% !important; }
.story-body { width: 816px !important; }

}To find out which elements to select do the following:

Firefox > Web Developer > DOM inspector >

Click on the Top Left Icon (Magnifying glass with white mouse cursor bottom right.)
"Find a node to inspect by clicking on it"

Then go back to the BBC web page and click on the sidebar that we want to remove...
(A red box will surround the object).

In the DOM inspector it is now displaying a tree view of the web page and the item "hyperpuff".

If you move a little up the tree you will see ".layout-block-b" is the one we want to hide and
".layout-block-a" the one to maximise.

How cool is that!

Note: The element selector "name" can be a LOT more involved, especially if its in a table.
But the solution is to right click the element and choose "Copy Selector" and then type of selector.

More examples of my newbie fumblings here http://userstyles.org/users/98352

__________________

General Note:

This relates to the newest version of Firefox only in that this Stylish replacement, for an unsupported add-on (platypus + greasemonkey), finally enables me to say goodbye to Firefox 3.6 and look forward to Firefox 5 and 6, with the confidence that none of my add-ons will be holding me back.

:-)

[SilverWave]

From a blog post "Deliberacy (http://blog.johnath.com/2011/04/19/deliberacy/)" this is interesting:

Features/Firefox (https://wiki.mozilla.org/Features/Firefox)

Here is a snapshot of the Top Ten P1 items:

[SilverWave]

Almost Tempted with 11.04 Very Impressed.

http://www.theregister.co.uk/Design/graphics/icons/comment/go_48.pngI had promised myself that, as 10.04 is great and rock solid, I would stick with Lucid until the next LTS release...
But having tried 11.04 in a VM I am very tempted...
Surprised that it is so usable so early in the development process TBH.

Decisions, decisions!
;-)

hmm it doesn't look as if you can add the System Monitor or Parcellite to the top bar :-(
Oh well maybe next year.
___

Oh one point about Firefox: If you want the Firefox Button to show once you turn off the Menu Bars, go into Add-ons and disable the "Global Menu Bar Integration".

[SilverWave]

I have just clean installed Natty 11.04 and I love it :-) (http://wp.me/pOd5E-qe).

http://silverwav.files.wordpress.com/2011/04/stunning-and-beautiful1.jpeg?w=700&h=210

Well done to everyone.

Global Menu Bar Integration is a great idea once you use it for a while ;-)

Firefox looks cool.

[SilverWave]

The latest and greatest successful build:

https://launchpad.net/@@/package-source firefox-trunk 6.0~a1~hg20110508r69097+nobinonly-0ubuntu1~umd1

[SilverWave]

Firefox 5 Compatibility Bump (http://blog.mozilla.com/addons/2011/05/21/firefox-5-compatibility-bump/)


Earlier tonight we updated compatibility information for add-ons that work with Firefox 4 to also work with Firefox 5, except in certain cases where we think the add-on may be incompatible. This coincided with the beta release (http://www.mozilla.com/en-US/firefox/channel/) of Firefox 5, though normally it would occur when the Nightly channel is promoted to Aurora, as described in the Rapid Releases Compatibility Plan (http://blog.mozilla.com/addons/2011/04/19/add-on-compatibility-rapid-releases/).
We were able to mark 3,890 add-ons as compatible with Firefox 5. There were 256 that failed our automatic scanners either due to including binary components or using navigator.language, which was changed in Firefox 5. All affected add-on authors received an email about the compatibility update and instructions depending on whether they passed or failed.


Hmm interesting...

I wonder if the Ubuntu Mozilla team are going to open a Beta channel...

[SilverWave]

Firefox 5 Compatibility Bump (http://blog.mozilla.com/addons/2011/05/21/firefox-5-compatibility-bump/)

Hmm interesting...

I wonder if the Ubuntu Mozilla team are going to open a Beta channel...

Looks as if they will, in time, support the Beta Channel but not the Aurora Channel.

firefox aurora channel (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/779646)


Chris Coulson (https://launchpad.net/%7Echrisccoulson) wrote on 2011-05-10: #2 (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/779646/comments/2) Sorry, I spend enough of my time maintaining the daily builds from mozilla-central, and we will support the beta channel too. There's no compelling reason to provide aurora PPA builds at the moment, as hardly anything has changed in Firefox 5.

[lovinglinux]

Firefox 5 Compatibility Bump (http://blog.mozilla.com/addons/2011/05/21/firefox-5-compatibility-bump/)

Hmm interesting...

Indeed. I received the update bump information yesterday. Mozilla has done a great job. The automated validation informed me that most of my extensions were compatible, but warned me about FoxTester using navigator.language and provided the correct method, so I could update the extension. Done.

BTW, Fast Dial is completely broken in FF 5 Beta.

[SilverWave]

https://launchpad.net/@@/package-source firefox-trunk 6.0~a1~hg20110520r69818+nobinonly-0ubuntu1~umd1~natty

[SilverWave]

PPA description


The latest firefox without the update hassle.
One Nightly a week from ubuntu-mozilla-daily.
______________________________
One Nightly A Week #3 - Oneiric
One update a week.
firefox-trunk only
______________________________
sudo add-apt-repository ppa:silverwave/testing3
sudo apt-get update
sudo apt-get install firefox-trunk
______________________________
Disclaimer: Use at your own risk, no guarantees.

[SilverWave]

Firefox Beta - Natty

https://launchpad.net/~silverwave/+archive/testing4 (https://launchpad.net/%7Esilverwave/+archive/testing4)

The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Natty #testing4
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing4
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Maverick

https://launchpad.net/~silverwave/+archive/testing5 (https://launchpad.net/%7Esilverwave/+archive/testing5)
The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Maverick #testing5
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing5
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Lucid

https://launchpad.net/~silverwave/+archive/testing6 (https://launchpad.net/%7Esilverwave/+archive/testing6)

The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Lucid #testing6
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing6
sudo apt-get update
sudo apt-get install firefox
______________________________


Beta – builds created out of the mozilla-beta repository.
Qualified by QA as being of sufficient quality to release to beta users

Note1: I haven't tested these yet but the should be OK as they are beta's :-)
Note2: We are up to firefox - 5.0~b2+build1+nobinonly-0ubuntu0 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra)

[chrisccoulson]

Firefox Beta - Natty

https://launchpad.net/~silverwave/+archive/testing4 (https://launchpad.net/%7Esilverwave/+archive/testing4)

The latest firefox Beta without the update hassle.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Natty #testing4
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing4
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Maverick

https://launchpad.net/~silverwave/+archive/testing5 (https://launchpad.net/%7Esilverwave/+archive/testing5)
The latest firefox Beta without the update hassle.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Maverick #testing5
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing5
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Lucid

https://launchpad.net/~silverwave/+archive/testing6 (https://launchpad.net/%7Esilverwave/+archive/testing6)

The latest firefox Beta without the update hassle.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Lucid #testing6
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing6
sudo apt-get update
sudo apt-get install firefox
______________________________


Beta – builds created out of the mozilla-beta repository.
Qualified by QA as being of sufficient quality to release to beta users

Note1: I haven't tested these yet but the should be OK as they are beta's :-)
Note2: We are up to firefox - 5.0~b2+build1+nobinonly-0ubuntu0 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra)

You say "The latest firefox Beta without the update hassle", but what hassle is that with the beta PPA?

[SilverWave]

You say "The latest firefox Beta without the update hassle", but what hassle is that with the beta PPA?

Not much its just about perfect...

Except Firefox is not the only package in the PPA.

It was also pretty much boiler plate text, so I have removed it now it has been pointed out :-)

[chrisccoulson]

Not much its just about perfect...

Except Firefox is not the only package in the PPA.



The reason for that is because users who had those packages installed before installing the beta will want the updates from the PPA so that they carry on working.

[SilverWave]

https://launchpad.net/~mozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra


* Rebase packaging on Natty, some notable changes: * Drop abrowser. The abrowser branding doesn't work since Firefox 4, and is going to be difficult to maintain going forwards. The Firefox logo is freely licensed now, which was the main reason for the existance of abrowser. Current abrowser users will be migrated to Firefox

-- Chris Coulson



>The Firefox logo is freely licensed now

Well that's good news :-)

[SilverWave]

Firefox Beta - Natty

https://launchpad.net/~silverwave/+archive/testing4 (https://launchpad.net/%7Esilverwave/+archive/testing4)

The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Natty #testing4
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing4
sudo apt-get update
sudo apt-get install firefox
______________________________


Beta – builds created out of the mozilla-beta repository.
Qualified by QA as being of sufficient quality to release to beta users

Note1: I haven't tested these yet but the should be OK as they are beta's :-)
Note2: We are up to firefox - 5.0~b2+build1+nobinonly-0ubuntu0 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra)


Updated Firefox to 5b2 on Natty 64bit and I have some issues:

1. Zoom not working [Fixed #413 (http://ubuntuforums.org/showpost.php?p=10861721&postcount=413)]
2. The "About Help" gives an error (see screenshot) [Fixed#412 (http://ubuntuforums.org/showpost.php?p=10861425&postcount=412)]

Note that this is not a clean profile and I have a lot of add-ons.

Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 ID:20110523215551

[Update]
>1. Zoom not working
This was down to NoSquint - disable, reboot and Zoom works OK.

[chrisccoulson]

Updated Firefox to 5b2 on Natty 64bit and I have some issues:

1. Zoom not working
2. The "About Help" gives an error (see screenshoot)

Note that this is not a clean profile and I have a lot of add-ons.

Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 ID:20110523215551

[Update]
>1. Zoom not working
This was down to NoSquint - disable, reboot and Zoom works OK.

I'm guessing you have the addon compatibility reporter installed? If so, then the incompatible Firefox 4 translation packs will still be enabled, causing the error you see in Help -> About

[SilverWave]

I'm guessing you have the addon compatibility reporter installed? If so, then the incompatible Firefox 4 translation packs will still be enabled, causing the error you see in Help -> About

Yes thanks for the advice, it did the trick :-)

hmm now, how to uninstall them... /goes looking

[SilverWave]

https://launchpad.net/~mozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1742194/+listing-archive-extra)




* Build language packs directly from the firefox source
+ Fixes LP:#294187 (https://launchpad.net/bugs/294187) - Firefox Locales should install locale specific
search plugins
+ Rip out the bits to create a en-US.xpi
- update debian/rules
- remove debian/translation-support/install.rdf.in
+ Include compare-locales FIREFOX_5_0b1_BUILD1 from
http://hg.mozilla.org/build/compare-locales. It's needed for merging
en-US strings with incomplete locales
+ Pull l10n data in to tarball from bzr
- update debian/mozclient/firefox.conf
+ Configure build for creating language packs by configuring with
"--with-l10n-base="
- update debian/mozconfig.in
+ Store the list of locales to ship, and provide a way of automatically
generating that list and the control file entries from the upstream
source. Also provide a way to blacklist languages. We map languages
to package names using langpack-o-matic (and also get descriptions
from there too)
- update debian/rules
- add debian/locales.shipped
- add debian/control.langpacks
- update debian/control.in
- add debian/locale.blacklist
- add debian/refresh-supported-locales.pl
+ Add common-build-indep hook to build the translation xpi's
- update debian/rules
+ Add common-binary-post-install-indep to install the xpi's and
searchplugins in to the correct debian packages
- update debian/rules
- add debian/get-xpi-id.py

[SilverWave]

I'm guessing you have the addon compatibility reporter installed? If so, then the incompatible Firefox 4 translation packs will still be enabled, causing the error you see in Help -> About



Yes thanks for the advice, it did the trick :-)

hmm now, how to uninstall them... /goes looking


Looks as if this is what I was looking for:

/usr/lib/firefox-addons/extensions

I just deleted the .xpi files that were language related.

[SilverWave]

Updated Firefox to 5b2 on Natty 64bit and I have some issues:

[Update]
>1. Zoom not working
This was down to NoSquint - disable, reboot and Zoom works OK.

Latest Version 2.1.1 Works fine with FF5B2

NoSquint Version History (https://addons.mozilla.org/en-US/firefox/addon/nosquint/versions/)

[SilverWave]

extensions.checkCompatibility.nightly


We’ve now changed this and any nightly, try, or self-made builds (anything not on the aurora, beta or release channels) will instead use the single preference extensions.checkCompatibility.nightly from now on, regardless of version. This will be available from tonight’s nightly onwards.

http://www.oxymoronical.com/blog/2011/05/How-to-disable-extension-compatibility-checking-on-Nightly-builds-of-Firefox

[SilverWave]

And the fast release policy really starts to kick in...


Changes for the versions:
6.0~a1~hg20110520r69818+nobinonly-0ubuntu1~umd1
7.0~a1~hg20110529r70295+nobinonly-0ubuntu1~umd1

This change is not from a source that supports changelogs.

Details here:

https://launchpad.net/~silverwave

[SilverWave]

extensions.checkCompatibility.nightly



http://www.oxymoronical.com/blog/2011/05/How-to-disable-extension-compatibility-checking-on-Nightly-builds-of-Firefox

I didn't bother with this on the 6.0 to 7.0 bump...

Instead I accepted the add-on upgrade for Add-on Compatibility Reporter and once loaded rebooted.

All OK so far ;-)

[SilverWave]

Looks as if they will, in time, support the Beta Channel but not the Aurora Channel.

firefox aurora channel (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/779646)

Packages in “Firefox Aurora” (https://launchpad.net/~ubuntu-mozilla-daily/+archive/firefox-aurora/+packages)

Well now it gets interesting :-)

Looks as if we are now first class Firefox citizens :-) and have access to all the Firefox channels.

[SilverWave]

Packages in “Firefox Aurora” (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/firefox-aurora/+packages)

Well now it gets interesting :-)

Looks as if we are now first class Firefox citizens :-) and have access to all the Firefox channels.

Hmm...

Something to be aware of is that the Aurora packages will replace your existing firefox...

I think I prefer to use the Nightly packages as being firefox-trunk you get to keep firefox as well.

Best of both worlds... :-D

I actually use the Beta packages of firefox (atm 5.0b2) in place of the stable 4.0 for my main browser day-to-day.

I use Nightly packages of firefox-trunk to keep in touch with the latest developments.

YMMV

[lovinglinux]

The latest Aurora (6.0a2) has an interesting new feature, the Permissions Manager:

http://www5.picturepush.com/photo/a/5774293/640/5774293.png (http://picturepush.com/public/5774293)

To access it, just type about:permissions in the address bar.

I hope this will evolve into a full-feature site preferences tool like Opera has.

[SilverWave]

The latest Aurora (6.0a2) has an interesting new feature, the Permissions Manager:

http://www5.picturepush.com/photo/a/5774293/640/5774293.png (http://picturepush.com/public/5774293)

To access it, just type about:permissions in the address bar.

I hope this will evolve into a full-feature site preferences tool like Opera has.

Hey this is a good idea! Thanks for the tip.

[SilverWave]

Changes for the versions:
5.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn2
5.0~b3+build1+nobinonly-0ubuntu0.11.04.1~mfn1

Details: https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 5.0~b3+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Esilverwave/+archive/testing4/+sourcepub/1756755/+listing-archive-extra)




Firefox Beta - Natty

https://launchpad.net/~silverwave/+archive/testing4 (https://launchpad.net/%7Esilverwave/+archive/testing4)

The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Natty #testing4
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing4
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Maverick

https://launchpad.net/~silverwave/+archive/testing5 (https://launchpad.net/%7Esilverwave/+archive/testing5)
The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Maverick #testing5
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing5
sudo apt-get update
sudo apt-get install firefox
______________________________


Firefox Beta - Lucid

https://launchpad.net/~silverwave/+archive/testing6 (https://launchpad.net/%7Esilverwave/+archive/testing6)

The latest firefox Beta.
From mozillateam/firefox-next.
______________________________
Firefox Beta - Lucid #testing6
firefox only
______________________________
sudo add-apt-repository ppa:silverwave/testing6
sudo apt-get update
sudo apt-get install firefox
______________________________

[SilverWave]

Changes for the versions:
4.0.1+build1+nobinonly-0ubuntu0.11.04.3
5.0~b6+build1+nobinonly-0ubuntu0.11.04.1~mfn1

Details: https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 5.0~b6+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1773382/+listing-archive-extra)

[SilverWave]

The Latest:

https://launchpad.net/@@/package-source firefox-trunk - 7.0~a1~hg20110613r71005+nobinonly-0ubuntu1~umd2~natty (https://launchpad.net/%7Esilverwave/+archive/testing1/+sourcepub/1774694/+listing-archive-extra)

[SilverWave]

Interesting...


Mozilla to add built-in PDF viewer to Firefox Claims HTML5-JavaScript viewer safer than Chrome's PDF plug-in (http://www.computerworld.com/s/article/9217733/Mozilla_to_add_built_in_PDF_viewer_to_Firefox?sour ce=rss_latest_content&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+computerworld%2Fnews%2Ffeed+% 28Latest+from+Computerworld%29)

[SilverWave]

Here is the latest:

Details: https://launchpad.net/@@/package-source firefox - 5.0~b7+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Esilverwave/+archive/testing4/+sourcepub/1778902/+listing-archive-extra)[/QUOTE]

[lovinglinux]

Interesting...

Indeed. Very interesting.

[SilverWave]

With the new Firefox Beta PPA's now available there is less of a need for the Monthly PPA's.
So the main page will link here allowing me to streamline the First Post instructions.
______________________________

One Nightly A Month #4 - Oneiric (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-4)
One update a month.
Firefox only.
______________________________
sudo add-apt-repository ppa:silverwave/one-daily-a-month-4
sudo apt-get update
sudo apt-get install firefox-trunk
______________________________

One Nightly A Month #3 - Natty (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-3)
One update a month.
Firefox only.
______________________________
sudo add-apt-repository ppa:silverwave/one-daily-a-month-3
sudo apt-get update
sudo apt-get install firefox-trunk
______________________________

One Nightly A Month #5 - Maverick (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-5)
One update a month.
Firefox only.
______________________________
sudo add-apt-repository ppa:silverwave/one-daily-a-month-5
sudo apt-get update
sudo apt-get install firefox-trunk
______________________________

One Nightly A Month #1 - Lucid (https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-1)
One update a month.
Firefox only.
______________________________
sudo add-apt-repository ppa:silverwave/one-daily-a-month-1
sudo apt-get update
sudo apt-get install firefox-trunk
______________________________




(https://launchpad.net/%7Esilverwave/+archive/one-daily-a-month-5)

[SilverWave]

Firefox Beta (https://launchpad.net/%7Emozillateam/+archive/firefox-next)
Firefox Aurora (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/firefox-aurora)
Firefox Nightly (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa?field.series_filter=)

As the Nightly packages are not called firefox, rather firefox-trunk, they can be run side-by-side with firefox.

I think this this is highly desirable and very useful.

The Firefox Beta Channel is working great but it does replace your existing firefox :-(

The same is true for Firefox Aurora Channel :-(

It seems a real shame tbh.

I wonder if the naming of the packages in the other channels could be changed to follow that of the Nightly Channel?

e.g.

Firefox Beta Channel:
firefox-beta

Firefox Aurora Channel:
firefox-aurora

hmmm...

[lovinglinux]

Firefox Beta (https://launchpad.net/%7Emozillateam/+archive/firefox-next)
Firefox Aurora (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/firefox-aurora)
Firefox Nightly (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa?field.series_filter=)

As the Nightly packages are not called firefox, rather firefox-trunk, they can be run side-by-side with firefox.

I think this this is highly desirable and very useful.

The Firefox Beta Channel is working great but it does replace your existing firefox :-(

The same is true for Firefox Aurora Channel :-(

It seems a real shame tbh.

I wonder if the naming of the packages in the other channels could be changed to follow that of the Nightly Channel?

e.g.

Firefox Beta Channel:
firefox-beta

Firefox Aurora Channel:
firefox-aurora

hmmm...

I disagree. I think it is great that firefox-next replaces your existing firefox. This way, there is no more confusion with cloned profiles and customized launchers. It is easier for new users to adopt it.

[chrisccoulson]

Indeed, lovinglinux is right.

Firstly, the beta packages are where we test packages that are eventually going to end up in the distro. Making them parallel installable introduces several problems:

The packaging is totally different, so they are completely useless for testing future distro upgrades. The beta packages should be production quality packages
They rely on ugly hacks to make them fully parallel installable (ie, changing the profile location)
We can't distribute them with the official branding turned on (because of reason 2


The aurora package isn't parallel installable because it makes it impossible for people to swap between channels, for the reason that lovinglinux mentioned. In addition to this, I wanted to hook the channel switcher UI in to the package manager at some point (that was, until Mozilla disabled the UI). Also, having them all parallel installable means maintaining 4 lots of packaging, which is a total headache.

There is a genuine use-case for people wanting to test nightly builds alongside a more stable version (which is what I do), and this is why the nightly build is parallel installable.

We're not going to change the aurora or beta package to be parallel installable.

Also, your beta packages are out-of-date already. The latest beta fixes a critical security issue, so distributing out-of-date packages (with my name on too!) is quite irresponsible. Please fix that. People should be running the latest beta anyway, there is no point in people testing out-of-date builds.

[SilverWave]

Indeed, lovinglinux is right.

Firstly, the beta packages are where we test packages that are eventually going to end up in the distro. Making them parallel installable introduces several problems:

The packaging is totally different, so they are completely useless for testing future distro upgrades. The beta packages should be production quality packages
They rely on ugly hacks to make them fully parallel installable (ie, changing the profile location)
We can't distribute them with the official branding turned on (because of reason 2


The aurora package isn't parallel installable because it makes it impossible for people to swap between channels, for the reason that lovinglinux mentioned. In addition to this, I wanted to hook the channel switcher UI in to the package manager at some point (that was, until Mozilla disabled the UI). Also, having them all parallel installable means maintaining 4 lots of packaging, which is a total headache.

There is a genuine use-case for people wanting to test nightly builds alongside a more stable version (which is what I do), and this is why the nightly build is parallel installable.

We're not going to change the aurora or beta package to be parallel installable.

Also, your beta packages are out-of-date already. The latest beta fixes a critical security issue, so distributing out-of-date packages (with my name on too!) is quite irresponsible. Please fix that. People should be running the latest beta anyway, there is no point in people testing out-of-date builds.

>Also, your beta packages are out-of-date already.

What are you referring to I don't see a Beta 8 in the Beta Channel?

[chrisccoulson]

Oh, you're right, sorry. I only saw when you copied beta 6 in my inbox, I didn't get another notification after that

[SilverWave]

Indeed, lovinglinux is right.

Firstly, the beta packages are where we test packages that are eventually going to end up in the distro. Making them parallel installable introduces several problems:

The packaging is totally different, so they are completely useless for testing future distro upgrades. The beta packages should be production quality packages
They rely on ugly hacks to make them fully parallel installable (ie, changing the profile location)

Fair enough.


3. We can't distribute them with the official branding turned on (because of reason 2Hmm I get the Official "Nightly" branding with firefox-trunk are the terms different for Aurora and Beta?


The aurora package isn't parallel installable because it makes it impossible for people to swap between channels, for the reason that lovinglinux mentioned. In addition to this, I wanted to hook the channel switcher UI in to the package manager at some point (that was, until Mozilla disabled the UI). Also, having them all parallel installable means maintaining 4 lots of packaging, which is a total headache.Yes I can see that, pity as I think a lot of ppl would like to use Aurora in place of Nightly.


There is a genuine use-case for people wanting to test nightly builds alongside a more stable version (which is what I do), and this is why the nightly build is parallel installable.Agreed.


We're not going to change the aurora or beta package to be parallel installable.Hmm I'll take that as a tentative "No" then. :-)

[SilverWave]

I disagree. I think it is great that firefox-next replaces your existing firefox. This way, there is no more confusion with cloned profiles and customized launchers. It is easier for new users to adopt it.

Hmm I can see that from a support point of view that this is better. :-)

Although I think side-by-side installs for aurora would encourage a lot more users to become Aurora Channel testers.

Which would be a "Good Thing".

[chrisccoulson]

Fair enough.

Hmm I get the Official "Nightly" branding with firefox-trunk are the terms different for Aurora and Beta?



The official branding is the Firefox name and logo

[lovinglinux]

Hmm I can see that from a support point of view that this is better. :-)

Although I think side-by-side installs for aurora would encourage a lot more users to become Aurora Channel testers.

Which would be a "Good Thing".

I haven't thought about that. My main concern is the support, after all I need to regularly test more versions than those provided by aurora and nightly. So I don't use the repositories for testing anyway.

[SilverWave]

5.0+build1+nobinonly-0ubuntu0.11.04.1

Changes for the versions:

Changes for the versions:
5.0~b7+build1+nobinonly-0ubuntu0.11.04.1~mfn1
5.0+build1+nobinonly-0ubuntu0.11.04.1

Version 5.0+build1+nobinonly-0ubuntu0.11.04.1:

* New upstream release from the stable channel (FIREFOX_5_0_BUILD1)
- see LP: #798484 for USN information

* Update globalmenu-extension to 1.0.6
* Switch to mozilla-beta
- update debian/mozclient/firefox.conf
* Drop the ability to build with an external xulrunner, and all the packaging
complexity which went with it
- update debian/apport/firefox.in
- update debian/firefox.install.in
- update debian/firefox.lintian-overrides.in
- update debian/firefox.sh.in
- update debian/mozconfig.in
- update debian/rules
* Build language packs directly from the firefox source
+ Fixes LP: #294187 - Firefox Locales should install locale specific
search plugins
+ Rip out the bits to create a en-US.xpi
- update debian/rules
- remove debian/translation-support/install.rdf.in
+ Include compare-locales FIREFOX_5_0b1_BUILD1 from
http://hg.mozilla.org/build/compare-locales. It's needed for merging
en-US strings with incomplete locales
+ Pull l10n data in to tarball from bzr
- update debian/mozclient/firefox.conf
+ Configure build for creating language packs by configuring with
"--with-l10n-base="
- update debian/mozconfig.in
+ Store the list of locales to ship, and provide a way of automatically
generating that list and the control file entries from the upstream
source. Also provide a way to blacklist languages. We map languages
to package names using langpack-o-matic (and also get descriptions
from there too)
- update debian/rules
- add debian/locales-supported
- add debian/control.langpacks
- update debian/control
- add debian/locale-blacklist
- add debian/refresh-supported-locales.pl
+ Add common-build-indep hook to build the translation xpi's
- update debian/rules
+ Add common-binary-post-install-indep to install the xpi's and
searchplugins in to the correct debian packages
- update debian/rules
- add debian/get-xpi-id.py
+ When rebuilding debian/control in the clean target, fail the build
if the control file was out-of-date. This ensures that we don't
accidentally drop language packs, and forces me to maintain an
up-to-date control file in bzr
- update debian/rules
+ Apply vendor patches to localized searchplugins too
- update debian/patches/ubuntu-codes-amazon.patch
- add debian/patches/ubuntu-codes-baidu.patch
- update debian/patches/ubuntu-codes-google.patch
* Ditch all the version-number based branding selection. Do this all
purely on the channel name now
- remove debian/firefox-beta.desktop.in
- remove debian/firefox-nightly.desktop.in
- remove debian/firefox-unofficial.desktop.in
- rename debian/firefox-final.desktop.in => debian/firefox.desktop.in
- update debian/firefox.desktop.in
- update debian/rules
- update debian/firefox.sh.in
* Drop the DEB_ENABLE_IPC option, now that IPC is mandatory
- update debian/rules
- update debian/apport/firefox.in
- update debian/firefox.install.in
- update debian/mozconfig.in
* Add some missing options to the manpage
- update debian/firefox.1.in
* Ensure we set LD_LIBRARY_PATH before running "firefox -h"
- update debian/firefox.sh.in
* Drop patches merged upstream:
- 64-bit-be-fix.patch
* Refresh patches:
- mozilla-kde.patch
* Ship channel-prefs.js. We used to ship this in Firefox 3.6, and it's
required by Test Pilot now
- update debian/firefox.install.in
* Backport patch from mozilla-central to fix powerpc build failure
- add debian/patches/powerpc-build-fix.patch
- update debian/patches/series
* Support storing language descriptions in locales.unavailable. This
will be useful for translations which disappear temporarily
- update debian/rules
- update debian/refresh-supported-locales.pl
* Add languages that are currently dropped in FF5 (compared with FF4) to
locales.unavailable. Having transitional packages now will make
transitioning easier later on if they come back
- update debian/locales.unavailable
* Refresh debian/control to pick up transitional packages
* Don't bundle our vendor preferences in the omni.jar. This needs a distro
patch and it turns out that Firefox does still read prefs from
$LIBDIR/defaults/pref, so just install it there instead
- update debian/rules
- update debian/firefox.install.in
- remove debian/patches/install-vendor-prefs.patch
- update debian/patches/series
* Add a global pref file again (/etc/firefox/syspref.js) and add the
necessary preinst/postinst magic to move the old file there if it
was previously customized
- add debian/syspref.js
- update debian/firefox.install.in
- update debian/firefox.links.in
- update debian/firefox.postinst.in
- update debian/firefox.preinst.in
* Ensure "Depends: ${misc:Depends}" is added to all transitional
language packs
- update debian/control.langpacks.unavail
- refresh debian/control
* Ship testpilot on aurora too
- update debian/firefox.install.in
* Set the right Vcs-Bzr URL
- update debian/control.in
- refresh debian/control
* Update list of language packs to include new ones added upstream
- refresh debian/locales.shipped and debian/locals.unavailable
- refresh debian/control
apt-cache policy firefox
sil@irop:~$ apt-cache policy firefox
firefox:
Installed: 5.0+build1+nobinonly-0ubuntu0.11.04.1
Candidate: 5.0+build1+nobinonly-0ubuntu0.11.04.1
Version table:
*** 5.0+build1+nobinonly-0ubuntu0.11.04.1 0
500 http://gb.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ natty-security/main amd64 Packages
100 /var/lib/dpkg/status
5.0~b7+build1+nobinonly-0ubuntu0.11.04.1~mfn1 0
500 http://ppa.launchpad.net/silverwave/testing4/ubuntu/ natty/main amd64 Packages
4.0+nobinonly-0ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
sil@irop:~$

[SilverWave]

Interesting :-)

Firefox 5 Benchmarked – Faster And Better Than Ever Before! (http://digitizor.com/2011/06/21/firefox-5-benchmark/)

- Uses Less Memory Than Chrome

http://files.digitizor.com/wp-content/uploads/2011/06/ff5-memory.png

[SilverWave]

Changes for the versions:
7.0~a1~hg20110619r71298+nobinonly-0ubuntu1~umd1~natty

[SilverWave]

Hmm interesting...

Asa to write a channels blog post about running different channels side-by-side (http://blog.mozilla.com/channels/2011/06/22/aurora-channeltriage-meeting-%e2%80%93-june-21st-2011/)

... one to watch out for.

[SilverWave]

oh oh...


Christian wanted to talk about why Aurora seems to have a higher crash rate than both Nightly and Beta (https://crash-stats.mozilla.com/products/Firefox). We discussed at the last meeting and expected it to come down but it has not

[SilverWave]

Mozilla retires Firefox 4 from security support (http://www.computerworld.com/s/article/9217837/Mozilla_retires_Firefox_4_from_security_support)


Christian Legnitto, the Firefox release manager, put it most succinctly in a May 25 message. "Firefox 5 will be the security update for Firefox 4," Legnitto said.

Wow.

[lovinglinux]

Mozilla retires Firefox 4 from security support (http://www.computerworld.com/s/article/9217837/Mozilla_retires_Firefox_4_from_security_support)


Wow.

Yes, Firefox 5 replaces Firefox 4 completely. There won't be multiple supported versions anymore, as soon as they drop support for Firefox 3.5 and 3.6. Then, Firefox will become essentially a "rolling distribution". However, I don't think they have figured out everything yet. There is still the possibility of the release of a 4.0.2, although that is very unlikely.

[SilverWave]

Yes, Firefox 5 replaces Firefox 4 completely. There won't be multiple supported versions anymore, as soon as they drop support for Firefox 3.5 and 3.6. Then, Firefox will become essentially a "rolling distribution". However, I don't think they have figured out everything yet. There is still the possibility of the release of a 4.0.2, although that is very unlikely.


Good move by Mozilla.

This whole new fast release change, has breathed a new lease of life into to Firefox development.

I was surprised by the security support stop for ff4, but it makes a lot of sense once I gave it some thought, you concentrate your efforts on the main game instead of wasting them on yesterdays tech.

The add-on issue is being addressed in the short-term by auto bumping all working add-ons.

Long term Jetpack and other initiatives will sort this out.

Well done Mozilla, Well done.

Of course not everyone is going to be happy with this change ;-)

[lovinglinux]

Good move by Mozilla.

This whole new fast release change, has breathed a new lease of life into to Firefox development.

I was surprised by the security support stop for ff4, but it makes a lot of sense once I gave it some thought, you concentrate your efforts on the main game instead of wasting them on yesterdays tech.

The add-on issue is being addressed in the short-term by auto bumping all working add-ons.

Long term Jetpack and other initiatives will sort this out.

Well done Mozilla, Well done.

Indeed.


Of course not everyone is going to be happy with this change ;-)

See this thread (http://ubuntuforums.org/showthread.php?t=1788496) for example.

[SilverWave]

Indeed.
See this thread (http://ubuntuforums.org/showthread.php?t=1788496) for example.


Just a final thought...
Previously we would get very few firefox updates and we received them late...
Under the new model this is no longer the case.
This is a big win for Linux firefox users.

[graabein]

Hey what's the Firefox 5 PPA for us guys on Ubuntu 10.10?

[SilverWave]

Hey what's the Firefox 5 PPA for us guys on Ubuntu 10.10?

The Stable FF5 is here:

10.04 & 10.10:
https://launchpad.net/~mozillateam/+archive/firefox-stable (https://launchpad.net/%7Emozillateam/+archive/firefox-stable)

sudo add-apt-repository ppa:mozillateam/firefox-stable Update & Install

sudo apt-get update
sudo apt-get install firefox

[SilverWave]

This is a great article full of interesting information:

Why do Firefox updates break add-ons? (http://www.oxymoronical.com/blog/2011/06/Why-do-Firefox-updates-break-add-ons)


The crux of the matter is in how deeply we allow add-ons integrate with Firefox. Most browsers separate add-ons from their code using what can be called an add-on API. All the add-on can see and use is what the browser makes available through that API and this is normally a restricted set of functionality. Firefox has no such separation. Add-on code runs in exactly the same setting as the browser code, they can call any of the internal functionality that we write to make the browser work in the first place.
There are big advantages to the Firefox way:


Add-ons can do basically anything, allowing really complicated add-ons like Firebug and NoScript to exist.
Authors don’t have to wait for features to be exposed through some API to be able to use it, as soon as the feature is in the application add-ons can use it.

There are also some disadvantages:


Add-ons can do basically anything so you should be wary about installing add-ons from people you don’t trust!
Because we aren’t forced to provide an API specifically for add-ons sometimes what is there can be cumbersome for add-ons to use.
Add-ons rely on internal functions, if we make a change to one then it breaks the add-on.

It is that last point which explains why Firefox updates break add-ons. Any time we add, remove or change some code we run a risk that some add-on depends on it and so will break. Some bits of code are more important than others but we have such a vast library of add-ons now that it’s probably getting to the point where almost everything is in use. When people say that Firefox updates shouldn’t break add-ons what they don’t realise is that they’re asking us to stop making changes to Firefox: no new features, no bug fixes.


And here is the fix for a lot of add-ons, at least in theory...


How does the Add-ons SDK fit in?

With the most recent update to Firefox we also made the first official release of the new add-ons SDK (https://addons.mozilla.org/en-US/developers/builder) available. These are tools designed to make developing add-ons for Firefox easier and faster and they largely serve as an add-ons API sitting between the add-on and Firefox with one difference, the API is actually a part of the add-on so you can actually write your own additional APIs to supplement those in the core SDK.
Add-ons written with the SDK (and only using the core APIs) gain a lot of the benefits of add-ons for other browsers. The APIs in the SDK can be far more stable than those in the browser itself, as the browser code changes the internal SDK code can adapt to match allowing add-ons to work just by rebuilding with the newer SDK. This makes the problem of Firefox updates much smaller for those that can move their add-ons to the SDK.
I don’t foresee a future where the only add-ons are SDK based though. We’d lose too many really important add-ons that way so the SDK doesn’t completely solve the problem.

[lovinglinux]

Why do Firefox updates break add-ons? (http://www.oxymoronical.com/blog/2011/06/Why-do-Firefox-updates-break-add-ons)

Also why Firefox add-ons are better than other browsers, in terms of functionality.

[SilverWave]

Also why Firefox add-ons are better than other browsers, in terms of functionality.

True true...

I should also point out that you are giving the add-on developer a lot of trust, as he has such low level access to your browser.

[lovinglinux]

True true...

I should also point out that you are giving the add-on developer a lot of trust, as he has such low level access to your browser.

Indeed, but Mozilla scan and review all ad-ons, including new versions, prior to making them public.

I hope you don't mind, but I am leeching your posts with nice articles and reposting in the Mega Thread (http://ubuntuforums.org/showpost.php?p=10979968&postcount=1036). You find some really nice stuff. :-)

[graabein]

Thanks for the link :)

[geazzy]

nice threads :)

[SilverWave]

Telemetry is on in Nightly Firefox builds (http://blog.mozilla.com/tglek/2011/06/27/telemetry-is-on-in-nightly-firefox-builds/)


Telemetry went live in Firefox Nightly builds over the weekend. Everyone who wants to contribute to making Firefox better now has an easy new way: opt-in to telemetry.
There are two ways to opt in:
A) Click yes when prompted to report performance
B) Enable it by going to Options/Preferences, then Advanced/General tab

[SilverWave]

Firefox 6 will be released in eight weeks (http://blog.mozilla.com/nnethercote/2011/06/28/firefox-6-will-be-released-in-six-weeks/)


Update: Mike Hommey has kindly corrected me; there will be 8 weeks between FF5 and FF6. There will then be 6 weeks between all subsequent releases. The 12 week gap between FF4 and FF5 and the 8-week gap between FF5 and FF6 were artifacts of the timeline used to get the rapid release process up to speed.
Nicholas Nethercote Glandium: thanks for the correction. https://wiki.mozilla.org/RapidRelease doesn’t have much detail beyond FF5, but I just found https://wiki.mozilla.org/RapidRelease/Calendar which has this:
2011-07-05: Firefox 7 -> mozilla-aurora; Firefox 6 -> mozilla-beta
2011-08-16: Firefox 8 -> mozilla-aurora; Firefox 7 -> mozilla-beta; Firefox 6 -> mozilla-release
2011-09-27: Firefox 9 -> mozilla-aurora; Firefox 8 -> mozilla-beta; Firefox 7 -> mozilla-release
2011-11-08: Firefox 10 -> mozilla-aurora; Firefox 9 -> mozilla-beta; Firefox 8 -> mozilla-release
2011-12-20: Firefox 11 -> mozilla-aurora; Firefox 10 -> mozilla-beta; Firefox 9 -> mozilla-release

[SilverWave]

Add-ons can do basically anything, allowing really complicated add-ons like Firebug and NoScript to exist.

Also why Firefox add-ons are better than other browsers, in terms of functionality.
I don’t foresee a future where the only add-ons are SDK based though. We’d lose too many really important add-ons that way so the SDK doesn’t completely solve the problem.I have a real world example of this with Boox 3.0 (https://addons.mozilla.org/en-US/firefox/addon/boox/)

Unfortunatly, it's impossible to develop Boox with the sdk.


Oh that's a shame :-( I am just concerned regarding the new FF fast release being every 6 weeks in future (8weeks for ff6).
Well... they are apparently doing more testing of Add-ons to help to keep the breakage to a minimum

Hopefully they wont make any changes that affect Boox ;-)


So I am in the same boat as everyone else regarding add-ons, as this one add-on is a deal breaker for me re updating...
...while wanting to be as secure as possible, and so needing the latest security updates :-|

[lovinglinux]

I have a real world example of this with Boox 3.0 (https://addons.mozilla.org/en-US/firefox/addon/boox/)

So I am in the same boat as everyone else regarding add-ons, as this one add-on is a deal breaker for me re updating.

But Boox is already compatible with FF 6.

[SilverWave]

But Boox is already compatible with FF 6.

Indeed but as the author can not use the SDK there is no guarantee that this will be so with later versions.

And with new versions hitting every 6 weeks... well I am keeping my fingers crossed :-D

[lovinglinux]

Indeed but as the author can not use the SDK there is no guarantee that this will be so with later versions.

And with new versions hitting every 6 weeks... well I am keeping my fingers crossed :-D

At least you are safe for at least the next 14 weeks.

[SilverWave]

Firefox 5 A Success For Mozilla (http://www.conceivablytech.com/8186/products/firefox-5-a-success-for-mozilla)


This is a browser that was created as a launch platform for future Mozilla browsers. In some way, Firefox 5 is a browser that Mozilla made for itself.
After one week of availability, Firefox 5 was listed with a market share of 10.78%, which translates to about 38.5% of Firefox’ entire user base. Firefox 4 had only 5.34% of share after one week, or about 18.0% of the Firefox user base. Firefox 3.6 was even slower, capturing only 3.06% market share or 9.6% of the Firefox user base within the first week.

http://www.conceivablytech.com/wp-content/uploads/2011/06/browsertransition.jpg

[SilverWave]

Changes for the versions:
7.0~a1~hg20110619r71298+nobinonly-0ubuntu1~umd1~natty
7.0~a1~hg20110701r72120+nobinonly-0ubuntu1~umd1~natty

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 7.0~a1~hg20110701r72120+nobinonly-0ubuntu1~umd1~natty (https://launchpad.net/%7Esilverwave/+archive/testing1/+sourcepub/1803685/+listing-archive-extra)


Interesting...


* Drop the profile migrator, as it doesn't really make any sense with the new
release cycle. Instead, just copy the firefox profile (if it exists) to
firefox-trunk (if it doesn't exist)
- remove debian/migrator/xulapp-profilemigrator
- update debian/firefox.sh.in
- update debian/firefox.install.in
- update debian/rules
- update debian/control{.in}
* Now we have no profile migrator and upstream lazily load libxul, drop our
shell wrapper for eveerything except firefox-trunk builds (where we want
to clone the firefox profile)
- update debian/firefox.sh.in
- update debian/rules
- update debian/firefox.install.in
* Ensure we install dependentlibs.list so that Firefox knows which libs
to dlopen before libxul
- update debian/firefox.install.in
-- Chris Coulson <chris.coulson@canonical.com> Fri, 01 Jul 2011 11:37:13 +0100

[SilverWave]

Interesting...

Behind the scene mechanics of Firefox5.0 / Fennec5.0 (http://oduinn.com/blog/2011/07/01/behind-the-scene-mechanics-of-firefox5-0-fennec5-0/)


3) In the days leading up to the Firefox5.0/Fennec5.0/3.6.18 release, we did nine last-minute betas/releases in quick succession (http://oduinn.com/blog/2011/06/20/10-releases-in-9-days/).
This fast turnaround was only possible because RelEng’s ongoing automation improvements has reduced our build times from 45hours down to 8hours. It was only because of this fast turnaround that Mozilla could accommodate some last minute fixes without impacting the release schedule. I feel its important to point out that, while there were tight deadlines, and a lot of very precise fast moving footwork, this was all done without burning out the humans in RelEng working those releases.

[SilverWave]

So here we go again :-)


Source Migration Notice: FINISHED mozilla-central → mozilla-aurora

Source Migration Notice: We have finished the mozilla-central → mozilla-aurora source code migration.

This entry was posted on Tuesday, July 5th, 2011 at 9:48 am and is filed under Source Migration (http://blog.mozilla.com/channels/category/source-migration/).

here (http://blog.mozilla.com/channels/2011/07/05/source-migration-notice-finished-mozilla-central-mozilla-aurora-2/)

[SilverWave]

Changes for the versions:
7.0~a1~hg20110701r72120+nobinonly-0ubuntu1~umd1~natty
8.0~a1~hg20110706r72416+nobinonly-0ubuntu1~umd1~natty

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 8.0~a1~hg20110706r72416+nobinonly-0ubuntu1~umd1~natty (https://launchpad.net/%7Esilverwave/+archive/testing1/+sourcepub/1808813/+listing-archive-extra)

[SilverWave]

hmmm...

Firefox 8 First Taste, Firefox 6 Beta and Firefox 7 Aurora Soon (http://news.softpedia.com/news/Firefox-8-First-Taste-Firefox-6-Beta-and-Firefox-7-Aurora-Soon-210100.shtml)


Various sources claimed that July 5 would bring with it the availability of Firefox 6 Beta and Firefox 7 Aurora. Obviously, this was not the case.

The reason for this is that July 5 was actually the merge date for Firefox 6 Beta and Firefox 7 Aurora, and not the launch deadline for the two development milestones.

It will still be some time before the fully-fledged Firefox 6 Beta and Firefox 7 Aurora are ready to be shipped to testers, which will be soon enough.

[SilverWave]

hmmm...

Firefox 8 First Taste, Firefox 6 Beta and Firefox 7 Aurora Soon (http://news.softpedia.com/news/Firefox-8-First-Taste-Firefox-6-Beta-and-Firefox-7-Aurora-Soon-210100.shtml)

Well the Aurora (https://launchpad.net/~ubuntu-mozilla-daily/+archive/firefox-aurora/+packages) packages are being built as I write this...

[lovinglinux]

Firefox 8 brings memory tests page. Just type about:memory in the address bar.

http://www4.picturepush.com/photo/a/6043007/640/6043007.png (http://picturepush.com/public/6043007)

[SilverWave]

This was the final week of development for Firefox 7, and lots of exciting MemShrink stuff happened. (http://blog.mozilla.com/nnethercote/2011/07/06/memshrink-progress-week-3/)

Well this is great news -)


Parts of Firefox itself are implemented in JavaScript, and many objects belonging to Firefox itself (more specifically, objects in the “system principal” and “atoms” compartments) are long-lived. So Gregor added simple chunk segregation; objects belonging to Firefox get put in one group of chunks, and all other objects (i.e. those from websites) get put in a second group of chunks. This made a huge difference. See this comment (https://bugzilla.mozilla.org/show_bug.cgi?id=666058#c31) and subsequent comments for some detailed measurements of a short browsing session; in short, the size of the heap was over 5x smaller (21MB vs. 108MB) after closing a number of tabs and forcing garbage collection.

[SilverWave]

Firefox 8 brings memory tests page. Just type about:memory in the address bar.

http://www4.picturepush.com/photo/a/6043007/640/6043007.png (http://picturepush.com/public/6043007)

Thanks just starting to play about with that :-)

[SilverWave]

hmmm...

Firefox 8 First Taste, Firefox 6 Beta and Firefox 7 Aurora Soon (http://news.softpedia.com/news/Firefox-8-First-Taste-Firefox-6-Beta-and-Firefox-7-Aurora-Soon-210100.shtml)

And here we go with the Beta (https://launchpad.net/~mozillateam/+archive/firefox-next/+packages) :-)

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 6.0~b1+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1809007/+listing-archive-extra)

Again building as I write this...

[SilverWave]

________________________________________

Firefox 6 currently in BETA channel moves to RELEASED on August 16, 2011.

https://wiki.mozilla.org/images/1/1e/Final-50slice.png (https://wiki.mozilla.org/File:Final-50slice.png)

Firefox 7 currently in AURORA channel moves to BETA on August 16, 2011.

https://wiki.mozilla.org/images/4/4f/Aurora-50slice.png (https://wiki.mozilla.org/File:Aurora-50slice.png)

Firefox 8 currently in NIGHTLY channel moves to AURORA on August 16, 2011.

https://wiki.mozilla.org/images/f/fa/Nightly-50slice.png (https://wiki.mozilla.org/File:Nightly-50slice.png)

________________________________________

[SilverWave]

And here we go with the Beta (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+packages) :-)

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 6.0~b1+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1809007/+listing-archive-extra)

Again building as I write this...


Updated Firefox on my Natty box to the new beta 1 and all looks OK so far.

Note: The other builds failed.

[chrisccoulson]

Updated Firefox on my Natty box to the new beta 1 and all looks OK so far.

Note: The other builds failed.

Publishing is currently disabled for the firefox-next PPA because Mozilla haven't even officially released 6.0 to beta testers yet (that might happen later today). Could you please not copy these pre-release builds and publish them to everyone before they are released?

[SilverWave]

Publishing is currently disabled for the firefox-next PPA because Mozilla haven't even officially released 6.0 to beta testers yet (that might happen later today). Could you please not copy these pre-release builds and publish them to everyone before they are released?

Yes I stopped after Natty, once I noticed Publishing was disabled.

Saying which the natty build looks OK and I am using it to post this reply.

[SilverWave]

Firefox 6 arrives in Beta Channel (http://www.h-online.com/open/news/item/Firefox-6-arrives-in-Beta-Channel-1274620.html)

Release Notes (http://www.mozilla.com/en-US/firefox/6.0beta/releasenotes/)

[SilverWave]

The Beta 1's are now Published.

Changes for the versions:
6.0~b1+build1+nobinonly-0ubuntu0.11.04.1~mfn1
6.0~b1+build1+nobinonly-0ubuntu0.11.04.1~mfn2

Natty
Maverick
Lucid

https://launchpad.net/@@/treeExpanded https://launchpad.net/@@/package-source firefox - 6.0~b1+build1+nobinonly-0ubuntu0.11.04.1~mfn2 (https://launchpad.net/%7Esilverwave/+archive/testing4/+sourcepub/1812529/+listing-archive-extra)

[SilverWave]

Here we go...

https://launchpad.net/@@/package-source firefox-trunk 8.0~a1~hg20110711r72585+nobinonly-0ubuntu1~umd1~natty

As I have heard great things regarding the new nightlies I am going to see if I cant use 8.0a as my main browser...
we shall see :-)

[SilverWave]

Here we go...

https://launchpad.net/@@/package-source firefox-trunk 8.0~a1~hg20110711r72585+nobinonly-0ubuntu1~umd1~natty

As I have heard great things regarding the new nightlies I am going to see if I cant use 8.0a as my main browser...
we shall see :-)

Happy to report that everything works perfectly - you would think it was a Beta rather than a nightly :-D

All I did was add the PPA for the Natty Nightly then update and accept the package offered.

Once it had updated I copied my profile from firefox to firefox-trunk(after deleting the contents of firefox-trunk).

All my add-ons work! Nice :smile:

[SilverWave]

...

All my add-ons work! Nice :smile:

Here is a dump of everything I have loaded in the Nightly:


Adblock Plus 1.3.9
Add-on Compatibility Reporter 0.8.5
Barlesque 1.15
Boox 3.0
Default 8.0a1
DivX® Web Player [DISABLED]
DOM Inspector 2.0.10
Download Statusbar 0.9.8
Gawker 2011 - Vintage Gawker (Removed Sidebar) FIX
Global Menu Bar integration 1.8pre
IcedTea-Web Plugin (using IcedTea-Web 1.1pre (1.1~20110420-0ubuntu1.1)) [DISABLED]
Image Zoom 0.4.6
Locationbar² 1.0.6
Make Link 11.03
Menu Editor 1.2.7
Mozilla Labs 1260925626 [DISABLED]
Nightly Tester Tools 3.1.7
NoSquint 2.1.2
OPML Support 1.6
OptimizeGoogle 0.78.2
Places’ Full Titles 4
QuickTime Plug-in 7.6.6 [DISABLED]
Re-Pagination 2011.03.24
Readability 1.5
Reliby 1.5.0
RequestPolicy 0.5.21
Shelve 1.23
Shockwave Flash
SilverWave - ARS0. No Sidebar. arstechnica.com
SilverWave - BB00. No Sidebar. bloomberg.com
SilverWave - BBC0. No Sidebar. bbc.co.uk
SilverWave - BF00. No Sidebar. blogs.forbes.com
SilverWave - CNET. No Sidebar. cnet.com
SilverWave - CTEC. No Sidebar. conceivablytech.com
SilverWave - CW00. No Sidebar. computerworld.com
SilverWave - CWU0. No Sidebar. computerworlduk.com
SilverWave - FOOL. No Sidebar. fool.com
SilverWave - H000. No Sidebar. h-online.com
SilverWave - MP00. No Sidebar. www.maximumpc.com (http://www.maximumpc.com/)
SilverWave - NYT0. No Sidebar. nytimes.com
SilverWave - PCM0. No Sidebar. pcmag.com
SilverWave - PCO0. No Sidebar. paidcontent.org
SilverWave - PCW0. No Sidebar. www.pcworld.com (http://www.pcworld.com/)
SilverWave - REG0. No Sidebar. theregister.co.uk
SilverWave - RWW0. No Sidebar. www.readwriteweb.co (http://www.readwriteweb.co/)
SilverWave - SEL0. No Sidebar. searchengineland.co
SilverWave - SH00. No Sidebar. singularityhub.com
SilverWave - SP00. No Sidebar. softpedia.com
SilverWave - TC00. No Sidebar. techcrunch.com
SilverWave - TCRU. No Sidebar. techcrunch.com
SilverWave - TD00. No Sidebar. techdrivein.com
SilverWave - TFLA. No Sidebar. techflash.com
SilverWave - TNW0. No Sidebar. thenextweb.com
SilverWave - TR00. No Sidebar. www.techrepublic.co (http://www.techrepublic.co/)
SilverWave - TST0. No Sidebar. tested.com
SilverWave - TT00. No Sidebar. searchsqlserver.tec
SilverWave - UF00. Big Edit. ubuntuforums.org/edit
SilverWave - UG00. No Sidebar. ubuntugeek.com
SilverWave - UT00. No Sidebar. universetoday.com
SilverWave - VARG. No Sidebar. thevarguy.com
SilverWave - WASH. No Sidebar. washingtonpost.com
SilverWave - WSJ0. No Sidebar. online.wsj.com
SilverWave - ZDNT. No Sidebar. zdnet.com
Stylish 1.2
Stylish-Custom 0.7.7
Tab Utilities 1.1
Toolbar Buttons 1.0
Tree Style Tab 0.12.2011061701
Ubuntu Firefox Modifications 0.9.1
VLC Multimedia Plugin (compatible Totem 2.32.0)
Web Developer 1.1.9
Windows Media Player Plug-in 10 (compatible; Totem) [DISABLED]

[SilverWave]

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 6.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1818348/+listing-archive-extra)

[SilverWave]

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox-trunk - 8.0~a1~hg20110714r72818+nobinonly-0ubuntu1~umd1~natty (https://launchpad.net/%7Eubuntu-mozilla-daily/+archive/ppa/+sourcepub/1819249/+listing-archive-extra)

All look OK except the i386 Oneiric build.

[SilverWave]

https://launchpad.net/@@/treeCollapsed https://launchpad.net/@@/package-source firefox - 6.0~b2+build1+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Emozillateam/+archive/firefox-next/+sourcepub/1818348/+listing-archive-extra)

Just updated with the latest Beta refresh aka b2

[SilverWave]

Every Six Weeks (http://blog.johnath.com/2011/07/18/every-six-weeks/comment-page-1/)

http://blog.johnath.com/wp-content/uploads/2011/07/rrprocess2-1024x965.png

[lovinglinux]

Electrolysis project coming back:

http://arstechnica.com/open-source/news/2011/07/mozilla-outlines-goals-for-multiprocess-browsing-implementation.ars

http://blog.mozilla.com/products/2011/07/15/goals-for-multi-process-firefox/

http://www.conceivablytech.com/8478/products/electrolysis-firefox-gets-atomized-to-run-faster

[SilverWave]

Electrolysis project coming back:

http://arstechnica.com/open-source/news/2011/07/mozilla-outlines-goals-for-multiprocess-browsing-implementation.ars

http://blog.mozilla.com/products/2011/07/15/goals-for-multi-process-firefox/

http://www.conceivablytech.com/8478/products/electrolysis-firefox-gets-atomized-to-run-faster


Interesting but I don’t think I will be holding my breath while we wait ;-)

[lovinglinux]

Interesting but I don’t think I will be holding my breath while we wait ;-)

It will certainly take a lot of time to land on our hands.

[lovinglinux]

Good news about Panorama feature.

http://www.conceivablytech.com/8520/products/mozilla-overhauls-firefox-panorama

The new improvements are already available in Firefox 6, 7 and 8.

I am becoming a big fan of the fast release cycle :-)

[SilverWave]

Well natty 64bit is done and working fine ATM, but the rest may take a little longer show up in the PPA's

Changes for the versions:
8.0~a1~hg20110714r72818+nobinonly-0ubuntu1~umd1~natty
8.0~a1~hg20110721r73087+nobinonly-0ubuntu1~umd1~natty

This change is not from a source that supports changelogs.

[lovinglinux]

Automated daily builds now only occur if there are changes (http://blog.mozilla.com/channels/2011/07/21/automated-daily-builds-now-only-occur-if-there-are-changes/)



Previously, early in the morning the build system blindly updated to the latest tip of tree, built it, generated updates, and made them available on the proper channel–even if there were no changes since the last time. This was inefficient for users, a poor use of build system resources, and unnecessarily contributed to update fatigue for less-active channels.

The new behavior makes it so automated morning builds only occur when the code or dependent localizations have actually changed since the last update.

[SilverWave]

Good news about Panorama feature.

http://www.conceivablytech.com/8520/products/mozilla-overhauls-firefox-panorama

The new improvements are already available in Firefox 6, 7 and 8.

Hmm may give it another go...
TBH its going to have to go some to beat "Tree Style Tabs" though.


I am becoming a big fan of the fast release cycle :-)So am I its just starting but you can see how good thing are going to get :-)

[SilverWave]

Just to underline how much cross site stuff this add-on protects you from, have a look at the screen shot!

You are cutting out 99% of the risk with this one add-on.

I am highlighting it here as having this type of add-on is *the* difference between Firefox and Chrome, and as expected it always gets bumped to work whenever a new Firefox comes out.


RequestPolicy (https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/)



Be in control of which cross-site requests are allowed. Improve the privacy of your browsing by not letting other sites know your browsing habits. Secure yourself from Cross-Site Request Forgery (CSRF) and other attacks.

[lovinglinux]

Just to underline how much cross site stuff this add-on protects you from, have a look at the screen shot!

You are cutting out 99% of the risk with this one add-on.

I am highlighting it here as having this type of add-on is *the* difference between Firefox and Chrome, and as expected it always gets bumped to work whenever a new Firefox comes out.


RequestPolicy (https://addons.mozilla.org/en-US/firefox/addon/requestpolicy/)

Nice. Thanks for sharing. So far it seems to catch all the stuff Ghostery blocks and more.

[SilverWave]

6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1 Not copied to my PPA's yet as Chris has Publishing disabled atm.

So the polishing of Firefox 6.0 continues with this beta refresh from Mozilla... nice :-)

[SilverWave]

https://launchpad.net/@@/package-source firefox - 6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Esilverwave/+archive/testing4/+sourcepub/1833242/+listing-archive-extra)

[SilverWave]

https://launchpad.net/@@/package-source firefox - 6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1 (https://launchpad.net/%7Esilverwave/+archive/testing4/+sourcepub/1833242/+listing-archive-extra)

Interesting...



Changelog

firefox (6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1) natty; urgency=low * New upstream release from the beta channel (FIREFOX_6_0b3_BUILD2) * Unconditionally build with --disable-elf-hack. It's basically a noop on Ubuntu, as we don't get any of the nice space saving and startup time improvements that upstream builds get with it. Enabling it is problematic (it fails to build on all architectures in Ubuntu from Firefox 7 onwards, and is problematic on armel when building on older Ubuntu versions) - update debian/rules - update debian/mozconfig.in * Refresh debian/patches/reload-new-plugins.patch -- Chris Coulson <chris.coulson@canonical.com (https://launchpad.net/%7Echrisccoulson)> Fri, 22 Jul 2011 17:29:01 +0100Elfhack

Home (http://wiki.mozilla.org/) » Elfhack (http://wiki.mozilla.org/Elfhack)
elfhack is a part of the Mozilla build system that optimizes relocations in compiled libraries. For more information about elfhack, see:


bug 606145 (https://bugzilla.mozilla.org/show_bug.cgi?id=606145) - Compress/pack relocations in ELF binaries (elfhack)
Improving libxul startup I/O by hacking the ELF format with elfhack (http://glandium.org/blog/?p=1177)
Link-Time Optimization (LTO) (http://blog.mozilla.com/respindola/2011/02/22/lto/)

[ron999]

@SilverWave
I can't use that version "firefox (6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1)" with Lucid Lynx.
But I'm interested to find out what build options have been used.
Please will you post the "Configure arguments" from about:buildconfig.

[SilverWave]

@SilverWave
I can't use that version "firefox (6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1)" with Lucid Lynx.
But I'm interested to find out what build options have been used.
Please will you post the "Configure arguments" from about:buildconfig.

You need to use this PPA for Lucid:


Lucid
https://launchpad.net/~silverwave/+archive/testing6 (https://launchpad.net/%7Esilverwave/+archive/testing6)

sudo add-apt-repository ppa:silverwave/testing6
Update & Install


sudo apt-get update sudo apt-get install firefox
I have just tested in a VM and it upgrades from FF3.6 fine.

[SilverWave]

@SilverWave
I can't use that version "firefox (6.0~b3+build2+nobinonly-0ubuntu0.11.04.1~mfn1)" with Lucid Lynx.
But I'm interested to find out what build options have been used.
Please will you post the "Configure arguments" from about:buildconfig.

Just in case you still need this...


about:buildconfig
Build platform
target
x86_64-unknown-linux-gnu
Build tools
Compiler Version Compiler flags
gcc gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) -Wall -W -Wno-unused -Wpointer-arith -Wcast-align -W -pedantic -Wno-long-long -g -fno-strict-aliasing -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer
c++ gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -pedantic -Wno-long-long -g -fno-strict-aliasing -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer
Configure arguments

--build=x86_64-linux-gnu --prefix=/usr --localstatedir=/var --libexecdir=/usr/lib/firefox-6.0 '--with-l10n-base=/build/buildd/firefox-6.0~b3+build2+nobinonly/build-tree/mozilla/l10n' --disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules '--srcdir=/build/buildd/firefox-6.0~b3+build2+nobinonly/build-tree/mozilla' --disable-elf-dynstr-gc --disable-install-strip --disable-strip --disable-updater --enable-application=browser --enable-default-toolkit=cairo-gtk2 --enable-startup-notification --enable-pango --enable-svg --enable-mathml --enable-safe-browsing --with-distribution-id=com.ubuntu --without-system-jpeg --without-system-png --without-system-zlib --enable-optimize --enable-tests --enable-mochitest --enable-ipdl-tests --disable-system-cairo --without-system-nspr --without-system-nss --disable-system-sqlite --disable-system-hunspell --enable-crashreporter --enable-official-branding --enable-gnomevfs --enable-update-channel=beta --disable-debug --disable-elf-hack

[ron999]

Just in case you still need this...


Yes, thanks.:)