Round 2 Jarek's spec (i386, x86_64, src) ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/i386/RPMS/firefox/firefox-1.5.0.5-0.SL3.1.i386.rpm ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/x86_64/RPMS/firefox/firefox-1.5.0.5-0.SL3.1.x86_64.rpm ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/i386/SRPMS/firefox/firefox-1.5.0.5-0.SL3.1.src.rpm Stephan's spec (i386, src) ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/i386/RPMS/firefox/firefox-1.5.0.5-0.SL3.2.i386.rpm ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/i386/SRPMS/firefox/firefox-1.5.0.5-0.SL3.2.src.rpm So, it sounds like Stephan's spec file is almost doing the same thing as Jarek's, just in a different way. But I guess it wouldn't hurt to try both of them. Troy Troy Dawson wrote: > Rount 1 - i386. > > ftp://ftp.scientificlinux.org/linux/scientific/30rolling/testing/i386/RPMS/firefox/firefox-1.5.0.5-0.SL3.1.i386.rpm > > > This is using Jarek's spec's, with changes in SOURCES/firefox-mozconfig > The source rpm and x86_64 rpm will be up in about an hour and a half. > > I am currently rebuilding firefox using Stephan's spec file, without > SOURCES/firefox-mozconfig changed. Rebuild's take about 2 1/2 on the > machine (It was fast for it's time), so expect about 3 hours for the > i386 version. > > I will post when that is ready. It will be > firefox-1.5.0.5-0.SL3.2.i386.rpm > > Troy > > Jon Peatfield wrote: > >> On Mon, 31 Jul 2006, Troy Dawson wrote: >> >>> Stephan Wiesand wrote: >> >> >> <snip> >> >>>> Just in case it may help (I'm quite sure you don't need it, but who >>>> knows), I've put up the spec for my test build here: >>>> >>>> http://www-zeuthen.desy.de/~wiesand/firefox-SL.spec >>>> >>>> No input files were changed except the spec and Source12 (the default >>>> bookmarks). >>>> >>> >>> First answer >>> Yes, we plan on backporting the firefox 1.5.x to S.L. 3.0.x. >>> We do not plan on pushing it right out into the mainstream errata >>> because this is a major change. It will go into the 30rolling, or >>> maybe the 30rolling/testing area. We want people to be able to have >>> access to them and test them out. >> >> >> >> I'll put the test (i386) versions on a couple of boxes for some >> (light) testing once I know where to pull them from... >> >> I can't see an obvious 30rolling/testing area or I couldn't 10 mins >> ago anyway. Did it just get created? >> >> Anyway I still need to re-work some of my post-install hacks to cope >> with having seamonkey instead of mozilla... >> >>> I already have the i386 version done, based on Jarek's changes. The >>> only variation is he didn't mention changing the bookmarks, which I >>> have done. >>> >>> I am a little supprised that people are having problem with Pango, >>> because for the older backports (firefox 1.0.x) we pulled the pango >>> patches out, and nobody complained about those. But, as has been >>> said, this is a major change. >> >> >> >> For firefox 1.0.x (1.0.8 at least) the specfile had pango-related >> *patches* commented out, but was still linked against the SL3 pango >> (1.2.x). [ The patches required a newer version of pango (I think!) ]. >> >> Disabling pango might cause problems for some (e.g. Far-Eastern) text, >> or it might be that ffox just uses it's own routines if pango is >> unavailable or disabled. >> >> Firefox 1.5.x seems to need a newer version of pango than SL3 comes with. >> >>> I am not against making another compile of the firefox with your >>> (Stephan) spec file, and put it up to let people see if it fixes or >>> breaks anything. If we don't have to change the firefox-mozconfig >>> file that would be nice, one less change we have to worry about. >> >> >> >> The specfile mentioned above says: >> >> * Sat Jul 29 2006 Stephan Wiesand <[log in to unmask]> - >> 1.5.0.5-0.SL3.1 >> - made it build and install on SL3 (no pango) >> - replaced default bookmarks with SL ones >> >> so I'd assume that it *is* disabling pango too... >> >> I'd certainly be happy with a pango-less version initially (hey most >> of the world just uses iso-8859-1 anyway!!) though if that annoys lots >> of people it might be worth re-visiting later... >> >> -- Jon > > > -- __________________________________________________ Troy Dawson [log in to unmask] (630)840-6468 Fermilab ComputingDivision/CSS CSI Group __________________________________________________