PDA

View Full Version : New Firefox 1.0.4 Backport Available


jdong
May 24th, 2005, 05:07 PM
I've backported Breezy's Firefox 1.0.4 (before, I applied old Ubuntu patches to official source).


Note that it's now compiled with GCC 4.0 (as specified by the build scripts explicitly, so I complied!), and is called "firefox" instead of "mozilla-firefox"


This is quite interesting, as it marks the first GCC 4.0 build to hit Backports. :)

My initial testing shows it works, and that it's snappier!

NateC
May 24th, 2005, 05:25 PM
Yay... firefox now opens in 1.5 seconds :)

jdong
May 24th, 2005, 05:30 PM
That's not the only point of GCC 4.0.... From a security standpoint, Firefox will be immune to buffer/stack overflow attacks.

ow50
May 24th, 2005, 05:53 PM
Just upgraded, seems to work fine. One problem with the name update though, I had to uninstall libdevhelp-1-0. For some reason, it doesn't accept firefox providing mozilla-firefox and wants to install mozilla-firefox. Not that I'd necessarily need libdevhelp-1-0, I can't even remember why I have it.

vassalle
May 24th, 2005, 06:14 PM
Just upgraded, seems to work fine. One problem with the name update though, I had to uninstall libdevhelp-1-0. For some reason, it doesn't accept firefox providing mozilla-firefox and wants to install mozilla-firefox. Not that I'd necessarily need libdevhelp-1-0, I can't even remember why I have it.
cant find it.. :(

Ali_Baba
May 24th, 2005, 06:18 PM
I updated firefox too.It opens really fast now :grin: Will be great if all gcc 4.0 applications are as fast as this.

jdong
May 24th, 2005, 06:18 PM
sudo apt-get install firefox

For some reason, APT doesn't understand this transition. I don't know how to force it.

vassalle
May 24th, 2005, 06:24 PM
sudo apt-get install firefox

For some reason, APT doesn't understand this transition. I don't know how to force it.
dont mind me.. im just plain stupid i guess... didnt unmark the backports-staging in my sources.list.. managed to installed it tho.. ;)

Technoviking
May 24th, 2005, 06:50 PM
We may want a dummy transition package for mozilla-firefox, so ubuntu-desktop does not have to be uninstalled.

Mike

jdong
May 24th, 2005, 07:19 PM
I updated firefox too.It opens really fast now :grin: Will be great if all gcc 4.0 applications are as fast as this.

From my initial testing of Fedora, it seems that way :)

dodongo
May 24th, 2005, 09:27 PM
That's not the only point of GCC 4.0.... From a security standpoint, Firefox will be immune to buffer/stack overflow attacks.

Just out of curiosity, why is the C compiler so much smarter all of a sudden? It would seem to me (as someone who only knows enough about C to break things) that this type of thing should require a lot of work on the part of the developer. Is GCC 4.0 just more strict about how it allocates memory space?

And if you don't really want to answer, I'd settle for an informative URL :)

Thanks for the great work, too!

jdong
May 25th, 2005, 06:38 AM
http://www.google.com/search?hl=en&lr=&client=firefox&rls=org.mozilla%3Aen-US%3Aunofficial&q=mudflap+gcc&btnG=Search

http://www.google.com/search?hl=en&lr=&client=firefox&rls=org.mozilla%3Aen-US%3Aunofficial&q=gcc+FORTIFY_SOURCE&btnG=Search

jdong
May 25th, 2005, 06:38 AM
We may want a dummy transition package for mozilla-firefox, so ubuntu-desktop does not have to be uninstalled.

Mike
great suggestion.

man.life
May 25th, 2005, 08:25 AM
Will this new firefox work with mozilla-firefox-locale-*? Or do we have to wait for a firefox-locale-* backport?

jdong
May 25th, 2005, 10:58 AM
Hmm, the name change might warrant the need for a new locales backport, but I don't even see them present in Breezy at the moment.

jasplund
May 25th, 2005, 12:26 PM
Will this new firefox work with mozilla-firefox-locale-*? Or do we have to wait for a firefox-locale-* backport?

I was also wondering about this. Is the namechange really necessary?

aboe
May 25th, 2005, 02:35 PM
I was also wondering about this. Is the namechange really necessary?
I'm dutch, and installed the new firefox, it's menu is in dutch, so are the dialogs

so guessing it works, with the locale

jdong
May 25th, 2005, 02:58 PM
I was also wondering about this. Is the namechange really necessary?
This happened in Breezy, so it's out of my control.

From the looks, all the "mozilla-firefox-dev"-dependent packages may suffer from incompatibility thanks to this change.


Please see if , for example, you can get epiphany to work with this backport.

man.life
May 25th, 2005, 02:59 PM
Much faster and it detects the language pack. That menu entry is annoying, they should have left it as it was and not rename it to just "Firefox". [-X

ow50
May 25th, 2005, 03:02 PM
I can try crafting transitional dummy packages.

I think we need transitional dummy packages for all the packages (firefox, firefox-gnome-support, firefox-dom-inspector, firefox-dev). There's already a transitional dummy package for firefox-dev in the breezy source. Also, I think the firefox-* packages should thereby only conflict with versions < 1.0.4 of mozilla-firefox-* packages.

ow50
May 25th, 2005, 03:04 PM
From the looks, all the "mozilla-firefox-dev"-dependent packages may suffer from incompatibility thanks to this change.
But that has a transitional dummy package. Doesn't that solve the dependencies?

Please see if , for example, you can get epiphany to work with this backport.
Epiphany works.

fluideye
May 26th, 2005, 11:17 AM
I've backported Breezy's Firefox 1.0.4 (before, I applied old Ubuntu patches to official source).


Note that it's now compiled with GCC 4.0 (as specified by the build scripts explicitly, so I complied!), and is called "firefox" instead of "mozilla-firefox"
I have added the backports and am unable to find the firefox package. Tried apt-get and synaptic and no go. Is this still available?

jdong
May 26th, 2005, 12:07 PM
It's in the -staging area now. This backport will need time for testing because of the potential issues introduced by the new compiler and the new name.

fluideye
May 26th, 2005, 01:59 PM
It's in the -staging area now. This backport will need time for testing because of the potential issues introduced by the new compiler and the new name.
Thanks for the heads up.