Date: Thu, 4 Sep 2014 11:41:45 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Nicolas <lists@tropicdreams.net>
Cc: alpine-devel <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Shorewall in 3.0.4
Message-ID: <20140904114145.1de777a1@ncopa-desktop.alpinelinux.org>
In-Reply-To: <8f17a1227d6f286de4542c0486aa2704@tropicdreams.net>
References: <f6227532f1a220ad8fb1480eb006ac5d@tropicdreams.net>
	<20140903081336.31bb5c2a@ncopa-desktop.alpinelinux.org>
	<8f17a1227d6f286de4542c0486aa2704@tropicdreams.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 03 Sep 2014 15:03:48 +0200
Nicolas <lists@tropicdreams.net> wrote:

> Le 2014-09-03 08:13, Natanael Copa a =C3=A9crit=C2=A0:
> > On Tue, 02 Sep 2014 21:07:19 +0200
> > Nicolas <lists@tropicdreams.net> wrote:
> >=20
> >> Hello everyone,
> >>=20
> >> I'm planning to migrate some firewall machines running AlpineLinux 2.7
> >> to AlpineLinux 3.0.4
> >>=20
> >> Maybe I make a mistake but
> >>=20
> >> On alpine 2.7 I have :
> >>=20
> >> apk search shorewall -=3D=3D>
> >>=20
> >> shorewall-core-4.5.21.3-r0
> >> shorewall-common-4.2.11-r3
> >> shorewall-shell-4.2.11-r6
> >> shorewall6-4.5.21.3-r0
> >> shorewall6-doc-4.5.21.3-r0
> >> shorewall-4.5.21.3-r0
> >> acf-shorewall-0.10.0-r0
> >> shorewall-common-doc-4.2.11-r3
> >> shorewall-doc-4.5.21.3-r0
> >>=20
> >>=20
> >> On the fresh 3.0.4 I got this only :
> >>=20
> >>=20
> >> shorewall-common-4.2.11-r3
> >> shorewall-shell-4.2.11-r6
> >> acf-shorewall-0.11.0-r0
> >> shorewall-common-doc-4.2.11-r3
> >>=20
> >> Both boxes have the same /etc/apk/repositories configuration (just
> >> version number changes in the mirror).
> >> Is it normal or aren't the working 4.5 shorewall not yet in stable
> >> alpine 3.0.4 ?
> >=20
> > Latest shorewall does not build:
> > http://bugs.alpinelinux.org/issues/2981
> >=20
> > IIRC they have a static whitelist of known distros in configure script
> > and Alpine is not one those.
> >=20
> > I believe it is easy to fix.
>=20
> Hi Natanel,
>=20
> As you advised i had a look in the configure script of a shorewall=20
> 4.6.3.
> First the script depends bash but that's not a problem for building.
>=20
> The script tries to recognize the OS version based at begining on the ID=
=20
> variable in /etc/os-release.
> As you know (better than me) this is 'alpine' for an alpine.
> Then it fails because it doesnt find a shorewallrc.alpine file.
>=20
> If we consider alpine is like a generic linux a workaround is
>=20
> ln -s shorewallrc.default shorewallrc.alpine
>=20
> In the base directory of extracted shorewall.
>=20
> The the configure passes. Maybe we could use a more specific rc file=20
> based on debian or other.

I pushed it to edge/main with a custom shorewallrc.alpine.

Could you please do basic testing in edge and verify that it is not
totally non-functional. Then I can add it to the 3.0-stable.

Thanks!

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---