> Sent: Sunday, March 10, 2019 at 5:59 PM > From: "Douglas R. Reno via blfs-support" > <[email protected]> > To: "BLFS Support List" <[email protected]> > Cc: "Douglas R. Reno" <[email protected]> > Subject: Re: [blfs-support] BLFS 8.4 - Firefox 65.0.1 showing up as Nightly > on my system > > On 2019-03-09 17:11, Ken Moffat via blfs-support wrote: > > On Sat, Mar 09, 2019 at 04:54:56PM -0600, Bruce Dubbs via blfs-support > > wrote: > >> > >> I found build/moz.configure/init.configure > >> > >> is_nightly = is_release_or_beta = None > >> > >> if 'a1' in milestone: > >> is_nightly = True > >> elif 'a' not in milestone: > >> is_release_or_beta = True > >> > > I salute your expertise with searching :) > >> > >> It is a python script and I'm not exactly fluent in python, but it > >> should > >> return is_release_or_beta = True and is_nightly = None > >> > >> -- Bruce > >> > > > > I would expect the milestone to be 65.0.1 (although I only recall > > 'version' notation when looking at diffs beweeen betas/releases). > > > > ĸen > > -- > > It is said that there are two great unsolved problems in computer > > science: naming, cache invalidation, and off-by-one errors. > > -- Ben Bullock > > Alright guys, after a long night of troubleshooting, I figured it out. > > There must have been something wrong with my original script. It > installed Firefox Nightly into /usr/local/bin and /usr/local/lib/firefox > respectively. My guess is that it was a problem with my script. Here was > the whole process: > > - Upgrade to latest node, cbindgen, NSPR, sqlite > - Install Firefox-65.0.2 > - Determine that for some reason Firefox Nightly was still being opened > - Run 'update-desktop-database' and find out that it was pulling from > /usr/local/* before /usr/* > - Read the desktop file and determine that "Exec=firefox" means that > it'll pull any firefox that it can find, often times being the first in > the search path (which seems to be /usr/local) > - Remove firefox nightly from /usr/local and... > - VOLIA! I have a working Firefox-65.0.2. > > Now with this, I uncovered another problem (although I'm comfortably in > firefox). > > For some reason, xterm installed it's binaries to /usr/local/bin! Can > someone else confirm this? I verified that $XORG_CONFIG was present at > build-time and even rebuilt it, and found that it still placed binaries > in the wrong location. > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
Only a rookie linux user should make a mistake as basic as not test compiling from scratch without a script, BEFORE posting to a mailing list. Like the saying goes, a script is only as good as the one who wrote it. In this case, it would seem not very good at all. Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
