On 24/10/13 21:39, Tom Eastep wrote: > On 10/24/2013 10:36 AM, Brian Burch wrote: >> On 21/10/13 18:11, Tom Eastep wrote: >>> Shorewall 4.5.21.2 is now available for download. >> <snip/> >> >> Tom, >> >> I am sorry that I didn't find time to test the beta. I couldn't find a >> set of bz2's to download, so assumed I would have to do a git clone - >> was that right? >> >> Anyway, when the 4.5.21.2 bz2's were distributed to the mirrors, I tried >> to install them... >> >>> Problems Corrected: >> <snip/> >>> 6) Support has been added to the Shorewall-core configure scripts and >>> installer for Ubuntu Raring. >> >> I'm sorry to say the fix did not work on my ubuntu raring system. >> >> core configure and install run ok. shorewall-4 install is ok too. >> >> BUT shorewall-init install fails with the line: >> >> ERROR: Unknown BUILD environment (ubuntu) >> >> >> As I explained before, /etc/os-release contains two lines relevant to >> the failure: >> >> ID=ubuntu >> ID_LIKE=debian >> >> However, your script's BUILD detection inner case section examines this >> file for an "ID" line, but it does not have a specific case for the >> string "ubuntu". I simply edited my own copy, cloned the "debian" >> section and made it handle "ubuntu" the same way, then the install worked. >> >> I'm not sure what should be done for the best long-term solution. >> Perhaps you should test for "ID_LIKE" first, and use that value if it >> exists, then only fall back to the bare "ID" test if a value wasn't found? >> > > You reported the problem against Shorewall-core, not against > Shorewall-init. I tested Shorewall-core's configure/installer on a > Raring system and installed Shorewall after that. > > For Shorewall-init, the following workaround is still available: > > BUILD=debian ./install.sh > > I'll fix Shorewall-init in the next release. > > -Tom
Thanks Tom. Sorry about my confusion between core and init, but even now I'm not entirely clear what is going on during my installation process. I run the recommended sequence: core/configure, core/install, shorewall-4/install, shorewall-init/install. 1. the source for configure is identical in all three bz2's 2. configure (I think) creates ./shorewallrc in the current directory. 3. configure does not create or update ~/.shorewallrc 4. .shorewallrc is created by shorewall-4/install 5. shorewall-init/configure does not determine the value to be used as $BUILD, so does not store it in ~/.shorewallrc or ./shorewallrc 6. shorewall-init/install dynamically determines the value to be used as $BUILD This seems prone to user errors (i.e. me)... am I missing an important concept? Brian > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
