Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] stable-rc firefox patch error

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Arwed von Merkatz <v.merkatz AT gmx.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] stable-rc firefox patch error
  • Date: Mon, 30 May 2005 09:59:02 +0200

On Sun, May 29, 2005 at 04:37:17PM -0700, Seth Alan Woolley wrote:
> I had a working firefox 1.0.3 from the previous version of stable and
> then decided to try to get 1.0.4 in stable-rc working.
>
> My idea was that it would figure out what to do to upgrade. Everything
> built according to plan, then an error happened after all the building
> and installing was done:
>
> patching file chrome/chrome.rdf
> patching file chrome/overlayinfo/browser/content/overlays.rdf
> patching file chrome/overlayinfo/communicator/content/overlays.rdf
> patching file chrome/overlayinfo/inspector/content/overlays.rdf
> patching file chrome/overlayinfo/messenger/content/overlays.rdf
> patching file chrome/overlayinfo/navigator/content/overlays.rdf
> The next patch would create the file components/xpti.dat,
> which already exists! Skipping patch.
> 1 out of 1 hunk ignored -- saving rejects to file components/xpti.dat.rej
> The next patch would create the file components.ini,
> which already exists! Skipping patch.
> 1 out of 1 hunk ignored -- saving rejects to file components.ini.rej
> The next patch would create the file defaults.ini,
> which already exists! Skipping patch.
> 1 out of 1 hunk ignored -- saving rejects to file defaults.ini.rej
> patching file extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}/install.rdf
> patching file extensions/Extensions.rdf
> patching file extensions/installed-extensions-processed.txt
>
> The only thing I had done to firefox was to install the googlerank
> plugin as a non-root user. In any case, the build failed at this point.
> I don't think we can expect users to know they need to rm -rf something,
> however I could put this in the next release notes, or we could have an
> upgrade process that works perfectly. Should we do the latter? And if
> we do the former, what do I need to do to get it to build, just rm -rf
> /usr/lib/firefox and try again? I'm not sure exactly what's going on
> under the hood of the nspr and nss spells at this point or even if it's
> near completeness. Any input is appreciated.

It's the firefox-init patch that works around the problem of users
having to run firefox as root first before it works as user.
See http://bugs.sourcemage.org/show_bug.cgi?id=8874 for the discussion
about it. I think the easiest way to get it working is to remove the
files the patch creates in INSTALL.

--
Arwed v. Merkatz Source Mage GNU/Linux developer
http://www.sourcemage.org




Archive powered by MHonArc 2.6.24.

Top of Page