holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Update Upgrade Issues

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6710 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-06-29 16:32:49 +00:00
parent 7b186c1a61
commit 3fb876ef1b
1 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/upgrade_issues.xml
View File

@ -79,7 +79,7 @@
compiler(s) you install. In Shorewall 4.0.0, there are the following compiler(s) you install. In Shorewall 4.0.0, there are the following
packages:<itemizedlist> packages:<itemizedlist>
<listitem> <listitem>
<para>Shorewall ( common files )</para> <para>Shorewall-common ( common files )</para>
</listitem> </listitem>
<listitem> <listitem>
@ -93,27 +93,31 @@
<listitem> <listitem>
<para>Shorewall-lite</para> <para>Shorewall-lite</para>
</listitem> </listitem>
</itemizedlist>You must install Shorewall and at least one of the </itemizedlist>You must install Shorewall-common and at least one of
compiler packages (you may install them both).</para> the compiler packages (you may install them both).</para>
<para>You cannot simply upgrade your existing Shorewall package. You <para>You cannot simply upgrade your existing Shorewall package. You
must upgrade Shorewall <emphasis role="bold">and</emphasis> install must upgrade Shorewall-common <emphasis role="bold">and</emphasis>
one or both of the compilers.</para> install one or both of the compilers.</para>
<para>If you attempt to upgrade using the RPM, you get this <para>If you attempt to upgrade using the common RPM, you get this
result:<programlisting>gateway:~ # rpm -Uvh shorewall-4.0.0.noarch.rpm result:<programlisting>gateway:~ # rpm -Uvh shorewall-common-4.0.0.noarch.rpm
error: Failed dependencies: error: Failed dependencies:
shorewall_compiler is needed by shorewall-4.0.0-1.noarch shorewall_compiler is needed by shorewall-common-4.0.0-1.noarch
gateway:~ #</programlisting> You must either:<programlisting>rpm -U shorewall-4.0.0.noarch.rpm shorewall-shell-4.0.0.noarch.rpm</programlisting>or<programlisting>rpm -U shorewall-4.0.0.noarch.rpm shorewall-perl-4.0.0.noarch.rpm</programlisting>or<programlisting>rpm -i shorewall-shell-4.0.0.noarch.rpm gateway:~ #</programlisting> You must either:<programlisting>rpm -U shorewall-common-4.0.0.noarch.rpm shorewall-shell-4.0.0.noarch.rpm</programlisting>or<programlisting>rpm -U shorewall-common-4.0.0.noarch.rpm shorewall-perl-4.0.0.noarch.rpm</programlisting>or<programlisting>rpm -U shorewall-common-4.0.0.noarch.rpm shorewall-shell-4.0.0.noarch.rpm shorewall-perl-4.0.0.noarch.rpm</programlisting>If
rpm -U shorewall-4.0.0.noarch.rpm</programlisting>or<programlisting>rpm -i shorewall-perl-4.0.0.noarch.rpm you are upgrading using the tarball, you must install either
rpm -U shorewall-4.0.0.noarch.rpm</programlisting>If you are upgrading using shorewall-shell or shorewall-perl before you upgrade Shorewall using
the tarball, you must install either shorewall-shell or shorewall-perl the Shorewall-common tarball. Otherwise, the install.sh script fails
before you upgrade Shorewall. Otherwise, the install.sh script fails
with:<simplelist> with:<simplelist>
<member>ERROR: No Shorewall compiler is installed</member> <member>ERROR: No Shorewall compiler is installed</member>
</simplelist>The shorewall-shell and shorewall-perl packages are </simplelist>The shorewall-shell and shorewall-perl packages are
installed from the tarball in the expected way; untar the package, and installed from the tarball in the expected way; untar the package, and
run the install.sh script.</para> run the install.sh script.</para>
<para>The RPMs are set up so that if you upgrade an existing Shorewall
installation as part of a distribution upgrade and you have not
already installed shorewall-perl, then you will end up with
Shorewall-common and Shorewall-shell installed. </para>
</listitem> </listitem>
<listitem> <listitem>