Public SourceMage Discussion List

["Sergey A. Lipnevich" <sergey AT optimaltec.com>]

Neither NSPR nor NSS use /usr/lib/firefox, chrome, or extensions, so
they're not likely to be involved here. The only patch I added to remove
NSS build from Firefox is to security/manager tree. Also, I remove
several directories, like NSPR, DBM, and NSS. The whole thing is in
mozilla_remove_nspr_nss() function in grimoire FUNCTIONS. The patch
firefox-init.patch didn't change in any way. In fact, I didn't touch
that part of the INSTALL at all.

I remember Eric saying that Firefox along with NSPR/NSS rewrite should
not go into stable-rc, is that not the case?

I admit there's nothing here that can help you but it looks like the
spell needs to find a better way of fixing installed files, especially
if there are other plugins involved. Maybe an XSLT transform or
something like that?

Sergey.

On Sun, 2005-05-29 at 16:37 -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.
> 
> Thanks,
> 
> Seth
> 
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
-- 
Sergey A. Lipnevich <sergey AT optimaltec.com>
Optimal Technologies