From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 128 => 129 - iptables not shipped?
Date: Mon, 09 Sep 2019 10:56:17 +0100
Message-ID: <6FD7330C-0145-41F6-8155-8D3F63DD67D9@ipfire.org>
In-Reply-To: <24c70849-0bc9-e3ad-9ee2-d8d28a4f726d@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8358847802305650500=="
List-Id: <development.lists.ipfire.org>

--===============8358847802305650500==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Yeah, it looks like I forgot this one.

Unfortunately that happens very often because I am just stupid.

Arne will merge the next update and so users will received that one :)

Best,
-Michael

> On 8 Sep 2019, at 18:10, Matthias Fischer <matthias.fischer(a)ipfire.org> w=
rote:
>=20
> Hi,
>=20
> In Core update 128 =3D> Core 129 the 'iptables'-udpdate from 1.6.2 to
> 1.8.2 is missing:
>=20
> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dtree;f=3Dconfig/rootfiles/co=
re/129/filelists;h=3Deeb0842b426fcd48228a08cd1e3e808fff86a186;hb=3Drefs/heads=
/core129
>=20
> The former update from 1.4.21 (Core 122 =3D> Core 123) to 1.6.2 was ok:
>=20
> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dtree;f=3Dconfig/rootfiles/co=
re/123/filelists;h=3Dacaca6cf1f3c2218f72cb7e9bdbaf1d34035c23c;hb=3Drefs/heads=
/core123
>=20
> This would mean that machines, which were updated through Pakfire from
> Core 128 to Core 129 didn't get this update. So did mine. Found per
> chance today.
>=20
> Can someone confirm?
>=20
> Best,
> Matthias


--===============8358847802305650500==--